[Bug 246552] aarch64 ACPI detection fails on some platforms

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon May 25 19:33:40 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246552

--- Comment #6 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
(In reply to Greg V from comment #0)

I've tried https://github.com/pftf/RPi4 v1.13 and v1.7
materials and have never gotten any output from the
FreeBSD loader (serial console or HDMI display). If I
leave it that way the UEFI watchdog eventually reboots
the RPi4 so it tries again. So I do not get close to
testing how the kernel behaves. No combination of
UEFI settings and RPi4 config.txt settings that I've
tried has behaved differently. (My context is based
on FreeBSD head -r360311 via a non-debug build.)

For reference: I've had no trouble with booting NetBSD
and see its loader output just fine. (Same
https://github.com/pftf/RPi4 v1.13 materials used.)
(I've not tried the new hybrid gpt/mbr based content
for NetBSD current's Generic 64-bit download from
armbsd.org yet. It was still just MBR-based when I
tried it.)


Separately, if I understand what has happened in LX2K
testing, it turned out that the LX2K did not need the
"has_acpi = true" change and is not an example context
for ACPI detection failure. (Comment 5's result, if I
understand right.)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-acpi mailing list