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 9600 baud; rows 0; columns 0; line = 0; ... this works ... > 3. serial-getty@ttyUSB0.service disabled && picocom -b 115200 /dev/ttyUSB0 > > speed 115200 baud; rows 0; columns 0; line = 0; ... and this works as well?! I think before debugging a potential problem with the new flow control feature, it would be a good idea to first make sure the baud rate is configured correctly. Maybe agetty's baud rate selection is somehow influenced by the new flow control support? I don't see how it would, and maybe that's still a bug somehow, but I suspect that there is no flow control problem at all, but rather it's just a baud rate mismatch that prevents communication. Regards, Florian
