Ok. So this is the cause. The driver gets a '0xfe' response, which means
"error, command not supported, or device not present'.
A keyboard must support the 0xf5 command ('reset').
So, the error response might be coming either from the mouse, or the
controller, and somehow gets passed to the keyboard (they unfortunately
share the same registers), or the response somes from the mouse driver
first trying to probe for a mouse on the port.
So, please #define I8042_DEBUG_IO in drivers/input/serio/i8042.h as
well, and try again. Then we'll know more.
> > Most likely you have a somewhat unusual keyboard - it may be responding
> > too slow perhaps, so that the driver times out - or doesn't support some
> > of the commands the driver expects to use.
> > Or the mouse kills the keyboard. This also can happen - they share
> > common resources. This would need more debugging then.
> > So, what's the keyboard, what's the mouse, and what's the mainboard
> > exactly?
> I've tried this with 3 different keyboards, 3 different mice, and 3
> combinations of each: wireless 104-key ps/2 keyboard. PS/2 cord from the box
> to the keyboard base, actual keyboard is wireless. bought it 4 years ago;
> 104-key keybord (w/power, sleep, and wake keys) bought 3 weeks ago, 104-key
> acer keyboard from a P100 from 7 years ago. all 3 mice are PS/2 mice; Acer
> mouse to go along with the Acer box and Acer keyboard, Microsoft PS/2 mouse,
> and MS Optical wheel mouse. The Acer and MS PS/2 mouse are straight PS/2. The
> optical is IMPS/2. motherboard is a Tyan S2390B, VIA82c686b chipset.
> All 9 different combinations gave the same result. Mouse working,
> keyboard not working.
Very intersting. It works for me on my via82c686b.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/