A while ago (around the freeze of FC29) grub2-efi on top of Uboot was proposed as the (potentially) default setup for armhfp too. Unfortunately (IMHO) it did not materialize and I'm searching for the game-breaker.
On buggzilla found a few hints, " we have at least a grub2 <-> kernel bug" (1) among them, they did not make the holdup clear to me.
My investigation so-far:
* It works pretty good with a close to upstream build grub, not with the default gub2 packages. Which makes me believe loading an arm32 kernel as an Portable Executable instead of grub's LoadImage() and StartImage() services may be a game-stopper. NOTE : I understand this is necessary for chain loading efi stubs for secure-boot. IMO this is not the pursued goal here.
* Since kernel patch "efi: libstub/arm: account for firmware reserved memory at the base of RAM" (2) it works on RPI's too (given a "custom" build grub2)
All feedback is appreciated,
Taking a stab at fedora 32 on a R Pi 3A+. Looks like there's missing firmware. Based on the FAQ the wifi should work out of the box but it doesn't seem to be the case:
[ 43.501327] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt failed with error -2
[ 43.501632] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
I do not see this file in: /usr/lib/firmware/brcm. I do see one for model b: "brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt"
Used the following for firmware:
arm-image-installer --image=Fedora-Server-armhfp-32-1.6-sda.raw.xz --target=rpi3 --media=/dev/sdf
Let me know what additional info you might need, and I'm happy to test.
As stated here , in order to use HATs, and overlays in general on
the Raspberry, you have to remove the /boot/dtb symlink.
You know, I'm not an expert. What does this mean? Why do you need to do
that? Why this symlink is here by default? And, there are some
downsides by removing such symlink?
After successfully testing an OpenVPN link on a x86_64, I get the following
error on aarch64, as root:
# nmcli connection import type ovpn file <file>.ovpn
Error: failed to find VPN plugin for ovpn.
Both systems have openvn, NetworkManager-openvpn, and NetworkManager-openvpn-
gnome packages installed.
journalctl -f is completely silent, during this.
The only thing I can think of: the x86_64 server is headless, but has a user
session autologging into a desktop, on the console. The aarch64 VM is also
headless. In both cases I'm ssh-ing in. Maybe something gets started when
there's a desktop login, that's required for this. The only thing I see
running, on the x86_64 server is nm-applet, that surely can't be required.
The x86_64 server desktop login is not a root login, but I can ssh to the
x86_64 server, as root, and install the same ovpn connection without any