Opened 2 years ago
#18175 new bug
USB mouse sometimes does not work at boot
Reported by: | RetroHacker | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Input/HID/USB | Version: | R1/beta4 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Using R1/Beta4. Mouse in question is a USB corded mouse, three button (Sun Type 6 "Crossbow" USB) which shows up in a USB listing as Fujitsu. Sometimes (but not all the time), when the system boots, the mouse is nonfunctional. Plugging a second mouse in works fine, and the first one shows up in Devices, but not in Input. Unplugging and replugging the affected mouse *sometimes* doesn't work - in fact the device will go away from the Devices listing as well. Even when plugged into a different port. But then on other boots, unplugging the mouse and plugging it in to a different port does work. In this case, that's what happened, and I have the log files from before (when the mouse didn't work at boot) and the after ones, where it did work after I unplugged it and plugged it into a different port.
Attachments (10)
Change History (10)
by , 2 years ago
by , 2 years ago
Attachment: | listdevafter added |
---|
by , 2 years ago
by , 2 years ago
Attachment: | listdevdafter added |
---|
listdev -d after unplugging mouse and plugging it into a different port
by , 2 years ago
by , 2 years ago
Attachment: | listimageafter added |
---|
listimage |grep drivers after unplugging mouse and plugging it into a different port
by , 2 years ago
by , 2 years ago
Attachment: | listusbvafter added |
---|
listusb -v after unplugging mouse and pluging it into a different port
by , 2 years ago
by , 2 years ago
Attachment: | syslogafter added |
---|
syslog after unplugging mouse and plugging it into a different port
listdev after unplugging mosue and plugging it into another port