Date: Thu, 15 Apr 2010 17:59:18 +0100 From: Rui Paulo <rpaulo@gmail.com> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com, Mike Tancsa <mike@sentex.net> Subject: Re: disabling all serial input / output at boot time Message-ID: <7C872B09-2644-42FB-969F-4FFA26FE6417@gmail.com> In-Reply-To: <4BC73C56.4080105@elischer.org> References: <201004141357.o3EDvuxt067902@lava.sentex.ca> <4bc6905e.9tkYBdShtBRdGu5Q%perryh@pluto.rain.com> <201004151003.o3FA3886074754@lava.sentex.ca> <4BC73C56.4080105@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 Apr 2010, at 17:18, Julian Elischer wrote: > On 4/15/10 3:03 AM, Mike Tancsa wrote: >> At 12:04 AM 4/15/2010, perryh@pluto.rain.com wrote: >>> Mike Tancsa <mike@sentex.net> wrote: >>> >>> > I have an embedded device (Alix box) that is running RELENG_8 off >>> > a CF that is designed to monitor / control a serial sensor device. >>> > The sensor is quite chatty and is always outputing data at 115200. >>> > The problem is that this will interrupt the boot process. >>> >>> > I even tried to "fake" it out, but trying to make com2, the console >>> > in /boot/device.hints ... >>> > >>> > Is there any way to completely disable serial interaction and >>> > to truly make the bootup process quiet and non interactive ? >>> >>> More of a workaround than a fix, but does it work any better >>> if you connect the device to com2 instead of com1? >> >> >> Unfortunately there is only one serial port on the board we are using. > > yes but can the bios map it to be com2? If not, maybe there's some way to do this by changing the hints file. Regards, -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7C872B09-2644-42FB-969F-4FFA26FE6417>