Hi all,

since yesterday (my bday) I can call myself as more proudly tux+fux owner.

That's great! I love him (or her!?)...


As I am only use linux for servers and not for desktops, I've got problems to play with my tux.

Therefore I turned on my sweet little VMware Workstation 6 and goes on with a CentOS 5 Desktop Appliance.

The first thought was frustrating as nothing really works, but after I upgraded software 1.2 to 1.3, tux was born
But now there was some doubts f.e. tux will not turn around with factory firmware. (Yes, I recognized the power cable )

Then I read on your page it would be appreciate to upgrade the firmware, which I naturally also did.

Using the GUI FW Upgrader breaks my fux with a common error... After some research in your forum I love the tuxup hex function

Okay, then I further tried to go on with upgrading tux&fux on bash... This also failed, and tux dies! It's really frustrating!!!!

I searched and searched and tried several steps suggested by David, but it still won't work.

Then I used my old physical firewall gateway (CentOS 4.4 i386) with software 1.3, which hangs with the known GLIBC_24 error...
After trying to upgrade GLIBC, my system brings some other unlikely errors
So I'd turned back to glibc 2.3.6 and download the older one, tuxsetup 1.2, which works PERFECTLY with older glibc versions

After this I tried to tuxup' the firmware of tux with success! All core's are upgraded successfully

So back to the root's physical is still the best


Thanks to David & everyone else who had same problems...

Now I have only problems with TTS (tried with German, US) which still not work
Tux can play sounds like yummy, hello or local music (slot 8 or so), but nothing which belongs to TTS.

BTW: After upgrading firmware my tux also can turn around and close the eyes

Regards,
Timo

Glad you finally got through. VMware doesn't work for updating the firmware. We made some tests and actually we got some really strange things and ended up with the wrong bytes on the dongle side so that the firmware could be corrupted. This isn't a real problem for most firmware, but it is for tuxrf and fuxrf as those ones can be permanently damaged. I think I posted that warning already.
I don't know why it didn't spin previously.

For the TTS, I can't help you. But you'll have to post more details about what doesn't work, the steps you did, etc. in order for people to help you.
Did you try to start tuxttsd manually in a terminal? That may output some debug messages already.

David

Hi David,

I think that is my problem... I don't have the tuxttsd command or I missed a step in your instruction...

System: CentOS release 5 (Final) Desktop, VMware
[root@tuxstation ~]# uname -a
Linux tuxstation 2.6.18-53.el5 #1 SMP Mon Nov 12 02:22:48 EST 2007 i686 i686 i386 GNU/Linux

I downloaded tuxsetup-1.3, extract the files and run make install...

-------------------------------------------------------------------------------
tuxsetup-1.3.0013-rc1
-------------------------------------------------------------------------------
Python API       v 0.2.4
USB daemon       v 0.3.2
Tux framework    v 0.1.3
-------------------------------------------------------------------------------
files are been copied
tuxsetup: dfu-programmer has been found on this system:
dfu-programmer 0.4.1
-------------------------------------------------------------------------------

Don't know what there goes wrong...
These are my tux* commands...

[root@tuxstation tuxsetup-1.3.0013-rc1]# tux
tuxd     tuxfw    tuxgdg   tuxosld  tuxsh    tuxup

Hmm... I don't get the warning @RF, but there is also an advantage....
Now I know how tux and fux works

My problem is that the tux can't say anything which belongs to TTS. Local sounds are not a problem...
Also if I click on a gadget... The mouth opens and close... But there is no sound...

Are there any incompatiblities or experience with RedHat?

Do you need some more information?

Thanks,
Timo

I suggest if you have problems with vmware, that you try first by booting an ubuntu gutsy 7.10 live cd (not the hardy 8.04 one!) and install things in there.
TTS has its own driver. For 1.3 this is a python script that is started. Somethhing with osl in it I think.

Yeah right, tuxttsd has been replaced by the OSL driver in 1.3 and I have no idea how it works so I'm afraid I won't be of much help anymore on that side (if I ever was about the TTS anyway )