Re: No valid device tree blob found!

2024-11-08 Thread Alexander Leidinger
Am 2024-11-08 14:27, schrieb Warner Losh: On Fri, Nov 8, 2024, 12:34 AM Alexander Leidinger wrote: Am 2024-11-08 05:46, schrieb Warner Losh: OK. I'm confused... but no matter. Three more things to help... (1) kenv after boot with a fixed kernel COLUMNS="100" LINES="31" acpi.oem="BOCHS " ac

Re: No valid device tree blob found!

2024-11-08 Thread Dave Cottlehuber
On Thu, 7 Nov 2024, at 22:41, Alexander Leidinger wrote: > Am 2024-11-07 20:59, schrieb Warner Losh: > >> >> >> On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger >> wrote: >>> Am 2024-11-02 17:08, schrieb Warner Losh: >>> On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger

Re: No valid device tree blob found!

2024-11-08 Thread Warner Losh
On Fri, Nov 8, 2024, 12:34 AM Alexander Leidinger wrote: > Am 2024-11-08 05:46, schrieb Warner Losh: > > OK. I'm confused... but no matter. > > Three more things to help... > (1) kenv after boot with a fixed kernel > > > COLUMNS="100" > LINES="31" > acpi.oem="BOCHS " > acpi.revision="2" > acpi.rs

Re: No valid device tree blob found!

2024-11-08 Thread Alexander Leidinger
Am 2024-11-08 05:46, schrieb Warner Losh: OK. I'm confused... but no matter. Three more things to help... (1) kenv after boot with a fixed kernel COLUMNS="100" LINES="31" acpi.oem="BOCHS " acpi.revision="2" acpi.rsdp="0x0006385c0018" acpi.rsdt="0x" acpi.xsdt="0x0006385

Re: No valid device tree blob found!

2024-11-07 Thread Warner Losh
OK. I'm confused... but no matter. Three more things to help... (1) kenv after boot with a fixed kernel (2) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn (3) sudo efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut Warner On Thu, Nov 7, 2024 at 2:41 PM Alexand

Re: No valid device tree blob found!

2024-11-07 Thread Alexander Leidinger
Am 2024-11-07 20:59, schrieb Warner Losh: On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger wrote: Am 2024-11-02 17:08, schrieb Warner Losh: On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger wrote: Am 2024-10-30 22:11, schrieb Alexander Leidinger: WARNING! Trying to fire up the kernel

Re: No valid device tree blob found!

2024-11-07 Thread Warner Losh
On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger wrote: > Am 2024-11-02 17:08, schrieb Warner Losh: > > > > On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger > wrote: > > Am 2024-10-30 22:11, schrieb Alexander Leidinger: > > > WARNING! Trying to fire up the kernel, but no device tree blob foun

Re: No valid device tree blob found!

2024-11-06 Thread Alexander Leidinger
Am 2024-11-02 17:08, schrieb Warner Losh: On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger wrote: Am 2024-10-30 22:11, schrieb Alexander Leidinger: WARNING! Trying to fire up the kernel, but no device tree blob found! For anyone interested, I opened https://bugs.freebsd.org/bugzilla/sho

Re: No valid device tree blob found!

2024-11-02 Thread Alexander Leidinger
Am 2024-11-02 17:08, schrieb Warner Losh: On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger wrote: Am 2024-10-30 22:11, schrieb Alexander Leidinger: WARNING! Trying to fire up the kernel, but no device tree blob found! For anyone interested, I opened https://bugs.freebsd.org/bugzilla/sho

Re: No valid device tree blob found!

2024-11-02 Thread Warner Losh
On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger wrote: > Am 2024-10-30 22:11, schrieb Alexander Leidinger: > > > WARNING! Trying to fire up the kernel, but no device tree blob found! > > For anyone interested, I opened > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493 for this. > Yea.

Re: No valid device tree blob found!

2024-11-02 Thread Alexander Leidinger
Am 2024-10-30 22:11, schrieb Alexander Leidinger: WARNING! Trying to fire up the kernel, but no device tree blob found! For anyone interested, I opened https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493 for this. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PG

Re: No valid device tree blob found!

2024-10-31 Thread Paul Mather
543 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 t

Re: No valid device tree blob found!

2024-10-31 Thread Alexander Leidinger
y 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 i

RE: No valid device tree blob found!

2024-10-31 Thread Mark Millard
ooting [/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? . . .

No valid device tree blob found!

2024-10-30 Thread Alexander Leidinger
Hi, 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! WA

Re: FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!

2017-04-30 Thread Mark Millard
: >>>> acpi0: Power Button (fixed) >>>> acpi0: Sleep Button (fixed) >>> >>> ACPI is not fully supported on arm64. >> >> Good to know. Thanks. >> >> But the messages: >> >> No valid device tree blob found! >> WARN

Re: FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!

2017-04-30 Thread Andrew Turner
d) >> >> ACPI is not fully supported on arm64. > > Good to know. Thanks. > > But the messages: > > No valid device tree blob found! > WARNING! Trying to fire up the kernel, but no device tree blob found! > > were well before the acpi0 messages so I'd

Re: FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!

2017-04-30 Thread Mark Millard
On 2017-Apr-30, at 1:57 AM, Andrew Turner wrote: >> On 30 Apr 2017, at 04:29, Mark Millard wrote: >> ... >> acpi0: >> acpi0: Power Button (fixed) >> acpi0: Sleep Button (fixed) > > ACPI is not fully supported on arm64. Good to know. Thanks. But the messag

Re: FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!

2017-04-30 Thread Andrew Turner
> On 30 Apr 2017, at 04:29, Mark Millard wrote: > ... > acpi0: > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) ACPI is not fully supported on arm64. Andrew ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/li

FYI: FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw under qemu-system-aarch64 on odroid-c2 under UbuntuMate : No valid device tree blob found!

2017-04-29 Thread Mark Millard
oting [/boot/kernel/kernel]... No valid device tree blob found! WARNING! Trying to fire up the kernel, but no device tree blob found! . . . generic_timer0: irq 29,30,27 on acpi0 panic: Attempt to copy invalid resource id: 29 In full detail: >> FreeBSD EFI boot block Loader