From owner-freebsd-questions@FreeBSD.ORG Mon Aug 16 21:30:14 2010 Return-Path: Delivered-To: Freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 287171065673 for ; Mon, 16 Aug 2010 21:30:14 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id 066358FC13 for ; Mon, 16 Aug 2010 21:30:13 +0000 (UTC) Received: from unknown (client-86-31-88-103.midd.adsl.virginmedia.com [86.31.88.103]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 172EB5F65; Mon, 16 Aug 2010 21:30:05 +0000 (UTC) Date: Mon, 16 Aug 2010 22:30:07 +0100 From: Bruce Cran To: Mubeesh ali Message-ID: <20100816223007.000060d2@unknown> In-Reply-To: References: X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Freebsd-questions@freebsd.org Subject: Re: Not booting after freebsd install X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Aug 2010 21:30:14 -0000 On Mon, 16 Aug 2010 23:54:51 +0530 Mubeesh ali wrote: > Hi, i have an acer 5745 which had ubuntu running not booting after an > attempted freebsd install .i understand that i might have wiped by > choosing auto partition :-( and had not written mbr so that we could > manage all from grub .now the laptop is stuck at bios splash screen.it > refuses to go even to bios setup. > please advice how i can recover and start over Specific configurations of partitions (or rather, byte patterns) are known to cause some BIOSes to hang during POST - on mine it was Windows and FreeBSD. If you can, try switching from AHCI to IDE or vice versa. Otherwise you might have to remove the drive and reconfigure it on another system with a less buggy BIOS. -- Bruce Cran