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!

From: Mark Millard <markmi_at_dsl-only.net>
Date: Sun, 30 Apr 2017 04:02:26 -0700
On 2017-Apr-30, at 1:57 AM, Andrew Turner <andrew at fubar.geek.nz> wrote:

>> On 30 Apr 2017, at 04:29, Mark Millard <markmi at dsl-only.net> wrote:
>> ...
>> acpi0: <BOCHS BXPCFACP>
>> 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!
WARNING! Trying to fire up the kernel, but no device tree blob found!

were well before the acpi0 messages so I'd expect
that the lack of a "device tree blob" is a separate,
earlier issue, likely to do with the content of:

FreeBSD-12.0-CURRENT-arm64-aarch64-20170420-r317181.raw

My old 2016-Sep. notes showed no such notifications
for the 11-RELEASE attempt I made back then.


(After the acpi0 messages:) I guessed that the "29"s in:

generic_timer0: <ARM Generic Timer> irq 29,30,27 on acpi0
panic: Attempt to copy invalid resource id: 29

were the same "29"s: i.e., that the "resource id" was the
generic_time0: 29 irq number.

But being after the acpi0 messages and after the notice
of a lack of a "device tree blob" may be things are
already messed up by that point --or may be my guess
about the "29"s is just wrong and "resource id" 29
is something else, possibly related to the acpi0
notices.

===
Mark Millard
markmi at dsl-only.net
Received on Sun Apr 30 2017 - 09:02:30 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:11 UTC