On Mon, Nov 26, 2018 at 02:29:53PM +0200, Jarkko Nikula wrote:
> On 11/24/18 7:32 PM, Florian Zumbiehl wrote:
> > Hi,
> >
> >> Requested baud setting looks odd to me. Maybe related to this
> >> --keep-baud flag in "/sbin/agetty -o -p -- \u --keep-baud
> >> 115200,38400,9600 ttyUSB0 vt220"?
That i
On 11/24/18 7:32 PM, Florian Zumbiehl wrote:
Hi,
Requested baud setting looks odd to me. Maybe related to this
--keep-baud flag in "/sbin/agetty -o -p -- \u --keep-baud
115200,38400,9600 ttyUSB0 vt220"?
Well, what is the baud rate of the other side? It seems a bit strange
that ...
115200.
Hi,
> Requested baud setting looks odd to me. Maybe related to this
> --keep-baud flag in "/sbin/agetty -o -p -- \u --keep-baud
> 115200,38400,9600 ttyUSB0 vt220"?
Well, what is the baud rate of the other side? It seems a bit strange
that ...
> 1. serial-getty@ttyUSB0.service disabled
>
> speed
On 11/23/18 10:21 AM, Johan Hovold wrote:
On Fri, Nov 23, 2018 at 04:19:49AM +0100, Florian Zumbiehl wrote:
Can you tell what the physical chip is labeled as, if anything?
First one is Aten UC-232A:
https://www.aten.com/global/en/products/usb-&-thunderbolt/usb-converters/uc232a/
and another i
On Fri, Nov 23, 2018 at 04:19:49AM +0100, Florian Zumbiehl wrote:
> Hi,
>
> > T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> > P: Vendor=0557 ProdID=2008 Rev=03.00
> > S: Manufacturer=Prolific Technology Inc.
>
Hi,
> T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=0557 ProdID=2008 Rev=03.00
> S: Manufacturer=Prolific Technology Inc.
> S: Product=USB-Serial Controller D
> C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
On 11/21/18 5:12 PM, Florian Zumbiehl wrote:
I have two pl2303 based adapters which behave the same:
ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]
ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
What is the output of usb-devices for those?
T: Bus=01 Lev=02
Hi,
> >Could you try what happens when you manually disable ixon on the port once
> >it's stuck?
> >
> Is this the right way to do it?
>
> # stty -ixon -F /dev/ttyUSB0
>
> If yes it doesn't change behavior. Neither ixon or [-]ixoff.
Seems about right--and I just checked, that immediately resume
Hi
On 11/21/18 2:06 PM, Florian Zumbiehl wrote:
Could you try what happens when you manually disable ixon on the port once
it's stuck?
Is this the right way to do it?
# stty -ixon -F /dev/ttyUSB0
If yes it doesn't change behavior. Neither ixon or [-]ixoff.
Does the IXON behavior differ fro
Hi,
> >And what if you disable the getty? Does the port work then?
> >
> systemctl disable serial-getty@ttyUSB0.service followed by reboot
> and I can see everything what systemd is outputting there as well as
> what is dumped to /dev/kmsg so it looks getty started by systemd
> changes or triggers
On 11/20/18 6:42 PM, Johan Hovold wrote:
On Tue, Nov 20, 2018 at 01:17:34PM +0200, Jarkko Nikula wrote:
Hi
I'm using PL2303 based USB serial adapter for the kernel and getty
serial console. I noticed getty console stopped working in v4.18 and
bisected this into commit 7041d9c3f01b ("USB: serial
On Tue, Nov 20, 2018 at 01:17:34PM +0200, Jarkko Nikula wrote:
> Hi
>
> I'm using PL2303 based USB serial adapter for the kernel and getty
> serial console. I noticed getty console stopped working in v4.18 and
> bisected this into commit 7041d9c3f01b ("USB: serial: pl2303: add
> support for tx
Hi
I'm using PL2303 based USB serial adapter for the kernel and getty
serial console. I noticed getty console stopped working in v4.18 and
bisected this into commit 7041d9c3f01b ("USB: serial: pl2303: add
support for tx xon/xoff flow control").
Serial console works up to somewhere after when
13 matches
Mail list logo
