I am using this device on Fedora 9 (preview) 2.6.25-0.234.rc9 and by running
modprobe ftdi_sio product=0x0155 vendor=0x1b3d
I am able to get the /proc/bus/usb/devices file to show a registered driver
However, every time I try to access it (even using 'cat' on the command line) I get the error:
bash: /dev/ttyUSB0: Message too long
and in /var/log/messages:
ftdi_sio.c: ftdi_open - failed submitting read urb, error -90
There are no other USB devices connected.
Any ideas how to fix this?
LK202-25-USB - linux - "message too long" error
-
Ray
- Matrix Orbital
- Posts: 745
- Joined: Thu Dec 13, 2001 4:00 pm
- Location: Earth.... I think..
- Contact:
When have you ordered and recieved this unit? This is a known issue and can be easily corrected however I want to make sure new units shipping from the factory have the correct settings.
The reason you are having this issue is a faulty USB Descriptor, the windows drivers don't mind it and work fine, linux is a bit more picky.
To fix this issue you do need a windows computer however
1) Download mprog from the FTDI site.
2) Use Mprog to read the settings from the unit ,save them and then write 'm back to the unit.
The error will sort it self out during this process and after that linux will work fine with the unit.
The reason you are having this issue is a faulty USB Descriptor, the windows drivers don't mind it and work fine, linux is a bit more picky.
To fix this issue you do need a windows computer however
1) Download mprog from the FTDI site.
2) Use Mprog to read the settings from the unit ,save them and then write 'm back to the unit.
The error will sort it self out during this process and after that linux will work fine with the unit.
-
Ray
- Matrix Orbital
- Posts: 745
- Joined: Thu Dec 13, 2001 4:00 pm
- Location: Earth.... I think..
- Contact:
Distributers have units in stock for a reasonable ammount of time your unit must have been shipped to them before we corrected the problem. I verified that new units shipping from the factory are correct now (and have been for a while)
We also submitted a patch to the linux kernel that adds support for all current and future ftdi based products (so no more messing around with modprobe) that also included a work around for this issue for all units that could possibly be experiencing it. This fix is currently available in the 2.6.26-rc5 kernel.
Now about your unit, you can either use the mprog to fix the problem as described in a few posts above this one or use the bleeding edge 2.6.26-rc5 kernel (or newer when available) I strongly suggest to take the mprog route though since it actually fixes the problem and running an -rc kernel on a production system just feels very very very wrong
If you have any more problems/questions feel free to let me know!
We also submitted a patch to the linux kernel that adds support for all current and future ftdi based products (so no more messing around with modprobe) that also included a work around for this issue for all units that could possibly be experiencing it. This fix is currently available in the 2.6.26-rc5 kernel.
Now about your unit, you can either use the mprog to fix the problem as described in a few posts above this one or use the bleeding edge 2.6.26-rc5 kernel (or newer when available) I strongly suggest to take the mprog route though since it actually fixes the problem and running an -rc kernel on a production system just feels very very very wrong
If you have any more problems/questions feel free to let me know!