Fedora Running On 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.
   

[tllim]

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.

Awesome, I have announced at PINE64 Facebook.

[heatfanjohn]

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.

Sorry for the newbie question, but how do I use this to create an SD card to use on my A64+?

[Gnx]

you can use several programs, win32diskimager, or etcher. you just use one of those programs to burn the image to the sd card.

pine wiki instructions:
http://wiki.pine64.org/index.php/Main_Pa...2F8.1.2F10


win32diskimager:
https://sourceforge.net/projects/win32diskimager/

Etcher:
https://etcher.io/

[pfeerick]

you can use several programs, win32diskimager, or etcher. you just use one of those programs to burn the image to the sd card.

pine wiki instructions:
http://wiki.pine64.org/index.php/Main_Pa...2F8.1.2F10


win32diskimager:
https://sourceforge.net/projects/win32diskimager/

Etcher:
https://etcher.io/

Don't think it's quite that easy Gnx... from what I remember of cztian's commentary on the IRC, the fedora image was on a USB drive, and he basically had a minimal image on the SD card, with something deleted, so that uboot skipped to the USB drive to look for the next boot option... hopefully someone can add a simple step by step, or a basic image that can be used. And maybe also a heads up as to if this worked in the end

And please consider linking to Rufus in the future instead of win32diskimager... as win32diskimager has zero verification abilities, so can't tell you if the medium is faulty. Rufus can at least run a check for bad blocks before it writes the image, and is handy have to have around for general formatting needs also.

[heatfanjohn]

Don't think it's quite that easy Gnx... from what I remember of cztian's commentary on the IRC, the fedora image was on a USB drive, and he basically had a minimal image on the SD card, with something deleted, so that uboot skipped to the USB drive to look for the next boot option... hopefully someone can add a simple step by step, or a basic image that can be used. And maybe also a heads up as to if this worked in the end

I think that this may work for using the Fedora .iso Image to build an SD card for the Pine64:

Well, just write the stuff to the sdcard again (eg. from another system). Eg. use https://github.com/longsleep/build-pine6...ot_only.sh

If you do not want to build it yourself, follow https://github.com/longsleep/build-pine6...sh#L67-L68 for instructions. Also that whole script can be easily adapted to work on another linux system.

Cheers
Simon

[Gnx]

rufus should allow you to burn the image to usb correctly in windows

[cztian]

you can use several programs, win32diskimager, or etcher. you just use one of those programs to burn the image to the sd card.

pine wiki instructions:
http://wiki.pine64.org/index.php/Main_Pa...2F8.1.2F10


win32diskimager:
https://sourceforge.net/projects/win32diskimager/

Etcher:
https://etcher.io/

Don't think it's quite that easy Gnx... from what I remember of cztian's commentary on the IRC, the fedora image was on a USB drive, and he basically had a minimal image on the SD card, with something deleted, so that uboot skipped to the USB drive to look for the next boot option... hopefully someone can add a simple step by step, or a basic image that can be used. And maybe also a heads up as to if this worked in the end

And please consider linking to Rufus in the future instead of win32diskimager... as win32diskimager has zero verification abilities, so can't tell you if the medium is faulty. Rufus can at least run a check for bad blocks before it writes the image, and is handy have to have around for general formatting needs also.

There is only a uboot image on the SD card, and we can use setenv command to change boot order

[heatfanjohn]

Why isn't there a PINE64 target in `fedora-arm-image-installer`?

Code:

 Usage: fedora-arm-image-installer <options>    --image=IMAGE    - xz compressed image file name    --target=TARGET  - target board      [A10-OLinuXino-Lime|A20-OLinuXino-Lime|A20-OLinuXino-Lime2|A20-OLinuXino_MICRO|Bananapi|Bananapro|beaglebone|Cubieboard|Cubieboard2|Cubietruck|Mele_A1000|Mini-X|none|novena|panda|riotboard|trimslice|wandboard_dl|wandboard_quad|wandboard_solo]    --media=DEVICE   - media device file (/dev/[sdX|mmcblkX])    --selinux=ON/OFF - Turn SELinux off/on as needed    --norootpass     - Remove the root password     -y    - Assumes yes, will not wait for confirmation    --version    - Display version and exit Example: fedora-arm-image-installer --image=Fedora-Rawhide.xz --target=panda --media=/dev/mmcblk0 --selinux=OFF

This is from the Fedora ARM Installation Manual:

https://fedoraproject.org/wiki/Architect...ion#Manual

I'm hoping that one of the existing ARM boards may also work for the Pine64 A64+.  Although from my experience with the RaspberryPi and NTC CHIP I know that I need a Linux Device Tree (DTB) for the A64+

I've also downloaded the aarch64 Fedora Workstation image `Fedora-Workstation-armhfp-26-1.5-sda.raw` which from the Fedora ARM Installation Manual appears to be a disk image for an SD card.  I'm going to try to`dd` that image to an SD card and see what I get.

[heatfanjohn]

I downloaded the server ARM image for Fedora 26 `Fedora-Server-armhfp-26-1.5-sda.raw.xz` and uncompressed it.

    unxz Fedora-Server-armhfp-26-1.5-sda.raw.xz

Then thanks to [this SO answer](https://askubuntu.com/questions/69363/mo...isk-device) I was able to mount the various partitions inside this raw image.  For example for the `/boot` partition:

Code:

~/Downloads$ sudo fdisk -lu Fedora-Server-armhfp-26-1.5-sda.raw Disk Fedora-Server-armhfp-26-1.5-sda.raw: 3.5 GiB, 3726639104 bytes, 7278592 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x337b9d3d Device                               Boot   Start     End Sectors  Size Id Type Fedora-Server-armhfp-26-1.5-sda.raw1         2048   61439   59392   29M  c W95 FAT32 (LBA) Fedora-Server-armhfp-26-1.5-sda.raw2 *      61440 1060863  999424  488M 83 Linux Fedora-Server-armhfp-26-1.5-sda.raw3      1060864 2060287  999424  488M 82 Linux swap / Solaris Fedora-Server-armhfp-26-1.5-sda.raw4      2060288 6942719 4882432  2.3G 82 Linux swap / Solaris ~/Downloads$ bc bc 1.06.95 Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'.  512*2048 1048576 ~/Downloads$ sudo losetup -o 1048576 /dev/loop0 Fedora-Server-armhfp-26-1.5-sda.raw  ~/Downloads$ sudo fsck -fv /dev/loop0 fsck from util-linux 2.27.1 fsck.fat 3.0.28 (2015-05-16) Checking we can access the last sector of the filesystem Boot sector contents: System ID "mkfs.fat" Media byte 0xf8 (hard disk)        512 bytes per logical sector       2048 bytes per cluster          4 reserved sectors First FAT starts at byte 2048 (sector 4)          2 FATs, 16 bit entries      30720 bytes per FAT (= 60 sectors) Root directory starts at byte 63488 (sector 124)        512 root directory entries Data area starts at byte 79872 (sector 156)      14809 data clusters (30328832 bytes) 32 sectors/track, 64 heads          0 hidden sectors      59392 sectors total Reclaiming unconnected clusters. /dev/loop0: 15 files, 6505/14809 clusters ~/Downloads$ sudo mount /dev/loop0 /mnt ~/Downloads$ ls -l /mnt total 12948 -rwxr-xr-x 1 root root   50268 Jul  5 18:20 bootcode.bin -rwxr-xr-x 1 root root    4371 Jul  5 18:20 config-64.txt -rwxr-xr-x 1 root root    4214 Jul  5 18:20 config.txt -rwxr-xr-x 1 root root    2581 Jul  5 18:20 fixup_cd.dat -rwxr-xr-x 1 root root    6660 Jul  5 18:20 fixup.dat -rwxr-xr-x 1 root root    9802 Jul  5 18:20 fixup_db.dat -rwxr-xr-x 1 root root    9798 Jul  5 18:20 fixup_x.dat drwxr-xr-x 2 root root    2048 Jul  5 18:20 overlays -rwxr-xr-x 1 root root  360008 Jul  5 18:20 rpi2-u-boot.bin -rwxr-xr-x 1 root root  359744 Jul  5 18:20 rpi3-u-boot.bin -rwxr-xr-x 1 root root  657828 Jul  5 18:20 start_cd.elf -rwxr-xr-x 1 root root 4990532 Jul  5 18:20 start_db.elf -rwxr-xr-x 1 root root 2852356 Jul  5 18:20 start.elf -rwxr-xr-x 1 root root 3935908 Jul  5 18:20 start_x.elf ~/Downloads$

From this it appears that this image is geared for a Raspberry Pi device.

---

The 2nd partition looks promising.

Code:

    Disk Fedora-Server-armhfp-26-1.5-sda.raw: 3.5 GiB, 3726639104 bytes, 7278592 sectors     Units: sectors of 1 * 512 = 512 bytes     Sector size (logical/physical): 512 bytes / 512 bytes     I/O size (minimum/optimal): 512 bytes / 512 bytes     Disklabel type: dos     Disk identifier: 0x337b9d3d     Device                               Boot   Start     End Sectors  Size Id Type     Fedora-Server-armhfp-26-1.5-sda.raw1         2048   61439   59392   29M  c W95 FAT32 (LBA)     Fedora-Server-armhfp-26-1.5-sda.raw2 *      61440 1060863  999424  488M 83 Linux      Fedora-Server-armhfp-26-1.5-sda.raw3      1060864 2060287  999424  488M 82 Linux swap / Solaris      Fedora-Server-armhfp-26-1.5-sda.raw4      2060288 6942719 4882432  2.3G 82 Linux swap / Solaris     ~/Downloads$ ls -l /media/johnma/__boot/     total 185884     drwxr-xr-x. 3 root root     4096 Jul  5 18:15 735cc24f805341718e3aa8125ba1010a     -rw-r--r--. 1 root root        2 Feb 10 16:35 boot.scr     -rw-r--r--. 1 root root   199611 Jun 29 18:39 config-4.11.8-300.fc26.armv7hl     drwxr-xr-x. 2 root root    24576 Jul  5 18:13 dtb-4.11.8-300.fc26.armv7hl     drwxr-xr-x. 2 root root     4096 Jul  5 18:20 extlinux     drwxrwxr-x. 2 root root     4096 Jul  5 18:06 fw     drwxrwxr-x. 2 root root     4096 Jul  5 18:20 grub     -rw-------. 1 root root 55990814 Jul  5 18:19 initramfs-4.11.8-300.fc26.armv7hl.img     -rw-r--r--. 1 root root       24 Jul  5 18:19 klist.txt     drwx------  2 root root    16384 Jul  5 18:06 lost+found     -rw-------. 1 root root  3226489 Jun 29 18:38 System.map-4.11.8-300.fc26.armv7hl     -rw-r--r--. 1 root root  6267680 Jul  5 18:19 uImage     -rw-r--r--. 1 root root  6267680 Jul  5 18:19 uImage-4.11.8-300.fc26.armv7hl     -rw-r--r--. 1 root root 55990878 Jul  5 18:19 uInitrd     -rw-r--r--. 1 root root 55990878 Jul  5 18:19 uInitrd-4.11.8-300.fc26.armv7hl     -rwxr-xr-x. 1 root root  6267616 Jun 29 18:39 vmlinuz-4.11.8-300.fc26.armv7hl

---

The 2.3 GB 4th partition is the root file system of Fedora:

Code:

~/Downloads$ sudo losetup -o 1054867456 /dev/loop3 Fedora-Server-armhfp-26-1.5-sda.raw  ~/Downloads$ ls -l /media//johnma/__ total 12 lrwxrwxrwx.  1 root root    7 Feb 10 11:37 bin -> usr/bin drwxrwxr-x.  2 root root    6 Jul  5 18:06 boot drwxr-xr-x.  4 root root  179 Jul  5 18:15 dev drwxr-xr-x. 96 root root 8192 Jul  5 18:20 etc drwxr-xr-x.  2 root root    6 Feb 10 11:37 home lrwxrwxrwx.  1 root root    7 Feb 10 11:37 lib -> usr/lib drwxr-xr-x.  2 root root    6 Feb 10 11:37 media drwxr-xr-x.  2 root root    6 Feb 10 11:37 mnt drwxr-xr-x.  2 root root    6 Feb 10 11:37 opt drwxrwxr-x.  2 root root    6 Jul  5 18:06 proc dr-xr-x---.  2 root root  114 Jul  5 18:20 root drwxr-xr-x. 18 root root  232 Jul  5 18:13 run lrwxrwxrwx.  1 root root    8 Feb 10 11:37 sbin -> usr/sbin drwxr-xr-x.  2 root root    6 Feb 10 11:37 srv drwxrwxr-x.  2 root root    6 Jul  5 18:06 sys drwxrwxrwt.  7 root root   93 Jul  5 18:20 tmp drwxr-xr-x. 11 root root  131 Jul  5 18:11 usr drwxr-xr-x. 21 root root  277 Jul  5 18:14 var