Ubuntu

FTDI USB to Serial device stopped working with Feisty

Asked by G Allen

I was successfully using an FTDI USB to Serial converter under Edgy with the Serial Port Terminal. The serial device was identified in the list of ports as "/dev/usb0" (or something very close to that). After upgrading to Feisty, the converter when attached causes periodic mouse cursor freeze (mouse is a PS2 port mouse) and is never recognized or "mounted." I have observed a number of posts in the forums about USB related problems that were introduced with Feisty and am wondering...1) if this problem is related and 2) if a workaround or solution has been identified. Again, it was working perfectly under Edgy.

More information on FTDI's device: http://www.ftdichip.com/

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Massimo Forti
Solved:
Last query:
Last reply:
Revision history for this message
Massimo Forti (slackwarelife) said : 		#1

Thanks for your question, when you put it in the serial bus which kind of messages you have in /var/log/messages or /var/log/syslog. You can open this file after you insert the converter and post the last lines.

thanks

Revision history for this message
G Allen (glablj-gmail) said : 		#2

Hello Massimo:

Thank you for responding. Here is a log of messages when the device is plugged in:

May 2 12:34:59 localhost kernel: [13537.596000] usb 1-1: new full speed USB device using ohci_hcd and address 2
May 2 12:34:59 localhost kernel: [13537.812000] usb 1-1: configuration #1 chosen from 1 choice
May 2 12:35:00 localhost kernel: [13538.812000] usbcore: registered new interface driver usbserial
May 2 12:35:00 localhost kernel: [13538.812000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
May 2 12:35:00 localhost kernel: [13538.816000] usbcore: registered new interface driver usbserial_generic
May 2 12:35:00 localhost kernel: [13538.816000] drivers/usb/serial/usb-serial.c: USB Serial Driver core
May 2 12:35:00 localhost kernel: [13538.824000] drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
May 2 12:35:00 localhost kernel: [13538.824000] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
May 2 12:35:00 localhost kernel: [13538.824000] drivers/usb/serial/ftdi_sio.c: Detected FT232BM
May 2 12:35:00 localhost kernel: [13538.824000] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
May 2 12:35:00 localhost kernel: [13538.824000] usbcore: registered new interface driver ftdi_sio
May 2 12:35:00 localhost kernel: [13538.824000] drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
May 2 12:35:00 localhost kernel: [13539.068000] usb 1-1: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1
May 2 12:35:00 localhost kernel: [13539.112000] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
May 2 12:35:00 localhost kernel: [13539.116000] ftdi_sio 1-1:1.0: device disconnected
May 2 12:35:08 localhost kernel: [13546.572000] usb 1-1: usbfs: process 3663 (brltty) did not claim interface 0 before use
May 2 12:35:08 localhost kernel: [13546.572000] usb 1-1: usbfs: process 3663 (brltty) did not claim interface 0 before use
May 2 12:35:13 localhost kernel: [13551.992000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use
May 2 12:35:13 localhost kernel: [13551.992000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use
May 2 12:35:19 localhost kernel: [13557.408000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use
May 2 12:35:19 localhost kernel: [13557.408000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use
May 2 12:35:26 localhost kernel: [13564.508000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use
May 2 12:35:26 localhost kernel: [13564.508000] usb 1-1: usbfs: process 14935 (brltty) did not claim interface 0 before use

Revision history for this message
Best Massimo Forti (slackwarelife) said : 		#3

Ok, in a shell do:

sudo apt-get remove brltty

let me know. Thanks

Revision history for this message
G Allen (glablj-gmail) said : 		#4

Thanks Massimo Forti, that solved my question.

Revision history for this message
Joachim Nilsson (troglobit) said : 		#5

Hi,

and thanks for the help! I had the exact same problem with my Feisty. It worked in Dapper and Edgy and stopped working due to brltty in Feisty.

Why did this happen, and who is this brl?

Revision history for this message
G Allen (glablj-gmail) said : 		#6

Hello:

I agree, Joachim, the Ubuntu community is by far the most helpful support community I know of. No offense to anyone in any other community or support forum, but the rapid response from Massimo Forti is one example of many in the Ubuntu community- part of a gigantic list of reasons why I now use Ubuntu instead of Windows in my work. The OS rocks and the support is just as excellent. If a problem comes up, there is more than likely a solution available in short order. I could not go back to Windows now...

Once again, thank you Massimo for such a timely solution!! :)