Page 1 of 1

ttyUSB dev not created in Ubuntu

Posted: Mon Feb 02, 2015 10:07 pm
by strips
Hi,

I have just started to test tellstick in Ubuntu 14.04 LTS (32 bit). Telldus-Core and center worked fine before trying OpenNetHome.

I am not getting ant ttyUSB devices. I followed the README-install only installing Oracle Java through PPA.

Did the udev fix

Code: Select all

cp ./drivers/linux/ftdi/98-nethome.rules /etc/udev/rules.d/
udevadm control --reload-rules
# cat /etc/udev/rules.d/98-nethome.rules

Code: Select all

# /etc/udev/rules.d/98-nethome.rules contains nethome udev rules
# ELV FHZ 1000 PC
SYSFS{idProduct}=="f06f", SYSFS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xf06f vendor=0x0403"
SUBSYSTEM=="usb",ATTRS{idProduct}=="f06f", ATTRS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xf06f vendor=0x0403"
SUBSYSTEM=="usbmisc",ATTRS{idProduct}=="f06f", ATTRS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xf06f vendor=0x0403"
# ELV FHZ 1300 PC
SYSFS{idProduct}=="e0e8", SYSFS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xe0e8 vendor=0x0403"
SUBSYSTEM=="usb",ATTRS{idProduct}=="e0e8", ATTRS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xe0e8 vendor=0x0403"
SUBSYSTEM=="usbmisc",ATTRS{idProduct}=="e0e8", ATTRS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio product=0xe0e8 vendor=0x0403"
# Tellstick
SYSFS{idProduct}=="0c31", SYSFS{idVendor}=="1781", RUN+="/sbin/modprobe -q ftdi_sio product=0x0c31 vendor=0x1781"
SUBSYSTEM=="usb",ATTRS{idProduct}=="0c31", ATTRS{idVendor}=="1781", RUN+="/sbin/modprobe -q ftdi_sio product=0x0c31 vendor=0x1781"
SUBSYSTEM=="usbmisc",ATTRS{idProduct}=="0c31", ATTRS{idVendor}=="1781", RUN+="/sbin/modprobe -q ftdi_sio product=0x0c31 vendor=0x1781"
# lsusb

Code: Select all

...
Bus 005 Device 004: ID 1781:0c31 Multiple Vendors Telldus TellStick Duo
...
# dmesg (when connecting tellstick)

Code: Select all

[ 4351.068239] usb 5-1: new full-speed USB device number 4 using uhci_hcd
[ 4351.266320] usb 5-1: New USB device found, idVendor=1781, idProduct=0c31
[ 4351.266336] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4351.266348] usb 5-1: Product: TellStick Duo
[ 4351.266357] usb 5-1: Manufacturer: Telldus
[ 4351.266366] usb 5-1: SerialNumber: A501WEFX
I have tried to reboot.

Re: ttyUSB dev not created in Ubuntu

Posted: Tue Feb 03, 2015 12:03 pm
by Nasty76
You need remove complete all telldus software , if not telldus keep that ttyusb port open and nethome cant open that.
there is below some topic in Ubuntu server where is little problem. look that and if you use 32bit Ubuntu you need replace this file http://jlog.org/v4/linux/x86_64-unknown ... xSerial.so to this http://jlog.org/v4/linux/i686-pc-linux- ... xSerial.so
and look help that other topic. Ps. I realy recommend to use raspberry pi to run nethome , Rock solid solution to run nethome 24/7/365. if see pi crash probably people use bad power adapter which cant give enough Power to pi.

Re: ttyUSB dev not created in Ubuntu

Posted: Tue Feb 03, 2015 9:42 pm
by strips
Thanks. That might be it. Will uninstall telldus software. I'm using an old mini laptop as server. I will probably invest in a few RPi v2 soon.

Re: ttyUSB dev not created in Ubuntu

Posted: Sun Feb 15, 2015 11:55 am
by strips
I got the tty device and replaced the files you mentioned. I have read the other thread but now I'm trying to add a tellstick device but can only choose COM14. So I'm wondering if this is a permission problem or still using the wrong drivers.

Re: ttyUSB dev not created in Ubuntu

Posted: Sun Feb 15, 2015 12:28 pm
by strips
Wtf!

I'm sure I had the ttyUSB device last week but now it's gone. I have no idea where it went. I have done a apt-get dist-upgrade, reboot since last time. Maybe reinstalling Ubuntu server LTS?

I do not have any package with name telldus or tellstick installed anymore.

UPDATE:

I just did a new dist-upgrade and rebooted without tellstick connected. Connected it and looked for ttyUSB device but could not find one. I checked dmesg and I got the "usbserial: USB Serial support registered for FTDI USB Serial Device". Doing a new disconnect and connect this is the dmesg dump. You can see the forst connect, disconnect and reconnect. I did not get any FTDI-message the second time. At no stage I got any ttyUSB device.

[ 146.800265] usb 5-1: new full-speed USB device number 2 using uhci_hcd
[ 147.000321] usb 5-1: New USB device found, idVendor=1781, idProduct=0c31
[ 147.000337] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 147.000349] usb 5-1: Product: TellStick Duo
[ 147.000358] usb 5-1: Manufacturer: Telldus
[ 147.000367] usb 5-1: SerialNumber: A501WEFX
[ 147.085718] usbcore: registered new interface driver usbserial
[ 147.085761] usbcore: registered new interface driver usbserial_generic
[ 147.085795] usbserial: USB Serial support registered for generic
[ 147.133439] ftdi_sio: unknown parameter 'product' ignored
[ 147.133449] ftdi_sio: unknown parameter 'vendor' ignored
[ 147.133918] usbcore: registered new interface driver ftdi_sio
[ 147.133972] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 196.816406] usb 5-1: USB disconnect, device number 2
[ 208.240266] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[ 208.437352] usb 5-1: New USB device found, idVendor=1781, idProduct=0c31
[ 208.437368] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 208.437379] usb 5-1: Product: TellStick Duo
[ 208.437389] usb 5-1: Manufacturer: Telldus
[ 208.437398] usb 5-1: SerialNumber: A501WEFX

Re: ttyUSB dev not created in Ubuntu

Posted: Sun Feb 15, 2015 1:15 pm
by strips
Looks like those UDEV rules are deprecated from kernel 3.12.

Found this post:
https://bbs.archlinux.org/viewtopic.php?id=175499

this made my ttyUSB device:

Code: Select all

echo 1781 0c31 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
Now I'm working on reinstalling everything.

Re: ttyUSB dev not created in Ubuntu

Posted: Sun Feb 15, 2015 3:56 pm
by Nasty76
uh yeah Linux is sometimes weird you get something to work and after apt-get upgrade-dist broke something :D. example onewire system was messed in new raspberry pi image.