|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
You dont have to reboot if your keyboard gets stuck in raw mode.
This happened to me a few times while playing quake/doom. YOu can
telnet in like you did and do a "kbd_mode -a" to reset the
keyboard. You'll need to su, but you'd see that rather quickly. Or,
if you dont have annother PC to telnet in from.....
Odds are you're running an svgalib game, if you are, you're probably not
running X. The next trick depends on X not running. So shut down xdm or
whatever while you play games from the console.
Situation:
Ok, you're stuck at the console. Keyboard is in raw mode. You're about
to hit the reset button.
Solution:
Press and hold down 2, F12 and hit the "=" key. That'll start X. You
have to hit the keys kinda fast, or the keys will repeat. Its kinda a
3 fingered salute.
Anyways, you'll get a nice happy grey X screen. You wont be able to
do much since it bypasses your xinitrc, but you can ctrl+alt+Fn to a
DIFFERENT console than you were on. Now do a sleep 10; kbd_mode -a. Then
go back and quit X & return to the console that was fubar. In 10
seconds, it will reset.
This was in a HOWTO somewhere. I forget which one. Look for one that
mentions kbd_mode a lot :)
Hope this helps. That used to irritate the hell out of me when I got
stuck like that....
J.
When I grow up, I wanna be more like me.
I had a clue. I didn't like it. I took it back and exchanged it for an
attitude.
On Sun, 1 Aug 1999, Nick R wrote:
> Today (well, now so late it's yesterday) I got & ran doom which promptly
> proceeded to alter every key on my computer including keys such as alt,
> ctrl, & return. Fortunately I thought to telnet in and reboot gracefully.
> The thing is that even though this problem caused my keyboard to mess up & X
> to hang I was still able to exert control remotely. It got me started to
> wondering how many of the very few (one for me ever) crashes under linux
> could be averted by telnetting in. That's some pretty simple stuff working
> there & if the telnet daemon can run ps & kill w/o all the overhead of
> things like xterm & X bogging things down then I'd think that you could
> recover from somewhat severe looking problems during which the normal
> ctrl-alt-bksp doesn't work because you don't even need your keyboard. Just a
> thought. Any others?
> (Oh, & incidentally I must've hit the right rearranged combination to log
> out and get back to a login prompt and I was able to use the mouse to cut
> and paste the letters to form root and then a carriage return from the Red
> Hat prompt:
> Red Hat Linux release 5.2 (Apollo)
> Kernel 2.0.36 on an i586
>
> localhost login:
> The r from release, 2 o's from Apollo, on, localhost, or login, & the t from
> Hat, only I couldn't find enough of the characters in my password. Oh well!)
>
>
> _______________________________________________________________
> Get Free Email and Do More On The Web. Visit http://www.msn.com
>
> _______________________________________________
> Plug maillist - Plug@lists.nothinbut.net
> http://lists.nothinbut.net/mail/listinfo/plug
>
_______________________________________________
Plug maillist - Plug@lists.nothinbut.net
http://lists.nothinbut.net/mail/listinfo/plug
|
|