From owner-freebsd-mobile Thu May 6 9:54:30 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (castles530.castles.com [208.214.165.94]) by hub.freebsd.org (Postfix) with ESMTP id CFFC815001 for ; Thu, 6 May 1999 09:54:28 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA04287; Thu, 6 May 1999 09:53:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905061653.JAA04287@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kent Hauser Cc: mobile@freebsd.org Subject: Re: Bootmgr problem In-reply-to: Your message of "Thu, 06 May 1999 12:10:36 EDT." <199905061610.MAA03869@rtp.tfd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 May 1999 09:53:11 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I've got a new ThinkPad 600E (which is great with FreeBSD 3.1) *except* > that it appears that the bootmgr somehow queries the bios and disables > my com port. I put a serial datascope on the thing & once I've enabled > the serial port via the config mgr in W98, the port stays on thru the POST > & is disabled as soon as the F1=DOS/F2=FreeBSD prompt appears. > > Is there anyway to make the bootmgr just prompt the keyboard/screen & > leave the serial ports alone? It doesn't touch them; your BIOS is doing it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message