after synology DSM 4.3 update, I can't use CUL any more.

[amigob]

Hi All
I realy don't know what is going on I update my NAS DS411 to 4.3 and
TRXcom and the CUL didn't work any more
I got the TRXcom to work again, by creating /dev/usb/ttyUSB0
In the past this was in the /dev directory.

but what ever I do I can't get the CUL to work
if I do dmesg I get the following after reboot
[  157.140000] usbcore: registered new interface driver usbserial
[  157.200000] USB Serial support registered for generic
[  157.200000] usbcore: registered new interface driver usbserial_generic
[  157.210000] usbserial: USB Serial Driver core
[  157.340000] USB Serial support registered for FTDI USB Serial Device
[  157.400000] usbcore: registered new interface driver ftdi_sio
[  157.400000] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
[  157.490000] usbcore: registered new interface driver cdc_acm
[  157.500000] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[  157.560000] USB Serial support registered for pl2303
[  157.610000] usbcore: registered new interface driver pl2303
[  157.610000] pl2303: Prolific PL2303 USB to serial adaptor driver

so linux sees it but some how it doesn't attach it to ttyACM0 not in /dev or /dev/usb ( I disconected the TRXcom )

anybody any idea ?

Building now new usbserial.ko and ftdi_sio.ko, synology is now delivering these with DSM, so I don't think it will help.

Bart

[justme1968]

it depends on the model you have. the larger intel based models do include the drivers, the smaller arm based ones do not.

there is a german thread here: http://forum.fhem.de/index.php/topic,14324.0.html with step by step instructions here: http://forum.fhem.de/index.php/topic,14324.msg93685.html#msg93685 for the arm based systems.

for the intel based systems probalby only the device special files are not automaticaly created and you can just add the following lines to the fhem.sh directly after the echo "Starting fhem " line:

Code Auswählen Erweitern

                 /sbin/insmod /lib/modules/cdc-acm.ko
                 /sbin/insmod /lib/modules/usbserial.ko
                 /sbin/insmod /lib/modules/ftdi_sio.ko
                 mknod /dev/ttyACM0 c 166 0
                 mknod /dev/ttyACM1 c 166 1
                 mknod /dev/ttyUSB0 c 188 0
                 mknod /dev/ttyUSB1 c 188 1

  andre

[amigob]

Thanks

I used the USB driver version that where posed in the threat and it is working for me again.

I think I will have one problem and that is that at reboot it does not work any more sometime.
Both of the transceivers ar now ttyUSB devices, And I already read some where that it possible that the
CUL and he TRXcom will change the number. There was a solution for that, I need to find that again.

Bart,

[justme1968]

you can set up some udev rules to assign fixed usb device names based on the serial numbers of the devices. so this is independent of any changes in device ordering.

a simplified way that should also work if both devices respond fast enough during initialization is to plug both in and reboot. normally the devices should get their device names based on the order of the usb ports. this will not work of course if you plug them into different ports.

  andre

[amigob]

fund a good example for the udev definition
http://www.domoticaforum.eu/viewtopic.php?f=31&t=608

bart

[amigob]

Sitting now behind the computer and see that the synology NAS doesn't have /etc/rules

So the example is not going to work

Bart

[justme1968]

you are right. it looks like udev is not available on the synology diskstations.

the fallback would be to plug everyting in and reboot and then not to change ports and not add an external hub or other usb device.

  andre