Bug#436271: PS/2 mouse not working
On Wed, Aug 08, 2007 at 07:31:14AM +0200, Brice Goglin wrote:
> Adrian Mariano wrote:
> > I have never observed /dev/input/mice to work when the mouse was
> > plugged into the PS/2 port. At the moment I am using evdev and have
> > the mouse plugged into the USB and the mouse works. If I switch it to
> > the PS/2 it doesn't work.
> >
> > After switching the mouse to the PS/2 I tried "cat /dev/input/mice"
> > and saw nothing. I also tried "cat /dev/psaux" and also saw nothing.
> > (Is some action required for the PS/2 port to realize it's got a mouse
> > connected?)
> >
> > Just as a confirmation I put the mouse back in the USB and did "cat
> > /dev/input/mice" and when I moved the mouse I got characters.
> >
>
> Then the bug is not in X. If psmouse is loaded and events don't appear
> in /dev/psaux or /dev/input/mice, something is missing in the kernel or
> so. Did the ps/2 mouse ever work before installing this Debian? In
> another Linux? In Windows? Any BIOS option to enable it?
When I first installed, the mouse was on the ps/2 port. The
configuration that was supplied by the installer was
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
EndSection
The mouse did not work. I moved the mouse from the ps/2 port to the
USB port and it worked fine.
Then I tried changing /dev/input/mice to /dev/psaux. The mouse WORKED
FINE with this setup. (It worked just as well as it worked on the USB
or as it now works with evdev on the USB---everything worked but the
tilting of the tilt wheel.)
This seems puzzling in light of the recent behavior with /dev/psaux.
Is it possible that some action (e.g. reboot) is necessary to cause
the kernel to realize there is a mouse on the ps/2 port?
Reply to: