[tuxdroid-user] Error : Tux dongle is busy or disconnected

[david <da...@ja...>]

If you didn't follow the forum or IRC, there's been some issue with the =
 =

dongle connection on most >=3D2.6.18 kernels.

That was a bug of the dongle which is now FIXED !

Thanks to all of you who were on IRC and helped to get a clear view on  =

this. We found that a delay used by the interrupt interface was set to 0=
ms  =

(that's the case in bulk) but should have been a 1ms at least.
Don't ask me why it could work like this with the older kernels, I have =
no  =

idea but it seems they corrected that in 2.6.18.

So update your firmware :)

I wrote a howto, check it at  =

http://www.tuxisalive.com/documentation/how-to/updating-the-firmware
You only need to update fuxusb.hex so you can stop after the second step=
  =

of 'Testing tuxup'

There's no release of tuxup yet, but you can get it from SVN with
     svn co https://svn.kysoh.com/firmware/tuxup/trunk tuxup

Then you need to update the daemon, I didn't make a release neither so  =

once more svn is your friend:
     svn co https://svn.kysoh.com/daemon/trunk tuxdaemon
     build the daemon and copy tuxdaemon to /opt/tuxdroid/bin if you did=
 so  =

in the past

I'll do a release of tuxup, the daemon and other firmwares next week but=
  =

for all of you who have a kernel >=3D 2.6.18, you can at least fix your =
 =

problems right now. Hope that works for everybody. Let me know about any=
  =

problem you encounter with the procedure.

Cheers,
david