'cu' hangs up really easily. use 'kermit' (it's in ports) and the hangup problem will disappear. i tried to find an option to cu to modify its hangup behavior but to no avail.
your second problem sounds like it could be terminal sizing -- have you tried this with a default 80x24 window, set and exported TERM properly, etc? i was not able to get my console to work properly past 38400 baud; i am not sure why. 38400 has been just fine speed-wise for me, though, so i'm not that upset. :) (also see http://www.arctic.org/~aaron/tips/freebsd-serial-console) aaron On Tue, 22 Jun 1999 13:31:33 EDT, "Bill G." writes: >I got a serial console working on COM2, to which I have connected >another FreeBSD box. I connect with 'cu' fine, but I'm running into >a couple of problems which I haven't been able to find and answer >for. > >o When I connect, when the machine is first turned on, I get > disconnected twice during the boot up sequence (cu reports > Got hangup signal) -- looks like when the sio1 device is > probed, and also when getty runs. > >o 9600 was rather slow, so I changed it to 115200, which worked, > however I had a few problems with terminal display -- any > output that scrolls down past the bottom of the screen gets > 'garbled'. (IE, I run clear; ls -l / -- the first 23 lines > look ok then it gets messed up). Same results from console > mode of my client machine and from an xterm. I thought that > 115200 might be too fast, so I slowed it down to 38400, but > same trouble. I'm not sure if this occured at 9600. > >Any thoughts / ideas / suggestions would be appreciated. Thanks, To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
