keyboard not recognized with 2.5 kernels

DISCUSSION Matt Pharr 2 participants 4 messages Nov 3, 2002 – Nov 4, 2002

Share & tools

Matt Pharr

author

2002-11-03 23:10 UTC #0 lore raw

(I've had this problem with both 2.5.39 and 2.5.45; haven't tried any other versions.)

After 2.5 boots, my keyboard doesn't seem to be recognized (it's an old-style one plugged into the keyboard port, not a USB keyboard). Everything is fine up to the login: prompt, but then any key I hit doesn't cause anything to happen (including ctrl-alt-del).

I have tried booting with "i8042_direct=1" on the kernel command line (as suggested in another thread about other keyboard problems), and that didn't help, and I have tried plugging in a plain old Dell keyboard instead of the Logitech iTouch I've got plugged in now. Neither of those helped. I also tried building without SMP support, and that didn't change the situation either.

This is on a home-built machine, Asus A7M266-D motherboard, dual athlon 1900MPs, etc.

I don't think I did anything dumb in the configuration step--I used my working 2.4.19 .config file, did a 'make oldconfig', and answered questions in conservative ways. In particular, I do have CONFIG_INPUT_KEYBOARD set properly:

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

Any thoughts about how to debug further? I fear that I've forgotten something obvious, but can't think of anything else to try.

thanks,
-matt

Petr Baudis

2002-11-03 23:18 UTC #1 lore raw

Dear diary, on Mon, Nov 04, 2002 at 12:17:04AM CET, I got a letter, where Matt Pharr <[email protected]> told me, that... ..snip..

Quoted 4 lines

After 2.5 boots, my keyboard doesn't seem to be recognized (it's an old-style one plugged into the keyboard port, not a USB keyboard). Everything is fine up to the login: prompt, but then any key I hit doesn't cause anything to happen (including ctrl-alt-del).

..snip..

Quoted 5 lines

I don't think I did anything dumb in the configuration step--I used my working 2.4.19 .config file, did a 'make oldconfig', and answered questions in conservative ways. In particular, I do have CONFIG_INPUT_KEYBOARD set properly:

Quoted 13 lines

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_INPUT_MOUSE=y
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
# CONFIG_INPUT_UINPUT is not set

Try to answer yes to the Serial i/o support (under Input device support) and then enable support of the i8042 PC Keyboard controller.

Making the keyboard configuration under 2.5.x more obvious is currently in the process of discussion.

Signature · 7 lines

				Petr "Pasky" Baudis
.
This host is a black hole at HTTP wavelengths. GETs go in, and nothing
comes out, not even Hawking radiation.
                -- Graaagh the Mighty on rec.games.roguelike.angband
.
Public PGP key && geekcode && homepage: http://pasky.ji.cz/~pasky/

Matt Pharr

author

2002-11-04 00:06 UTC #2 lore raw

Quoted 7 lines · Petr Baudis

Dear diary, on Mon, Nov 04, 2002 at 12:17:04AM CET, I got a letter, where Matt Pharr <[email protected]> told me, that... ..snip..
Quoted 4 lines
After 2.5 boots, my keyboard doesn't seem to be recognized (it's an old-style one plugged into the keyboard port, not a USB keyboard). Everything is fine up to the login: prompt, but then any key I hit doesn't cause anything to happen (including ctrl-alt-del).

Quoted 8 lines

..snip..
Quoted 4 lines
I don't think I did anything dumb in the configuration step--I used my working 2.4.19 .config file, did a 'make oldconfig', and answered questions in conservative ways. In particular, I do have CONFIG_INPUT_KEYBOARD set
properly: [...]
Try to answer yes to the Serial i/o support (under Input device support) and then enable support of the i8042 PC Keyboard controller.

Hmm, I didn't have that set before, but setting it and rebuilding doesn't make things better, with or without the 'i8042_direct=1' flag at boot-time. (I've rebuilt it all twice now, with an extra 'make clean' in the middle, just to be sure.)

bash-2.05a# grep SERI !$
grep SERI .config
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_SERIAL_8250 is not set
# CONFIG_SND_SERIAL_U16550 is not set

Any other ideas?

Quoted 2 lines

Making the keyboard configuration under 2.5.x more obvious is currently in the process of discussion.

Sounds good. I'm guessing that I missed some other important config option here. Perhaps someone could send me their .config file, I can enable what extra stuff I need (xfs, etc), and I can then figure out what else I needed to enable?

thanks,
-matt

Signature · 4 lines

Matt Pharr    [email protected]    <URL:http://graphics.stanford.edu/~mmp>
=======================================================================
In a cruel and evil world, being cynical can allow you to get some
entertainment out of it. --Daniel Waters

Matt Pharr

author

2002-11-04 18:45 UTC #3 lore raw

Thanks to Adam J. Richter, who was clever enough to figure out that CONFIG_KEYBOARD_ATKBD wasn't set correctly in my .config file. I have no idea how I missed that when I was grepping through trying to figure out what else I needed to set. Sorry for the trouble.

-matt

Quoted 45 lines · Matt Pharr

Quoted 7 lines · Petr Baudis
Dear diary, on Mon, Nov 04, 2002 at 12:17:04AM CET, I got a letter, where Matt Pharr <[email protected]> told me, that... ..snip..
Quoted 4 lines
After 2.5 boots, my keyboard doesn't seem to be recognized (it's an old-style one plugged into the keyboard port, not a USB keyboard). Everything is fine up to the login: prompt, but then any key I hit doesn't cause anything to happen (including ctrl-alt-del).
Quoted 8 lines
..snip..
Quoted 4 lines
I don't think I did anything dumb in the configuration step--I used my working 2.4.19 .config file, did a 'make oldconfig', and answered questions in conservative ways. In particular, I do have CONFIG_INPUT_KEYBOARD set
properly: [...]
Try to answer yes to the Serial i/o support (under Input device support) and then enable support of the i8042 PC Keyboard controller.
Hmm, I didn't have that set before, but setting it and rebuilding doesn't make things better, with or without the 'i8042_direct=1' flag at boot-time. (I've rebuilt it all twice now, with an extra 'make clean' in the middle, just to be sure.)
bash-2.05a# grep SERI !$
grep SERI .config
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_SERIAL_8250 is not set
# CONFIG_SND_SERIAL_U16550 is not set
Any other ideas?
Quoted 2 lines
Making the keyboard configuration under 2.5.x more obvious is currently in the process of discussion.
Sounds good. I'm guessing that I missed some other important config option here. Perhaps someone could send me their .config file, I can enable what extra stuff I need (xfs, etc), and I can then figure out what else I needed to enable?
thanks,
-matt