From nobody Sat Sep 7 13:19:24 2024 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 4X1DG66Tkqz5VKG1 for ; Sat, 07 Sep 2024 13:19:26 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh5-smtp.messagingengine.com (fhigh5-smtp.messagingengine.com [103.168.172.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X1DG62SHvz3xK0 for ; Sat, 7 Sep 2024 13:19:26 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=nZtCMiiP; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=HW0msrYb; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.156 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-10.internal (phl-compute-10.phl.internal [10.202.2.50]) by mailfhigh.phl.internal (Postfix) with ESMTP id 24AF11140253 for ; Sat, 7 Sep 2024 09:19:26 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-10.internal (MEProxy); Sat, 07 Sep 2024 09:19:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1725715166; x=1725801566; bh=AHNYkEBQET k14BGNuB2o6YpassTo8vcfotHjGeZL3I0=; b=nZtCMiiPw9DCP0qGpb1UklTAbE lJJZ8NHSNK8NbjXUGcJgmwfVR9XxFmkpV1nTeSKmhmYme3E9Z+fGcqcvVoEPcA49 caiLDiMSz7Ld667TossQYueU9H75ixu5WsVX0IRaBvmowc1MSWRg9dPqBTf7hVER LsMaulG1r2JsTJ0NT8PeZleSeyliGxk4FusCLYdcyUcIf5PvbVkS7b105RhibEGb h3i0meRafufoRwZ/ht8aJNoa+XPZ7vI13hls5loBYNG9+PxkF2STGL166C7iGrhP 1pb9w/Lqf8/QpxtcTPXRljhIoLt/bJakDmD4xJ/4QlttRQbaFzsm0sV/Cjfg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1725715166; x=1725801566; bh=AHNYkEBQETk14BGNuB2o6YpassTo 8vcfotHjGeZL3I0=; b=HW0msrYbQaNT1KIecgWuJ4MKfRNHohbk3Q544aSVNWYh ykozVPkb/o5uimBQ+Rw0SbuLpTVls8Rxtu7KcZ+6KRKNvFCIsNheiCG9tZBUa9FY mMc0q7dfAGoqmQDCufGRWNVA+10n/d3eH3O3ab1ebZZrgm/GiGPXYEkWa2Mge4qT 6Nr5qz/fCAPuV0xeMLxrBwkr5aM2X4sSmx2r883HqVgBg354REj9jsj97w7WXYtA geF5MOBMosFr1YuB46/HIOaFcHvaK444qb7ZCOmwr878BHnfa3YgfitV5PD69z8+ Pk9wcrReDudVElARbGW9pb+C8vudRJm6ndN3jZm97g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeifedgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhm rdhfmheqnecuggftrfgrthhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgf dugfdvgeekjeejuddtheehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepuddpmh houggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthes fhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 7 Sep 2024 09:19:25 -0400 (EDT) Date: Sat, 7 Sep 2024 14:19:24 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: Loader needs to be updated message Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <4DC8866B-BEF1-4D53-962F-3B7F93232A7E.ref@yahoo.com> <4DC8866B-BEF1-4D53-962F-3B7F93232A7E@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4DC8866B-BEF1-4D53-962F-3B7F93232A7E@yahoo.com> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.76 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.963]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; RWL_MAILSPIKE_VERYGOOD(-0.20)[103.168.172.156:from]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.156:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4X1DG62SHvz3xK0 hello again, On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: > >What shows if you do the likes of (showing an amd64 context example): > ># ls -lah /boot/efi/efi/*/* >-r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi >-rwxr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/FREEBSD/loader.efi > >If one is old, then it is probably the one actually being used. >(The name bootx64.efi is amd64 specific: other platforms use >other names.) > >In such a case, you might need something like: > ># cp -a /boot/loader.efi /boot/efi/efi/BOOT/bootx64.efi I have the same issue in a completely different context: 1. amd64 not arm64 2. a vm running in bhyve, not baremetal 3. the host is 15.0-CURRENT #0 n270917-5dbf886104b4 amd64 1500019 1500019 zfs-on-root built July 4th. 4. the guest is 13.4-STABLE stable/13-n258323-e7b4f6e0c064 amd64 1304500 1304500 zfs-on-root 5. on the guest :- % gpart list | grep -Ew '(Name|efi)' 1. Name: vtbd0p1 2. Name: vtbd0p2 3. Name: vtbd0p3 1. Name: vtbd0 on the guest, there is no ESP in this case, no bootx64.efi, /boot/efi is empty After source building to latest stable in the usual way, same error message 'loader needs updating'. Any ideas? --