> > > Any further idea ?
> >
> > Yes. Can you try, with i8042 debugging enabled, after the kernel boots,
> > moving the mouse? I suspect the data will appear in the log ...
>
> Maybe I wasn't very clear, but if I disable the 'return -1', the mouse
> will work, and the debugging data is like in:
> ...
> i8042.c: 08 <- i8042 (interrupt, aux, 12) [627526]
> i8042.c: 03 <- i8042 (interrupt, aux, 12) [627527]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [627528]
> ...
>
> If I do not disable the 'return -1', the mouse will not be found at
> all, and moving it will get no messages in the logs...
Ok, that's what I wanted to know - I was wondering whether the mouse
would simply ignore all control commands. And it doesn't not. It needs
the commands, but doesn't send any replies.
Can you check what happens if you use an external mouse together with
the internal one?
I suspect both will work OK.
-- Vojtech Pavlik SuSE Labs - 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/