I find it useful to start off by setting RUNLEVEL = 3 in the lts.conf file. This way the terminal doesn't try and go into X, but just stops at the bash prompt. This gives you a chance to read any error messages, etc. If you then want to try starting X, you can do so manually by typing /tmp/start_ws.
John On Thu, 28 Nov 2002 21:35:46 -0600 "Jerome Edwards LISD" <[EMAIL PROTECTED]> wrote: > Our school district is new to LTSP and is having a few problems > getting started. First of all, we are using a server with the > following: P4 1.7 GHz with one gig of ram, etc, etc. The terminals are > 233 MHz with 32meg ram. Using K12LTSP 2.1.0. > OK, to the problem, when trying to boot from a floppy on the terminal, > the system locals the server and attempts to startup process but > before (I think, I have never actually seen the entire boot process) > it get to the X screen, the monitor goes blank and the keyboard > becomes inaccessible. The system goes through about two screens of > rapid commands and halts briefly with a warning about the sound card > being misconfigured before the monitor goes blank. When the monitor > goes blank, the green led light on the monitor goes from green to > orange. I have tried the boot up on several computers to find the same > result, even removed all PCI cards except the network and video. I > even tried it on a new system. Is there a step I am leaving out or a > setting that needs correcting? Any help or advice would be greatly > appreciated. > > Jerome Edwards > LISD ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _____________________________________________________________________ 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
