08-25-2017, 08:08 PM
(08-20-2017, 07:43 PM)KrYpToNiTe Wrote:(08-20-2017, 08:13 AM)Absurd Wrote: Hi heatfanjohn,
so you are not using the Fedora kernel but build your own like me.
I build u-boot 2017.07 and linux 4.9.43 with pine64 patches. Create a new MBR on SD card and three partitions, 1st (1GB) ext4 for /boot, 2nd (615MB) swap and 3rd btrfs for rootfs. The Fedora aarch64 rootfs was extracted with guestfish from virt-builder generated Fedora 26 server image. With my kernel the system boots and is useable.
Now I am trying to replace my kernel with the Fedora kernel. My linux kernel didn't need an initramfs, but the Fedora kernel needs it. The generated initramfs contains mmc_core.ko and sunxi-mmc.ko which is not enough for accessing the rootfs. I think the mmc_block.ko is necessary, but until now I had no success. The initramfs waits endless for the rootfs device, with or without mmc_block.ko module in initramfs.
BR,
Absurd
I was able to boot the 4.12.5-300.fc26.aarch64 fedora kernel on my pine64 with u-boot 2017.07, I rebuilt the initramfs on a qemu aarch64 VM with dracut -f -N. That way it produces a generic initramfs, once booted you can then rebuild it again without the -N so that the initramfs size shrinks back to normal.
You can use the initramfs in Fedora installation iso file