This bug is reproducible when using the KeyTronic FlexPro ergonomic
keyboard. You may have seen them; they're the ones that split in the
middle, and go at an angle. Anyways, back to the bug.
2.1.98, all updates except for NFS in place (don't use NFS on this
machine). Compiles cleanly. Surprisingly cleanly (well, not quite. I'll
see if I can't sort out scsi_debug.c on my own, I think it's a bad
comment:). So I'm sitting here, all happy and stuff. Yay. I do the good
ol' three finger salute, *wham* and here's my brand new shiny 2.1.98.
Everything's booting great, no errors, no warnings, no complaints...
Apr 26 17:31:42 eiterra kernel: AWE32: not detected
Apr 26 17:31:42 eiterra kernel: js: no joysticks found
Apr 26 17:31:42 eiterra kernel: ftape v3.04d 25/11/97 for Linux 2.1.98
Apr 26 17:31:42 eiterra kernel: [000] ftape-init.c (ftape_init) -
installing QI
<snip ftape stuff>
Apr 26 17:31:42 eiterra kernel: Keyboard timeout
Apr 26 17:31:42 eiterra kernel: Keyboard timeout
AWE32 error is normal, I have an AWE64. js is normal, I'd knocked out my
gamepad. It's the last two lines that are the problem.
I looked at my keyboard, and noticed something. NumLock was STILL ON. Now,
for those of you who are going "huh? So?" let me explain something. Linux
will automatically turn off NumLock at boot. Within seconds. Now, this is
my first time booting, and I'm thinking that maybe that got shoved down in
the chain. Then I see "Keyboard timeout" scroll by, and get worried.
Finally, I get my "eiterra login:" and start typing. NOTHING! Smack
keyboard harder, STILL NOTHING! Unplug and replug (Standard DIN5, so
NYAH!), still nothing. Three-finger salute, NOTHING. So I smack reset, and
smack the keyboard against the desk, figuring it's fscked up again.
I boot into 2.0.33, keyboard's fine. I figure everything's okay again,
after a manual fsck (we need a more fault tolerant filesystem! *whine*),
so I reboot, and try 2.1.98 again.
Same thing. Same keyboard timeouts. Now, I'm thinking, and I recall a
problem I had with 2.0.29 to 2.0.31 with this keyboard, and an 'unknown
scan code'. I don't remember what it is, if it's that relevant, I can try
to reproduce it sometime. Anyways, when I got the 'unknown scan code' the
first keystroke would be lost, and everything would be fine from there on
in. I guess that maybe it's the E0, since there's a DIP switch for that on
the keyboard. I throw the switch, and try it with E0 disabled. Same
problem. No keyboard.
So now, here I am, with 2.0.33 again, trying to figure out just what the
problem could POSSIBLY be. If anybody's got any ideas or fixes, I'm
listening. Quick rundown of the box;
AMD K6-233 VXpro+ chipset
PS/2 Mouse (header)
DIN5 Keyboard
2 Serial, 1 Parallel
AHA-1520B Clone, sans BIOS
AWE64
Intel EE/Pro 10+ ISA
Diamond FireGL 1000 Pro
If anybody's got *ANY* ideas or suggestions, I'll try 'em. Thanks! :)
-Phil R. Jaenke (kernel@nls.net / prj@nls.net)
TheGuyInCharge(tm), Ketyra Designs - We get paid to break stuff :)
Linux pkrea.ketyra.INT 2.0.33 #69 Sat Apr 18 00:40:21 EDT 1998 i586
Linux eiterra.nls.net 2.0.33 #42 Fri Apr 17 00:22:13 EDT 1998 i586
- Linus says for 'brave people only.' I say 'keep a backup.' - :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu