Followup to my original post, and to the replies.
I am now using kermit -- which works great (better than having to reconnect
with cu all the time).
I was able to get rid of the garbage (anytime output scrolled past the end
of the screen[24 lines]), by using a different terminal program. I was
using plain old xterm, I fired up Eterm - and it works without a hitch.
Also, I did re-compile and am now successfully connecting at 115200.
Bill
>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.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
