[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#655387: Samsung galaxy S won't tether trough usb due to bad CDC descriptors

El 10 de enero de 2012 21:21, Jonathan Nieder <jrnieder@gmail.com> escribió:
Iker Salmón San Millán wrote:

> This bug affects all kernels i've tried in debian wheezy, sid and
> experimental, I found a bug report in ubuntu where i found this patch that
> solves the problem, but the user who wrote the patch described it as
> workaroung instead of fix:

Link, please.

Also, could you describe the symptoms further?  What steps would I
perform to reproduce the bug if I had the hardware, what are the
expected and actual results, and how does the difference indicate a

If you connect the samsung galaxy S (i know also SII is affected) to the usb hub and activate usb tethering it won't create usb0 interface and dmesg shows this:

[  509.033511] usb 2-2: USB disconnect, device number 5
[  509.304059] usb 2-2: new high-speed USB device number 6 using ehci_hcd
[  509.438155] usb 2-2: New USB device found, idVendor=04e8, idProduct=6881
[  509.438165] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  509.438172] usb 2-2: Product: SAMSUNG_Android
[  509.438178] usb 2-2: Manufacturer: SAMSUNG
[  509.438183] usb 2-2: SerialNumber: 353271BC9D8400EC
[  509.743606] usbcore: registered new interface driver cdc_ether
[  509.745205] usb 2-2: bad CDC descriptors
[  509.745231] usbcore: registered new interface driver rndis_host
[  509.753788] usb 2-2: bad CDC descriptors
[  509.753821] usbcore: registered new interface driver rndis_wlan

If you apply the patch and rebuild the kernel the usb0 interface is created correctly when you activate usb tether.

I don't know what else can i comment, surely there are people much more prepared than me to report this things, but i'll try my best if you ask me something or ask me tro try anything
Thanks for your work,

No, Thanks for yours

Reply to: