From owner-freebsd-current Mon Mar 29 12:10:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id D0CC514C19 for ; Mon, 29 Mar 1999 12:10:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00525; Mon, 29 Mar 1999 12:03:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903292003.MAA00525@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tony Finch Cc: "Jan B. Koum " , current@freebsd.org Subject: Re: booting systems with lots of memory In-reply-to: Your message of "Mon, 29 Mar 1999 18:18:47 +0100." <14079.46583.208347.306328@chiark.greenend.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 29 Mar 1999 12:03:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did, yes. Most of that is now in the loader(8) manual. I tried > changing /boot.config to contain "/boot/loader -h" which improved > matters. There's still some garbage but it's fine after ">> FreeBSD > BOOT @ 0x10000: 634/15360 k of memory, serial console". We suspect a > BIOS that's being too damn clever for its own good. That sounds about right. If your BIOS on the Intel box is set for a serial console, you could try poking it again to make sure that it's set for 9600 bps and that the various 'magic' options relating to remote health monitoring are all off. I'd fire the one here up to be more specific, but it trips the breaker on this row of offices... -- \\ 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-current" in the body of the message