Date: Thu, 31 Oct 2024 16:47:25 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Current FreeBSD <freebsd-current@freebsd.org> Cc: Mark Millard <marklmi@yahoo.com>, Alexander Leidinger <Alexander@Leidinger.net> Subject: Re: No valid device tree blob found! Message-ID: <A4439A77-668B-4641-A2A2-EF1BED1074C2@gromit.dlib.vt.edu> In-Reply-To: <99bc07ade06a2b7ddfe6990fb59dcaea@Leidinger.net> References: <AA3E1F57-19BD-49DB-A70A-E762DBE09540.ref@yahoo.com> <AA3E1F57-19BD-49DB-A70A-E762DBE09540@yahoo.com> <99bc07ade06a2b7ddfe6990fb59dcaea@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 31, 2024, at 3:50=E2=80=AFpm, Alexander Leidinger = <Alexander@Leidinger.net> wrote: > Am 2024-10-31 20:43, schrieb Mark Millard: >> lexander Leidinger <Alexander_at_Leidinger.net> 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! >> ---<<BOOT>>--- >> . . . >> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A4439A77-668B-4641-A2A2-EF1BED1074C2>