[ KernelModules ] Kernel module USB drivers
Re: [ KernelModules ] Kernel module USB drivers
There is no release note
Re: [ KernelModules ] Kernel module USB drivers
{L_BUTTON_AT}outkastm
Something strange, bluetooth module is not loaded, but cdc_acm is loaded (I have reboot my TNAS after updating version and enabling all modules)
Code: Select all
[root@TNAS-xxx ~]# lsusb -vt
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 1: Dev 2, If 1, Class=, Driver=cdc_acm, 12M
|__ Port 1: Dev 2, If 0, Class=, Driver=cdc_acm, 12M
|__ Port 2: Dev 3, If 0, Class=, Driver=, 12M
|__ Port 2: Dev 3, If 1, Class=, Driver=, 12M
|__ Port 5: Dev 4, If 0, Class=, Driver=usb-storage, 480M
Code: Select all
btusb driver set to be loaded: reconnect device or reboot NAS
btbcm driver set to be loaded: reconnect device or reboot NAS
btintel driver set to be loaded: reconnect device or reboot NAS
btrtl driver set to be loaded: reconnect device or reboot NAS
usblp driver set to be loaded: reconnect device or reboot NAS
cdc-acm driver set to be loaded: reconnect device or reboot NAS
usbserial driver set to be loaded: reconnect device or reboot NAS
ch341 driver set to be loaded: reconnect device or reboot NAS
cp210x driver set to be loaded: reconnect device or reboot NAS
pl2303 driver set to be loaded: reconnect device or reboot NAS
ftdi_sio driver set to be loaded: reconnect device or reboot NAS
f81232 driver set to be loaded: reconnect device or reboot NAS
f81534 driver set to be loaded: reconnect device or reboot NAS
garmin_gps driver set to be loaded: reconnect device or reboot NAS
ipw driver set to be loaded: reconnect device or reboot NAS
ir-usb driver set to be loaded: reconnect device or reboot NAS
mxuport driver set to be loaded: reconnect device or reboot NAS
navman driver set to be loaded: reconnect device or reboot NAS
option driver set to be loaded: reconnect device or reboot NAS
oti6858 driver set to be loaded: reconnect device or reboot NAS
qcserial driver set to be loaded: reconnect device or reboot NAS
sierra driver set to be loaded: reconnect device or reboot NAS
spcp8x5 driver set to be loaded: reconnect device or reboot NAS
symbolserial driver set to be loaded: reconnect device or reboot NAS
ti_usb_3410_5052 driver set to be loaded: reconnect device or reboot NAS
usb_debug driver set to be loaded: reconnect device or reboot NAS
usb-serial-simple driver set to be loaded: reconnect device or reboot NAS
usb_wwan driver set to be loaded: reconnect device or reboot NAS
Re: [ KernelModules ] Kernel module USB drivers
sorry i have no bluetooth dongle to test further.
Re: [ KernelModules ] Kernel module USB drivers
{L_BUTTON_AT}outkastm
Mb I can test it?
Re: [ KernelModules ] Kernel module USB drivers
Hi again,
When using the updated kernelmodules no "connection" with the device is possible. Is there anything I'm dong wrong?
Greets
When using the updated kernelmodules no "connection" with the device is possible. Is there anything I'm dong wrong?
Greets
Code: Select all
Bus 001 Device 018: ID 0403:6001
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403
idProduct 0x6001
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 FT232R USB UART
iSerial 3 AC2EZ4E0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255
bInterfaceSubClass 255
bInterfaceProtocol 255
iInterface 2 FT232R USB UART
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
Code: Select all
[remkofaes@TNAS-5DA3 ~]# ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 remkofaes remkofaes 13 May 4 17:17 usb-FTDI_FT232R_USB_UART_AC2EZ4E0-if00-port0 -> ../../ttyUSB0
[remkofaes@TNAS-5DA3 ~]# ls -l /dev/ttyUSB0
crw-rw---- 1 remkofaes dialout 188, 0 May 4 17:17 /dev/ttyUSB0
Re: [ KernelModules ] Kernel module USB drivers
the user which need to connect to FTDI adapter must be part of the dialout group.
As example for homeassistant user
restart the app or log out / log in
As example for homeassistant user
Code: Select all
usermod -a -G dialout homeassistant
Code: Select all
[user@TNAS-xxx ~]# cat /etc/group | grep dialout
dialout:x:18:homeassistant
Re: [ KernelModules ] Kernel module USB drivers
It’s working!!!! Thanks
Re: [ KernelModules ] Kernel module USB drivers
updated (fixed the bluetooth driver load)
Re: [ KernelModules ] Kernel module USB drivers
Hi! Now I see driver in lsusb
Code: Select all
# lsusb -vt
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 1: Dev 2, If 1, Class=, Driver=cdc_acm, 12M
|__ Port 1: Dev 2, If 0, Class=, Driver=cdc_acm, 12M
|__ Port 2: Dev 3, If 0, Class=, Driver=btusb, 12M
|__ Port 2: Dev 3, If 1, Class=, Driver=btusb, 12M
|__ Port 5: Dev 4, If 0, Class=, Driver=usb-storage, 480M