But I wonder if there would be anyone technically inclined enough.......
I have a CH340 USB relais. This is run using the usbserial.ko and
ch341.ko device drivers.
On Ubuntu 16.04 this device is recognised instantly and works.
But on an older 2.6.32 system (NAS) I can load the modules just fine...
But the device is not given a /dev/ttyUSB# device.
When I search for the device in /sys based on its usb number that I get
And cat all the files there, it turns out to register something under
Normally USB serial devices go under 188, X.
Now I know that 188 means "ttyUSB" and 189 means "usb_device" so that's
not much help.
[106717.320000] usb 1-1.2: new full speed USB device using orion-ehci
and address 5
[106717.430000] Got empty serial number. Generate serial number from
[106717.430000] usb 1-1.2: configuration #1 chosen from 1 choice
How do I go about troubleshooting why it does not hook onto the CH341
[101405.540000] usbcore: registered new interface driver usbserial
[101405.550000] usbserial: USB Serial Driver core
[101410.490000] USB Serial support registered for ch341-uart
[101410.540000] usbcore: registered new interface driver ch341
[ 19.922291] usbcore: registered new interface driver usbserial
[ 19.998511] usbcore: registered new interface driver ch341
[ 19.998526] usbserial: USB Serial support registered for ch341-uart
[ 19.998547] ch341 3-1.1:1.0: ch341-uart converter detected
[ 20.012994] usb 3-1.1: ch341-uart converter now attached to ttyUSB0
So my driver on the other machine does not detect the ch341-uart
attached to the USB port, while the USB device itself is recognised...