[SOLVED] uart ftdi adapter not attached

la7low · 2016-09-18 18:38:17

Hello,

I have a Digitus UART Adapter with FTDI chip. The problem I have is that it is not attached to any /dev/ttyS* or anywhere.
This is the only dmesg output I get upon plugging the device into my laptop's usb port:

usb 1-1: new full-speed USB device number 60 using xhci_hcd

Does anybody have any idea what should I do to make it attached?
Thanks in advance!

As I understand the driver should be in the kernel, still the uname -a:

Linux  4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016 x86_64 GNU/Linux

The lsusb -v:

Bus 001 Device 060: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 FTDI
  iProduct                2 FT232R USB UART
  iSerial                 3 AI04Q37Z
  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 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      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)

Last edited by la7low (2016-09-22 17:23:16)

ewaller · 2016-09-18 18:54:29

It should show up as /dev/ttyACM0

Connect the device then post the output of journalctl -b | tail -20

la7low · 2016-09-19 05:00:45

ewaller wrote:

It should show up as /dev/ttyACM0
Connect the device then post the output of journalctl -b | tail -20

Hello,

thanks, here is the output. So the system thinks it is a MTP device. Why?

Sep 19 06:45:30 lacopc NetworkManager[419]: <info>  [1474260330.1510] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 19 06:45:30 lacopc NetworkManager[419]: <info>  [1474260330.1510] policy: set 'plague 2' (wlp6s0) as default for IPv4 routing and DNS
Sep 19 06:45:30 lacopc NetworkManager[419]: <info>  [1474260330.1511] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Sep 19 06:45:30 lacopc dbus[413]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Sep 19 06:45:30 lacopc systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 19 06:45:30 lacopc dbus[413]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 19 06:45:30 lacopc systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 19 06:45:30 lacopc nm-dispatcher[25557]: req:1 'connectivity-change': new request (0 scripts)
Sep 19 06:45:30 lacopc nm-dispatcher[25557]: req:1 'connectivity-change': completed: no scripts
Sep 19 06:45:30 lacopc NetworkManager[419]: <info>  [1474260330.1830] device (wlp6s0): Activation: successful, device activated.
Sep 19 06:45:30 lacopc nm-dispatcher[25557]: req:2 'up' [wlp6s0]: new request (0 scripts)
Sep 19 06:45:30 lacopc nm-dispatcher[25557]: req:2 'up' [wlp6s0]: completed: no scripts
Sep 19 06:46:01 lacopc kernel: acer_wmi: Unknown function number - 6 - 1
Sep 19 06:46:01 lacopc root[25666]: ACPI group/action undefined: PNP0C14:01 / 000000bc
Sep 19 06:46:06 lacopc wpa_supplicant[513]: p2p-dev-wlp6s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Sep 19 06:49:14 lacopc kernel: usb 1-6: new full-speed USB device number 61 using xhci_hcd
Sep 19 06:49:14 lacopc mtp-probe[25752]: checking bus 1, device 61: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Sep 19 06:49:14 lacopc mtp-probe[25752]: bus: 1, device: 61 was not an MTP device
Sep 19 06:49:16 lacopc dbus[413]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 19 06:49:16 lacopc dbus[413]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.

I saw the avahi service also failed so I did 'sudo systemctl start avahi-daemon.service' but the problem persists:

Sep 19 06:58:23 lacopc systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Sep 19 06:58:23 lacopc sudo[26089]: pam_unix(sudo:session): session closed for user root
Sep 19 06:58:24 lacopc avahi-daemon[26092]: Server startup complete. Host name is lacopc.local. Local service cookie is 236622303.
Sep 19 06:58:39 lacopc kernel: usb 1-6: USB disconnect, device number 61
Sep 19 06:58:42 lacopc kernel: usb 1-6: new full-speed USB device number 62 using xhci_hcd
Sep 19 06:58:42 lacopc mtp-probe[26116]: checking bus 1, device 62: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Sep 19 06:58:42 lacopc mtp-probe[26116]: bus: 1, device: 62 was not an MTP device

Last edited by la7low (2016-09-19 05:02:12)

R00KIE · 2016-09-19 13:35:25

I have a few (fake/counterfeit) FT232RL and FT232BL based adapters and all of them attach to /dev/ttyUSB*.

dmesg:

usb 1-3.1: new full-speed USB device number 8 using xhci_hcd
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-3.1:1.0: FTDI USB Serial Device converter detected
usb 1-3.1: Detected FT232RL
usb 1-3.1: FTDI USB Serial Device converter now attached to ttyUSB0

lsusb:

Bus 001 Device 008: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 FTDI
  iProduct                2 FT232R USB UART
  iSerial                 3 A9KJ79D9
  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 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      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
Device Status:     0x0000
  (Bus Powered)

ewaller · 2016-09-19 14:23:12

Yeah, I have some devices that connect as /dev/tty/USBxx as well. It is not obvious when it calls them a serial device and when it declares them an "abstract control model" device
Regardless, the kernel jumps in right after the MTP check and adds a couple lines to the journal about registering the new device. Lines that are missing in la7low's logs.

la7low, just a shot in the dark, but run pacman -Q linux and verify that the version number is 4.7.2-1 (that which you said had been reported by uname -a )

la7low · 2016-09-19 20:11:00

ewaller wrote:

Yeah, I have some devices that connect as /dev/tty/USBxx as well. It is not obvious when it calls them a serial device and when it declares them an "abstract control model" device
Regardless, the kernel jumps in right after the MTP check and adds a couple lines to the journal about registering the new device. Lines that are missing in la7low's logs.

But how much should I wait? Those lines are really not coming.
Can I disable MTP for the device somehow?

Well, the kernel version is strange:
$ pacman -Q linux
linux 4.7.4-1
$ uname -a
Linux lacopc 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016 x86_64 GNU/Linux

ewaller · 2016-09-19 20:14:19

There is your problem. You have the 4.7.4 kernel installed, but you are running the 4.7.2 kernel. The running kernel cannot find the modules it needs.
As your system is running otherwise, I am guessing that you have updated the kernel without having rebooted yet. The other possibility is that you updated the kernel when your boot partition was not mounted on /boot.

la7low · 2016-09-20 16:22:03

ewaller wrote:

There is your problem. You have the 4.7.4 kernel installed, but you are running the 4.7.2 kernel. The running kernel cannot find the modules it needs.
As your system is running otherwise, I am guessing that you have updated the kernel without having rebooted yet. The other possibility is that you updated the kernel when your boot partition was not mounted on /boot.

Thanks, I just needed a restart. (I just dont like restarts,I use suspend a lot.)

ewaller · 2016-09-20 16:27:50

Cool. Don't forget to edit your first post to edit the thread title by prepending [SOLVED]

Arch Linux

#1 2016-09-18 18:38:17

[SOLVED] uart ftdi adapter not attached

#2 2016-09-18 18:54:29

Re: [SOLVED] uart ftdi adapter not attached

#3 2016-09-19 05:00:45

Re: [SOLVED] uart ftdi adapter not attached

#4 2016-09-19 13:35:25

Re: [SOLVED] uart ftdi adapter not attached

#5 2016-09-19 14:23:12

Re: [SOLVED] uart ftdi adapter not attached

#6 2016-09-19 20:11:00

Re: [SOLVED] uart ftdi adapter not attached

#7 2016-09-19 20:14:19

Re: [SOLVED] uart ftdi adapter not attached

#8 2016-09-20 16:22:03

Re: [SOLVED] uart ftdi adapter not attached

#9 2016-09-20 16:27:50

Re: [SOLVED] uart ftdi adapter not attached

Board footer