FreeBSD on Layerscape/QorIQ LX2160X

[greg at unrelenting.technology]

May 18, 2020 7:11 PM, "Dan Kotowski" <dan.kotowski at a9development.com> wrote:

>>>>>> The 12.1 aarch64 memstick installer iamge fails out trying to mount the UFS partition and
>> drops into the mountroot> shell with error 19. Listing GEOM managed disk devices returned an empty
>> list.
>>>>> 
>>>>> What devices does the boot log show? No xhci I guess, how about pci, sdhci?
>>>> 
>>>> Does this answer your question?
>> https://gist.github.com/agrajag9/ce1107a1962283b64205bc8f35123a5c
>>>> If not, I'll happily run what's needed to get you something better.
>>> 
>>> No, the interesting part is the kernel boot log (dmesg) – the one where you saw the mountroot
>> prompt!
>> 
>> Better? https://gist.github.com/agrajag9/9a69b5baff70c8c1040fabeebd037214
>> 
>> Oh, well that explains the lack of devices:
>> 
>> Using DTB provided by EFI
>> 
>> Try choosing ACPI in the UEFI setup menu if that's available.
>> And/or setting kern.cfg.order=acpi in the FreeBSD loader menu / /boot/loader.conf
> 
> I couldn't find any options regarding ACPI in the UEFI menus, so I tried using `set
> kern.cfg.order=acpi` but that still failed in the same way.
> 
> https://gist.github.com/agrajag9/2fa73fc21bff10c9bee9eba810ea283d

Same as in it still says "using DTB"?

I wonder if that's the same weirdness I saw on the RPi4,
FreeBSD failing acpi_find_table(ACPI_SIG_SPCR) even though the SPCR table
is present and deciding we don't have ACPI..

You could try my current kernel which has has_acpi hardcoded to true
(extract into the root of the memstick's ufs partition):

https://send.firefox.com/download/c3d69444ce92d3cf/#AuYrYtDvJWNYbEeJWRX4fA