PS/2 mouse/mice does not work

Bug #108350 reported by Aero Leviathan
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
New
High
Unassigned

Bug Description

My PS/2 mouse will not work under 7.04, though it worked perfectly under 6.10 with no configuration. Just a plain 2-button+wheel wired mouse. Ubuntu's running on the bare hardware (no VM).

sudo cat /dev/input/mice and sudo cat /dev/psaux produces no output. (6.10 was using /dev/input/mice)

Several reports on the forums:

http://ubuntuforums.org/showthread.php?t=415872 (mine)
http://ubuntuforums.org/showthread.php?t=415462
http://ubuntuforums.org/showthread.php?t=415318

There are also many reported VirtualPC/USB mouse problems, but I wasn't sure if those were separate issues.

Some people are saying this is a 'kernel bug' but I couldn't find anything else about that and I don't know where they got it from.

Sorry I couldn't think of any more information to include; I'll do my best to answer if you can think of any questions.

Tags: feisty mouse
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
Aero Leviathan (ubuntu-aeroleviathan) wrote :

Here you go.

Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i586 GNU/Linux

This was captured while the system was running from the Desktop CD. I'll do the hard drive upgrade to 7.04 if you think it will make a difference. I haven't yet because not having a mouse makes things difficult...

Revision history for this message
Aero Leviathan (ubuntu-aeroleviathan) wrote :
Revision history for this message
Simon G Best (simon-g-best) wrote :

I've also come across the same problem.

Here's my uname -a output:-

Linux olympus 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

I'll add my dmesg.log and lspci-vvnn.log in a moment.

My mouse is an ordinary, three-button, PS/2 mouse. It's an old one. It's an IBM one from an IBM RS/6000. It's nothing special, not exotic at all. Works fine with older kernels.

Revision history for this message
Simon G Best (simon-g-best) wrote :

Here's my dmesg output.

Revision history for this message
Simon G Best (simon-g-best) wrote :

Here's my lspci -vvnn output.

Revision history for this message
Brian Murray (brian-murray) wrote :

I have been unable to reproduce this using a PS2 mouse on a Intel 440BX motherboard. The mouse works fine using the Ubuntu Feisty Final Live CD and the device shows up as /dev/input/mice.

Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-team
importance: Undecided → Medium
status: Needs Info → Unconfirmed
importance: Medium → High
Revision history for this message
indianabeck (davidb-beckb) wrote :

Since the same problem exists when using Windows Virtual PC 2007, it may be easier to re-create this in a virtual machine. I believe that the Virtual machine emulates the same hardware regardless of the acutal hardware installed. That way we don't all have to replace our motherboards with Intel 440BX ones. :)

Revision history for this message
Aero Leviathan (ubuntu-aeroleviathan) wrote :

Do you have a reason to conclude that the Virtual PC problem is the same problem? I think that's premature.

I have been having trouble determining what my motherboard type is (suggestions?) but I note that in System > Administration > Device Manager, almost everything seems to be from Silicon Integrated Systems (SiS). I wonder if Mr Best could tell us whether his configuration is similar? If so, this may be a duplicate of bug 108221, which does not seem to have received any attention thus far.

I also note that I did not have any problems with my PS/2 keyboard in Feisty, which I had meant to include in the original report but forgot.

Bug 108382 seems to be a duplicate of this bug, but the level of discourse in that report does not seem to be at all constructive... :)

Revision history for this message
Simon G Best (simon-g-best) wrote :

Well, my PC seems to be SiS this, SiS that, and SiS the other. If you look at my lspci output thingy, attached to an earlier comment, you'll see that my PC does seem to be wall-to-wall SiS.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.