On Fri, Jan 28, 2005 at 09:46:41AM -0500, Dmitry Torokhov wrote: > On Fri, 28 Jan 2005 15:31:21 +0100, Vojtech Pavlik <[EMAIL PROTECTED]> wrote: > > On Tue, Jan 25, 2005 at 08:37:34PM +0100, Wiktor wrote: > > > Hi, > > > > > > here you are gzip-ed dmesg from booting 2.6.8.1 - i've been playing > > > keyboard while booting, maybe interrupt reports will help you. also my > > > .config part follows: > > > CONFIG_INPUT=y > > > CONFIG_INPUT_MOUSEDEV=y > > > CONFIG_SOUND_GAMEPORT=y > > > CONFIG_SERIO=y > > > CONFIG_SERIO_I8042=y > > > CONFIG_INPUT_KEYBOARD=y > > > CONFIG_KEYBOARD_ATKBD=y > > > no modules or other built-ins. maybe it is some simple way to fall back > > > to old handling mechanism? in my system most of programs (i mean > > > x-server) uses hardware directly (what means uses /dev/ttyS0 as mouse > > > device). i'm grateful for any help. > > > > This dmesg looks like the keyboard works perfectly OK. Do new lines > > appear in dmesg when you press keys while the system is running? > > > > It does no report any IDs but ACKs GETID command. Not very nice... Very old AT keyboards can do that.
-- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
