Subject: Re: port-i386/25550: i386 boot selector broken
To: None <netbsd-bugs@netbsd.org>
From: David Laight <david@l8s.co.uk>
List: netbsd-bugs
Date: 05/13/2004 22:12:21
> >Number:         25550
> >Synopsis:       i386 boot selector broken
 
> I have NetBSD 2.0 installed in the first MBR partition on wd0 and
> Windows installed in the first MBR partition on wd1.  The old boot
> selector would allow me to assign the names "NetBSD" and "Windows"
> to the F1 and F5 keys to boot from these partitions.

I doubt it, F1 would have booted the first partition of wd0, and F5
thembr of wd1.  You ould have a menu name for F1, but not F5.

> No it has the following problems:
> 
> 1) It doesn't display any text on the display and sits there waiting
> until the timeout expires.

This will be because there are no names in the menu table.
I've changed 'current' so that it will boot the default partition

> 2) None of the F* keys work (it prints "Error?" to the display), except
> for _F2_, which boots from the NetBSD partition.  

RTFM (and the display!) the keys got changed, F1 boots the mbr from disk0,
and F2 that of disk1 (etc).  You need to type '1' to get the first bootable
partition of the current disk booted and '2' for the second (dense numbering).
This was changed because you can now boot netbsd from an extended partition
and there can be more than 4 menu ites.

> As per PR25113, I think there has been a regression in functionality
> of the boot selector, since it won't allow names to be allocated to
> partitions and the F* keys.  But then, I would mind so much if they worked.

The bootselect menu strings are now configured whith the partition parameters.

> As an aside, and perhaps should be a separate PR, when I was originally
> trying to install NetBSD on wd1, the boot blocks were installed on wd1,
> rather than wd0.  I could never boot NetBSD.

Yes - you have to have boot blocks on wd1, getting wd1 booted is your problem!
If you install the netbsd mbr onto wd0, then (now) F1 will boot wd1.

> Consequently, I had to swap the drives between master and slave.
> But now I cannot boot Windows, because the boot selector is hosed.
I'm not actually sure windoze will like you moving the disk from disk0
to disk1....

Run netbsd's fdisk on your windoze disk, edit ptn 0 and set a boot menu
name.

Swap the disks back.

Then '1' will boot windows and F2 netbsd on the other disk.

You may want to force /usr/mdec/mbr to be used on the netbsd disk.
(since you don't want a  bootmenu for that disk displayed.

	David

-- 
David Laight: david@l8s.co.uk