Fedora Running On Pine64!

[Absurd]

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

[KrYpToNiTe]

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.

[cztian]

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

[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.

Thank you very much! With option "-N" I was able to generate a working initramfs.

[joe]

Install CD: https://dl.fedoraproject.org/pub/alt/sta...s/boot.iso
Kernel Package: kernel-core-4.11.8-300.fc26.aarch64 (Provided by Fedora Install CD)
DTB File: /lib/modules/4.11.8-300.fc26.aarch64/dtb/allwinner/sun50i-a64-pine64-plus.dtb
I haven't tried to install it yet, but the system booted well.
1. Use grubaa64.efi to boot to GRUB prompt.
2.

Code:

set root=hd1,gpt1 (Please change this to your installation source)
linux /images/pxeboot/vmlinuz ip=10.254.254.99::10.254.254.100:255.255.255.0:pine64:eth0:off root=live:http://10.254.254.2:8888/E%3A/fedora/install.img (Please change this to your installation source, and your IP address)
initrd /images/pxeboot/initrd.img
boot

3. Installation begins.

Hi ,

i have the question and don't understand fedora only 13 months updates why you don't use centos7 ?
Centos support time line is very long .

Full Updates  Q4 2020
Maintenance Updates June 30th, 2024

And at least for 2020 years before you don't need to anytime to release new version  .

If running the server not want very quickly to upgrade the new version just need to stable .  

But anyway thank you help pine64

[cztian]

Install CD: https://dl.fedoraproject.org/pub/alt/sta...s/boot.iso
Kernel Package: kernel-core-4.11.8-300.fc26.aarch64 (Provided by Fedora Install CD)
DTB File: /lib/modules/4.11.8-300.fc26.aarch64/dtb/allwinner/sun50i-a64-pine64-plus.dtb
I haven't tried to install it yet, but the system booted well.
1. Use grubaa64.efi to boot to GRUB prompt.
2.

Code:

set root=hd1,gpt1 (Please change this to your installation source)
linux /images/pxeboot/vmlinuz ip=10.254.254.99::10.254.254.100:255.255.255.0:pine64:eth0:off root=live:http://10.254.254.2:8888/E%3A/fedora/install.img (Please change this to your installation source, and your IP address)
initrd /images/pxeboot/initrd.img
boot

3. Installation begins.

Hi ,

i have the question and don't understand fedora only 13 months updates why you don't use centos7 ?
Centos support time line is very long .

Full Updates  Q4 2020
Maintenance Updates June 30th, 2024

And at least for 2020 years before you don't need to anytime to release new version  .

If running the server not want very quickly to upgrade the new version just need to stable .  

But anyway thank you help pine64

But centos doesn't have sun8i-emac support yet.

[gregjo]

For pre-release Fedora 27 support, see this thread: https://forum.pine64.org/showthread.php?tid=5314