<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/ftdi-usb-sio/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 29 Sep 2015 19:14:04 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ftdi-usb-sio/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Won't load for 0403:6007 device</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;For unknown to me reasons the module is not loading automatically for 0403:6007 device.&lt;br/&gt;
Last year i had the same problem and back then someone helped me to devise this script that was solving the issue on per-session basis:&lt;/p&gt;
&lt;table class="codehilitetable"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td class="linenos"&gt;&lt;div class="linenodiv"&gt;&lt;pre&gt;1
2
3
4&lt;/pre&gt;&lt;/div&gt;&lt;/td&gt;&lt;td class="code"&gt;&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span class="c"&gt;#!/bin/sh&lt;/span&gt;
modprobe -v -r ftdi-sio
modprobe -v ftdi-sio
&lt;span class="nb"&gt;echo &lt;/span&gt;&lt;span class="m"&gt;0403&lt;/span&gt; &lt;span class="m"&gt;6007&lt;/span&gt; &amp;gt; /sys/bus/usb-serial/drivers/ftdi_sio/new_id
&lt;/pre&gt;&lt;/div&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;

&lt;p&gt;Is there a chance this module could load with the mentioned above device and add /dev/ttyUSB0 node automatically?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">InnerBushman</dc:creator><pubDate>Tue, 29 Sep 2015 19:14:04 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc4e6a061e3ae87f24eb36a92cad209c22fd4422f</guid></item><item><title>Not working with 64 bit Linux</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Using the latest version of 64 bit Ubuntu Linux, (2.6.x), the driver does not generate a "/dev/ttyUSB0" device.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Laughton</dc:creator><pubDate>Thu, 20 Sep 2007 09:46:02 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netb89bd893b24654dfd63c8150ab399cb80a3ee222</guid></item><item><title>Random Crashes on 2.4.29</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I don't understand exactly, but ftdi_sio seems to be&lt;br /&gt;
the problem. There is an 8x USB to serial adapter&lt;br /&gt;
installed with 4 modems for hylafax, a connection to&lt;br /&gt;
the USV and a serial label printer. The oops occurs on&lt;br /&gt;
an irregular basis. Help appreciated.&lt;/p&gt;
&lt;p&gt;---------------------------------------&lt;br /&gt;
ksymoops 2.4.5 on i686 2.4.29-msi1.  Options used&lt;br /&gt;
-V (default)&lt;br /&gt;
-k /proc/ksyms (default)&lt;br /&gt;
-l /proc/modules (default)&lt;br /&gt;
-o /lib/modules/2.4.29-msi1/ (default)&lt;br /&gt;
-m /boot/System.map-2.4.29.nogood (specified)&lt;/p&gt;
&lt;p&gt;Unable to handle kernel paging request at virtual&lt;br /&gt;
addresss ffffffff&lt;br /&gt;
f8a3589d&lt;br /&gt;
*pde = 00000000&lt;br /&gt;
Oops: 0002&lt;br /&gt;
CPU:    0&lt;br /&gt;
EIP:    0010:[&amp;lt;f8a3589d&amp;gt;]    Not tainted&lt;br /&gt;
Using defaults from ksymoops -t elf32-i386 -a i386&lt;br /&gt;
EFLAGS: 00010256&lt;br /&gt;
eax: ffffffff   ebx: 00000002   ecx: f5942000   edx:&lt;br /&gt;
0000000d&lt;br /&gt;
esi: e162f000   edi: 00000000   ebp: f60d701c   esp:&lt;br /&gt;
c0379ee4&lt;br /&gt;
ds: 0018   es: 0018   ss: 0018&lt;br /&gt;
Process swapper (pid: 0, stackpage=c0379000)&lt;br /&gt;
Stack: 00000000 f593d580 00000000 f77ba480 00000040&lt;br /&gt;
f60d7000 00000000 f5942000&lt;br /&gt;
0093d580 f593fd80 f8a24982 f593d580 f6347188&lt;br /&gt;
f77ba480 00000002 00000000&lt;br /&gt;
00000000 00000000 f5942200 00000000 f8a24a61&lt;br /&gt;
f77ba480 f593d588 f621ec40&lt;br /&gt;
Call Trace:    [&amp;lt;f8a24982&amp;gt;] [&amp;lt;f8a24a61&amp;gt;] [&amp;lt;c010a041&amp;gt;]&lt;br /&gt;
[&amp;lt;c010a236&amp;gt;] [&amp;lt;c0106d60&amp;gt;]&lt;br /&gt;
[&amp;lt;c0106d60&amp;gt;] [&amp;lt;c0106d60&amp;gt;] [&amp;lt;c0106d60&amp;gt;] [&amp;lt;c0106d89&amp;gt;]&lt;br /&gt;
[&amp;lt;c0106df2&amp;gt;] [&amp;lt;c0105000&amp;gt;]&lt;br /&gt;
[&amp;lt;c010504f&amp;gt;]&lt;br /&gt;
&amp;lt;0&amp;gt;Kernel panic: Aiee, killing interrupt handler!&lt;br /&gt;
Warning (Oops_read): Code line not seen, dumping what&lt;br /&gt;
data is available&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;EIP; f8a3589d&lt;br /&gt;
&amp;lt;[ftdi_sio]ftdi_read_bulk_callback+361/438&amp;gt;   &amp;lt;=====&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;eax; ffffffff &amp;lt;END_OF_CODE+754d54c/????&amp;gt;&lt;br /&gt;
&amp;gt;&amp;gt;ecx; f5942000 &amp;lt;_end+35507244/385d6244&amp;gt;&lt;br /&gt;
&amp;gt;&amp;gt;esi; e162f000 &amp;lt;_end+211f4244/385d6244&amp;gt;&lt;br /&gt;
&amp;gt;&amp;gt;ebp; f60d701c &amp;lt;_end+35c9c260/385d6244&amp;gt;&lt;br /&gt;
&amp;gt;&amp;gt;esp; c0379ee4 &amp;lt;init_task_union+1ee4/2000&amp;gt;&lt;/p&gt;
&lt;p&gt;Trace; f8a24982 &amp;lt;[usb-uhci]process_urb+1e6/230&amp;gt;&lt;br /&gt;
Trace; f8a24a61 &amp;lt;[usb-uhci]uhci_interrupt+95/fc&amp;gt;&lt;br /&gt;
Trace; c010a041 &amp;lt;handle_IRQ_event+5d/88&amp;gt;&lt;br /&gt;
Trace; c010a236 &amp;lt;do_IRQ+a6/ec&amp;gt;&lt;br /&gt;
Trace; c0106d60 &amp;lt;default_idle+0/34&amp;gt;&lt;br /&gt;
Trace; c0106d60 &amp;lt;default_idle+0/34&amp;gt;&lt;br /&gt;
Trace; c0106d60 &amp;lt;default_idle+0/34&amp;gt;&lt;br /&gt;
Trace; c0106d60 &amp;lt;default_idle+0/34&amp;gt;&lt;br /&gt;
Trace; c0106d89 &amp;lt;default_idle+29/34&amp;gt;&lt;br /&gt;
Trace; c0106df2 &amp;lt;cpu_idle+3e/54&amp;gt;&lt;br /&gt;
Trace; c0105000 &amp;lt;_stext+0/0&amp;gt;&lt;br /&gt;
Trace; c010504f &amp;lt;rest_init+4f/50&amp;gt;&lt;/p&gt;
&lt;p&gt;1 warning issued.  Results may not be reliable.&lt;br /&gt;
---------------------------------------&lt;/p&gt;
&lt;p&gt;klaus&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Klaus Muth</dc:creator><pubDate>Mon, 21 Feb 2005 09:24:03 -0000</pubDate><guid isPermaLink="false">https://sourceforge.nete6768d2af00b3018f38951d777ce5ae39bcb352b</guid></item><item><title>FTDI doesn't work with statserial</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Kernel 2.4.18-27.8.0&lt;br /&gt;
FTDI_SIO version: stock&lt;br /&gt;
statserial version: 1.1-30 (redhat rpm)&lt;/p&gt;
&lt;p&gt;statserial /dev/ttyUSB0 just hangs but minicom seems to&lt;br /&gt;
work.&lt;br /&gt;
This has been observed on two different computers, one&lt;br /&gt;
a desktop&lt;br /&gt;
and one a laptop.&lt;br /&gt;
I am guessing this is due to some unsupported ioctls.&lt;/p&gt;
&lt;p&gt;statserial has a number of uses.   One is identifying&lt;br /&gt;
which port is which.  short pins 7 &amp;amp; 8 (9 pin) together&lt;br /&gt;
or connect/disconnect  a device which asserts CTS.   I&lt;br /&gt;
have four FTDI based byterunner serial adapters so you&lt;br /&gt;
can see why this can be just as important as figuring&lt;br /&gt;
out which port on the serial port on your motherboard&lt;br /&gt;
is which.   Even more so, because which USB port is&lt;br /&gt;
which can easily change.&lt;/p&gt;
&lt;p&gt;On my laptop, &lt;br /&gt;
echo "hello, world" &amp;gt;/dev/ttyUSB0&lt;br /&gt;
also produced an error, I think it was the "write&lt;br /&gt;
request of 0 bytes", &lt;br /&gt;
but I think it sent the characters ok.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Whitis</dc:creator><pubDate>Wed, 15 Dec 2004 07:27:17 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net27fb051e9b9796c35343ff620917eb64c2c78c20</guid></item><item><title>Random crashes with ftdi driver</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi. I'm getting random system crashes with the ftdi&lt;br /&gt;
driver.&lt;br /&gt;
It works for a few minutes (of sparatic data transfer)&lt;br /&gt;
and then crahses&lt;br /&gt;
the machine.&lt;/p&gt;
&lt;p&gt;It crashes because  urb-&amp;gt;dev is NULL in td_submit_urb&lt;br /&gt;
(usb-ohci.c).&lt;br /&gt;
I do not think the problem is in the ohci, or usbcore&lt;br /&gt;
parts of my USB stack&lt;br /&gt;
because all of my other USB devices work just fine.&lt;br /&gt;
I've tried&lt;br /&gt;
version 1.3.3, 1.3.2, and 1.2.1 and they all crash in&lt;br /&gt;
the same way.&lt;br /&gt;
Configuration: Dual athlon MPX, 512MB ram.&lt;/p&gt;
&lt;p&gt;PCI config&lt;br /&gt;
00:00.0 Host bridge: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-760 MP [IGD4-2P] System Controller (rev 11)&lt;br /&gt;
00:01.0 PCI bridge: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-760 MP [IGD4-2P] AGP Bridge&lt;br /&gt;
00:07.0 ISA bridge: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-768 [Opus] ISA (rev 05)&lt;br /&gt;
00:07.1 IDE interface: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-768 [Opus] IDE (rev 04)&lt;br /&gt;
00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-768&lt;br /&gt;
[Opus] ACPI (rev 03)&lt;br /&gt;
00:09.0 SCSI storage controller: Adaptec AHA-3960D /&lt;br /&gt;
AIC-7899A U160/m (rev 01)&lt;br /&gt;
00:09.1 SCSI storage controller: Adaptec AHA-3960D /&lt;br /&gt;
AIC-7899A U160/m (rev 01)&lt;br /&gt;
00:10.0 PCI bridge: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-768 [Opus] PCI (rev 05)&lt;br /&gt;
01:05.0 VGA compatible controller: Matrox Graphics,&lt;br /&gt;
Inc. MGA G550 AGP (rev 01)&lt;br /&gt;
02:00.0 USB Controller: Advanced Micro Devices [AMD]&lt;br /&gt;
AMD-768 [Opus] USB (rev 07)&lt;br /&gt;
02:04.0 Multimedia audio controller: IC Ensemble Inc&lt;br /&gt;
ICE1712 [Envy24] (rev 02)&lt;br /&gt;
02:05.0 VGA compatible controller: ATI Technologies Inc&lt;br /&gt;
Radeon VE QY&lt;br /&gt;
02:06.0 Class ff00: Sealevel Systems Inc: Unknown&lt;br /&gt;
device 8008 (rev 01)&lt;br /&gt;
02:07.0 Multimedia video controller: Brooktree&lt;br /&gt;
Corporation Bt848 Video Capture (rev 12)&lt;br /&gt;
02:08.0 Ethernet controller: 3Com Corporation&lt;br /&gt;
3c905C-TX/TX-M [Tornado] (rev 78)&lt;/p&gt;
&lt;p&gt;kernel: 2.4.21 with brk patch manually applied&lt;/p&gt;
&lt;p&gt;Modules loaded&lt;br /&gt;
ftdi_sio               15064   0  (unused)&lt;br /&gt;
usbserial              16764   0  [ftdi_sio]&lt;br /&gt;
usb-ohci               18600   0  (unused)&lt;br /&gt;
usbcore                57728   0  [ftdi_sio usbserial&lt;br /&gt;
usb-ohci]&lt;br /&gt;
snd-pcm-oss            36132   0  (unused)&lt;br /&gt;
snd-mixer-oss           9436   0  [snd-pcm-oss]&lt;br /&gt;
ice1712                32556   0  (unused)&lt;br /&gt;
snd-mpu401-uart         2880   0  [ice1712]&lt;br /&gt;
snd-ac97-codec         23780   0  [ice1712]&lt;br /&gt;
rawmidi                12768   0  [snd-mpu401-uart]&lt;br /&gt;
snd-seq-device          3680   0  [rawmidi]&lt;br /&gt;
snd-cs8427              3868   0  [ice1712]&lt;br /&gt;
snd-i2c                 2120   0  [ice1712 snd-cs8427]&lt;br /&gt;
snd-seq                40080   0  (unused)&lt;br /&gt;
snd-pcm                50336   0  [snd-pcm-oss ice1712]&lt;br /&gt;
snd-timer              10952   0  [snd-seq snd-pcm]&lt;br /&gt;
snd                    25420   0  [snd-pcm-oss&lt;br /&gt;
snd-mixer-oss ice1712 snd-mpu401-&lt;br /&gt;
uart snd-ac97-codec rawmidi snd-seq-device snd-cs8427&lt;br /&gt;
snd-i2c snd-seq snd-pcm sn&lt;br /&gt;
d-timer]&lt;br /&gt;
soundcore               3460   5  [snd]&lt;br /&gt;
i2c-dev                 3780   0  (unused)&lt;br /&gt;
i2c-proc                6192   0  (unused)&lt;br /&gt;
i2c-core               12324   0  [i2c-dev i2c-proc]&lt;br /&gt;
ipchains               41712  18&lt;br /&gt;
msdos                   4876   0  (unused)&lt;br /&gt;
fat                    30232   0  [msdos]&lt;br /&gt;
nfsd                   45544   1&lt;br /&gt;
nfs                    47316   0  (unused)&lt;br /&gt;
lockd                  37648   1  [nfsd nfs]&lt;br /&gt;
sunrpc                 64796   1  [nfsd nfs lockd]&lt;br /&gt;
sr_mod                 12304   0  (unused)&lt;br /&gt;
3c59x                  25872   1&lt;/p&gt;
&lt;p&gt;dstaff(at)ugcs.caltech.edu&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 06 Feb 2004 07:08:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2244e5ce201b66b7a6bf328c1ecd85dda759e642</guid></item><item><title>Problems w/ Crystalfontz USB LCDs</title><link>https://sourceforge.net/p/ftdi-usb-sio/bugs/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Here's the first SourceForge bug report for you.&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;Using the 1.2.1 driver with RH 8.0 and the 2.4.18&lt;br /&gt;
kernel.  I'm trying to connect to a CrystalFontz 632&lt;br /&gt;
USB LCD display.  This is basically their 16X2 serial&lt;br /&gt;
LCD display with the FT8U232AM used to provide a USB&lt;br /&gt;
interface.&lt;/p&gt;
&lt;p&gt;Using minicom, I'm able to connect to /dev/usb/ttyUSB0&lt;br /&gt;
at 19200 N81 and the text I type is echoed to the LCD.&lt;br /&gt;
The problem is that attempting to close the port (or&lt;br /&gt;
apparently change port parameters (lcd4linux gets as&lt;br /&gt;
far as clearing the screen)) results in the driver&lt;br /&gt;
hanging hard.  At this point, I can't kill the&lt;br /&gt;
controlling process and must reboot to clear the port.&lt;br /&gt;
Since the process can't be killed, this results in the&lt;br /&gt;
filesystem not being unmounted cleanly.  It makes for&lt;br /&gt;
an ugly cycle for trying to debug.&lt;/p&gt;
&lt;p&gt;As mentioned above, it should be a stock FT8U232AM&lt;br /&gt;
according to CrystalFontz support. They have used a&lt;br /&gt;
serial EEPROM to provide custom product IDs, so some&lt;br /&gt;
hacking was done to associate the product ID with the&lt;br /&gt;
FT8U232AM in the driver.  You may want to consider&lt;br /&gt;
adding product ID aliases in the driver that point back&lt;br /&gt;
to the FT8U232AM.  Here are the IDs for the products:&lt;/p&gt;
&lt;p&gt;0x0403:0xFC08 is a 632&lt;br /&gt;
0x0403:0xFC09 is a 634&lt;/p&gt;
&lt;p&gt;Please let me know what I can do as far as providing&lt;br /&gt;
you with any information you might need to resolve the&lt;br /&gt;
driver hang issue.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tom&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tom Webster</dc:creator><pubDate>Wed, 29 Jan 2003 19:38:49 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netec066b416dcdff6f1b88fa1786b8abe58bb0ea40</guid></item></channel></rss>