From owner-freebsd-questions@FreeBSD.ORG Sun Nov 5 13:11:14 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB69016A412 for ; Sun, 5 Nov 2006 13:11:14 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8717A43D5A for ; Sun, 5 Nov 2006 13:11:12 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 26528 invoked from network); 5 Nov 2006 13:11:12 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Nov 2006 13:11:11 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 25EDA28430; Sun, 5 Nov 2006 08:11:11 -0500 (EST) To: Peo Nilsson References: <1162668828.8001.19.camel@zeus.se> From: Lowell Gilbert Date: Sun, 05 Nov 2006 08:11:10 -0500 In-Reply-To: <1162668828.8001.19.camel@zeus.se> (Peo Nilsson's message of "Sat, 04 Nov 2006 20:33:48 +0100") Message-ID: <44slgy2g41.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Installing FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Nov 2006 13:11:14 -0000 Peo Nilsson writes: > I just can=B4t get FreeBSD to boot... > I have been trying everything I can think of. [snip] > Can anyone give me a hint? You need to show the actual errors you get when FreeBSD tries and fails to boot.=20=20 And the mismatching disk geometry error messages aren't necessarily a problem; lots of systems can go ahead and boot despite that. (Geometries are generally made-up anyway, these days.)