Hmmm, there are only two files on the EFI partition - bootx64.efi and bootia32.efi. They’re both in the EFI/boot directory. There is a minimal boot menu that comes up and I assume it’s some default menu inside the code. I’ll try moving the /boot.cfg file over and see what happens - after making the disk name adjustments.
Thanks! -bob On Feb 28, 2017, at 6:49 PM, Paul Goyette <[email protected]> wrote: > On Tue, 28 Feb 2017, Robert Nestor wrote: > >> When I was a young man doing IT support I was always frustrated to >> find a user who needed help but had sprinkled his scripts with all >> sorts of random commands he'd found someplace. Now that I'm an old >> man I find myself doing that very same thing, so I understand and >> appreciate your confusion and frustration on my screwed up approach. >> :-) > > :) From one old man to another, I understand completely! :) > >> However, I faithfully implemented your advice and lo-and-behold I >> almost have a booting system! It does come up with the NetBSD boot >> menu and then fails because it can't find the NetBSD kernel file on >> hd0a. Of course, that's the EFI/FAT16 partition, so I entered "boot >> hd0b:netbsd" at the prompt and I'm up and running! > > Kewl! > >> I'm thinking there must be some configuration file I can play with >> that modifies this behavior, but for now I’m one happy camper! > > /boot.cfg is usually where the boot menu is located, probably on the FAT16 > partition. Change the boot commands appropriately... > > > +------------------+--------------------------+------------------------+ > | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | > | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com | > | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org | > +------------------+--------------------------+------------------------+
