Doc, Scott, Thanks for the reply. I have been booting to run level 5 until the same lockup occurred at the graphical login screen. I just intervened in Grub to run level 3 to see what happens starting as root or skipping the login screen. The same lockup happens only at the Desk Top screen (login screen not used). I've also tried booting from 2 earlier kernels with the same result. The only thing done on the last working session was to check the mouse configuration in xwindows and even if that corrupted a file I wouldn't think it could get the keyboard as well. Does anyone know of any logs I might look at or any reload options.? Bob >-----Original Message----- >From: shrike-list-admin@xxxxxxxxxx >[mailto:shrike-list-admin@xxxxxxxxxx]On Behalf Of >Scott Helms >Sent: Friday, July 18, 2003 12:02 PM >To: shrike-list@xxxxxxxxxx >Subject: Re: x-windows broke > > >Doc, > > I am not sure why you think that startx >isn't common, many people >prefer to start that way for control purposes. In >any case its a fully >supported method of invoking X and sets all of the >appropriate >variables, albeit differently than using runlevel >5 since that method >doesn't have a human logged in until after X is started.: >http://www.redhat.com/docs/manuals/linux/RHL-9-Manu >al/ref-guide/s1-x-runlevels.html > >Bob, unfortunately there's no easy answer as to >why this happening now, >since it can be one of many things. It is a sure >bet that something >changed from either a hardware or software point >of since X was >working. A couple things to try: > >1. startx as a different (not root) user, its >quite possible for the >.xinitrc or .Xclients in your home directory to >get munged up > >2. regress to a previous (working) kernel version >if you recently >upgraded. > >3. Try starting reverting whatever you changed >since it was working. > >On Fri, 2003-07-18 at 12:17, dsavage@xxxxxxxxxxx wrote: >> On Friday July 18, 2003 Bob Mclaughlin wrote: >> > When I enter 'startx' I immediately get a 'no signal' >> > message on screen. After about a minute the >usual startup >> > screen appears and it slowly loads to the >desktop screen. >> > It then continues unresponsive to mouse or >keyboard input >> > until the 'no signal' message reappears and the screen >> > blanks. I'm running the latest shrike kernel and no >> > non-redhat supplied goodies. Can someone give >me (command >> > line dummy) some hints on how to get and read >the proper >> > logs, what files may have gotten corrupted or >any other >> > hints? TIA >> >> Bob, >> >> These days 'startx' is not a common way to start >X. Is there a particular >> reason why you are using that rather than >runlevel 5 (which ensures all of >> the companion stuff starts in the proper order)? >> >> --Doc Savage >> Fairview Heights, IL >-- >Scott Helms >Director of Technology >ZCorum, Inc >(770) 888-8900 > > >-- >Shrike-list mailing list >Shrike-list@xxxxxxxxxx >https://www.redhat.com/mailman/listinfo/shrike-list > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
