From nobody Sat Aug 13 15:47:31 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4M4lL767y8z4Z9Jh for ; Sat, 13 Aug 2022 15:47:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua1-x92d.google.com (mail-ua1-x92d.google.com [IPv6:2607:f8b0:4864:20::92d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4M4lL66NNxz3Grd for ; Sat, 13 Aug 2022 15:47:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua1-x92d.google.com with SMTP id b4so1361255uaw.11 for ; Sat, 13 Aug 2022 08:47:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=ci+9VUw4Nn98nstHNVZW90eobejU3FgJ+OTSGgzmaLI=; b=fe1mr7pGL96xc/ognBgJZdLvtr/jzhj8mdhBNuoJXryRaThvkrLxn1rhkb0I+A0fRq F/XnyVhBnkF1Il96msZNtp+l9tdRc06pSXRlje/FSb/m7ozXDuWdyaIoHIW3TNEgYA+R pi1VMHsl7ugmsbcudUf44HxGi/SLqcHNCFFhnTpnC55FpVYQX74R3QSCyv6BP08HRFLU O0tAx5jxCQQPXLsHWlVuQD7iDe0Qd4JNypyHgKN4Dybm3/UVkE8LAiLltBv/sDur+leX lccSfHP3llK2d9+BhieKDII+iEU7SGo+ZBPvuOnZnwhsJLFW0VIw8IcBUdrcPNS1oCG/ 6hWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=ci+9VUw4Nn98nstHNVZW90eobejU3FgJ+OTSGgzmaLI=; b=0YOsTe2PdNY7b7fuMq25n3t4kxokYgUqYmtmck1Tnqzu3y0uD2t+LstJa9l1F3nE5a 30Y4Bv8UQOG5X2Cnkbec1FgTZ3Hy5kfVcOIYq/PJvhLBi50Hbjc/ovaF74vUPFOVu4kE DDajOKuwGvtz1vWiw/k+nli4mmY4R/sowdC5cuYUwbQZWFVsg40uCMi5gKtlWbZKNebw YK0VwOGGAnpB/wxukaV/2L8hEDdYaw7QL7XfXZQxL5eGxqd568X/QHPpiG59jhmwZn5/ KOcxxRMw6yiOJbSIGKOE2HbUHnpAPmZBvTetFOi0RxnkXIV5Gc3NWsG5bumaofshzD3N kQOA== X-Gm-Message-State: ACgBeo1/YrlVKbsbQ5VfVknTZ3WgUJG3rgAC7ne7+lct645t4xXnsGE9 X1TiTVqniGuk573M3K5Ga0fHGUVV4vtRs29i3eaGOA== X-Google-Smtp-Source: AA6agR7VHDQ3XbB1xDLCBd2ln/4hewUsO5kSD282YvPArwFg1ve2iHOHs9M5fseLfNFR8Fhwzbvg1ITIBlObVefU+Oc= X-Received: by 2002:ab0:3bc6:0:b0:381:c4db:ef5 with SMTP id q6-20020ab03bc6000000b00381c4db0ef5mr3890464uaw.81.1660405662190; Sat, 13 Aug 2022 08:47:42 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20220813.015426.809710797578801280.yasu@FreeBSD.org> <20220813.024435.741655799390389695.yasu@FreeBSD.org> <78c22181179d9c7f9fcea829002095eb@lerctr.org> In-Reply-To: From: Warner Losh Date: Sat, 13 Aug 2022 09:47:31 -0600 Message-ID: Subject: Re: Updating EFI boot loader results in boot hangup To: Nuno Teixeira Cc: Larry Rosenman , Yasuhiro Kimura , FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000ada38a05e621512c" X-Rspamd-Queue-Id: 4M4lL66NNxz3Grd X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20210112.gappssmtp.com header.s=20210112 header.b=fe1mr7pG; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::92d) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20210112.gappssmtp.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::92d:from]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_SPF_NA(0.00)[no SPF record]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; RCPT_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20210112.gappssmtp.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --000000000000ada38a05e621512c Content-Type: text/plain; charset="UTF-8" On Sat, Aug 13, 2022 at 9:37 AM Nuno Teixeira wrote: > Hi Larry, > > boot off a memstick? >> > Yes, that's it. > With it we can mount efi partition and use bkp efi file by renaming it. > Yup. > I forgot that efi boot is restricted to use bootx64.efi (amd64) and my > though was looking for a command to load bootx64.efi.old avoiding use of a > memstick (e.g.). > I've tested it, and from now on I will update efi boot more often along > with current tracking. > Kinda. You can create a new UEFI (not ZFS) boot environment that uses something else. In addition, if you are fortunate enough to have EFI SHELL in your BIOS and/or in your ESP, you can run any XXX.efi program in the ESP, or any DOS partition... I have a known good loader.efi that I use a special BootXXXX variable so that if I AFU my loader.efi in testing, it's easier to get back online, though I also have shell.efi that I downloaded from the edk2 folks that also helps me fix things... But I know I'm a bit of a special case.... Warmer --000000000000ada38a05e621512c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Aug 13, 2022 at 9:37 AM Nuno = Teixeira <eduardo@freebsd.org= > wrote:
Hi Larry,

=

boot off a memstick?

Yes, that's it.
<= /div>
With it we can mount efi partition and use bkp efi file by renami= ng it.

Yup.
=C2= =A0
I forgot that efi boot is restricted to us= e bootx64.efi (amd64) and my though was looking for a command to load bootx= 64.efi.old avoiding use of a memstick (e.g.).
I've tested it, and from now on I will update = efi boot more often along with current tracking.

Kinda. You can create a new UEFI (not ZFS) boot= environment that uses something else. In addition, if you are fortunate en= ough to have EFI SHELL in your BIOS and/or in your ESP, you can run any XXX= .efi program in the ESP, or any DOS partition...

I= have a known good loader.efi that I use a special BootXXXX variable so tha= t if I AFU my loader.efi in testing, it's easier to get back online, th= ough I also have shell.efi that I downloaded from the edk2 folks that also = helps me fix things... But I know I'm a bit of a special case....
=
=C2=A0
Warmer
--000000000000ada38a05e621512c--