Skip to contentSkip to conversation

2.6.6 breaks my Logitech USB mouse

DISCUSSION Felix von Leitner 2 participants 2 messages May 12, 2004

lore
Share & tools
lore
#0 lore raw

When booting into 2.6.6 (compiled with gcc 3.4, could that be the problem?), my USB mouse does not work any more. Neither hot nor cold plugging it works. USB detects a low speed device and then hangs.

Now I am used to USB not working at all under Linux on my desktop with VIA chipset, but now USB is also hosed for Intel chipsets? Here is the dmesg from 2.6.5, where my USB mouse still worked:

drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub
USB Universal Host Controller Interface driver v2.2
PCI: Found IRQ 10 for device 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:0f.0
PCI: Sharing IRQ 10 with 0000:02:0f.1
PCI: Sharing IRQ 10 with 0000:02:0f.2
uhci_hcd 0000:00:1f.2: Intel Corp. 82801BA/BAM USB (Hub #1)
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: irq 10, io base 0000bce0
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
drivers/usb/core/usb.c: registered new driver hiddev drivers/usb/core/usb.c: registered new driver hid drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 1-1: new low speed USB device using address 2
input: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1f.2-1 drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found

2.6.6 never reaches the "input: " line. What gives?

Felix

#1 lore raw
Quoted 2 lines · Felix von Leitner

2.6.6 never reaches the "input: " line. What gives?

Don't know, can you enable CONFIG_USB_DEBUG and send the kernel log to the linux-usb-devel mailing list?

thanks,

greg k-h