Problem with usb cable: device descriptor read/64, error -110

Kevin Zuber Kevin at
Tue Aug 5 11:47:02 CEST 2008

Hi Andy,

thanks for your quick answer!

Ok, that's the reason for the problem but it doesn't fix it completely.
After flashing uboot (flashing works quite well so no problem with the
cable) there was no more error message but also no success message. 
If I connect now my Freerunner to the usb port (when the Freerunner is
powered up) there isn't any kind of message in dmesg on the host and
there is also no new networking interface (usb0).

So usb networking is still not working.

Do I have to wait for an fix?


Am Montag, den 04.08.2008, 19:28 +0100 schrieb Andy Green:
> Hash: SHA1
> Somebody in the thread at some point said:
> | So it should be the cable (hardware defect?) oder the neo update (using
> | 2007.2 with latest updates).
> | Did I miss something, any other ideas? Has someone this problems, too?
> |
> | It also seems, that the neo isn't charging anymore when it is connected
> | to the cable. The usb power supply is still working fine and can charge
> | the neo.
> |
> | Thanks a lot for your answer!
> This sounds exactly like the fault of the bad U-Boot we put out for a
> while.  Boot into your NOR U-Boot by holding AUX while powering up, then
> dfu over today's U-Boot image.  After that this should be no longer a
> problem.
> - -Andy
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora -
> AHsAn0ZEqZKAT8uFabtUk8KeYqk4bUfF
> =OC8N
> _______________________________________________
> Openmoko community mailing list
> community at

More information about the community mailing list