Enabling CH340/CH341 driver

[wisebear]

Several requests have already been made on the forum (Link 1 and Link 2) to add support for CH340 USB to TTL converter. I have already sent a request also to Limetech, but haven't received any feedback yet. Enabling the driver that should be present in the kernel, would allow the use of cheap arduino boards for home automation purposes. 

[Reynald]

Hello all,

 

@limetech

We are several users using Unraid with home automation or other hobbyist using arduinos. Me it will be to use a USB Watchdog, very usefull on an unRaid server when system hangout and you're not at home. I will do a writeup when got it working.

Please, may you include the driver in next kernel compile? Here is the official driver from ch340/ch341 chip manufacturer: http://www.wch.cn/downloads/CH341SER_LINUX_ZIP.html

Also, maybe modules are already available in kernel source also: http://manpages.ubuntu.com/manpages/xenial/man4/uchcom.4freebsd.html

 

Unfortunatly, IDK how to compile unraid kernel and documentation is outdated

[limetech]

On 3/1/2018 at 12:49 PM, wisebear said:

Several requests have already been made on the forum (Link 1 and Link 2) to add support for CH340 USB to TTL converter. I have already sent a request also to Limetech, but haven't received any feedback yet. Enabling the driver that should be present in the kernel, would allow the use of cheap arduino boards for home automation purposes. 

Added for Unraid 6.7

[wisebear]

On 12/23/2018 at 6:45 PM, limetech said:

Added for Unraid 6.7

Thank you very much! 

[goinsnoopin]

On 12/23/2018 at 12:45 PM, limetech said:

Added for Unraid 6.7

@limetech

 

I updated to 6.7 stable and am trying to get my usb to serial adapter working.  Here is a link to the CH340T adapter I am using https://www.amazon.com/gp/product/B00NKAJGZM/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

When I plug it in, I get the following in syslog...full diagnostics attached.  I did unplug and replug it a couple of times.

May 13 19:38:42 Tower kernel: usb 3-10: new full-speed USB device number 10 using xhci_hcd
May 13 19:38:42 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:38:43 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:38:43 Tower kernel: usb 3-10: device not accepting address 10, error -71
May 13 19:38:43 Tower kernel: usb 3-10: new full-speed USB device number 11 using xhci_hcd
May 13 19:38:43 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:38:43 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:38:44 Tower kernel: usb 3-10: device not accepting address 11, error -71
May 13 19:38:44 Tower kernel: usb usb3-port10: attempt power cycle
May 13 19:38:44 Tower kernel: usb 3-10: new full-speed USB device number 12 using xhci_hcd
May 13 19:38:44 Tower kernel: usblp 3-10:1.0: usblp0: USB Bidirectional printer dev 12 if 0 alt 0 proto 2 vid 0x1A86 pid 0x7584
May 13 19:38:44 Tower kernel: usbcore: registered new interface driver usblp
May 13 19:39:14 Tower kernel: usb 3-10: USB disconnect, device number 12
May 13 19:39:14 Tower kernel: usblp0: removed
May 13 19:39:23 Tower kernel: usb 3-10: new full-speed USB device number 13 using xhci_hcd
May 13 19:39:40 Tower kernel: usb 3-10: device descriptor read/64, error -110
May 13 19:39:40 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:39:40 Tower kernel: usb 3-10: Device not responding to setup address.
May 13 19:39:40 Tower kernel: usb 3-10: device not accepting address 13, error -71
May 13 19:40:03 Tower kernel: usb 3-10: new full-speed USB device number 15 using xhci_hcd
May 13 19:40:19 Tower kernel: usb 3-10: device descriptor read/64, error -110
May 13 19:40:34 Tower kernel: usb 3-10: device descriptor read/64, error -110
May 13 19:40:35 Tower kernel: usb 3-10: new full-speed USB device number 16 using xhci_hcd
May 13 19:40:50 Tower kernel: usb 3-10: device descriptor read/64, error -110

 

tower-diagnostics-20190515-1746.zip

[goinsnoopin]

@limetech

 

My issue is resolved.  I had the serial adapter plugged into a usb 3 port. When I moved the device to a usb 2.0 port everything started working as expected.  Unraid assigned it to /dev/ttyusb0 and all is well.

 

Dan

[limetech]

4 hours ago, goinsnoopin said:

@limetech

 

My issue is resolved.  I had the serial adapter plugged into a usb 3 port. When I moved the device to a usb 2.0 port everything started working as expected.  Unraid assigned it to /dev/ttyusb0 and all is well.

 

Dan

Thank you for the update!