Fedora Running On Pine64!
#21
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
  Reply
#22
(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.
  Reply
#23
(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
  Reply
#24
(08-20-2017, 07:43 PM)KrYpToNiTe Wrote: 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.
  Reply
#25
(07-20-2017, 10:23 PM)cztian Wrote: 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
If I am wrong please correct my content , thank !



1. Use Pine64 Running Ubuntu 16.04 Web Server ( LAMP )

2. Use Pine64 Running Official Android 6  for Media player
3. Use Pine64 Running Volumio Digital Audio Player





  Reply
#26
(09-09-2017, 08:37 AM)joe Wrote:
(07-20-2017, 10:23 PM)cztian Wrote: 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.
  Reply
#27
For pre-release Fedora 27 support, see this thread: https://forum.pine64.org/showthread.php?tid=5314
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Manjaro arm on pine64+ roel 2 173 10-19-2019, 05:13 AM
Last Post: roel
  +PINEBOOK Fedora 30 on Pinebook sdgathman 0 113 08-14-2019, 11:41 AM
Last Post: sdgathman
  Volumio for PINE64 Released mikelangeloz 11 6,513 03-22-2019, 09:25 AM
Last Post: llungster
  I2S Audio patches for Pine64+ uploaded to GitHub ramstadt 1 258 01-19-2019, 11:31 AM
Last Post: ramstadt
  Pine64: Minimal SDL config Max11 3 512 01-04-2019, 03:47 PM
Last Post: Max11
  Fedora 27 on Pine64 gregjo 18 7,166 01-02-2019, 10:42 PM
Last Post: heatfanjohn
  Official build procedure of ayufan pine64 r.tanaka 0 577 08-21-2018, 10:54 PM
Last Post: r.tanaka
  DKMS on kernel 3.10.107-pine64 obrienmd 5 707 06-21-2018, 05:45 PM
Last Post: evilbunny
  Programming languages support under PINE64 baryluk 5 3,121 03-09-2018, 01:52 AM
Last Post: kaokaobang
  Gentoo for pine64 - longsleep kernel incoherent 0 828 12-09-2017, 08:14 AM
Last Post: incoherent

Forum Jump:


Users browsing this thread: 1 Guest(s)