From owner-freebsd-current@freebsd.org Mon Dec 18 14:17:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D50BCE8DD29 for ; Mon, 18 Dec 2017 14:17:04 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CB677C511 for ; Mon, 18 Dec 2017 14:17:03 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-18bc70d5.06-431-73746f70.cust.bredbandsbolaget.se ([213.112.188.24] helo=sigyn.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1eQvoD-0007d2-WC; Mon, 18 Dec 2017 14:50:22 +0100 Received: from gw.bright-group.se ([193.12.143.142] helo=[192.168.30.20]) by sigyn.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1eQvo9-0004kI-W6; Mon, 18 Dec 2017 14:50:18 +0100 Subject: Re: UEFI booting survey To: Warner Losh , FreeBSD Current References: From: Jakob Alvermark Message-ID: Date: Mon, 18 Dec 2017 14:50:18 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 18 Dec 2017 14:17:04 -0000 On 12/17/17 20:52, Warner Losh wrote: > Greetings > > If you are booting off UEFI and have a bit of an unusual setup, I'd like > you to drop me a line. > > The setup that I'm looking for is any case where you load boot1.efi off one > drive (cd, ssd, hdd, nvme, etc), but don't have a FreeBSD system on that > drive, but on a different drive on the system. > > An example of this may be loading boot1.efi off what FreeBSD would call > /dev/ada0p1, but having root come from /dev/ada1p1. > > It's my belief that due to the fragility of this setup, few, if any, people > have this setup. If you do, please take a minute to reply to this message. > In the coming months, we're looking at dropping boot1.efi and instead > installing /boot/loader.efi onto the ESP (most likely as > \efi\freebsd\loader.efi). As part of the move to fully support the UEFI > Boot Manager, we're dropping the 'search every device in the system' part > of the current boot1 algorithm. It will be possible to configure the system > to continue booting (either via the new efibootmgr which will allow any > imaginable combination, or possibly via a fallback mechanism needed for the > embedded EFIs that have poor UEFI Variable support at the moment), but as > part of an upgrade to a future FreeBSD 12, some intervention will be > necessary. > > Please let me know if you have an unusual setup like this. > > Warner Hi Warner, I have what I guess is an unusual setup, not like what you describe above, but unusual because I tripple-boot my laptop using only the UEFI boot manager to select the OS to boot. I have FreeBSD-current, OpenBSD-current and Windows 10 on different partitions on one SSD. By default it boots FreeBSD. This was accomplished with bcdedit.exe in Windows, but now I realize this could be done with the new efibootmgr. I wanted to try it out, but it panics on my laptop. Sometimes just 'kldload efirt' just panics, sometimes it loads but panics as soon as I run efibootmgr or efivar. How can I help debugging this? Jakob