Date: Mon, 4 Mar 2013 11:59:42 -0800 From: Doug Ambrisko <ambrisko@ambrisko.com> To: "Eggert, Lars" <lars@netapp.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Dimitry Andric <dim@freebsd.org> Subject: Re: serial console not accepting input? Message-ID: <20130304195942.GA56928@ambrisko.com> In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F65BC32@SACEXCMBX01-PRD.hq.netapp.com> References: <D4D47BCFFE5A004F95D707546AC0D7E91F656991@SACEXCMBX01-PRD.hq.netapp.com> <51000A18.1020001@FreeBSD.org> <D4D47BCFFE5A004F95D707546AC0D7E91F65BC32@SACEXCMBX01-PRD.hq.netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 24, 2013 at 01:23:50PM +0000, Eggert, Lars wrote:
| Hi,
|
| On Jan 23, 2013, at 17:04, Dimitry Andric <dim@freebsd.org> wrote:
| > CTS/RTS hardware flow control, maybe? E.g. add ":hw" to the default
| > settings in /etc/gettytab, or make a specific entry with an added ":hw"
| > setting.
|
| nope, I don't even get a login prompt if I do that.
|
| > If it is a physical serial console, you could also simply have a bad
| > cable. Try swapping it with working system. :)
|
| Spent the last few hours fiddling with the cabling and the various BIOS
| serial redirection options (it's a Dell 2950). My best guess is that
| the serial port on the box is physically broken.
Try to do a {Ctrl}D to see if works. We've seen that the TX on reset
hangs but input works fine. I'm not sure if we ran into this with
uart(4) but had a problem with sio(4).
Doug A.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130304195942.GA56928>