From owner-freebsd-current@FreeBSD.ORG Thu Mar 25 03:14:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A95CF16A4CE for ; Thu, 25 Mar 2004 03:14:37 -0800 (PST) Received: from amonsul.esperi.net (amonsul.esperi.net [194.216.214.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7670243D45 for ; Thu, 25 Mar 2004 03:14:37 -0800 (PST) (envelope-from nicolai@esperi.org) Received: from nicolai by amonsul.esperi.net with local (Exim 4.21) id 1B6Som-000NXv-Na; Thu, 25 Mar 2004 11:14:36 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16482.48922.657420.534911@amonsul.esperi.net> Date: Thu, 25 Mar 2004 11:14:34 +0000 In-Reply-To: <40621CE9.6030204@alumni.rice.edu> References: <16482.3506.550989.340221@amonsul.esperi.net> <40621CE9.6030204@alumni.rice.edu> X-Mailer: VM 7.07 under Emacs 21.3.1 From: Nicolai E M Plum To: noackjr@alumni.rice.edu Sender: Nicolai E M Plum cc: freebsd-current@freebsd.org Subject: Re: 5.2.1 boot fails; "Could not find Primary Volume Descriptor" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2004 11:14:37 -0000 Jon Noack writes: > Nicolai E M Plum writes: > > Booting from CD gives me: > > ---- > > [other messages from the BIOS] > > CD Loader 1.01 > > > > Building the boot loader arguments > > Read Error: 0x01 > > Could not find Primary Volume Descriptor > > ---- > The 5.x bootable install CDs no longer use floppy-emulation mode. The > change was made because some newer machines do not support this > emulation mode. However, older machines may not be able to boot CDs in > "native" (non-emulation) mode. We can't support everybody, so we > support the new machines. Ah, fair enough; I can understand that. > In many cases a BIOS update will fix this, so you might check for that. Will do. And now there's an archived answer to search for in the mailing lists :) Perhaps a document maintainer could add it to the Handbook as a gotcha. Thanks Nicolai