Open ykla opened 1 year ago
I can confirm this still happens with latest v 1.35
"armv8crypto0: CPU lacks AES instructions" is not a fatal error but just informational. Here is part of a "dmesg -a" from an RPi3B boot using the normal U-Boot style:
gpioled0:
The message is not special to RPi4B's or to EDK2 use at all. Nor does what it reports lead to stopping the boot sequence.
The actual problem is a FreeBSD kernel mishandling of reserving memory: treating a "Legacy master view of Address map" address as if it was already a 'ARM view of the Address Map in "Low Peripheral" mode' address. I.e., no translation between the address spaces is done. (I do not know the details of how this works for ACPI. So, both EDK2 and FreeBSD could have issues for all I know. I'm just reporting the overall misbehavior.)
See [changed to reference better, more detailed recent information instead of the old 2023-Sept report]:
https://lists.freebsd.org/archives/freebsd-arm/2024-January/003652.html
I am new, this is a change suggested to me, that allowed FreeBSD 15.0-CURRENT and GhostBSD-Arm64 14.0-STABLE to boot up. RPI 5 A76 cpu core with Armv9 might support some of these kernel modules from FreeBSD.org aarch64 software. loader.conf.txt rc.cont.txt
edit /boot/loader.conf file disable loading of aesni , geom_eli , and crypto modules. Random thoughts and disable loadable modules
RPI 4 A72 cpu core does not support aesni instruction. RPI 5 A76 cpu core might support armv9 , aesni cpu instruction note: aesni, geom_eli.ko, crypto These three x86-64 kernel modules should not be loaded for aarch64 , arm64 kernel. Just comment them out for now, or change "YES" to "NO" for aesni_load="NO".
or please don't edit /boot/defaults/loader.conf though, that should not be necessary. So do edit /boot/loader.conf file
crypto_load="NO" geom_eli_load="NO" #maybe YES in this option
aesni_load="NO"
attached file names have add '.txt' suffix for /boot/loader.conf and /etc/rc.conf file From the files look like I just needed to set crypto_load="NO" Welcome your comments as what works for you in booting FreeBSD aarch64 on your Arm64 hardware, for the other 2 modules geom_eli_load="NO" ; aesni_load="NO" ; . Fred
I am new, this is a change suggested to me, that allowed FreeBSD 15.0-CURRENT and GhostBSD-Arm64 14.0-STABLE to boot up. RPI 5 A76 cpu core with Armv9 might support some of these kernel modules from FreeBSD.org aarch64 software. loader.conf.txt rc.cont.txt
edit /boot/loader.conf file disable loading of aesni , geom_eli , and crypto modules. Random thoughts and disable loadable modules
RPI 4 A72 cpu core does not support aesni instruction. RPI 5 A76 cpu core might support armv9 , aesni cpu instruction note: aesni, geom_eli.ko, crypto These three x86-64 kernel modules should not be loaded for aarch64 , arm64 kernel. Just comment them out for now, or change "YES" to "NO" for aesni_load="NO".
or please don't edit /boot/defaults/loader.conf though, that should not be necessary. So do edit /boot/loader.conf file
Load geom support
crypto_load="NO" geom_eli_load="NO" #maybe YES in this option
Enable hardware crypto
aesni_load="NO"
attached file names have add '.txt' suffix for /boot/loader.conf and /etc/rc.conf file From the files look like I just needed to set crypto_load="NO" Welcome your comments as what works for you in booting FreeBSD aarch64 on your Arm64 hardware, for the other 2 modules geom_eli_load="NO" ; aesni_load="NO" ; . Fred
It is actually possible to boot FreeBSD 14 and 15 (using the rpi4 image) on a Raspberry Pi 5 without making any changes. Just use https://github.com/worproject/rpi5-uefi. I haven't tested Raspberry Pi 4 though.