hi ya travis
- try the various(6) consoles
( Alt-F1 ... alt-F6 )
- start X11 from console ( init 3 )
and you can kill X by control-C on cosole
- if your kb is dead...
- unplug it and try again...
- or try a different kb
- if your mouse is dead..
- restart gpm even if its not supposed to do anything in X11
- if you cann ssh-in....
if you can see X processes... kill those you dont want
or blinly kill X11
"init 3 ; sleep 5 ; init 5"
- hit reset
- than lastly try power button
c ya
alvin
On Wed, 4 Sep 2002, Travis Crump wrote:
> What is the recommended way to recover from an X lockup? Just a little
> bit ago, X locked up on me(I was using a GL program and had multiple[2]
> X's running) and I tried to get my system back by logging in remotely
> and killing the X process with "kill -s KILL <Xpid>" of the X that was
> frozen. Unfortunately, this only succeeded in killing my internet
> connection(dialup initiated from within X) without restoring local
> control so I was forced to just hit the power button. I plan on adding
> Alt+SysRq support[in the hope that Alt+SysRq+K will prove useful in
> these situations] the next time I upgrade the kernel, but am still
> curious as to how you go about regaining control remotely if it is
> possible. Should I have just bit the bullet and issued a reboot when I
> got in remotely since their isn't a good reason why I need to avoid
> rebooting?
>
> Mostly Sarge system if it matters.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
