From owner-freebsd-small Mon Nov 4 8:47:26 2002 Delivered-To: freebsd-small@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EA5637B401 for ; Mon, 4 Nov 2002 08:47:25 -0800 (PST) Received: from mail.cruzio.com (dsl3-63-249-66-221.cruzio.com [63.249.66.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3171E43E75 for ; Mon, 4 Nov 2002 08:47:24 -0800 (PST) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.11.3/8.11.3) id gA4HJiU00556; Mon, 4 Nov 2002 09:19:44 -0800 (PST) (envelope-from brucem) Date: Mon, 4 Nov 2002 09:19:44 -0800 (PST) From: "Bruce R. Montague" Message-Id: <200211041719.gA4HJiU00556@mail.cruzio.com> To: andrewdean@connexus.net.au, freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD boot problems? Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Re: > On Machine C it gets to "Uncompressing...done" then reboots ... Was the FreeBSD 4.7 from a current CVS or a Release? Has FreeBSD ever run on the machines that do not boot? Are you running the same config on all 4 machines, or have you tailored the configs (devices, etc.) to the machines? What are the BIOSes? > Any ideas? Just now I have a slightly similar problem with PicoBSD under 5.0-current that seems to be due to a recent patch to src/sys/i386/i386/machdep.c in "getmemsize()": "Change method to determine base memory size. Try INT 15H/E820H first, then fall back to the old compatibility method (INT 12H). This is a workaround for newer machines which have broken INT 12H BIOS service implementation." It looks like this was also recently MFC'd to 4.7. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/i386/machdep.c The new scheme seems to break something wrt a NatSemi XpressROM BIOS :) - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message