On Mon, Jul 28, 2003 at 11:09:10PM +0200, Claas Langbehn wrote:
> Hello!
>
> its strange. After switching debug on, it suddenly works.
Maybe the timing changed?
[It would also be nice to see a log where things failed.
Probably syslog would still work.]
> Below my debug info.
Thanks! Let me comment it.
-------------------------------------------------------------
check_mux: First we probe for a Synaptics mux. Find none.
check_aux: Then we probe for a PS/2 mouse port. Find one.
Good. Found something. Call serio_register_port().
This searches for attached devices.
We know already that it is the PS/2 mouse port, but who knows
what might be connected. Let us try all devices we know about.
Is it perhaps a keyboard?
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [0]
> drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [0]
We wait for 99 jiffies, but no keyboard ID shows up.
Then try to set LEDs.
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [99]
> drivers/input/serio/i8042.c: ed -> i8042 (parameter) [99]
> drivers/input/serio/i8042.c: fe <- i8042 (interrupt, aux, 0, timeout) [99]
Get an error back. This mouse doesnt want to set its LEDs.
Is it perhaps a mouse?
> drivers/input/serio/i8042.c: d4 -> i8042 (command) [113]
> drivers/input/serio/i8042.c: f2 -> i8042 (parameter) [113]
No mouse ID either. No devices connected to this port, but
at least we have a port:
> serio: i8042 AUX port at 0x60,0x64 irq 12
Then we continue, and check the keyboard side of the i8042 controller.
Things work satisfactorily, we detect a keyboard.
Silly enough we set it to scancode Set 2, but nevertheless give
commands that are only meaningful for scancode Set 3.
Keyboards that know only about Set 2 will be unhappy.
> input: AT Set 2 keyboard on isa0060/serio0
> serio: i8042 KBD port at 0x60,0x64 irq 1
OK, found keyboard.
-------------------------------------------------------------
So far the story of your debug file.
What is your actual hardware? Is there a mouse?
Andries
-
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/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:38 EST