[karmic] usbserial regression with MessPC Environment Sensors

Bug #474180 reported by Karsten Suehring
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm using a MessPC Environment Sensor which connects via USB emulating a serial device. The sensor data is sent as text to the serial port.

lsusb reports the device as

Bus 005 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

On karmic the usbserial and ftdi_sio seem to load without problems, but I cannot read any input from the serial port.

dmesg output when connecting:

[ 638.040267] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 638.040285] ftdi_sio 5-1:1.0: device disconnected
[ 642.610015] usb 5-1: new full speed USB device using uhci_hcd and address 3
[ 642.813044] usb 5-1: configuration #1 chosen from 1 choice
[ 642.819979] ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected
[ 642.820010] usb 5-1: Detected FT232RL
[ 642.820014] usb 5-1: Number of endpoints 2
[ 642.820021] usb 5-1: Endpoint 1 MaxPacketSize 64
[ 642.820023] usb 5-1: Endpoint 2 MaxPacketSize 64
[ 642.820025] usb 5-1: Setting MaxPacketSize 64
[ 642.821008] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0

I don't get any error messages. The devide /dev/ttyUSB0 can be opened and speed and other parameters can be configured. It only remains silent when trying to read the data.

The devices works fine on jaunty.

I only found a description of the device in German at:
http://www.messpc.de/sensor_alphanumerisch.php

Revision history for this message
Karsten Suehring (suehring) wrote :
Revision history for this message
Karsten Suehring (suehring) wrote :
Revision history for this message
Karsten Suehring (suehring) wrote :
Revision history for this message
Karsten Suehring (suehring) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Karsten Suehring (suehring) wrote :

It seems the problem is more related to the ftdi_sio module than to usbserial. A colleague told be, that he is able to communicate on karmic over a serial line using a USB-serial converter with a different chipset.

Revision history for this message
Karsten Suehring (suehring) wrote :

I just downloaded a vanilla 2.6.31.6 kernel from kernel.org and verified that the device works with that version.

Revision history for this message
Thiago Teixeira (tvst) wrote :

I'm having the same problems using two different USB serial devices that used to work fine on 9.04.

What is even stranger is that minicom can read them but other programs cannot.

Revision history for this message
Brad Campbell (brad-wasp) wrote :
Revision history for this message
Thiago Teixeira (tvst) wrote :

I'm not sure if that is the same problem I experience. In my case, setting O_NONBLOCK does not help. Either way, a kernel update would be nice. At least in the "proposed" repo.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.