On Mon, Apr 06, 2020 at 09:51:15AM -0400, rhkra...@gmail.com wrote: > On Monday, April 06, 2020 03:50:59 AM to...@tuxteam.de wrote: > > Besides, a wrong baud rate would much less explain that writing is > > possible, but reading isn't. Not for classical "serials" (i.e. RS-232). > > From the OP: " On this system a serial port can only receive data and not > transmit." > > Wouldn't that mean that (from the perspective of a program running on the > OP's > computer) that the serial port can read but not write?
My recollection is the other way around: write but not read. But hey, I'm old and that. That (and the fact that another serial over USB showed the same symptoms) prompted me to (reluctantly) hint at permissions [1], since, to my knowledge, a honest serial port cannot be configured to different send and receive speeds. But this seems to be ruled out. Another possibility is, of course, the cable :-) Do we know in which way the port fails to read/write or whatever it fails at? Error messages? Cheers [1] this could be explained by a broken udev script setting the wrong permissions -- that would, e.g. cover the USB adapter case. It was such a nice model :-) -- t
signature.asc
Description: Digital signature
