From owner-freebsd-questions Wed Jun 23 9:32:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (Postfix) with SMTP id BC0A514E81 for ; Wed, 23 Jun 1999 09:32:15 -0700 (PDT) (envelope-from mike@hyperreal.org) Received: (qmail 23929 invoked by uid 12); 23 Jun 1999 16:31:58 -0000 Message-ID: <19990623163158.23928.qmail@hyperreal.org> From: mike@hyperreal.org Subject: Solved: 3.2R boot menu problems To: freebsd-questions@freebsd.org Date: Wed, 23 Jun 1999 09:31:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL51 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FOLLOWUP: Last week I posted about trouble I was having with boot0 in FreeBSD 3.2-RELEASE. The symptom was that upon powerup, the system would give me a boot menu consisting of: F1 DOS F2 FreeBSD F3 Drive 0 However, F1 and F2 apparently actually tried to boot from the A: floppy drive. F3 resulted in a second menu: F1 DOS F2 FreeBSD F3 Drive 1 And from here, F1 and F2 behaved as they should. Robert Nordier, maintainer of the boot0 code, offered some assistance that got my boot menu to a more reasonable state. Although still not perfect, I now at least do not have to be at the console to hit a key after a reboot. Robert said the problem has to do with how the BIOS reports drive numbers, and how boot0 reacts to the numbers it gets. He said that "in 3.2R, the command to sort this out would have been: boot0cfg -v -d 0x80 -o setdrv wd0 which tells the boot manager that the BIOS doesn't pass in the drive number as expected, and that it should use 0x80 (first hard drive). The 3.2R version of boot0 isn't broken, it just isn't as smart as it could be. I suggest you try the -current version instead, which is also available here: http://www.freebsd.org/~rnordier/boot0-1.9.tar.gz Ensure that the 512 byte boot0 file ends up in /boot and then use the command boot0cfg -v -B wd0 to put it in your MBR." There were 3 of us from the freebsd-questions list who were having the same problem, and the new boot0 code solved it for two of us. The fact that the boot manager is still in development and that Robert is very responsive to our problem reports is encouraging, and I would like to publicly thank him for his help. Thanks! - Mike ______________________________________________________________________ Mike Brown / Hyperreal | Director, Hyperreal Music Archive PO Box 61334 | http://www.hyperreal.org/music/ Denver CO 80206-8334 USA | Software Engineer, www.netIgnite.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message