thanks for the input! i suspect it's the kernel; i don't see why cu would be at fault - it has been working fine for decades. my apologies for attaching a bug report to 'cu', but it's the only way to get attention to this...
anyway, i tried minicom. didn't work as a normal user, didn't work with sudo. fiddled with line settings, but alas... $ sudo minicom -b 115200 -t vt220 -D /dev/ttyS0 (cu starts, but apparently no connection; terminal is apparently a vt102) (the bar below says 'offline'; i need to set local echo manually if i want a display of my input) $ minicom -b 115200 -t vt220 -D /dev/ttyS0 (cu starts, but apparently no connection; terminal is apparently a vt102) (the bar below says 'offline'; i need to set local echo manually if i want a display of my input) one thing that comes to mind: the target host doesn't do utf8; can this be a problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094278 Title: cu doesn't connect properly to a serial console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/1094278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
