Hello all,
Now that Arch has provided an aarch64 rootfs for our Raspberry Pi's, I decided to switch over to it. It works great on the SD card, however on the 32-bit build I was using a powered external bay with a solid state for the filesystem, and a HDD for storage, I can't seem to get this to work with the 64 bit build, although I'm not sure if it is due to U-boot, the firmware or the kernel loading the necessary modules last. I have udev and systemd in initrd image. The beta firmware for the USB boot support is installed, however on the 32-bit build i was still using the SD card for boot, and mounting it with fstab, I found this faster and more reliable than full USB booting.
Has anyone had any experience with this, or seen this issue? It appears USB is not available until the kernel is fully booted and we are in the userspace, a keyboard/mouse experiences the same behavior. I have never used U-boot prior to aarch64, so I don't know where to begin, and was not very successful finding much about it online.
Is there a reason we must use U-boot in place of the pi bootloader that was used prior to this? Could the mainline kernel be built and used with the cmdline.txt and config.txt like it was previously (I know the manjaro version does this but with a much older kernel)
Thank you for reading, and my apologies if it is a jumbled mess to get through.