USB mouse does not work if usbhid loaded before plugging in

Please attach (do not paste into comments) the output of dmesg after the cycle of events you described above.

From what it looks like what is happening with my laptop tonight, I have to unload and reload the usbhid module for the mouse to work, even if usbhid has been unloaded before the mouse is plugged in. I'm now more puzzled.

I have the same problem as Steve, with the same "solution" of doing a rmmod / modprobe on usbhid. Please see attached dmesg / udevmonitor output.

https://lists.ubuntu.com/archives/ubuntu-users/2006-March/071497.html

I have the same problem and the above solution works as well. I actually have a USB keyboard with a built in touch-pad and touch-point both of which work, but the USB mouse plugged into the USB keyboard is what isn't working unless I rmmod/modprobe usbhid. The laptop's built in touch pad and touch-point both work as well. So all four of the methods except the primary pointer device I use are functional. I'll do some further testing to see if the mouse has the same problem when plugged directly into the laptop. In the meantime, here's my relevant information:

Ubuntu 6.06 "Dapper Drake" Development Branch \n \l
Linux lappy 2.6.15-19-686 #1 SMP PREEMPT Mon Mar 20 17:33:20 UTC 2006 i686 GNU/Linux

$ lsmod|grep usb
usbhid 40992 0
synaptics_usb 15520 0
hci_usb 17492 2
bluetooth 54084 7 rfcomm,l2cap,hci_usb
usbcore 137700 6 usbhid,synaptics_usb,hci_usb,ehci_hcd,uhci_hcd

$ dmesg|grep 'input'
[4294668.856000] input: AT Translated Set 2 keyboard as /class/input/input0
[4294753.751000] input: PS/2 Mouse as /class/input/input1
[4294753.776000] input: AlpsPS/2 ALPS GlidePoint as /class/input/input2
[4294783.864000] input: Cypress Sem PS2/USB Browser Combo Mouse as /class/input/input3
[4294783.865000] input: USB HID v1.00 Mouse [Cypress Sem PS2/USB Browser Combo Mouse] on usb-0000:00:1d.2-1.1
[4294783.886000] input: Lite-On Tech IBM USB Keyboard with UltraNav as /class/input/input4
[4294783.886000] input: USB HID v1.10 Keyboard [Lite-On Tech IBM USB Keyboard with UltraNav] on usb-0000:00:1d.2-1.3
[4294783.916000] input: Lite-On Tech IBM USB Keyboard with UltraNav as /class/input/input5
[4294783.916000] input: USB HID v1.10 Device [Lite-On Tech IBM USB Keyboard with UltraNav] on usb-0000:00:1d.2-1.3
[4294784.022000] input: Synaptics Inc. Composite TouchPad / TrackPoint as /class/input/input6
[4294784.022000] input: USB HID v1.00 Mouse [Synaptics Inc. Composite TouchPad / TrackPoint] on usb-0000:00:1d.2-1.4
[4294784.056000] input: Synaptics Inc. Composite TouchPad / TrackPoint as /class/input/input7
[4294784.057000] input: USB HID v1.00 Mouse [Synaptics Inc. Composite TouchPad / TrackPoint] on usb-0000:00:1d.2-1.4
[4294784.057000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[4294842.532000] input: Cypress Sem PS2/USB Browser Combo Mouse as /class/input/input8
[4294842.532000] input: USB HID v1.00 Mouse [Cypress Sem PS2/USB Browser Combo Mouse] on usb-0000:00:1d.2-1.1
[4294842.870000] input: Lite-On Tech IBM USB Keyboard with UltraNav as /class/input/input9
[4294842.870000] input: USB HID v1.10 Keyboard [Lite-On Tech IBM USB Keyboard with UltraNav] on usb-0000:00:1d.2-1.3
[4294842.899000] input: Lite-On Tech IBM USB Keyboard with UltraNav as /class/input/input10
[4294842.899000] input: USB HID v1.10 Device [Lite-On Tech IBM USB Keyboard with UltraNav] on usb-0000:00:1d.2-1.3
[4294843.250000] input: Synaptics Inc. Composite TouchPad / TrackPoint as /class/input/input11
[4294843.250000] input: USB HID v1.00 Mouse [Synaptics Inc. Composite TouchPad / TrackPoint] on usb-0000:00:1d.2-1.4
[4294843.276000] input: Synaptics Inc. Composite T...

My appologies, just noticed the comment about attaching, not pasting. Further information will be attached. My first launchpad post didn't play by the rules. :-(

I've attached udevmonitor logs for when I first plug in the mouse and it's non-functional, and then further logs that show udevmonitor while I rmmod and modprobe and the mouse works.

First half of the log shows the normal udevmonitor when I plugin the mouse. The second half shows what happens when I leave the non-working mouse plugged in, but re-run rmmod usbhid && modprobe usbhid .

#37366, 37059, 38555 seem to address same issue.

I currently use a workaround for this issue, which might be acceptable for the rest of you:

In "/etc/modprobe.d/blacklist" find:

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

add

blacklist usbhid

and comment out the entries for usbmouse / usbkbd as needed. I.e.

# these drivers are very simple, the HID drivers are usually preferred
#blacklist usbmouse
blacklist usbkbd
blacklist usbhid

Thanks! Commenting out usbkbd and usbmouse and adding usbhid worked for me. I don't really know the "why" of it, or if this is a better solution long-term, but it's working for me now, so it meets my needs. :-)

I see the same problem here.

The blacklisting usbhid workaround doesn't work here. I'm using a Logitech Bluetooth mouse/keyboard combo. When I blacklisted usbhid and enabled usbmouse and usbkbd, I couldn't get any response from my usb keyboard, and the usb mouse would only work in the vertical direction (up and down, no matter what I did with the mouse).

I am running Dapper 6.0.6 PPC on my iBook laptop (a dual boot) and I had the issue of the desktop freezing if my usb mouse was plugged in, it didn't freeze if I waited till after boot and then plugged it in. I use this mod and it was a positive work around.

#blacklist usbmouse
#blacklist usbkbd
blacklist usbhid

in /etc/modprobe.d/blacklist

I have now found that this issue has been resolved with the released version of Dapper. I can plug my USB mouse in whenever, and it Just Works[tm].

However, I think this bug should be closed if the other commenters have also seen the problem go away.

I haven't seen any difference between the release version and the version at the end of april. Still see the same problems (not that I have a keyboard/mouse logitech combo)

that shouldn't have been 'note', not 'not'. Also, I didn't have this problem until I moved to Kubuntu. I used that have a Debian sid/Sony laptop where I plugged this combination in (linux 2.6.15 or so), without problems.

As far as I am concerned, you my close it, I have moved to Fedora FC5.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Hi Steven,

Let me know if this is still an issue with Intrepid. Thanks.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!