On Thu, Sep 21, 2017 at 03:19:12PM -0500, Jeremy Linton wrote: > Hi, > > On 09/18/2017 02:18 PM, Konrad Rzeszutek Wilk wrote: > > Hey, > > > > The HiKey960 is one of the supported list of devices per (https://fedoraproject.org/wiki/Architectures/ARM?rd=Architectures/AArch64) where it mentions that the 96Boards. > > > > But I am not finding any docs on how to install? > > I don't have a 960, but I've been running fedora on the older hikey. My > suggestion is to use the prebuilt binaries install process to get a valid > uefi image running on the machine. > > http://snapshots.linaro.org/reference-platform/embedded/morty/hikey960/latest/rpb/bootloader/ > > Really, you should only need to flash the ptable (emmc partition table), > xloader/iloader, and fip.bin (uefi/armtf image). Then from that you _SHOULD_ > be able to download one of the fedora server/netboot images boot it and > install fedora like you would on any generic PC with uefi. OK, so I think you are saying extract: Fedora-Everything-netinst-aarch64-27-20170912.n.0.iso: /TRANS.TBL ./Fedora-Legal-README.txt ./boot.catalog ./LICENSE ./EFI ./EFI/BOOT ./EFI/BOOT/BOOTAA64.EFI ./EFI/BOOT/grub.cfg ./EFI/BOOT/TRANS.TBL ./EFI/BOOT/mmaa64.efi ./EFI/BOOT/fonts ./EFI/BOOT/fonts/TRANS.TBL ./EFI/BOOT/fonts/unicode.pf2 ./EFI/BOOT/grubaa64.efi ./images ./images/TRANS.TBL ./images/efiboot.img ./images/pxeboot ./images/pxeboot/TRANS.TBL ./images/pxeboot/initrd.img ./images/pxeboot/vmlinuz ./images/install.img from https://fedoraproject.org/wiki/Test_Results:Fedora_27_Branched_20170912.n.0_Installation?rd=Test_Results:Current_Installation_Test , then create an DOS partition image, put in the contents of that whole thing in there (456M), modify the grub.cfg to use the serial console (and VNC?), and then kick it off. .. But that seems a bit silly - why not just have pre-created images (boot and system.img) that could be loaded directly and have a basic install? > The remainder of the images (boot/system/etc) would just be overwritten by > the fedora install anyway. > > Will it work? No idea! The aarch64 fedora installers use basically upstream > grub/kernel/etc trees so linaro "workarounds" for machine/firmware problems > may not be in fedora. I intend to encourage more "standards" compliance with > regard to the UEFI images linaro ships when i'm at connect next week. > > Sorry, not be be more helpful. > > > > > The Linaro images are rootfs ones that would be loaded using fastboot (after a lot of pain of changing the boot to UEFI) and loading the right Android type images on the box. > > _______________________________________________ > > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
