-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD boot stuck at armv8crypto0: CPU lacks AES instructions #242
Comments
I can confirm this still happens with latest v 1.35 |
"armv8crypto0: CPU lacks AES instructions" is not a fatal error gpioled0: on ofwbus0 The message is not special to RPi4B's or to EDK2 use at all. The actual problem is a FreeBSD kernel mishandling of reserving See [changed to reference better, more detailed recent information 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. edit /boot/loader.conf file disable loading of aesni , geom_eli , and crypto modules. RPI 4 A72 cpu core does not support aesni instruction. RPI 5 A76 cpu core might support armv9 , aesni cpu instruction or please don't edit /boot/defaults/loader.conf though, that should not be necessary. So do edit /boot/loader.conf file Load geom supportcrypto_load="NO" Enable hardware cryptoaesni_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. |
The text was updated successfully, but these errors were encountered: