kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #185540
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc4-yakkety/
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1595656
Title:
modprobe ftdi_sio - nonfunctional for (some) devices
Status in linux package in Ubuntu:
Incomplete
Bug description:
$ cat /proc/version_signature
Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1
---
---
Some background:
I have recently acquired a Flashforge Creator Pro 2016, a FDM/FFF 3D-
printer that came with the [Open source "Sailfish" firmware][1].
Now to use the advanced features of the firmware you need to use
"[ReplicatorG][2]" (free software) and connect to the printer using
the provided USB-cable.
This relies on FTDI-based communications with it's ATMega 2560 -based controller board (Mightyboard 2560)
I can currently run Windows in a virtual machine (Virtualbox) and use ReplicatorG for the full set of features, including firmware updates (did that yesterday).
BUT, this is not possible using Ubuntu (14.04.4 and 16.04 installed
and used in attempts)
From what I can see I should use
<pre>
sudo modprobe ftdi-sio
sudo chmod 666 /sys/bus/usb-serial/drivers/ftdi_sio/new_id
sudo echo "23c1 d314" > /sys/bus/usb-serial/drivers/ftdi_sio/new_id
</pre>
... then simply connect the cable.
This DOES set up /dev/ttyUSB0 and /dev/ttyUSB1 as expected, but these
are nonfunctional
What I see is this, in dmesg
<pre>
[ 2832.712115] usb 1-7: USB disconnect, device number 10
[ 2832.712430] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 2832.712457] ftdi_sio 1-7:1.0: device disconnected
[ 2832.712775] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 2832.712815] ftdi_sio 1-7:1.1: device disconnected
[ 2840.832455] usb 1-7: new full-speed USB device number 11 using xhci_hcd
[ 2840.962313] usb 1-7: New USB device found, idVendor=23c1, idProduct=d314
[ 2840.962317] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=220
[ 2840.962319] usb 1-7: Product: The Replicator
[ 2840.962321] usb 1-7: Manufacturer: MakerBot Industries
[ 2840.962322] usb 1-7: SerialNumber: XXXXXXXXXXXXXXXXXXXX
[ 2840.962443] usb 1-7: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes
[ 2840.962871] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected
[ 2840.962898] usb 1-7: Detected FT2232C
[ 2840.962984] ftdi_sio ttyUSB0: Unable to read latency timer: -32
[ 2840.963048] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2840.963119] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0
[ 2840.963188] ftdi_sio 1-7:1.1: FTDI USB Serial Device converter detected
[ 2840.963210] usb 1-7: Detected FT2232C
[ 2840.963273] ftdi_sio ttyUSB1: Unable to read latency timer: -32
[ 2840.963365] ftdi_sio ttyUSB1: Unable to write latency timer: -32
[ 2840.963423] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB1
[ 2840.977742] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2840.977838] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2840.977932] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2840.978117] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2840.978207] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2840.978301] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2840.978393] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb
[ 2840.978581] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2840.978914] ftdi_sio ttyUSB1: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2840.979006] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate
[ 2840.979099] ftdi_sio ttyUSB1: urb failed to clear flow control
[ 2840.979274] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate
[ 2840.979372] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control
[ 2840.979470] ftdi_sio ttyUSB1: Unable to write latency timer: -32
[ 2840.979568] ftdi_sio ttyUSB1: ftdi_set_termios error from disable flowcontrol urb
[ 2840.979763] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control
[ 2841.078912] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.079142] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.079309] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.079437] ftdi_sio ttyUSB0: failed to get modem status: -32
[ 2841.079697] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2841.079761] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.079858] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.080070] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.080176] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.080279] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb
[ 2841.080471] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.080571] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate
[ 2841.080768] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control
[ 2841.180973] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.181177] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.181379] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.181500] ftdi_sio ttyUSB0: failed to get modem status: -32
[ 2841.181798] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2841.181952] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.182050] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.182244] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.182341] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.182440] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb
[ 2841.182634] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.282904] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.283102] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.283262] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.283385] ftdi_sio ttyUSB0: failed to get modem status: -32
[ 2841.283691] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2841.283856] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.283953] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.284150] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.284244] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.284342] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb
[ 2841.284535] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.384745] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.384976] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.385333] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.385495] ftdi_sio ttyUSB0: failed to get modem status: -32
[ 2841.386017] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[ 2841.386111] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.386208] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.386401] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.386498] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.386607] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb
[ 2841.386827] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.487043] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[ 2841.487240] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control
[ 2841.487561] ftdi_sio ttyUSB0: Unable to write latency timer: -32
[ 2841.487693] ftdi_sio ttyUSB0: failed to get modem status: -32
[ 2851.003248] ftdi_sio ttyUSB1: Unable to write latency timer: -32
</pre>
I also see
<pre>
$ ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 jun 23 19:13 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 jun 23 19:13 /dev/ttyUSB1
$ lsusb
...
Bus 001 Device 011: ID 23c1:d314
...
$ sudo modprobe -r ftdi_sio
[sudo] password for hannu:
$ lsusb -v -d 23c1:d314
Bus 001 Device 012: ID 23c1:d314
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x23c1
idProduct 0xd314
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 220
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 0
CDC Header:
bcdCDC 10.01
CDC ACM:
bmCapabilities 0x06
sends break
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
</pre>
Now, this failure seems to fairly general, in googling I have come
across a number of devices with very similar (if not the same) failure
on all of them.
So it seems to be some sort of shortcoming of the `ftdi_sio` module.
HELP!?
[1]: https://github.com/jetty840/Sailfish-MightyBoardFirmware
[2]: http://www.sailfishfirmware.com/doc/install-software-reqs.html#x33-820006.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1595656/+subscriptions
References
