Date: Wed, 22 Dec 1999 09:28:04 +1030 (CST) From: Justin Hawkins <justin@tardis.mx.com.au> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem Message-ID: <Pine.BSF.4.21.9912220923080.540-100000@tardis.mx.com.au> In-Reply-To: <3860003A.548F8343@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 22 Dec 1999, Daniel C. Sobral wrote: > I'd say this is an expected result, not a known problem. It is doing > exactly what it is being told to (gibberish). Junk in, junk out. :-) Sure. > > Is there enough room in there for some code, which checks for this? IE if > > the first line output to the serial device == the first input (some > > version string probably) then it just ignores it and does the default > > action? > > Just configure it correctly. Don't tell it to talk to a serial device > that will be sending it gibberish. Well that was what I was trying to do. Given the relatice complexity of setting up for a serial console on the second serial port (kernel recompile, boot loader(s) recompile, boot block install etc). There is a better than even chance it's going to take someone like me a couple of reboots to get it all working. When the (previously working) boot process inexplicably stops for no apparent reason (the reason being the boot loader has been confused by the modem) it's a little disconcerting. I understand it's not really a bug and perhaps is not worth the code effort. A note in the handbook might not go astray - I am sure a lot of people who need a COM2 console will have modem on COM1. Thanks for your time. - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.9912220923080.540-100000>