From nobody Thu Oct 31 20:47:25 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 4XfbfM4GkQz5cMJb for ; Thu, 31 Oct 2024 20:47:39 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.123]) (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 4XfbfM2HCtz4fTM for ; Thu, 31 Oct 2024 20:47:39 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Authentication-Results: mx1.freebsd.org; none Received: from smtpclient.apple (unknown [IPv6:2601:5cf:407e:55c1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 2FA093B713; Thu, 31 Oct 2024 16:47:36 -0400 (EDT) Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3826.200.121\)) Subject: Re: No valid device tree blob found! From: Paul Mather In-Reply-To: <99bc07ade06a2b7ddfe6990fb59dcaea@Leidinger.net> Date: Thu, 31 Oct 2024 16:47:25 -0400 Cc: Mark Millard , Alexander Leidinger Content-Transfer-Encoding: quoted-printable Message-Id: References: <99bc07ade06a2b7ddfe6990fb59dcaea@Leidinger.net> To: Current FreeBSD X-Mailer: Apple Mail (2.3826.200.121) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US] X-Rspamd-Queue-Id: 4XfbfM2HCtz4fTM X-Spamd-Bar: ---- On Oct 31, 2024, at 3:50=E2=80=AFpm, Alexander Leidinger = wrote: > Am 2024-10-31 20:43, schrieb Mark Millard: >> lexander Leidinger wrote on >> Date: Wed, 30 Oct 2024 21:11:52 UTC : >>> I've updated an oracle ampere instance running -current from >>> 2024-09-12-140543 to 2024-10-30-121420 and now I get: >>> ---snip--- >>> Hit [Enter] to boot immediately, or any other key for command = prompt. >>> Booting [/boot/kernel/kernel]... >>> Loading splash ok >>> No valid device tree blob found! >>> WARNING! Trying to fire up the kernel, but no device tree blob = found! >>> ---snip--- >>> I don't see anything in UPDATING about changing the kernel config... >>> what did I miss? >> . . . >> One possibility is this was an ACPI based boot. >> Booting ACPI (such as via EDK2 use with ACPI selected) normally >> produces the messages: >> No valid device tree blob found! >> WARNING! Trying to fire up the kernel, but no device tree blob found! >> I've got a bunch of historical ACPI-based boot logs with that text, >> including this year, not just many prior years. An example >> extraction is: >> . . . >> Loading configured modules... >> /boot/entropy size=3D0x1000 >> /etc/hostid size=3D0x25 >> No valid device tree blob found! >> WARNING! Trying to fire up the kernel, but no device tree blob found! >> ---<>--- >> . . . >> The lack of a device tree is the normal case for ACPI based booting. >> I do find this part of the messaging for an ACPI-based boot >> misleading. >=20 > It doesn't boot at all. It hangs after this message. > The previous BE boots just fine, so something is broken. I get the same thing trying to install FreeBSD/arm64 -CURRENT on a = MacBook Air M2 using UTM. I'm trying to boot = FreeBSD-15.0-CURRENT-arm64-aarch64-20241024-8b2e7da70855-273174-disc1.iso = and it fails to do so. I have a FreeBSD/arm64 14.1-RELEASE VM that runs = under UTM on the same hardware just fine. I guess I just got unlucky = choosing that particular snapshot? Something is broken? Cheers, Paul.