From owner-freebsd-current@freebsd.org Mon Dec 18 20:21:21 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 F2F03E844F2 for ; Mon, 18 Dec 2017 20:21:21 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (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 B440A6E11A for ; Mon, 18 Dec 2017 20:21:21 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mail-ua0-x22a.google.com with SMTP id i20so11515558uak.6 for ; Mon, 18 Dec 2017 12:21:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sippysoft-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=PFawPzCQHSHqsvjRvGc3ZzqIbEbJhzp918j8lDsfGb0=; b=IRqySzx9NXVianK2REHqQQiBPeu/pVTk2c69ryw+0kO2/Ai8CQqmi0uh0DEKfvtjY0 7dHCmYCpf/YtRj2NV3zouyvM3HorCdNOTVpMA4ytstlrqk0EjTy7yVgFRsIZMZSA9nSD muQ4pBJPfF9JlVuaOcmZBaCr4GpVH/k/OIjG4o0Lv6GSenaIjUlcHWqLFc/31tSOyCNF zHAIsygbApo6sAhJdpSxBoS7+HX3gQ0kpMHuj0GqfgXtoNRtDMD9OZKrxmdCjvWDRwMX qbF07jnuwSKAea4NRcymssJjYoI8G6lbRJjGInOQGJP8icQDLUpx+znKkKbAzVN5RBic 9MrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=PFawPzCQHSHqsvjRvGc3ZzqIbEbJhzp918j8lDsfGb0=; b=P//2iAp4DP8B+ffowpkBEfy4OcATgjXU79RQsQiopB688NjCxdEjhEUZ2sttJmlm2r opSgFj6NNUfSyirKWBp8Q71x9mgxI61Be9riqTFdKcU3U0yJbbkCedsGfAMkaPBNZ5Ri 0FUxVGBruJh190sNhP00HU262DEkbJ2M5Yke6M/ASXnRHC8ToWPj8/QlSwFs8ng5mtWf awfYHPhwxhEUxAjqXq2H1aWxXqlPS37aY0hDZ8LgvFwM6XNFYlmZan3JFzmn9BfgxeDd JZR/mymsouf/VA11tuxSAun0YhnqV/DMbbcDud2Mw1u+Cl7BGc+KGDkAS40cUZX7ugQc QPMQ== X-Gm-Message-State: AKGB3mI5sfjQrv9/fojMXp+Z7bHF5M0FgEJLJwexLhNFIRXGSefIdbwD wcbJzhzlKqjuX9mrXswUFG6k3pW9WelIqo+brnWUSA== X-Google-Smtp-Source: ACJfBovcYErRAVpccQ7w7pl6LPZJoTEo18UZmcHHNRoj0Hnv53Uj/koP8PB8+C2Mgktik3u7HNuBtDB8NXVSdlHLkHM= X-Received: by 10.176.25.70 with SMTP id u6mr1139542uag.114.1513628480719; Mon, 18 Dec 2017 12:21:20 -0800 (PST) MIME-Version: 1.0 Sender: sobomax@sippysoft.com Received: by 10.176.14.25 with HTTP; Mon, 18 Dec 2017 12:21:20 -0800 (PST) In-Reply-To: References: From: Maxim Sobolev Date: Mon, 18 Dec 2017 12:21:20 -0800 X-Google-Sender-Auth: Zlv_mx2VLJ_OP5J0kr59QV0BP0A Message-ID: Subject: Re: UEFI booting survey To: Jakob Alvermark Cc: Warner Losh , FreeBSD Current 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: Mon, 18 Dec 2017 20:21:22 -0000 Not really specific to UEFI, but when ZFS is in use the /boot might be partially or fully located on the drive that does not correspond to your boot drive. We've bumped into this issue on AWS recently when our kernel ended up on second drive after upgrade in a pool that were spanning two EBS volumes. Now, it does not work with AWS (as boot code only has access to the boot EBS volume apparently), but according to Alan such scenario is totally supported on a physical hardware. So I am worried that by not allowing loader to scan all drives in the system you'd make this scenario fundamentally impossible. -Max On Mon, Dec 18, 2017 at 5:50 AM, Jakob Alvermark wrote: > 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 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >