From owner-freebsd-current@freebsd.org Sun Dec 24 09:49:52 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 B1173E820E5 for ; Sun, 24 Dec 2017 09:49:52 +0000 (UTC) (envelope-from devries.arno@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D39471DDE for ; Sun, 24 Dec 2017 09:49:52 +0000 (UTC) (envelope-from devries.arno@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id g130so30105296wme.0 for ; Sun, 24 Dec 2017 01:49:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HM+s0IPVxrRYFl9LOJU2cvOnYLwoDSE+TK8NePyPz60=; b=qXrpFuDmRQptO6+uMoDSI786id9+9juWZZHp+mt5eW6n1FjhEW8mA8DhmOeAjh70Zf Mrr3cXS/nm30fXaIb68X4trHA0rSFIWe67fwLoSYP4V2ArfpYpeSXzIiOg2XSsGFVay/ zgACub6Sbq7DfmmBgVf0QLgJUbRQQT1G3YOhik5K42L4gnSEFDgSK7p453/PM37qKlA8 uEoWdaQCWWhcqLofBFV0PYIWjm6M63RBJyYz4jZ18aann4X9RgwMHWwaFvLhW8ixearY 9Bi/BTTPcmXx3dbyKx1AQ3y12jTXi9jTJzBcRCKFY2M5BINwG604yCzW0UChlRtTXmIw 1X1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HM+s0IPVxrRYFl9LOJU2cvOnYLwoDSE+TK8NePyPz60=; b=KXpns91LMWvrYRZ0cWyy6TL/AVbMZ9tOU9eGlTPR2ziPwEp5XbpfWpMhLN5qaYhzCv jQ/xeqVZZXBJK6C9SrISSb2N8LKWgK2OTIThJo4Yau0/eUS+NPyQFM7XZmSNTq3flAXq 3Yrk61ctoAn2iEp0SSNaKSRr0GjBU9bJVrwqosAk4SA5jHOOQhVOlTVyibG87HaRhC+e DCM6WMvxK6kbnLhOC7hpqg66+bFDe7d0FZCOM2/m/2IaEFa+yBqO3ecY86MkiC1GbQC+ FUBUd/ZbXG9/LyCriLGYztwjOkpY4/0nSWWEe5xtS7+6ZyD0EBNdwLsN0hct6w3MuQCz E3vw== X-Gm-Message-State: AKGB3mLTj0c7gkQT5RPprUXYa2qsHoOlsjzEmt9/WogKsUWD0PYKv27x mzhbx4mR12ALFj1AS/CpCo2Y9vOtZ8PDgKahtBHzyRGK X-Google-Smtp-Source: ACJfBouLMVdjVN8QhXINws3pmYVI0WMuMFkYNonXzqdAJBlGpLp9bBT1bQ+NNmta5P2uewJqQugRquV4N0HKs0IaFXg= X-Received: by 10.80.150.194 with SMTP id z2mr22744137eda.156.1514108989850; Sun, 24 Dec 2017 01:49:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.186.71 with HTTP; Sun, 24 Dec 2017 01:49:48 -0800 (PST) In-Reply-To: References: From: Arno de Vries Date: Sun, 24 Dec 2017 10:49:48 +0100 Message-ID: Subject: Re: UEFI booting survey To: Warner Losh Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sun, 24 Dec 2017 09:49:52 -0000 On Sun, Dec 17, 2017 at 8:52 PM, 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 > I use something similar in FreeBSD 11.1 . I boot from an USB drive with an EFI partition and an UFS partition containing only a modified loader.efi, loader.help,loader.conf and loader.rc The reason is I came from a BIOS system with a root raidz pool on raw disks. and my new motherboard no longer supported legacy boot. I had to modify loader.efi because it only probes partitions for zfs pools, not disks (also see bug report 220105). For those interested: comment out the 'continue' on line 123 in /sys/boot/efi/libefi/efipart.c (r 313355) I used info form https://lists.freebsd.org/pipermail/freebsd-hackers/2015-August/048141.html to get it booting. Arno Virusvrij. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>