Quote from
us on January 4, 2019, 1:07 am
Has anyone had any luck using a USB serial device with USB passthrough to an LXC container?
I'm trying to use an XBee with my IoT automation server antlet, which presents itself over USB as an FT231X USB UART, but while the device shows up in the antlet per lsusb:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 003 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 005: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And dmesg:
[4539309.525523] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[4539309.699875] usb 3-2: New USB device found, idVendor=0403, idProduct=6015
[4539309.699877] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[4539309.699878] usb 3-2: Product: FT231X USB UART
[4539309.699879] usb 3-2: Manufacturer: FTDI
[4539309.699880] usb 3-2: SerialNumber: DN04Q23F
I don't get the expected /dev/ttyUSB0 device, nor can I create a working one manually with mknod.
Looking at the antsle itself, rather than within an antlet, I get similar results showing it from lsusb and dmesg, but there's no /dev/ttyUSB0 on it, either. Does that mean there's no kernel support for USB serial devices, and if so, presumably that means there's no way to get it in the LXC, either? (Apologies for trivial questions; I'm not as familiar with Linux as I might be.)
Thanks,
Alistair
Has anyone had any luck using a USB serial device with USB passthrough to an LXC container?
I'm trying to use an XBee with my IoT automation server antlet, which presents itself over USB as an FT231X USB UART, but while the device shows up in the antlet per lsusb:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 003 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 005: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And dmesg:
[4539309.525523] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[4539309.699875] usb 3-2: New USB device found, idVendor=0403, idProduct=6015
[4539309.699877] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[4539309.699878] usb 3-2: Product: FT231X USB UART
[4539309.699879] usb 3-2: Manufacturer: FTDI
[4539309.699880] usb 3-2: SerialNumber: DN04Q23F
I don't get the expected /dev/ttyUSB0 device, nor can I create a working one manually with mknod.
Looking at the antsle itself, rather than within an antlet, I get similar results showing it from lsusb and dmesg, but there's no /dev/ttyUSB0 on it, either. Does that mean there's no kernel support for USB serial devices, and if so, presumably that means there's no way to get it in the LXC, either? (Apologies for trivial questions; I'm not as familiar with Linux as I might be.)
Thanks,
Alistair