Date: Mon, 5 Dec 2005 14:04:30 -0800 From: Aaron Glenn <aaron.glenn@gmail.com> To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-sparc64@freebsd.org Subject: Re: serial ports on the Ultra 5 Message-ID: <18f601940512051404j3a0ca860o3868b15e0265f1be@mail.gmail.com> In-Reply-To: <20051205204518.GB55657@funkthat.com> References: <18f601940512051025g71b9fc29y4ae37eb3ce2629df@mail.gmail.com> <200512051354.06372.jhb@freebsd.org> <18f601940512051128i142fd714g22004d8452cff29a@mail.gmail.com> <20051205204518.GB55657@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/5/05, John-Mark Gurney <gurney_j@resnet.uoregon.edu> wrote: > > You won't get a login prompt from the getty running on the local > machine... as soon as you open up ttyu1 the getty will "get" out > of the way and stop doing work... The above usually happens when > the otherside doesn't have CD raised and you haven't set the clocal > flag on the port... if you use the cuau1 port, that usually ignores > CD, and you can start typing... the cuau devices do not and have not worked. always "device busy link down" > what do you have on the other side? are they back to back? or? Also, > I usually disable getty's when I'm debugging as it can usually cause > other issues, and then once I have the serial ports mostly working, then > I enable getty and see what breaks... I've got the FreeBSD machine connected via serial port B to the OpenBSD machine on serial port A. I disabled getty and now I'm able to exit cu with ~^D instead of having to kill the process.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18f601940512051404j3a0ca860o3868b15e0265f1be>