by keithspg » Thu Aug 13, 2020 6:53 pm
No, actually, I did a pacman -Syu and I was running the RPi kernel I built using moonman's PKGBUILD.
What is the 'best way' to deal with this conflict with the RPi kernel and uboot?
I started with the aarch64 arch arm image: ArchLinuxARM-rpi-aarch64-latest.tar.gz
then I built the Moonman kernel and installed it and was able to boot and use olverlays and everything normal RPi. I had upgraded it a few times with pacman -Syu then uboot was upgraded last night and that seemed to mess it up. I guess I am looking for clarity on how best to deal with this as I need the RPi kernel for the overlays and such but do not need/want uboot, it is just there on the aarch64 installation file.
I tried removing uboot (pacman -R uboot-raspberrypi), but then it did not boot even though the kernel7.img was still on there and the initramfs-linux.img was as well. So I started over and built a new image then installed the RPi kernel then manually copied the dtbs and off I went.
Is there a way to remove the uboot and install the RPi kernel and have it boot like a normal Pi? I don't mind building the kernel and firmware periodically when I need to, but the rest of the image, I'd like to use the pre-packages aarch64 packages.
Keith