|
Bugzilla – Full Text Bug Listing |
| Summary: | USB mouse does not work during installation | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Bart Whiteley <bwhiteley> |
| Component: | Kernel | Assignee: | Vojtech Pavlik <vojtech> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | ms, snwint |
| Version: | Alpha 2plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
requested info. hwinfo, lsusb, y2log*
lsusb, dmesg, and proc files requested during install. |
||
|
Description
Bart Whiteley
2005-11-09 17:12:52 UTC
Please, provide more information. Is the mouse detected? Attach ylogs, lsusb and hwinfo output. Still broken on alpha3. I'm not sure how to tell if it is detected. The mouse works in SaX2 from runlevel 3 after the install. Just doesn't work during the install. Created attachment 57572 [details]
requested info. hwinfo, lsusb, y2log*
These lines from /var/log/messages are puzzling <3>shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5 <3>shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5 <3>shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5 <3>shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5 <3>shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5 <3>shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5 Looks more like a kernel/driver issue Vojtech, any idea? To comment #4,#5: The shpchp lines are irrelevant, it's a hotplug PCI module loading and failing. I doubt this machine has any hotpluggable PCI slots, and thus it's not a problem. The "HID" acronym in those messages isn't related to USB HID. I believe if anything, it's a hotplug/udev/module loading issue. Regarding the info provided in comment #3: I assume this was collected after the installation is completed? It shows a perfectly working USB mouse, To be able to say anything about the reason why the mouse didn't work, I need at least the 'dmesg', 'lsusb' and 'cat /proc/bus/usb/devices' and 'cat /proc/bus/input/devices' outputs at the time the mouse doesn't work. Created attachment 57674 [details]
lsusb, dmesg, and proc files requested during install.
Here is the requested info, gathered while the install was running and the mouse was not working.
Interestingly enough, all is good there as well. The mouse is found, identified and attached to correct userspace interfaces. Can you check whether 'cat /dev/input/mice' produces garbage on the screen when you move/click the mouse, during installation, when the mouse doesn't move the cursor? Also please take a look on /proc/interrupts, whether the USB interrupt is increasing. 'cat /dev/input/mice' does produce garbage as the mouse is moved during the install. I'm not sure what to look for in /proc/interrupts. None of the lines containing "usb" change as the mouse is moved. That means the mouse works correctly. This seems to be a duplicate of bug #134032. *** This bug has been marked as a duplicate of 134032 *** |