Messages in this thread | | | Date | Fri, 28 Jan 2005 20:35:42 +0100 | From | Vojtech Pavlik <> | Subject | Re: AT keyboard dead on 2.6 |
| |
On Fri, Jan 28, 2005 at 02:27:20PM -0500, Dmitry Torokhov wrote: > On Fri, 28 Jan 2005 20:22:32 +0100, Wiktor <victorjan@poczta.onet.pl> wrote: > > Hi, > > > > >This dmesg looks like the keyboard works perfectly OK. Do new lines > > >appear in dmesg when you press keys while the system is running? > > > > eeeeeeee.....no? no, they don't. i've new dmesg for you - it reports > > timeouts while trying to perform keyboard reset (by atkbd.reset=1). > > after detection pressing any keys has absolutley no effect. maybe it's > > some timeout-violation? > > > > Could you please try editing drivers/input/serio/i8042.c and add > udelay(20) before and after calls to i8042_write_data() in > i8042_kbd_write() and i8042_command().
Uh? What that'd help? All the communication proceeds OK, up to proper registration of the input device, but the keyboard seems to stay in a 'disabled' state. The keyboard, not the controller, because if it were the controller, atkbd.c wouldn't get the 'fa' responses back via functioning interrupts.
Wiktor, can you try atkbd.dumbkbd=1?
-- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |