Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 128810
| Summary: | Logitech USB keyboard unreliably detected | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernie Innocenti <bernie+fedora> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | pfrields, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-04 12:58:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 165247 | ||
any success with the current kernels ? No response, closing. Sorry for not answering before. Yes, the USB keyboard is now always detected corretly. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux 2.6.7-1.494custom; X11; i686; , en) (KHTML, like Gecko) Description of problem: I have a Logitech Navigator keyboard with an embedded mouse wheel (the keyboard is really *two* USB devices hooked together). There appears to be a race condition in the usbhid module because very often the keyboard doesn't get detected at boot time (see dmesg output in "Actual Results"). I can usually fix this by hooking a PS2 kbd and typing "rmmod usbhid; modprobe usbhid". Sometimes I need to do this twice or even three times. When the keyboard works, I get the dmesg output shown in "Expected Results" (see below). I sometimes successfully recovered also by unplugging and re-plugging the keyboard, but this trick appears to have stopped working with the latest kernels. The first time I've seen this bug is when I switched my motherboard to an Abit AN7 (nForce2 chipset). I was probably using kernel 2.6.1 or 2.6.2 at the time, so it's not a new bug. Version-Release number of selected component (if applicable): kernel-2.6.7-1.494 How reproducible: Sometimes Steps to Reproduce: 1.Boot with USB keyboard connected 2. 3. Actual Results: usbhid: probe of 2-1:1.0 failed with error -5 input: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-0000:00:02.0-1 input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-2 Expected Results: usbcore: deregistering driver hiddev usbcore: deregistering driver usbhid usbcore: registered new driver hiddev input: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:02.0-1 input: USB HID v1.10 Mouse [Logitech Logitech USB Keyboard] on usb-0000:00:02.0-1 input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-2 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver Additional info: