From owner-freebsd-current@freebsd.org Fri Mar 27 22:51:46 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 C5B03263DF1 for ; Fri, 27 Mar 2020 22:51:46 +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 48pxtS2Q0qz4CgC for ; Fri, 27 Mar 2020 22:51:43 +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 02RMqCpS074397 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 27 Mar 2020 15:52:18 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: freebsd-current In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Andrey Fesenko Subject: Re: When will the FreeBSD (u)EFI work? Date: Fri, 27 Mar 2020 15:52:18 -0700 Message-Id: <79dcf9ff2e4a233552bb1dff28c723ac@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 48pxtS2Q0qz4CgC X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.48 / 15.00]; NEURAL_HAM_MEDIUM(-0.85)[-0.847,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81]; NEURAL_HAM_LONG(-0.63)[-0.629,0] 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: Fri, 27 Mar 2020 22:51:46 -0000 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 wrote: > > > > 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 previous > > 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! > > >=20 > Require only single efi part >=20 > See > https://forums=2Efreebsd=2Eorg/threads/two-freebsd-installations-and-efi=2E7396= 8/ 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 That is; not without dropping to the loader prompt, or changing the status of slices, or boot entries pri= or to reboot=2E :( Looks like I'll need to install a third party OS, or bootmanager to use Fre= eBSD=2E Sigh=2E=2E=2E There *may* be hope in the future (https://bugs=2Efreebsd=2Eorg/bugzilla/show_b= ug=2Ecgi?id=3D207940) Thanks again, Andrey=2E Greatly appreciated! :) --Chris