From owner-freebsd-current@freebsd.org Sat Mar 28 03:28:13 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4971226E5A1 for ; Sat, 28 Mar 2020 03:28:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48q41P0lsHz3F46 for ; Sat, 28 Mar 2020 03:28:07 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 02S3SYQD078422 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 27 Mar 2020 20:28:40 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: When will the FreeBSD (u)EFI work? Date: Fri, 27 Mar 2020 20:28:40 -0700 Message-Id: <4f8f3e359207b923a6a3e49a1405a832@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48q41P0lsHz3F46 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-0.06 / 15.00]; NEURAL_HAM_MEDIUM(-0.17)[-0.172,0]; NEURAL_SPAM_LONG(0.12)[0.116,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 28 Mar 2020 03:28:13 -0000 On Fri, 27 Mar 2020 18:31:50 -0700 bsd-lists@BSDforge=2Ecom said > On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh imp@bsdimp=2Ecom said >=20 > > On Fri, Mar 27, 2020 at 4:54 PM Chris wrote: > >=20 > > > On Sat, 28 Mar 2020 01:10:37 +0300 Andrey Fesenko f0andrey@gmail=2Ecom = said > > > > > > > On Sat, Mar 28, 2020 at 12:53 AM Chris wro= te: > > > > > > > > > > On an experiment of the FreeBSD EFI implementation=2E I installed > > > > > a copy of releng/12 from install media=2E Which left me with: > > > > > # gpart show ada0 > > > > > =3D> 40 312581728 ada0 GPT (149G) > > > > > 40 409600 1 efi (200M) > > > > > 409640 31047680 2 freebsd-ufs (15G) > > > > > 31457320 7680000 3 freebsd-swap (3=2E7G) > > > > > 74788904 237792864 - free - (141G) > > > > > > > > > > On this Intel based system, I can stab the F12 key to pick > > > > > my UEFI bootable OS, or let it boot according to the order > > > > > I setup in the BIOS=2E So far, so good=2E > > > > > I needed a copy of releng/13 to also work with=2E Installed a copy > > > > > from install media=2E Which left me with: > > > > > # gpart show ada0 > > > > > =3D> 40 312581728 ada0 GPT (149G) > > > > > 40 409600 1 efi (200M) > > > > > 409640 31047680 2 freebsd-ufs (15G) > > > > > 31457320 7680000 3 freebsd-swap (3=2E7G) > > > > > 39137320 532480 4 efi (260M) > > > > > 39669800 35119104 5 freebsd-ufs (17G) > > > > > 74788904 237792864 - free - (113G) > > > > > I *assumed* that the install would activate the new install, and = I > > > > > would boot straight into it=2E But no=2E I am still on the previous > > > > > install, and worse, I can't get into the new install -- even if > > > > > picking it via stabbing the F12 key=2E I *still* end up in the prev= ious > > > > > install=2E So looking at what might be causing it=2E I found the > > following: > > > > > # releng/12 > > > > > # mount -t msdosfs /dev/ada0p1 /mnt/ > > > > > > > > > > # ls /mnt/efi/boot/ > > > > > BOOTx64=2Eefi > > > > > startup=2Ensh > > > > > > > > > > # cat /mnt/efi/boot/startup=2Ensh > > > > > BOOTx64=2Eefi > > > > > > > > > > # umount /mnt/ > > > > > > > > > > releng/13 > > > > > # mount -t msdosfs /dev/ada0p4 /mnt/ > > > > > > > > > > # ls /mnt/EFI/freebsd/ > > > > > loader=2Eefi > > > > > > > > > > Why the difference? When will FreeBSD (u)EFI work as expected? > > > > > > > > > > Thanks in advance for any insights! > > > > > > > > > > > > > Require only single efi part > > > > > > > > See > > > > > > > > > https://forums=2Efreebsd=2Eorg/threads/two-freebsd-installations-and-efi=2E73= 968/ > > > Thanks for they reply, and link, Andrey! > > > Well that confirms it=2E FreeBSD, unlike other OS implementations, will= not > > > permit booting your chosen "version" via EFI=2E > >=20 > >=20 > Firstly, *huge* thanks for your informative reply, Warner! > > It does today=2E If you use efibootmgr, you can boot exactly what you wan= t=2E I > > do it all the time=2E=2E=2E Though your BIOS may overwrite the EFI vars if y= ou > > set too many (I'm looking at you supermicro)=2E When you use the efi Boot= XXXX > > variables, it's possible to boot one of many different things on the > > system=2E=2E=2E Though I've not done 11, just 12 and current=2E > Well=2E That's the thing=2E I *am* on 12 && 13=2E Well *trying* to get into 13=2E > When I started this whole thing, I had some 15 entries returned by > efibootmgr(8) -v=2E > So I trimmed the list down to the 2 my BIOS presents as UEFI: > Boot0015 UEFI: WDC WD1600JS-98MHB0 > PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0xffff,0x0)/HD(4,GPT,6688c5af-6f93=2E=2E=2E > Boot0011* UEFI: WDC WD1600JS-98MHB0 > PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0xffff,0x0)/HD(1,GPT,260d2df2-6a10=2E=2E=2E > another entry created when I installed releng/13: > Boot0014 FreeBSD (ada0p4) > HD(4,GPT,6688c5af-6f93-11ea-adbb-4c72b9f5e07f,0x2553028,0x82000)/File(\EF= I\free=2E=2E=2E > and a Windows reference (currently not installed)=2E > I activated *both* Boot0015 and Boot0011: > efibootmgr -a 0015 0011=2E Output confirmed success=2E Bounced box, choose > Boot0015=2E Which booted > initial releng/12 install=2E Fail=2E OK Try something different; > efibootmgr -a 0014 -L FreeBSD-13=2E Output confirms the -L switch is broken= , > but 00114 is active=2E > Bounce box && choose 0014=2E Boots to initial releng/12 install=2E >=20 > Conclusion; FreeBSD EFI/ESP is not ready for prime time=2E :( >=20 > Thanks again for the reply, Warner! :) >=20 > --Chris > >=20 > >=20 > > > That is; not without dropping > > > to the loader prompt, or changing the status of slices, or boot entri= es > > > prior to > > > reboot=2E :( > > > > >=20 > > Not needed=2E > >=20 > >=20 > > > Looks like I'll need to install a third party OS, or bootmanager to u= se > > > FreeBSD=2E > > > Sigh=2E=2E=2E > > > > >=20 > > Again, not needed=2E Though there may be a few things that need to be MFC= 'd > > if you want 11 on that list=2E=2E=2E > >=20 > >=20 > > > There *may* be hope in the future ( > > > https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D207940) > > > > >=20 > > This would require you to stop to select on the way up=2E=2E=2E Or am I not > > understanding what you want? > >=20 > > We should add that functionality to loader=2Eefi, since boot1=2Eefi is in t= he > > process of being deprecated=2E=2E=2E It should be a simple LUA script there=2E=2E= =2E Isn't everything confined to stand/ ? I'd like to try and write all this so that FreeBSD performs EFI/ESP booting in a more intuitive way=2E It seems odd to me, that I can install Windows, an= d it'll add FreeBSD to the (efi) boot menu, but not vis-a-vis=2E --Chris > >=20 > >=20 > > > Thanks again, Andrey=2E Greatly appreciated! :) > > > >=20 >=20 > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= "