Date: Sat, 22 Jun 2019 13:05:52 -0600 From: Rebecca Cran <rebecca@bluestop.org> To: Karl Denninger <karl@denninger.net>, freebsd-current@freebsd.org Subject: Re: UEFI firmware and getting FreeBSD recognized by default: who to talk to? Message-ID: <cc6c9260-451b-ae5b-0612-51b1a5525116@bluestop.org> In-Reply-To: <db7c8df3-ead3-9d56-bd9c-9ff732b401e9@denninger.net> References: <1e08badd-a963-7e4b-98a7-52a9d3bd77a8@bluestop.org> <db7c8df3-ead3-9d56-bd9c-9ff732b401e9@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-06-22 12:59, Karl Denninger wrote: > > I use Refind for this sort of thing and it has (thus far!) survived > upgrades. The only "gotcha" is that I had a Windows 10 "Feature" > upgrade that reset the default boot in the firmware to Windows; it > didn't damage anything but did require that I go reset the UEFI default > to boot the Refind EFI loader instead of the Windows one. I do like that rEFInd knows about FreeBSD, and it's one of the "UEFI OS" entries that remains. But I'd prefer it if a "FreeBSD" entry was automatically created! -- Rebecca Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cc6c9260-451b-ae5b-0612-51b1a5525116>