*BSD News Article 29399


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!vixen.cso.uiuc.edu!milo.mcs.anl.gov!xray!winans
From: winans@xray.aps.anl.gov (John R. Winans)
Subject: Re: Problems with XFree86 2.0
Message-ID: <CoBnC8.8y3@mcs.anl.gov>
Sender: usenet@mcs.anl.gov
Organization: Argonne National Laboratory, Chicago Illinois
References: <765997388tim.news@xplora.toppoint.de>
Date: Fri, 15 Apr 1994 22:19:19 GMT
Lines: 45

In article <765997388tim.news@xplora.toppoint.de> tim@xplora.toppoint.de (Tim Weilkiens) writes:
>Hello,
>
>if I start XFree86 (startx) I get the graphic screen with the X and
>then I can see a window for very short time. Then the text screen
>appears with the 'XFree86 booting messages'. And then nothing more
>happens and I have to reset my computer.
>Using startx >& x.log the x.log - file contains the booting messages
>and a message that the X server was killed. 

If you are not really getting anything interesting in terms of error mesages,
perhaps your .xinitrc file is defective.  You might simply be starting
everything and then killing it right away.

I always start up some xterms and stuff and then start twm on the last line.
Everything EXCEPT twm is started in the background.  Then when I exit from 
twm, the X server dies and takes any active X clients with it.  I don't think
this is the generally accepted way, but has ALWAYS worked for me... since the
X11R3 days.

I have also seen the locked up console at the end of exiting X, and I never
knew what it was for sure... didn't care enough to find out I guess. 
I have two machines.  One (a gateway) behaves like yours with the locked up 
console, but I suspect I botched up this damn /dev/vga /dev/tty0 /dev/console 
manure.  Why the hell we don't just have one single console device, I will 
never know (until I am flamed for this comment.) And I never log off the other 
one (generic foreign import 486DX-40 with vesa local everything -- it ONLY 
crashes on SCSI bus timeouts... and then it is down all the way... NetBSD 0.9 
vanilla with XFree86 2.0 and one home brew tty driver hack.)

On the gateway, I just shut the thing down from inside X and don't worry about
it.  I don't recall ever having X crash on me since I finished screwing around 
with the Xconfig file.  I think the WORST thing was getting my stupid mouse 
working.

I hope my ramblings here will provide you with a clue or two.

Good luck,
--John

-- 
! John Winans                     Advanced Photon Source  (Controls)    !
! winans@phebos.aps.anl.gov       Argonne National Laboratory, Illinois !
!                                                                       !
!"The large print giveth, and the small print taketh away." - Tom Waits !