I just did a quick test of 8.99.51 amd64 from yesterday (self-built, but with no changes) to see how the EFI/GPT installation works using the latest sysinstall (good work, Martin). This was done under VirtualBox, using a newly created NetBSD/amd64 VM with EFI enabled.
Everything worked as it should for me this time, I didn't have to resort to manual creation of the GPT partitions etc. as described elsewhere. Even pkgin setup worked first time (I have a local pkgin repo using either ftp or nfs, the test was using ftp). On my present laptop I have been running NetBSD in EFI mode for quite some time, but the installation was manual, following the sequence described in the post about NetBSD on EFI. It is on a secondary disk, shared with instances of OpenSUSE/tumbleweed, RedHat 7.6 (the upgrade to 8.0 failed, so I reverted), and one GPT partition for some Windows data. The primary disk is also GPT, but it holds only Windows 10. On Mon, 29 Jul 2019 at 06:18, Thomas Mueller <[email protected]> wrote: > > > Emmanuel Dreyfus <[email protected]> wrote: > > > > - in UEFI mode, bootstrap does not read boot.cfg and while it sees the > > > GPT partitions, it is unable to access a RAID that has a GPT inside. It > > > can access a RAID that has a disklabel inside, though, but that does not > > > help for > 2 TB. > > > Reading the sources, I find that boot.cfg should be stored in the EFI > > partion as /EFI/NetBSD/boot.cfg and ineed if it is at this location, EFI > > bootstrap finds it. > > > I still have the problem with accessing a RAIDframe containing a GPT. > > > Emmanuel Dreyfus > > Where in the source tree would I find the stuff on booting EFI? > > I have NetBSD installations for both amd64 and i386, am also curious about /usr/mdec/bootx64.efi and bootia32.efi . > > I see FreeBSD 12-STABLE and HEAD (13-current) include efibootmgr. > > When I tried to boot NetBSD-current by UEFI, I had trouble specifying the root partition in a way that the boot loader would understand, finally got that far, but NetBSD (current amd64) hung after the first line of screen output. > > Tom > -- ---- -- ----
