Hi,

I hadn't used my tux droid for a while (yeah bad) and wanted to try all the new exciting stuff out there today.
I ran into some problems[57780.961809] usb 2-6: new full speed USB device using ohci_hcd and address 31
 with the fux dongle, plugin it in would not light the eyes.

I get the following logs:

[57781.141793] usb 2-6: device descriptor read/64, error -62

[57781.425773] usb 2-6: device descriptor read/64, error -62

[57781.705757] usb 2-6: new full speed USB device using ohci_hcd and address 32

[57781.885743] usb 2-6: device descriptor read/64, error -62

[57782.169726] usb 2-6: device descriptor read/64, error -62

[57782.449707] usb 2-6: new full speed USB device using ohci_hcd and address 33

[57782.857676] usb 2-6: device not accepting address 33, error -62

[57783.017668] usb 2-6: new full speed USB device using ohci_hcd and address 34

[57783.425638] usb 2-6: device not accepting address 34, error -62

I've seen a similar post on the forum (http://www.tuxisalive.com/tux-droid-forum/copy_of_forumtopic1/34329874/#77988763) and tried to plug fux with the belly button pressed and do a tuxup but to no avail:

$ tuxup fuxusb.hex
Programming fuxusb.hex in the USB CPU
Version 0.4.0
The dongle was not found, now exiting.

I remember this was working before.
also removing module ehci_hcd had no effect.

henry@home:~$ uname -a
Linux home 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

Maybe it is worth noting that I upgraded to hardy heron in the mean time but I tried to plug fux on my work laptop (Centos 5.1 with 2.6.18 kernel) and I get the same kind of messages.

could it be that my fux has been somewhat damaged?

any help warmly appreciated.

Henry

I think the problem is more on your side. You can always safely start tux in bootloader mode by pressing the belly button like you did. Then you can try to detect it with dfu-programmer directly:
$ dfu-programmer at89c5130 get bootloader-version
Bootloader Version: 0x03 (3)

This bootloader mode is hardware, not firmware related so there's no way you could damage it.

If that works, tuxup should work but if it doesn't, then I can give you the dfu-programmer commands to get your dongle updated.

Hi David, thanks for the response.

I'm not sure to understand. I think my dongle is not recognize at all.
I tried your hint:

henry@home:/opt/tuxdroid/bin$ dfu-programmer at89c5130 get bootloader-version
dfu-programmer: no device present.

is there something obvious I'm missing?

In that case, I'm sure there's a problem with your kernel and USB, as at least that one should show up correctly. What does lsusb show? (type lsusb as root)

henry@home:~$ sudo lsusb
Bus 002 Device 001: ID 0000:0000 
Bus 001 Device 001: ID 0000:0000 

all other usb devices I can find show up correctly as for my digital camera:

henry@home:~$ sudo lsusb
Bus 002 Device 001: ID 0000:0000 
Bus 001 Device 003: ID 0a17:0043 Pentax Corp. Pentax *ist DL
Bus 001 Device 001: ID 0000:0000 

but nothing happen with fux