Re: No valid device tree blob found!
- Reply: Paul Mather : "Re: No valid device tree blob found!"
- In reply to: Mark Millard : "RE: No valid device tree blob found!"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 31 Oct 2024 19:50:46 UTC
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