tmsr - Search: pl2303

diana_coman: asciilifeform: at 3-19, argh, put in there the exact place of pl2303 in kernel, it was annoying enough to have to track it down once.

asciilifeform: ( the above is == to the 'Tip for Linux Users' item in http://nosuchlabs.com/hardware.html , which i listed as workaround for 'more than 3 pl2303' infamous bugola )

diana_coman: asciilifeform, I get as I recalled this "[63939.499700] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32" but I don't see the others, hmm

asciilifeform: [8621835.463377] pl2303 ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32

asciilifeform: btw, diana_coman , mircea_popescu , there's visible sys log barf from pl2303 when operating diana_coman's test :

asciilifeform: diana_coman: ftr i am still on the lookout for anything like a practicable replacement for pl2303

diana_coman: a bit of reading on this famous pl2303 does suggest all sorts of "hanging" issues but I haven't found anything clearly applicable so far

asciilifeform: http://btcbase.org/log/2018-07-31#1838486 << i've only ever observed pl2303-specific headache when 3+ operating ( and even then , consisted of slow, rather than halted, signal ) ☝︎

diana_coman: I would say it looks more and more like some issue with pl2303 mod

asciilifeform: ( asciilifeform did not write the linux i/o subsystem ; nor the pl2303 kernel mod ; and will readily admit that they are sad. and if anyone has idea for some other means to connect a 115200 baud box to machine, that does not suffer from the weakness of these, i'm as always all ears )

asciilifeform: BingoBoingo: before you go to swap cabling, let's first see if the known sadness of pl2303 driver is the culprit.

asciilifeform: BingoBoingo: interesting. these are both chinese pl2303 , nominally identical.

asciilifeform: ( btw if anybody discovers a viable replacement for the pl2303 snake that dun cost an arm and leg and dun include flashable chips, i'd like to hear about it )

asciilifeform: ( above 7, pl2303 driver starts doing something odd, the boxes still work but several times slower )

asciilifeform: i can describe some known dead ends. for instance, you definitely do not want to marry the thing to the pl2303. because 1) you have no way of knowing that every pl2303 on usb is an fg 2) not every fg user got a pl2303 , they get whatever cheapest chinese cable is at any given moment 3) for all i know, pl2303 will not be gettable next month, next yr etc

a111: Logged on 2017-11-10 10:14 diana_coman: for the curious there are in fact 2 prolific-stamped documents describing pl2303 and pl2303x; pl2303x seems to be a sort of upgrade to 64bits but why couldn't it be properly identified as distinct I don't know

diana_coman: for the curious there are in fact 2 prolific-stamped documents describing pl2303 and pl2303x; pl2303x seems to be a sort of upgrade to 64bits but why couldn't it be properly identified as distinct I don't know ☟︎☟︎

a111: Logged on 2017-11-10 00:58 asciilifeform: it's a pl2303 , ought to work ( though see diana_coman 's recent thread , on certain egregiously braindamaged linuxen there is a bug )

diana_coman: http://btcbase.org/log/2017-11-10#1735788 <- I don't really see how it is linux' fault here; so prolific used to make the pl2303 and old linux worked fine with it and still does; THEN they (or chinese cheap copies dunno) made a DIFFERENT thing pl2303x that has however the same serial id and everything so you can't distinguish between them before plugging them in pretty much; and so yes, old linux won't work because it sees it as pl2303 whe ☝︎

asciilifeform: it's a pl2303 , ought to work ( though see diana_coman 's recent thread , on certain egregiously braindamaged linuxen there is a bug ) ☟︎

diana_coman: asciilifeform, one can patch the kernel to work with both pl2303 AND pl2303x; but otherwise yes, obv is obv, either actual serial port or otherwise finding a combo that works

diana_coman: asciilifeform, well, for various definitions of resolve; I'm satisfied that problem was as identified i.e. pl2303x vs pl2303

a111: Logged on 2017-10-20 18:49 diana_coman: on the possibly enraging more digging turned out a known shit -difference between pl2303 and pl2303x

a111: Logged on 2017-10-20 17:44 asciilifeform: i picked pl2303 because it is the most afaik widely supported, but apparently not even it worx everywhere

asciilifeform: also i'm open to shipping something other than pl2303, if anyone has suggestions. ftdi is BANNED because 1) it costs 10x moar than pl2303 2) it is american/tw 3) it has rewritable fw that cannot be disabled

diana_coman: "the pl2303x can be distinguished from a pl2303 by checking bMaxPacketSize0 for device using lsusb -v -d 067b:2303; if bmaxpacketsize0 is 64 you probably have pl2303x"

diana_coman: but detected as pl2303,hence barfs

diana_coman: on the possibly enraging more digging turned out a known shit -difference between pl2303 and pl2303x ☟︎

asciilifeform: phf: i suspect this will do 0, in buggy pl2303 driver i encountered, it's the bandwidth and flowcontrol setttings that didn't take. but other than that adapter behaves normally

asciilifeform: i picked pl2303 because it is the most afaik widely supported, but apparently not even it worx everywhere ☟︎

diana_coman: hm, it sees it/reports it fine as far as I can tell; pl2303 attached to ttyUSB0; ehci_hcd

assbot: Amazon.com: NooElec PL2303 USB to Serial (TTL) Module/Adapter with Female and Male Wiring Harnesses & Test Jumper. Compatible with Windows 98 through Windows 7; Mac OS 8 through OS X, Linux and Android!: Computers & Accessories ... ( http://bit.ly/1Fcekbo )