Hi, Fri, 12 Apr 2013, 9:43 +02:00 from Karsten Malcher <deb...@dct.mine.nu>: > Very strange. > As i have written i have an old mobile adapter with PL2303 H that's running > without no problem in Linux.
I suppose it's a genuine one :) > There are adapters with HL-340 chip (ID 1a86:7523), that are running without > problems in Linux too. It's not a PL-2303 clone, but a different device; ch341 kernel module is used for it. > > 2) Also, the pl2303 kernel module seems to have a debug option, maybe it > > can be of some help... > > Yes - in the time between i contacted Greg Kroah-Hartman from the kernel team. > He asks me the same question so i already have the results here. > Greg has no idea how to fix the problem because he has no such device. > > The most important thing is that there are no error messages. > There is no error message and sometimes some bytes are received after > connection. > But it must be possible to get it working as we can see with the windows > driver. > I think there must be only some little difference in the handling of received > data. > Sending of Data (TXD) is no problem. By the way, have you tried to do the simple loopback test? Just connect Rx & Tx pins together, try to send something and check what's received, e. g. with help of some terminal application. > I added the output of lsusb -v too I've compared your "lsusb -v" output for *HX adapter, and compared it with output for my (presumably genuine) *HX; no differences found, except the bus & device number :) Looks like you connect your problematic device directly, not using hub, so there should be no problem... I'm not sure if it's helpful, but you can also check if it works with older kernels (like one Debian Squeeze has) and newer kernels (e. g., from "experimental"). ---- Best wishes, Bob
