From owner-freebsd-current@FreeBSD.ORG Thu Dec 15 01:01:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 2036E16A41F for ; Thu, 15 Dec 2005 01:01:55 +0000 (GMT) (envelope-from m.r.orlando.1st@sbcglobal.net) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3101243D55 for ; Thu, 15 Dec 2005 01:01:49 +0000 (GMT) (envelope-from m.r.orlando.1st@sbcglobal.net) X-ORBL: [69.107.226.17] DomainKey-Signature: a=rsa-sha1; s=sbc01; d=sbcglobal.net; c=nofws; q=dns; h=message-id:date:from:user-agent:x-accept-language: mime-version:to:cc:subject:content-type:content-transfer-encoding; b=aKG7sup0Gu+rs+xKRTHaH/SwTqwi5hJqDrmGUsOCvnaQT+0dV4LHav5e0PeJVSJZT RBjD0OopMnlUAVebZxl5g== Received: from [69.107.226.17] (adsl-69-107-226-17.dsl.sndg02.pacbell.net [69.107.226.17]) by pimout3-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id jBF11k0j149330; Wed, 14 Dec 2005 20:01:47 -0500 Message-ID: <43A0C06C.8070200@sbcglobal.net> Date: Wed, 14 Dec 2005 17:01:32 -0800 From: "Michael R. Orlando" User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en To: noackjr@alumni.rice.edu Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 15 Dec 2005 01:19:01 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: DesktopBSD install problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Dec 2005 01:01:55 -0000 Jon: I am trying to install DesktopBSD (based on FreeBSD) and when I attempt to boot from the CD burned from v1.0-RC3 X86-CD.ISO (from the DesktopBSD download area), I get t he following message: CD Loader 1.2 Building the boot loader arguments Looking up /BOOT/LOADER... FOUND Read Error: 0X32 Could not find Primary Volume Descriptor Here are the particulars of my system: Shuttle AK12AS04 board (06/08/2001-8363-686-AK12AC-00) AMD Athlon 1.133MHz processor 256 MB memory 30 GB EIDE WD Caviar HD Award BIOS v6.00PG System Commander v7 (multi-boot manager) I have successfully installed multiple versions of DOS, Windows 9x, Win 2000 Pr o, OS/2, and Linux on this system. The most recent post on the DesktopBSD forum under installation says to try again after the release of v3, and that is the version I am attempting to install. Please excuse my ignorance, but is there a directory of error messages, and their meanings that I could consult to determine the cause and possible remedies for the above, as well as other, error messages? ______________________________________________________________________ I have found a prior post which you replied to on the FreeBSD forums, repeated here: ______________________________________________________________________ On 3/24/2004 4:37 PM, Nicolai E M Plum wrote: > Hi > > I am having problems booting FreeBSD 5.2.1-RELEASE on a system I > have. 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 > ---- > > Booting from floppies works OK. > > The same happens when trying to boot a CD of 5.1-RC1 that I happen to > still have around. 4.9-RELEASE boots fine from CD. > > Hardware is an older Dell Pentium Pro system, with a Samsung SM-532 > DVD-ROM CD-RW drive. > > Any ideas why this happens? I've worked around it, but it's a bit > awkward. I can't find any details of why it happens in searching mailing > lists. 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. In many cases a BIOS update will fix this, so you might check for that. Jon ______________________________________________________________________ Do you have any further information that might be helpful here? How can I find the meanings and actions required of any error messages generated during installations or operations? How is the error message I receive (0x32) different from the one in the post you replied to (0x01)? Do you know if the current version I am using is any different from the previous version mentioned in the earlier post in this regard? Whatever you can tell me will be greatly appreciated. Thank you. Sincerely, Michael R. Orlando