Fedora Running On Pine64!

[Absurd]

Hi all,

with https://rwmj.wordpress.com/2017/03/18/fe...he-pine64/ I was able to get an aarch64 Fedora image. The Pine64 needs an SPL for DRAM init code, so I did't tried the grubaa64.efi way. With http://git.denx.de/?p=u-boot.git;a=blob;...ME.sunxi64 I was able to build an u-boot-2017.07 and installed it to SD card. From aarch64 image the /boot directory was copied and extlinux/extlinux.conf created. But booting the kernel failed:

Code:

U-Boot SPL 2017.07 (Aug 02 2017 - 13:17:00) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE:  BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000)  *** U-Boot Boot Menu *** NOTICE:  Configuring AXP PMIC NOTICE:  PMIC: fixing DRAM voltage from 1.24V to 1.36V NOTICE:  PMIC: setup successful NOTICE:  SCPI: dummy stub handler, implementation level: 000000 INFO:    BL3-1: Initializing runtime services INFO:    BL3-1: Preparing for EL3 exit to normal world INFO:    BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.07 (Aug 02 2017 - 13:17:00 +0200) Allwinner Technology CPU:   Allwinner A64 (SUN50I) Model: Pine64+ DRAM:  2 GiB MMC:   SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In:    serial Out:   serial Err:   serial Net:   phy interface7 eth0: ethernet@01c30000 starting USB... USB0:   USB EHCI 1.00 USB1:   USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found       scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot:  0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1372 bytes read in 85 ms (15.6 KiB/s) Ignoring unknown command: ui Ignoring malformed menu command:  autoboot Ignoring malformed menu command:  hidden Fedora Boot Options. 1:      Fedora (4.11.10-300.fc26.aarch64) 26 (Twenty Six) 2:      Fedora(4.11.8-300.fc26.aarch64) 3:      Fedora-0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca(0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca) Enter choice: 1:        Fedora (4.11.10-300.fc26.aarch64) 26 (Twenty Six) Retrieving file: /initramfs-4.11.10-300.fc26.aarch64.img 14409584 bytes read in 823 ms (16.7 MiB/s) Retrieving file: /vmlinuz-4.11.10-300.fc26.aarch64 6614427 bytes read in 490 ms (12.9 MiB/s) append: root=UUID=f03cec28-d471-4d67-9d28-bcd2a389c183 rootflags=subvol=root ro console=tty0 rd_NO_PLYMOUTH console=ttyS0,115200n8 e arlycon=uart,mmio32,0x01c28000 LANG=en_US.UTF-8 Retrieving file: /dtb-4.11.10-300.fc26.aarch64/allwinner/sun50i-a64-pine64-plus.dtb 7949 bytes read in 206 ms (37.1 KiB/s) Bad Linux ARM64 Image magic! 2:      Fedora(4.11.8-300.fc26.aarch64) Retrieving file: /initramfs-4.11.8-300.fc26.aarch64.img 14376152 bytes read in 830 ms (16.5 MiB/s) Retrieving file: /vmlinuz-4.11.8-300.fc26.aarch64 6613757 bytes read in 499 ms (12.6 MiB/s) Bad Linux ARM64 Image magic!append: root=UUID=f03cec28-d471-4d67-9d28-bcd2a389c183 rootflags=subvol=root ro console=tty0 rd_NO_PLYMOUTH console=ttyS0,115200n8 e arlycon=uart,mmio32,0x01c28000 LANG=en_US.UTF-8 Retrieving file: /dtb-4.11.8-300.fc26.aarch64/allwinner/sun50i-a64-pine64-plus.dtb 7949 bytes read in 214 ms (36.1 KiB/s) Bad Linux ARM64 Image magic! 3:      Fedora-0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca(0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca) Retrieving file: /initramfs-0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca.img 37100644 bytes read in 1925 ms (18.4 MiB/s) Retrieving file: /vmlinuz-0-rescue-1f7b0ffbc2e84e5395b96acd4c9e00ca 6613757 bytes read in 482 ms (13.1 MiB/s) append: root=UUID=f03cec28-d471-4d67-9d28-bcd2a389c183 rootflags=subvol=root ro console=tty0 rd_NO_PLYMOUTH console=ttyS0,115200n8 e arlycon=uart,mmio32,0x01c28000 Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Found U-Boot script /boot.scr 2 bytes read in 56 ms (0 Bytes/s) ## Executing script at 4fc00000 Wrong image format for "source" command SCRIPT FAILED: continuing... USB device 0: unknown device BOOTP broadcast 1 BOOTP broadcast 2

Why do I get "Bad Linux ARM64 Image magic!"?