From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 15 10:03:10 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69FBB1065675 for ; Thu, 15 Apr 2010 10:03:10 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.freebsd.org (Postfix) with ESMTP id 2D5CD8FC1D for ; Thu, 15 Apr 2010 10:03:09 +0000 (UTC) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.3/8.14.3) with ESMTP id o3FA3886074754; Thu, 15 Apr 2010 06:03:08 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201004151003.o3FA3886074754@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 15 Apr 2010 06:03:10 -0400 To: perryh@pluto.rain.com From: Mike Tancsa In-Reply-To: <4bc6905e.9tkYBdShtBRdGu5Q%perryh@pluto.rain.com> References: <201004141357.o3EDvuxt067902@lava.sentex.ca> <4bc6905e.9tkYBdShtBRdGu5Q%perryh@pluto.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: disabling all serial input / output at boot time X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2010 10:03:10 -0000 At 12:04 AM 4/15/2010, perryh@pluto.rain.com wrote: >Mike Tancsa 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. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike