[Bug 1007652] New: FTDI adapter does not show up as ttyUSB
http://bugzilla.suse.com/show_bug.cgi?id=1007652 Bug ID: 1007652 Summary: FTDI adapter does not show up as ttyUSB Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: mbrugger@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When plugging in the FTDI adpater, it get's registered as ttyUSB but shortly afterwards it gets deregistered and reregistered as input device: udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[4096.004758] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) KERNEL[4096.007131] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4096.007175] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4096.007883] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4096.526145] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) UDEV [4096.531416] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4096.532623] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4096.538064] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4096.668041] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4096.668075] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4096.670253] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4096.671010] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4100.679481] add /devices/virtual/input/input38 (input) KERNEL[4100.679612] add /devices/virtual/input/input38/event20 (input) UDEV [4100.681392] add /devices/virtual/input/input38 (input) UDEV [4100.714831] add /devices/virtual/input/input38/event20 (input) lsusb Bus 001 Device 018: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC dmesg [ 4330.254760] usb 1-1.2: new full-speed USB device number 19 using ehci-pci [ 4330.371475] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001 [ 4330.371480] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4330.371484] usb 1-1.2: Product: FT232R USB UART [ 4330.371486] usb 1-1.2: Manufacturer: FTDI [ 4330.371488] usb 1-1.2: SerialNumber: A50285BI [ 4330.374746] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [ 4330.374826] usb 1-1.2: Detected FT232RL [ 4330.375406] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 4331.045927] usb 1-1.2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 [ 4331.046819] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 4331.046845] ftdi_sio 1-1.2:1.0: device disconnected -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c1
Matthias Brugger
When plugging in the FTDI adpater, it get's registered as ttyUSB but shortly afterwards it gets deregistered and reregistered as input device:
I forgot some dmesg lines
dmesg [ 4330.254760] usb 1-1.2: new full-speed USB device number 19 using ehci-pci [ 4330.371475] usb 1-1.2: New USB device found, idVendor=0403, idProduct=6001 [ 4330.371480] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4330.371484] usb 1-1.2: Product: FT232R USB UART [ 4330.371486] usb 1-1.2: Manufacturer: FTDI [ 4330.371488] usb 1-1.2: SerialNumber: A50285BI [ 4330.374746] ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected [ 4330.374826] usb 1-1.2: Detected FT232RL [ 4330.375406] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 [ 4331.045927] usb 1-1.2: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1 [ 4331.046819] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 4331.046845] ftdi_sio 1-1.2:1.0: device disconnected
[ 4337.270583] usb 1-1.2: usbfs: USBDEVFS_CONTROL failed cmd brltty rqt 128 rq 6 len 255 ret -110 [ 4340.012348] input: BRLTTY 5.4 Linux Screen Driver Keyboard as /devices/virtual/input/input39 [ 4378.329466] usb 1-1.2: usbfs: USBDEVFS_CONTROL failed cmd brltty rqt 128 rq 6 len 255 ret -110 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c2
--- Comment #2 from Matthias Brugger
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c3
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c4
John Whitmore
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c5
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c6
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c7
--- Comment #7 from Matthias Brugger
Michael,
it looks like the udev rules introduced with the update of brltty to version 5.3.1 broke some USB to RS232 converters by being to unspecific. Do you have a braille device of this kind so we can get better distinction?
From what I can see, it uses the FTDI converter as it's generic driver. It's not clear to me why. There shouldn't be a braille device which uses this ID to identify itself.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c8
Michael Gorse
Michael,
it looks like the udev rules introduced with the update of brltty to version 5.3.1 broke some USB to RS232 converters by being to unspecific. Do you have a braille device of this kind so we can get better distinction?
My display is a Baum (0403:fe72). There was a recent thread on the brltty list about this issue: http://mielke.cc/pipermail/brltty/2016-October/014365.html I don't see a good solution; apparently some of the Braille displays just have their manufacturer set to "FTDI". Maybe we should just comment out that line in the udev rules and add a README.SUSE to document this. Let me know if you'd like me to do that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c9
--- Comment #9 from Matthias Brugger
(In reply to Oliver Neukum from comment #6)
Michael,
it looks like the udev rules introduced with the update of brltty to version 5.3.1 broke some USB to RS232 converters by being to unspecific. Do you have a braille device of this kind so we can get better distinction?
My display is a Baum (0403:fe72). There was a recent thread on the brltty list about this issue: http://mielke.cc/pipermail/brltty/2016-October/014365.html
I don't see a good solution; apparently some of the Braille displays just have their manufacturer set to "FTDI".
Maybe we should just comment out that line in the udev rules and add a README.SUSE to document this. Let me know if you'd like me to do that.
Packages argyllcms does have lines with excactly the same Vendor:Product ids commented, so I think this is a reasonable approach. Thanks for looking/fixing this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c10
Oliver Neukum
(In reply to Michael Gorse from comment #8) http://mielke.cc/pipermail/brltty/2016-October/014365.html
I don't see a good solution; apparently some of the Braille displays just have their manufacturer set to "FTDI".
Maybe we should just comment out that line in the udev rules and add a README.SUSE to document this. Let me know if you'd like me to do that.
Packages argyllcms does have lines with excactly the same Vendor:Product ids commented, so I think this is a reasonable approach.
I am afraid it is not so clear. We'd push out an update that would break the console for some users. Is brltty installed by default in any product? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c14
Michael Gorse
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c15
--- Comment #15 from Oliver Neukum
It gets installed if the GNOME desktop is installed at least. It is needed there for orca to be able to interact with a Braille display.
Do we have a way to generate a message to be displayed if brltty is being updated? If so, then that might help to warn users who might have one of the affected Braille displays.
That is no good. If the package is installed by default we'd mess up the next update for the vast majority of users who don't even know what brltty is. We'd have to know whether the device is actually connected. If we could do that, the point would become moot and we could probe in the udev rule. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c16
Michal Marek
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Michal Marek
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c22
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c23
--- Comment #23 from Michael Gorse
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c24
Matthias Brugger
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Stefan Behlert
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c25
Matthias Brugger
udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent
KERNEL[4621.088941] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) KERNEL[4621.097121] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4621.097774] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4621.099971] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4621.100050] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4621.100126] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4621.100187] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) UDEV [4621.654409] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) UDEV [4621.659146] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4621.662476] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4621.670044] add /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4621.671403] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4621.672138] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4621.673399] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2 (usb) KERNEL[4622.826940] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) KERNEL[4622.827016] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4622.827053] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) KERNEL[4622.827107] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4622.827175] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4622.830975] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0 (tty) UDEV [4622.833293] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4622.835044] remove /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0 (usb-serial) UDEV [4622.836645] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4622.839450] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4625.870706] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4625.874526] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4626.006916] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4626.011022] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4627.876296] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4627.880304] unbind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) KERNEL[4628.010895] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) UDEV [4628.014727] bind /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0 (usb) And so on until I unplug the device. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c27
Ruediger Oertel
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c28
Ruediger Oertel
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Ruediger Oertel
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c30
--- Comment #30 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c31
--- Comment #31 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c32
--- Comment #32 from Swamp Workflow Management
http://bugzilla.suse.com/show_bug.cgi?id=1007652
http://bugzilla.suse.com/show_bug.cgi?id=1007652#c33
--- Comment #33 from Swamp Workflow Management
participants (1)
-
bugzilla_noreply@novell.com