[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Suddenly no keyboard?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I did the latest upgrade earlier this evening, which installed a new version of
locales.  All was fine for about an hour or so, until my keyboard locked and
the scroll lock, which had been blinking for new mail messages I hadn't read
yet, (mailleds), stayed on and didn't blink off, (total keyboard meltdown).  I
was able to use the power button to shut down the system properly, thanks to
ACPI, but when I powered up again, the numlock turned on of its own free will as
soon as the boot loader (grub) was run, and then, when I selected my kernel,
(2.6.5-1-k7), the keyboard just simply melts down again and I get message like:

atkbd.c: Unknown key pressed (raw set 0, code 0x0 on isa0060/serio1).
atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
atkbd.c: Keyboard on isa0060/serio1 reports too many keys pressed.

This kernel-image package was recently upgraded, but didn't change the end
result, (still a total meltdown of the keyboard).

I am logged into this machine using ssh now, as it is the only thing that lets
me type on it.  What can I do to solve this problem?  Is my keyboard bad?  My
BIOS?  Locales?  Why such a sudden and complete meltdown?

Thanks for any help,
PRINCE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAi0FoAl2SNUPt1I8RAlHDAKCHNMDKDQTA5JtZhdthFx44XzoRawCfVaS4
E2WqLX3QPvYdz1HOIjyvaek=
=gkM1
-----END PGP SIGNATURE-----



Reply to: