From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504 Galeon/1.3.20 Description of problem: After connecting Sharp Zaurus C-3000 it gets refused with: May 15 01:29:05 kashome kernel: usbnet 5-2:1.0: MDLM guid May 15 01:29:05 kashome kernel: usb 5-2: unsupported MDLM descriptors May 15 01:29:05 kashome kernel: usbcore: registered new driver usbnet (no usb0 device exists) After the attached trivia patch the error is different: May 15 02:28:38 kashome kernel: usbnet 5-2:1.0: bad MDLM detail, 6 0 13 May 15 02:28:38 kashome kernel: usb 5-2: unsupported MDLM descriptors May 15 02:28:38 kashome kernel: usbcore: registered new driver usbnet After replacing usbnet.c from Debian Sarge kernel-source-2.6.8_2.6.8-15 it works although the Debian driver is apparently older. Version-Release number of selected component (if applicable): kernel-2.6.11-1.1303_FC4 How reproducible: Always Steps to Reproduce: 1. Connect Sharp Zaurus C-3000. 2. See no usb0 appears. Actual Results: May 15 01:29:05 kashome kernel: usb 5-2: unsupported MDLM descriptors May 15 01:29:05 kashome kernel: usbcore: registered new driver usbnet Expected Results: May 15 03:10:00 kashome kernel: usb0: register usbnet at usb-0000:00:10.3-2, Sharp Zaurus, PXA-2xx based May 15 03:10:00 kashome kernel: usbcore: registered new driver usbnet Additional info:
Created attachment 114387 [details] Compatible Debian kernel-source-2.6.8_2.6.8-15 driver.
Created attachment 114388 [details] Insufficient patch for kernel-2.6.11-1.1303_FC4 usbnet.c
Created attachment 114389 [details] lsusb -v after connecting the device using Debian usnet.c
Mass update of -test bugs to update version to fc4. (Please retest on final release, and report results if you have not already done so). Thanks.
I have sold (/selling) Sharp Zaurus C-3000, I have no longer it available for tests. I expect the bug should get closed.
2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you.