by CaptainRage » Tue Sep 15, 2020 11:26 am
@Czar: I ended up installing the arm7 version and was really happy that everything worked and went smoothly (having the /boot partition on a microSD card while keeping the /root partition on an external SSD). I even managed to set up a web server and fire up Nextcloud! Then, of course, only to find out after a few hours of struggles that ~ 3 GB is the technical hard limit for file uploads on 32 bit php, which basically defeated the whole purpose.(.............................!!!!!!!!!!!!!!!!!!!!!!)
Now I've been trying to install aarch64, with u-boot, according to the instructions written on the Arch Linux ARM page, for over a day and haven't even managed to get the USB devices to work at boot. Adding pcie_brcmstb to MODULES=() in /etc/mkinitcpio.conf and rebuilding (mkinitcpio -P) does absolutely nothing. Installing and replacing the kernal to linux-aarch64-rc doesn't make any difference whatsoever and overall tiny problems appear and are waiting around every corner.
I guess my best course of action is to swallow my pride, stick to the 32 bit version and try to hold out until the 64 bit Arch Linux ARM system actually becomes usable. It is beyond comprehension how there is no official 64 bit support for the Raspberry Pi 4 at this point.
Thank you for all the information! Hopefully people will get around to make this work better, or at all.
I also don't understand why aarch64 is used with a mainline kernel with u-boot in the official instructions instead of a 64 bit kernel for the Raspberry Pi 4 from the AUR that is pointed out above and apparently is working with the official firmware.