Date: Thu, 31 Oct 2024 20:50:46 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Mark Millard <marklmi@yahoo.com> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: No valid device tree blob found! Message-ID: <99bc07ade06a2b7ddfe6990fb59dcaea@Leidinger.net> In-Reply-To: <AA3E1F57-19BD-49DB-A70A-E762DBE09540@yahoo.com> References: <AA3E1F57-19BD-49DB-A70A-E762DBE09540.ref@yahoo.com> <AA3E1F57-19BD-49DB-A70A-E762DBE09540@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_2f1a17805c41aa45fff184e70014d55f Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed 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=0x1000 > > /etc/hostid size=0x25 > > 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. It doesn't boot at all. It hangs after this message. The previous BE boots just fine, so something is broken. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_2f1a17805c41aa45fff184e70014d55f Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmcj36cACgkQEg2wmwP4 2IZLGw//fWyi+H16+WFaRXN2jLSDPx1e8BijQTuLSrF9Q6EY4qfHbJIU7uKdUa/L 3jSheSpFW6skQ9apMRfVoWee2uwSKrRNNeGXdHHr9kFua9xiJTczjq/fVBgAT1YE EN+r49n7rTO7HsoyXGgzwwgvn9iu9uxrJNEysHOqpVc6/ZqptKJiB7je5c9jbDeQ sht2otjdfJjSop9aGDIbtN7hwS6nFni3OXNpX3yoIUqPpVZAPBw6pVMlbJUWej6/ 10EB4vh8CVbeIuFbTTl51iRYr7AmNiqxufMBEbIeHkrW12UyWtuW3UP1wPbtRVFx ugY5E3OS9GQX58WL9DnwHzBAufnN5Xa3PJHTj1DlpnrMy5Lbh7Kx5yNAdRsJjLOS 5B7s+cvGDkRqkjBwNhEv6A5DDlxJkWXomb8rQU3eJarCQoNRS3VbP044hkmyEPU4 SgN880f+TqDkRyOxOKfhbjk7uTLbMNnfdJ9MYmW3kGTSTs9v0AUxThTUmD6JXqTo VQzH3wmHV/DsEDOJi+pIvAduVRZrSr4FfbhfYqD4WEPcf7JMHxCEH6NYiwvkafYM 5Z2T2uFJFrbVdjeoMwiefLVaQiGF0h+oiG0WSeACgF/Ic1xXKPhUaJPC/jzGrgvR hxzqlF8tK9aUqvMjx1d4xBb46pzqTfGdW292/owDeqoXXJC9Ne8= =phiE -----END PGP SIGNATURE----- --=_2f1a17805c41aa45fff184e70014d55f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99bc07ade06a2b7ddfe6990fb59dcaea>