Hello again, On Wed, Mar 09, 2005 at 06:18:46PM +0000, Jochen Voss wrote: > The dmesg output contains the following lines which look like error > messages: I mananged to overlook the one which might be most relevant: PCI: Enabling device 0001:10:1a.0 (0000 -> 0002) ohci_hcd 0001:10:1a.0: Apple Computer Inc. KeyLargo/Intrepid USB (#2) ohci_hcd 0001:10:1a.0: irq 29, pci mem 0xa0003000 ohci_hcd 0001:10:1a.0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected PCI: Enabling device 0001:10:1b.0 (0000 -> 0002) ohci_hcd 0001:10:1b.0: NEC Corporation USB ohci_hcd 0001:10:1b.0: irq 63, pci mem 0xa0002000 ohci_hcd 0001:10:1b.0: new USB bus registered, assigned bus number 2 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected usb 1-1: new full speed USB device using ohci_hcd and address 2 usb 1-1: device descriptor read/64, error -71 PCI: Enabling device 0001:10:1b.1 (0000 -> 0002) ohci_hcd 0001:10:1b.1: NEC Corporation USB (#2) ohci_hcd 0001:10:1b.1: irq 63, pci mem 0xa0001000 ohci_hcd 0001:10:1b.1: new USB bus registered, assigned bus number 3 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected usb 1-1: device descriptor read/64, error -71 usb 1-1: new full speed USB device using ohci_hcd and address 3 usb 1-1: device descriptor read/64, error -71 usb 1-1: device descriptor read/64, error -71 usb 1-2: new full speed USB device using ohci_hcd and address 4 ... input: USB HID v1.10 Keyboard [Apple Computer Apple Internal Keyboard/Trackpad] on usb-0001:10:1a.0-2 HID device not claimed by input or hiddev usbhid: probe of 1-2:1.1 failed with error -5 input: USB HID v1.10 Device [Apple Computer Apple Internal Keyboard/Trackpad] on usb-0001:10:1a.0-2 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver I think that "error -71" means "protocol error" (i.e. EPROTO). Maybe these errors are the cause for the I/O error (error -5, second half of the messages) which in turn might make the trackpad not work? The protocol error messages seem to be emitted by the function 'hub_port_init' in "drivers/usb/core/hub.c". Maybe the -EPROTO is somehow passed down from the 'usb_get_descriptor' function in "drivers/usb/core/message.c"? The flow of control there is a little bit hard for me to follow. I hope this helps, Jochen -- http://seehuhn.de/
Attachment:
signature.asc
Description: Digital signature