[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460857
This is going to have to be fixed upstream before we can even consider
backporting the fix to current Ubuntu kernels.
** Changed in: linux
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because
the bug also occurs since kernel =2.6.32-25 (10.04x64 server). its not
possible to use a MCR8 via USB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460857
Title:
ftdi serial driver broken in
Error still ocurse @Kernel 2.6.37-11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460857
Title:
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
--
ubuntu-bugs mailing
Can anyone confirm that a manual Kernel update with the Kernel from
kernel.org works ?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460857
Title:
ftdi serial driver broken in
If you need more logfiles just say.
We will provide you with the needed stuff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/460857
Title:
ftdi serial driver broken in linux-image-2.6.31-14-generic
It's not broken on just ubuntu, it's broken everywhere. There is no
current maintainer of the FTDI driver. I started to look at it but it's
going to take several days of learning how the USB stack works before I
can even think of doing a fix.
--
You received this bug notification because you are
I have the same Problem with different Cardreaders.
Samrgo and also pcscd devices. They suddenly stop working.
Can anyone take care of that Bug ?! Its open since 2009-10-26
Greetings
Loki
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yes, please! This is such a common USB chip that I can't believe this
is still not working. I have several devices that I can't use unless I
plug them into my Windows machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing behavior like this too. I'm running the 32-bit version of 10.10 on
an Acer Aspire X3400, with kernel version:
2.6.35-23-generic #41-Ubuntu SMP
and an nVidia USB controller:
lspci | grep USB
00:02.0 USB Controller: nVidia Corporation MCP78S [GeForce 8200] OHCI USB 1.1
Controller (rev
Kendrick: negative, same hang for me. I think this has been broken for a
long time, but different timing in the newer kernels (2.6.28+) seems to
make it much much worse.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Changed in: linux
Status: New = Confirmed
** Tags added: 2.6.35.22
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification
I'm also seeing the regression reported by @richard (#42). In
particular, the software for the Syscomp CGR-101 isn't seeing the scope
on a 64 bit Ubuntu Maverick 10.10. Building the latest version of the
ftdio_sio driver from the 2.6.35-8 linux tree didn't fix the bug, but
porting the version
** Tags added: kj-triage
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Regression in 2.6.32-35. Exact same symptoms.
** Changed in: linux (Ubuntu)
Status: Fix Released = New
** Changed in: linux
Status: Invalid = New
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received
** Tags added: patch
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm running kernel 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57
UTC 2010 x86_64 and I'm still affected by the nearly the same problem.
Although I can get some data, after a few seconds of data I end up in
the same state and no data will pass. All subsequent close/open's on
/dev/ttyUSB0
** Changed in: linux (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug
Kernel 2.6.31-20.58 works for me also.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Today i have got a kernel update to 2.6.1.20 #58 and now all works
perfect.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I also can not connet to a FDTI device ( 232BM - Chip ) :
Error: Serial Port: Timeout waiting for data
/dev/ttyUSB0 is connected / disconnected every time i plug or unplug this device
Kernel: 2.6.31-19-generic #56-Ubuntu
The ftdifix from #8 does not help and does not change anything
lsmod |
My VLSystem MPlay Blast mini remote control doesn't work with kernel
2.6.31-17.54 without the patch in comment #13.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of
My Smargo Smartreader plus still does not work using kernel 2.6.31-17.54
and also not with the patch from #8. The problem seems to be related to
resetting. Maybe kernel 2.6.31-18 solves this problem (see comment #35),
but I haven't tried that yet.
Output from sasc-ng:
Jan 20 19:01:38.198
Hi Brad Campbell,
Since you are the original bug reporter, can you test and confirm this
is resolved with the most reset 2.6.31-17.54 update? The reason I say
this is because the 2.6.31-17.54 kernel was rebased with the 2.6.31.5
and 2.6.31.6 upstream stable kernel:
I'm also closing the upstream kernel bug watch. Thanks.
** Changed in: linux
Status: Confirmed = Invalid
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of
Can confirm problem does not exist in 2.6.31-17.54. Thanks.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The kernel in proposed ...-18 also seems to fix the DTR reset with the
Arduino, at least with the current avrdude software. I don't have to
hit the reset button!.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received
@David (#30)
Unfortunately it looks like the drivers on the ftdi site may not work
with newer versions of the kernel, including the kernel in karmic. The
ftdi_sio.h and .c I grabbed were from the linux kernel tree (version
2.6.31.8). A number of changes seem to have been made without
increasing
** Changed in: linux
Status: New = Confirmed
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of
** Tags added: 2.6.31.5
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Kendric (#17):
Although this compiled and installed, it didn't fix my problem. I
contacted FTDI directly, and the engineer there said that the latest
driver (v 1.5.0) should work fine with 64-bit Karmic. He sent me a link
to the driver source -
Not to rub anything in for those folks (@David) who seem to still be
having issues, but WHOO-HOO!!! the steps in post #7 @tz and #8 @Kendrick
worked for me. 64-bit UbuntuStudio and an Ardunio Mega. Dang... this
Linux learning curve busting my chops... one of these days maybe it will
all make
Go ahead and gloat - you deserve it! But when you're done, how about
being a good, upstanding Linux community member and post some of your
system specs so that I can compare them with mine? :^)
Specifically, what kernel are you running (uname -a) and what
processor? A copy of /var/log/messages
Certainly the driver in the vanilla kernel later than 2.6.31.4 works
fine on x86_64.
The Changelog for the latest proposed kernel seems to show the relevant
upgrade.
b...@srv:~$ cat /proc/cpuinfo | grep model
model : 2
model name : AMD Phenom(tm) 9750 Quad-Core Processor
snip
Hotfix from #7/#8 worked for me
$ uname -a
Linux miki-desktop 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:01:29 UTC 2009
i686 GNU/Linux
Using a Smargo Smartreader+.
Before the fix:
$ ./srp_tools_x86
no smartreader found
After the fix:
$ ./srp_tools_x86
smartreader+ version v1.3
MODE
Well, I spoke too soon. The USB0 device will come and go with
plugging/unplugging the Arduino, but only if you don't leave it plugged
in too long. I can do a fresh reboot, plug in the Arduino, and if I
leave it plugged in for more than about 4 or 5 minutes it will stick
again, along with the
Anyone have any updates to this problem? As my system stands now, I can
make /dev/ttyUSB0 appear by plugging in my Arduino (well, it's a
Seeduino, but it still uses the FTDI chip). If I then unplug it, the
system log shows the disconnect, but the /dev/ttyUSB0 device is still
there. Any attempt
if khubd is crashing, nothing else will change. Also check with lsof
to see if something grabs the /dev/ttyUSB0.
Also, which kernel? uname -a. I'm running the proposed and have no
trouble with arduinos or ftdi breakouts. (except RTS-reset, but that's
another bug).
--
ftdi serial driver
typing dmesg |grep khubd yields
[ 960.991399] INFO: task khubd:40 blocked for more than 120 seconds.
[ 960.991411] khubd D 040 2 0x
[ 1080.990369] INFO: task khubd:40 blocked for more than 120 seconds.
[ 1080.990381] khubd D
My error - you should do lsof -i | grep /dev/ttyUSB0 to see if anything
is holding.
If you add proposed, (in the system-admin-software sourcest) you can
get:
Linux tz-hpmini 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC
2009 i686 GNU/Linux
which works for me.
--
ftdi serial driver
I was a little hesitant to do that, because last time I did it my
computer wouldn't boot any more and I had to reinstall from scratch,
because of a bug in grub. But I went ahead and tried it anyway, and
sure enough it helped. When I plug and unplug the Arduino, /dev/ttyUSB0
comes and goes with
Actually I'm only using 32 bit. It should work in 64 though.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: linux
Importance: Undecided
Status: New
** Changed in: linux
Status: New = Incomplete
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member
WHY do people here change things to Incomplete but NEVER GIVE ANY CLUE
AS TO WHAT IS MISSING?
If it is Incomplete, it would help everyone if you would state what it
would take to make the report complete.
Are we all just supposed to guess and play question and answer games?
Or is there
It appears that anyone can change the status of a bug (including us).
Kalda and Peter both have 0 lauchpad karma - Peter has posted two bug
comments in the past two years and Kalda's account was created today.
Neither one includes a public email address, so we can't contact them
directly. Thus
I'm sorry! My new project bug report was added accidentally while I've been
working on two PCs simultaneously.
I can't find out how to remove it.
This bug still affects the newest ubuntu kernel.
After reboot with FTDI device connected nobody is able to use it.
I/O operations end with Device or
I'm running the kernel from proposed and it appears to have the fix:
uname -a
Linux tz-hpmini 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009
i686 GNU/Linux
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You
VLSystem MPlay Blast mini remote control stopped working with lirc after
upgrade to 9.10.
The receiver can be made to work if the device is first opened (and then
closed) in minicom before the lirc daemon is started.
I found out it's because minicom sets the RTS signal. I'm adding a patch to
Sorry some one here at my home has been playing with my computer. I did
not mean to change the status.
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs,
It sounds like both of the status changes from new to incomplete were
unintentional, so I've changed the status back to new.
** Changed in: linux
Status: Incomplete = New
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
ftdi serial driver broken in
@Kendrick Shaw (#8)
Does this work on 64-bit Karmic? Because I tried it before I though
about that. When I plugged in my Arduino and typed cat /dev/ttyUSB0,
it hung. Can't even kill the [cat] process with the kill command. Did
I screw up?
BTW, sudo apt-get install kernel-headers-generic
@David (#16)
Good catch - that should be sudo apt-get install linux-headers-generic
(I shouldn't have typed it from memory). Hopefully this will get the
patch to work for you. If you see an error during the first make,
however, there are still problems - please post the error and we'll see
if
Thanks, Kendrik. My linux headers were up to date, and the make went
without error. The make install had one error, but it was only rmmod
saying that the driver wasn't listed in /proc/modules. Otherwise the
patch seemed to go in ok. But it didn't fix all of my problems.
If I type ls
tz's makefile worked like a charm. For those who don't want to download
the linux kernel sources for two files, here are the two files and a
modified version of tz's makefile (with a 'make install' option added).
To install:
1) open a terminal window
2) install the latest kernel headers:
# sudo
The process described above in the post works, but is fairly complicated
and time consuming (downloading two kernel trees, doing a graft of some
files, etc.). It would be nice if the ko file was available.
Most arduino modules and development are affected by this.
Note that I can use socat
Makefile - (also attached).
make a new directory, then copy the two fixed files, ftdi_sio.* from the
good tree into this new directory, copy this Makefile to the new
directory, enter the new directory and type Make. You will have a .ko
in a few seconds.
cut here:
-8-8-
Who do I have to sleep with to even get someone to look at this bug
report?
--
ftdi serial driver broken in linux-image-2.6.31-14-generic (2.6.31-14.48)
https://bugs.launchpad.net/bugs/460857
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi
I'd just like to add that a very helpful person in the Ubuntu forum has
keyed in a process to compile the ftdi_sio kernel module. I followed it
and it worked a treat! Here's the link:
http://ubuntuforums.org/showthread.php?p=8364508posted=1#post8364508
--
ftdi serial driver broken in
I'd like to follow up lawrni's comment; I've got some idea of what
Robert did to get the one-off module working, but not enough Ubuntu
kernel mojo to know exactly how to proceed. In the meantime, the
ftdi_sio bug leaves me unable to use my IRTrans transceiver module -
this is something of a pain.
Hi,
I'm having this same issue too. I have some programs that can access
the FTDI device and others that cannot. Any chance you could give me a
few pointers as to how to compile the 'one-off' FTDI_sio module using
the 2.6.31.5 code for ftdi_sio. I have done:
1. Install Linux headers (
Plus one. I have a radio modem (TNC-X) that uses an FTDI USB/serial chip
for communications to a PC host. The device connects fine, kicks off
udev, and the module loads ok, but some applications (including the
intended app, Xastir) cannot read from the device under the current
Karmic kernel
62 matches
Mail list logo
