Re: [tuxdroid-user] new to TuxDroid
Status: Beta
Brought to you by:
ks156
Menu
▾
▴
Re: [tuxdroid-user] new to TuxDroid
|
From: <pau...@c2...> - 2008-11-15 19:39:31
|
Hello Yellow Penguin,
> - why does the TD-dongle blocks the PC starting process when inserted in
> its
> USB-slot before the PC power-button is pressed ? Is this normal ?
That's not normal indeed. I think this is due to the PC mainboard, or bios
version, or something like this.
Usually, there is no problems to start the PC with the dongle connected.
But on some computers, you can't. I've this kind of problems on my desktop
PC at home : When the dongle is plugged when I start the computer, the BIOS
returns a strange error : "No keyboard found".
Maybe you've plugged the dongle on an USB-slot on the front ? You can try
to connect it on an other USB slot and see if the problem persist.
> - how to be sure of the communication between dogle and penguin: isn't
> there
> any simple commandline test we can do to check ? BTW, how far or high
> should
> the dongle be positionned to be sure that the Tux is seeing him ?
You can see if the communication has been established with the dongle's
LEDs.
When the communication is established, the LEDs will flicker quickly.
Otherwise, they're flickers slowly (ca 1 cycle per second).
> - is it normal that there isn't any shortcut-button on the Gnome desktop
?
> Is this due to the fact that I installed it from the commandline using
> dpkg
> -i ?
To create a shortcut on the desktop, the installer must know the user.
Technically, this is very difficult to do, because the installation must be
done as root.
You'll find shortcut in the gnome main menu : Applications / Accessories.
You can create a desktop shortcut directly from here.
> Here is also a 1st test I did; I hope anything is correct; I will anyway
> appreciate any feedback:
>
>
> # A newbie's TuxDroid installation/connection test:
>
> Script is gestart op vr 14 nov 2008 17:24:34 CET
> # Is the tuxdroid installation correct?
>
> # Before inserting the dongle:
>
> anita@beertje:~$ dpkg -l |grep tux
> ii tuxdroid-tts-voices.belgiandutch 1.0-1
> BelgianDutch TTS voice for Tuxdroid.
> ii tuxsetup 1.3-19
> Software kit for tuxdroid
> (tuxsetup 2.x doesn't install on this Ubuntu Feisty PC, that's why I
tried
> with v. 1.3.19 using
> sudo dpkg -i file.deb
> then apt-get -f install to add missing deps)
>
> anita@beertje:~$ locate -i tuxd
> /usr/local/bin/tuxd
> /usr/doc/tuxdroid-tts-voices.belgiandutch
> /usr/doc/tuxdroid-tts-voices.belgiandutch/README
> /etc/udev/rules.d/45-tuxdroid.rules
> /opt/tuxdroid
> /opt/tuxdroid/firmware
> /opt/tuxdroid/firmware/tuxdroid-firmware-hex.0.4.0.tar.gz
> /opt/tuxdroid/api
> /opt/tuxdroid/api/python
> /opt/tuxdroid/api/python/CHANGES
> /opt/tuxdroid/api/python/AUTHORS
> /opt/tuxdroid/api/python/COPYING
> /opt/tuxdroid/api/python/tuxapi_const.py
> /opt/tuxdroid/api/python/tuxapi_wav_merger.py
> /opt/tuxdroid/api/python/tux.py
> /opt/tuxdroid/api/python/tuxapi_class.py
> /opt/tuxdroid/api/python/TODO
> /opt/tuxdroid/api/python/README
> /opt/tuxdroid/doc
> /opt/tuxdroid/doc/examples
> /opt/tuxdroid/doc/examples/basescript.py
> /opt/tuxdroid/doc/python-api
> /opt/tuxdroid/doc/python-api/PythonApi-0.2.3.pdf
> /opt/tuxdroid/bin
> /opt/tuxdroid/bin/tuxgdg
> /opt/tuxdroid/bin/tuxsh
> /opt/tuxdroid/bin/tuxd
> /opt/tuxdroid/bin/tuxfw
> /opt/tuxdroid/bin/tuxup
> /opt/tuxdroid/bin/tuxatt
> /opt/tuxdroid/bin/tuxosld
> /opt/tuxdroid/bin/dfu-programmer
> /opt/tuxdroid/apps
> /opt/tuxdroid/apps/tux_framework
> /opt/tuxdroid/apps/tux_framework/libs
> /opt/tuxdroid/apps/tux_framework/libs/GdgDebug.py
> /opt/tuxdroid/apps/tux_framework/libs/GdgObject.py
> /opt/tuxdroid/apps/tux_framework/libs/thomas.py
> /opt/tuxdroid/apps/tux_framework/libs/GdgDownload.py
> /opt/tuxdroid/apps/tux_framework/libs/TGFormat.py
> /opt/tuxdroid/apps/tux_framework/libs/TGFXml.py
> /opt/tuxdroid/apps/tux_framework/libs/language_guesser.bay
> /opt/tuxdroid/apps/tux_framework/libs/FWObject.py
> /opt/tuxdroid/apps/tux_framework/libs/behavior_cb.py
> /opt/tuxdroid/apps/tux_framework/libs/TGFCanvas.py
> /opt/tuxdroid/apps/tux_framework/libs/_DTW.so
> /opt/tuxdroid/apps/tux_framework/libs/BabelfishTranslate.py
> /opt/tuxdroid/apps/tux_framework/libs/voice_cb.py
> /opt/tuxdroid/apps/tux_framework/libs/GdgVoiceRec.py
> /opt/tuxdroid/apps/tux_framework/libs/keyboard.py
> /opt/tuxdroid/apps/tux_framework/libs/SimpleGladeApp.py
> /opt/tuxdroid/apps/tux_framework/libs/TGFParser.py
> /opt/tuxdroid/apps/tux_framework/libs/GoogleTranslate.py
> /opt/tuxdroid/apps/tux_framework/libs/GdgGuiUpdate.py
> /opt/tuxdroid/apps/tux_framework/libs/GdgThreads.py
> /opt/tuxdroid/apps/tux_framework/libs/Languages.py
> /opt/tuxdroid/apps/tux_framework/libs/DTW.py
> /opt/tuxdroid/apps/tux_framework/libs/TextFilters.py
> /opt/tuxdroid/apps/tux_framework/libs/C2MEDoc.py
> /opt/tuxdroid/apps/tux_framework/libs/menu.py
> /opt/tuxdroid/apps/tux_framework/libs/tdrss.py
> /opt/tuxdroid/apps/tux_framework/libs/TimeLineReader.py
> /opt/tuxdroid/apps/tux_framework/libs/t9.py
> /opt/tuxdroid/apps/tux_framework/SDK
> /opt/tuxdroid/apps/tux_framework/SDK/doc
> /opt/tuxdroid/apps/tux_framework/SDK/doc/GdgSceneContainer_doc.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/TGFParser.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/GdgDebug_doc.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/PythonApi.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/GdgObject_doc.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/GdgScene_doc.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/doc/GdgScenario_doc.pdf
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/tuxgagdetmaker.glade
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/maker.png
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/otherpyp.base
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/tuxgagdetmaker.py
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/otherglade.base
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/config.py
> /opt/tuxdroid/apps/tux_framework/SDK/gadget_maker/Template.tgf
> /opt/tuxdroid/apps/tux_framework/TFW.py
> /opt/tuxdroid/apps/tux_framework/bin
> /opt/tuxdroid/apps/tux_framework/bin/frame
> /opt/tuxdroid/apps/tux_framework/bin/mgcep
> /opt/tuxdroid/apps/tux_framework/bin/x2x
> /opt/tuxdroid/apps/tux_framework/bin/mgc2mgc
> /opt/tuxdroid/apps/tux_framework/bin/pitch
> /opt/tuxdroid/apps/tux_framework/bin/README
> /opt/tuxdroid/apps/tux_framework/bin/window
> /opt/tuxdroid/apps/tux_framework/version.py
> /opt/tuxdroid/apps/tux_manager
> /opt/tuxdroid/apps/tux_manager/gadgets
> /opt/tuxdroid/apps/tux_manager/gadgets/Attitunes_studio.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Email.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Scenes_manager.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Clock.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/firmware_updater.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/VoiceRec_configurator.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Manager.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/TuxController.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Weather.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/audio_flash.tgf
> /opt/tuxdroid/apps/tux_manager/gadgets/Debug_control.tgf
> /opt/tuxdroid/apps/tuxosl
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_controler.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_service_server.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_cmd_client.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_obj.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_cmd_client.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_daemon.py
> /opt/tuxdroid/apps/tuxosl/service_daemonizer.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_wrapper.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_const.pyc
> /opt/tuxdroid/apps/tuxosl/service_daemonizer.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_cmd_server.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_service_server.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_api.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_cmd_server.pyc
> /opt/tuxdroid/apps/tuxosl/_TUX_OSL.so
> /opt/tuxdroid/apps/tuxosl/tux_osl_obj.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_const.py
> /opt/tuxdroid/apps/tuxosl/tux_osl_wrapper.pyc
> /opt/tuxdroid/apps/tuxosl/tux_osl_event_controler.py
> /opt/tuxdroid/apps/tuxgi
> /opt/tuxdroid/apps/tuxgi/sounds
> /opt/tuxdroid/apps/tuxgi/sounds/16.wav
> /opt/tuxdroid/apps/tuxgi/sounds/3.wav
> /opt/tuxdroid/apps/tuxgi/sounds/4.wav
> /opt/tuxdroid/apps/tuxgi/sounds/11.wav
> /opt/tuxdroid/apps/tuxgi/sounds/6.wav
> /opt/tuxdroid/apps/tuxgi/sounds/15.wav
> /opt/tuxdroid/apps/tuxgi/sounds/9.wav
> /opt/tuxdroid/apps/tuxgi/sounds/1.wav
> /opt/tuxdroid/apps/tuxgi/sounds/13.wav
> /opt/tuxdroid/apps/tuxgi/sounds/14.wav
> /opt/tuxdroid/apps/tuxgi/sounds/2.wav
> /opt/tuxdroid/apps/tuxgi/sounds/17.wav
> /opt/tuxdroid/apps/tuxgi/sounds/8.wav
> /opt/tuxdroid/apps/tuxgi/sounds/10.wav
> /opt/tuxdroid/apps/tuxgi/sounds/7.wav
> /opt/tuxdroid/apps/tuxgi/sounds/5.wav
> /opt/tuxdroid/apps/tuxgi/sounds/12.wav
> /var/lib/dpkg/info/tuxdroid-tts-voices.belgiandutch.conffiles
> /var/lib/dpkg/info/tuxdroid-tts-voices.belgiandutch.list
>
> # Now an usb and dmesg test
>
> anita@beertje:~$ lsusb
> (before inserting the dongle):
> Bus 005 Device 002: ID 04b4:6830 Cypress Semiconductor Corp. USB-2.0 IDE
> Adapter
> Bus 005 Device 001: ID 0000:0000
> Bus 002 Device 002: ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 004: ID 0a5c:2101 Broadcom Corp.
> Bus 001 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 001: ID 0000:0000
>
> anita@beertje:~$ dmesg -n 27
> klogctl: Bewerking niet toegestaan
> anita@beertje:~$ dmesg |tail -n 27
> [ 87.260379] NET: Registered protocol family 17
> [ 90.069567] ibm_acpi: ec object not found
> [ 90.144286] Using specific hotkey driver
> [ 90.277297] input: Power Button (FF) as /class/input/input4
> [ 90.277388] ACPI: Power Button (FF) [PWRF]
> [ 90.300806] input: Power Button (CM) as /class/input/input5
> [ 90.300828] ACPI: Power Button (CM) [PWRB]
> [ 90.308894] No dock devices found.
> [ 90.353110] pcc_acpi: loading...
> [ 93.416423] eth0: link down
> [ 93.416463] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 94.245986] ppdev: user-space parallel port driver
> [ 95.254172] [drm] Initialized drm 1.1.0 20060810
> [ 95.295012] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low)
> -> IRQ 19
> [ 95.295226] [drm] Initialized i915 1.6.0 20060119 on minor 0
> [ 96.406032] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
> [ 96.406036] apm: disabled - APM is not SMP safe.
> [ 98.159344] vboxdrv: Trying to deactivate the NMI watchdog
> permanently...
> [ 98.159348] vboxdrv: Successfully done.
> [ 98.159377] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
> 'normal'.
> [ 98.159378] vboxdrv: Successfully loaded version 1.5.6 (interface
> 0x00050002).
> [ 98.620666] Bluetooth: L2CAP ver 2.8
> [ 98.620669] Bluetooth: L2CAP socket layer initialized
> [ 98.821094] Bluetooth: RFCOMM socket layer initialized
> [ 98.821103] Bluetooth: RFCOMM TTY layer initialized
> [ 98.821104] Bluetooth: RFCOMM ver 1.8
> [ 104.989948] EXT2-fs warning: mounting unchecked fs, running e2fsck is
> recommended
>
> # After inserting the dongle
>
> anita@beertje:~$ lsmod |grep usb
> usbhid 26592 0
> hid 27392 1 usbhid
> snd_usb_audio 79744 1
> snd_usb_lib 17280 1 snd_usb_audio
> snd_pcm 79876 5
> snd_usb_audio,snd_emu10k1,snd_ac97_codec,snd_pcm_oss
> snd_hwdep 9988 3 snd_usb_audio,snd_emux_synth,snd_emu10k1
> snd_rawmidi 25472 4
> snd_usb_lib,snd_seq_virmidi,snd_emu10k1,snd_seq_midi
> snd 54020 18
>
snd_usb_audio,snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
> hci_usb 18204 2
> bluetooth 55908 7 rfcomm,l2cap,hci_usb
> usb_storage 72256 1
> libusual 17936 1 usb_storage
> scsi_mod 142348 5 usb_storage,sg,sr_mod,sd_mod,libata
> usbcore 134280 10
>
xpad,usbhid,snd_usb_audio,snd_usb_lib,hci_usb,usb_storage,libusual,ehci_hcd,uhci_hcd
>
> (snd_usb_audio seems to be loaded by the system...)
>
> anita@beertje:~$ lsusb
> (the Tux is recognized as an Atmel device)
> Bus 005 Device 002: ID 04b4:6830 Cypress Semiconductor Corp. USB-2.0 IDE
> Adapter
> Bus 005 Device 001: ID 0000:0000
> Bus 002 Device 002: ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20
> Bus 002 Device 001: ID 0000:0000
> Bus 001 Device 004: ID 0a5c:2101 Broadcom Corp.
> Bus 001 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 002: ID 03eb:ff07 Atmel Corp.
> Bus 003 Device 001: ID 0000:0000
>
> anita@beertje:~$ dmesg |tail -n 27
> [ 93.416463] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 94.245986] ppdev: user-space parallel port driver
> [ 95.254172] [drm] Initialized drm 1.1.0 20060810
> [ 95.295012] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low)
> -> IRQ 19
> [ 95.295226] [drm] Initialized i915 1.6.0 20060119 on minor 0
> [ 96.406032] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
> [ 96.406036] apm: disabled - APM is not SMP safe.
> [ 98.159344] vboxdrv: Trying to deactivate the NMI watchdog
> permanently...
> [ 98.159348] vboxdrv: Successfully done.
> [ 98.159377] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
> 'normal'.
> [ 98.159378] vboxdrv: Successfully loaded version 1.5.6 (interface
> 0x00050002).
> [ 98.620666] Bluetooth: L2CAP ver 2.8
> [ 98.620669] Bluetooth: L2CAP socket layer initialized
> [ 98.821094] Bluetooth: RFCOMM socket layer initialized
> [ 98.821103] Bluetooth: RFCOMM TTY layer initialized
> [ 98.821104] Bluetooth: RFCOMM ver 1.8
> [ 104.989948] EXT2-fs warning: mounting unchecked fs, running e2fsck is
> recommended
> [25662.801577] usb 3-1: new full speed USB device using uhci_hcd and
> address 2
> [25662.979470] usb 3-1: configuration #1 chosen from 1 choice
> [25663.857949] usbcore: registered new interface driver snd-usb-audio
> [25663.957518] usbcore: registered new interface driver hiddev
> [25663.963737] hiddev96: USB HID v1.10 Device [Kysoh TuxDroid] on
> usb-0000:00:1d.2-1
> [25663.963916] usbcore: registered new interface driver usbhid
> [25663.965834] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> [25663.968934] usbcore: registered new interface driver xpad
> [25663.969081] drivers/usb/input/xpad.c: driver for Xbox controllers
> v0.1.6
> [25665.123126] usb 3-1: usbfs: interface 0 claimed by snd-usb-audio while
> 'tuxd' sets config #1
>
> (I don't understand the last msg...)
>
> anita@beertje:~$ ps ax
> PID TTY STAT TIME COMMAND
> .....
> 16704 ? S<l 0:00 python
> /opt/tuxdroid/apps/tuxosl/tux_osl_daemon.py
>
> anita@beertje:~$ ps axxfwww
> PID TTY STAT TIME COMMAND
> .....
> 16704 ? S<l 0:00 python
> /opt/tuxdroid/apps/tuxosl/tux_osl_daemon.py
>
> (it seems something is really started!)
>
> anita@beertje:~$
A feedback? Nothing to say, except : perfect ;)
1. tuxsetup 2.x doesn't install on this Ubuntu Feisty PC
I still have some troubles to make an installer for Ubuntu < 8.04 :
- openJDK can't be found on the repositories. So, the dependancies list
must
be changed to install sun-java6-jre instead of the open version.
- libtuxdriver.so has been compiled with a too high version of libc6. We
need
to recompile it with a earlier version.
I'm working on it, so I hope I'll be able to release a new package for
Ubuntu
< 8.04 soon.
2. I don't understand the last msg...
(> [25665.123126] usb 3-1: usbfs: interface 0 claimed by snd-usb-audio
while
> 'tuxd' sets config #1)
The dongle is a composite device. When you plug it, the kernel will load
the
drivers, and the drivers will try to claims the interfaces.
What happens is that snd-usb-audio (the audio driver for USB sound
cards) tries
to claim the interface0 ("Audio Control" interface defined in the USB
descriptor)
while the daemon try to set the configuration 1 (the active configuration
for this
USB device). This warning is due to this concurencial access. But that's
not very
important.
3. it seems something is really started!
Indeed, tuxosl has been started. It means you can use the TTS engine.
You also
can verify the other daemon (tuxd). Usually, I use the command `ps -ef
|grep XXX`
to find an XXX process. For example, to find all the process running for
Tux, I
use `ps -ef |grep tux`. If you use this command, you should see "tuxd".
But I see you're using an HID dongle. Maybe it will be incompatible with
the
actual tuxsetup, which is made to work with libusb. If tuxd won't start
(you can
try to launched it with "tuxd -debug", and see what happens), you can
compile the
last version from SVN :
http://svn.tuxisalive.com/software_suite_v1/daemon/trunk.
(build-essentials and libusb-dev are required to compile the daemon).
Monday I will create a final version of tuxsetup1.3. I'll also try to
fix the
problems with Ubuntu < 8.04.
ks156
|
