Jeroen Ruigrok/asmodai wrote:
> Matt,
>
> for the past few weeks/months I've been plagued on this machine at work by
> a loss of the keyboard.
[snip]
Greetings:
I too am seeing this behavior. Jeroen has asked that I post a "me too".
I've installed the dfly-20041107-stable.iso on my old junker test box.
The mobo is an old Asus PI55T2P4 rev 3 which uses the Intel 430HX chipset.
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
installed MI handler for int 1
The install went flawlessly. However, the keyboard stops working without any
clue as to rhyme or reason. Sometimes it will fail at the login prompt
requiring 5-6 reboots or so before it returns. Other times it will work
fine for as long as 30 minutes before failing. I been through all the logs
and see no error messages.
Enabling inetd allows me to telnet in to the box. Everything seems to be
running fine when I do this. If I turn ssh on it works fine too.
I am a sysadmin at work in a mostly Windows environment. While I have played
around with a little coding over the years I do not consider myself a
programmer by any means, much less a kernel hacker. To set up the telnet
session is not too hard but I wouldn't know what to do with the ddb/gdb
debugging stuff. I do have a null modem serial cable which I have used for
SLIP before. It looks like the only way to cvsup and get box up to
-current/head would be to do it remotely. Even though it is somewhat a pain
in the ass I could do it if someone thinks it may help. If the box Jeroen
has the problem and the box is -current/head I don't think this will help.
However, if there is something a non kernel hacker such as myself can do to
help solve the problem I am willing.
--
Jason Bourne - GnuPG Key ID: 0x87E064D7