Not sure if you were thinking of my recent post about a X problems - but just in case... The first time the clients are booted everything is perfect, X starts cleanly and stays stable - until I reboot the clients. During the second and subsequent attempts to boot, the client appears to connect to the server just fine but when it should start X, all the screen does is go blank with occasional flashes. Through process of elimination I've found that just restarting dhcpd on the server solves the problem. This is repeatable over the several clients I'm using.

The server is a clone running RH 8, the clients are various machines - mostly with 3Com905 nics and a variety of older video cards. Any help is greatly appreciated - any ideas like the steps you outlined below
would be great.

Tim

At 11:35 PM 11/14/2002 -0500, you wrote:
Sorry, I haven't been saving my LTSP messages and
I can't seem to find this thread in the archives
even though it was just within the last couple
days...

Someone was having trouble with X going to a
black screen.  They were concerned about the
video card or the font server or some other
server-related config.  It sounds like they
weren't exactly sure where to start.  I've been
skimming the digests and didn't see a response, so...


In my experience, X going to a black screen means
that the driver is fine and the video card is
fine and there is nothing wrong with the font
server.  The problem is likely just a matter of
finding the right modeline for your video card
and monitor combination.  Most likely is that the
video card is exceeding one of the ranges on the
monitor.  The monitor recognizes this and just
doesn't display anything.

To debug, use runlevel 3 and start X manually:
# /tmp/start_ws > /tmp/x.log &
# cat /tmp/x.log | less

This should let you see what settings X is using.
 I'm not sure how LTSP is setting up its default
XF86Config files these days (or what you may
already have tried), but this will let you see
which modelines it is eliminating and why and
which modeline it finally settles on.

Then, find out the physical specs of the monitor.
 If at all possible, put a multisync monitor on
the unit and see if it works with that.

You probably just need to reign in the ranges.
If you have an old monitor, you may need to
generate a custom modeline to hit a particular
dotclock right on the nose.

You're almost there!

Jason


Race to Save the Primates - every click provides food!
http://www.care2.com/go/z/primates


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net

Reply via email to