[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: X problems on Blade 100



Tobias DiPasquale wrote (in a message from  1)
 > On Sun, 2002-12-01 at 02:50, Matthieu Herrb wrote:
 > > May be the  solution is in /var/log/XFree86.0.log. Read it and double
 > > check that the mode that was choosen by the X server is within the
 > > range you specified, and that it matches one of the supported modes
 > > listed  on the sunsolve page. 
 > > It may help to specify an explicit mode in the Screen section of
 > > XF86Config to avoid automatic selection of modes with too high
 > > frequencies. 
 > 
 > /var/log/XFree86.0.log is empty when the system comes back up, so that's
 > no help at all. 

How do you exit the X server ? Ctrl+Alt+BackSpace should work, or
login from the network and killing the server with SIGTERM should be
enough if the server machine is not hung. 

If you do a brutal reboot, the XFree86.0.log file is not closed and
has in fact great risks to be wiped out by fsck upon reboot. 

If the machine is hung, it's of course a different story. But I don't
remember seeing reports that the ATI driver hangs a sparc64. 
In this case start the server alone with the -logverbose option set to
99 (XFree86 -logverbose 99). This should produce enough output to the
log ifle so that at least part of it will get flushed to disk before
you powercylce teh machine. 


					Matthieu