Re: PS/2 Mouse/Keyboard conflict and lockup

[Peter Horton <pdh@colonel-panic.com>]

On Thu, Feb 08, 2001 at 03:35:00AM +0100, Udo A. Steinberg wrote:
> 
> I'm not sure whether this is related to the ominous ps/2 mouse bug
> you have been chasing, but this problem is 100% reproducible and
> very annoying.
> 
> After upgrading my Asus A7V Bios from 1003 to 1005D, gpm no longer
> receives any mouse events and the mouse doesn't work in text
> consoles. Once I kill gpm and restart gpm -t ps2 the keyboard
> locks up.
> 
> Logging in remotely and looking at dmesg revealed the following:
> 
> keyboard: Timeout - AT keyboard not present?
> keyboard: unrecognized scancode (70) - ignored
> 
> If I don't kill and restart gpm, but start X, the mouse works
> perfectly, but only in X.
> 

Similiar problems here after my upgrade to 1005D. Linux somehow kills
the keyboard if I start the box without a PS/2 mouse connected. I have
another machine (these are both 2.4.1) which is a much older K6-233, and
it too kills the keyboard if no mouse is present. Keyboard works at LILO
prompt but is dead by the time I get to login. GPM doesn't work for me
either.

P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/