[EMAIL PROTECTED] wrote: > > Hello, > > Apologies for the format of the quoted message, I don't like my mailer > either. > > Update: > > A couple trials indicated that there is even more weirdness going on here > than I previously thought. Firstly, it does not appear to be a problem > restoring when you are in X, just at the console. Secondly, the results are > not always the same but generally the same symptoms appear in some fasion. > Thirdly, switching virtual consoles (which still works when the keyboard is > muffed up) appears to fix the problems. > > This morning when I restored my machine, it appeared initially as if my > keyboard had be somehow remapped. Keys were not returning what they should > have. The enter key, for instance, worked. But several of the home row keys > either did nothing or beeped. I hit the 'f' key and I was loogged out of > the shell. (What kind of escape sequence does *that*?) > > I know next to nothing about Linux's keyboard implementation. But it > appears as if the APM BIOS is stepping on some data structure that handles > keyboard controls, maybe the keyboard buffer itself. (Is there a real > hardware buffer or is that a feature that is only relevant when programming > DOS applications?) But whatever it is, Linux apparantly already knows how > to fix the problem when it changes consoles so *maybe* it could be fixed by > doing that immediately aftert an APM restore is detected. Or, I could be > off-base. I have a similar "non-critical" problem: sometimes, when I resume from "Suspend to disk" (which on my Olivetti ECHOS P90M with Phoenix NoteBIOS seems to be what we call "hibernation" in this list) the keyboard does not respond at all. The best way to cope with this is to stay cool (too much accustomed to using the middle finger to reset the mashine ;-)) and NOT power off, just play with the function keys a little: switch from X to the text console(s), or try to switch to the extenal monitor, even if there isn't one, then back to LCD again. So using FN-F4 or Ctrl-Alt-Fx (x=1,...6) will revive the keyboard for me ;-). By now, I have come to consider it "normal", since it happens only on a small percentage of "hibernations". By the way, "Suspend to disk" works worderfully on this laptop - of course I have to (soft) eject any PCMCIA cards that happen to be inserted before I try it, otherwise the next tme I will have to stop and restart the /etc/rc.d/pcmcia script, after cs gives me a "received bogus resume event" message to remind me... Chris
