From nobody Fri Sep 6 22:08:04 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 4X0r2c10gRz5W5M0 for ; Fri, 06 Sep 2024 22:08:08 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh4-smtp.messagingengine.com (fhigh4-smtp.messagingengine.com [103.168.172.155]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4X0r2b47xkz4H6b for ; Fri, 6 Sep 2024 22:08:07 +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=cKPyZxhh; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=ZNJWlCJf; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.155 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-08.internal (phl-compute-08.phl.internal [10.202.2.48]) by mailfhigh.phl.internal (Postfix) with ESMTP id 6252E11401B1 for ; Fri, 6 Sep 2024 18:08:06 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-08.internal (MEProxy); Fri, 06 Sep 2024 18:08:06 -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=1725660486; x=1725746886; bh=XpluExqG9y dzN0+WwIIg5yLVm4wxK0orPlSn/TiG164=; b=cKPyZxhhY4Lo4P5C1aSwBXCkEN oaGVATn3wrOTE1hMEb8d7XBwaTvMRHVDgKcxu4t8xSwRnePK12Od8x41v7CZfyC+ uRwAfWWDEh1IB+uFRfxhgNlcJ1/tq+WhGDJ2qzCO4+iD8Vs7q7dBZJU/stmTe/iq xeqHC2wA8MhEy4cXEVRkyCcQpzANqakuc8BdQim51yRP+VkVhXQYyCHTwGbR94Rq vmao74xW/8xX9dgksDkeN1PVMCsrrrT/YN3j0ketROJBuV4c9+++aSVcFhOhY4F8 To5ZY2CXWUFaWpnMJuqY0Z6HxVhmk+TfBDJUerxbykOIzyGRp4LhV8/0Zkow== 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=1725660486; x=1725746886; bh=XpluExqG9ydzN0+WwIIg5yLVm4wx K0orPlSn/TiG164=; b=ZNJWlCJf8dHzVmuVHxzQC3d6QfUYZ35w77Ych8LCobnt a7xhTyR+VrM2Dhv2E8G50tci+2pafepbyCXrsFEpKCw2b40NF4bODa+Iloo+BagD YNAAvO0gOwwPJH8GzXXFgavqNmFCSsbGFPwo9y48oYLX0zadF79Dpcwoq7Lxcc9I FjdgNEMXG/ckyjX+5YQ/PnSMgNZqhYf9m535xBYL5nXrSBvBM5dkpeEvmDOwof9z kC7VS9mVreVrzjRWJ9Olf91OtvqO/T0qlhmkFEm2mm/JfvKnLRlhrssfc7crC9jr c4CqbMuMbRvVgdJxR0SjBCrKqADHNZeEkO5WEsBo4g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeivddgtdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhm rdhfmheqnecuggftrfgrthhtvghrnhepiedtvdeltdelhfdtgeejledvjeeugfdufeevhe eufeffleevgfefhfduvdeigedunecuffhomhgrihhnpegvfhhirdhinhenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfh hmpdhnsggprhgtphhtthhopedupdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehf rhgvvggsshguqdgtuhhrrhgvnhhtsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 6 Sep 2024 18:08:05 -0400 (EDT) Date: Fri, 6 Sep 2024 23:08:04 +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: <20240907025052.c93cd502dba60910f47a4c00@dec.sakura.ne.jp> 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: <20240907025052.c93cd502dba60910f47a4c00@dec.sakura.ne.jp> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.80 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; 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.155: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.155: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: 4X0r2b47xkz4H6b On Sat, Sep 07, 2024 at 02:50:52AM +0900, Tomoaki AOKI wrote: > >Some additional explanation. > >Before, loader.efi itself could not be kicked directly from UEFI >firmware and needs boot1.efi to kick loader.efi. >In this case, boot code in ESP (uEFI System Partition, formatted with >FAT32, 16 or possibly 12) was completely different >with /boot/loader.efi. > >But now (by default for new UEFI installations), loader.efi can be >kicked directly by UEFI firmware if it is put with proper directory >and name in ESP. This would be what confusing you. With >`make installworld` or usual freebsd-update, everything need updating >in /boot/ should be updated, but nothing in ESP is updated >automatically. This causes what you're experiencing. > >Unfortunately, how loader.efi should be installed in ESP depends on the >environment it is installed. Old or buggy UEFI firmware could force you >installing it as, for example for amd64, BOOT/EFI/BOOTx64.EFI in ESP to >work, but usually BOOT/FreeBSD/loader.efi would work if UEFI boot >manager is properly configured for it. >Some would need ESP on all drives and keep all of them in sync. >Yes, hard to automate properly for every possible situations, >unlike /boot/. Thanks for the explanation. The machine is headless. I grab the console from another pi via a usb <-> ttl cable. I've always associated (probably wrongly) UEFI with graphical-based installs and had to make a boot.config file in / to always use -h in order to get console output down the serial while booting. I'd use 'legacy' on this hardware if possible, rather than UEFI. if it's relevant, in /boot/efi there's, amongst other files, bcm2711-rpi-4-b.dtb bootcode.bin armstub8.bin fixup*.dat start*.elf u-boot.bin ubootefi.var These are all from the ESP from the image FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240725-82283cad12a4-271360 [1] Maybe I need to download latest -current snapshot and copy the contents of its ESP over to update the loader? [1] running bsdinstall [2] doesn't take care of the ESP completely. One has to run bsdinstall to the desired disk, then boot with the original image running, then copy the ESP from the original image to the ESP partition on the new disk, then reboot after unplugging the original image. [2] this was to facilitate a zfs-on-root install. [3] what I am trying to do now is source update the system in-situ in the normal way, on reboot the error popped up in the (ascii) beastie menu. It persists even after following the instructions in man 8 loader.efi --