Please excuse my ignorance as I'm really an HPC researcher working on building a small odroid-c2 cluster for parallel scaling research. You're correct that the kernel should be working out of the box and I don't believe that is my issue. It seems that u-boot isn't cooperating. I flashed the minimal image (https://download.fedoraproject.org/pub/fedora-secondary/releases/28/Spins/aarch64/images/Fedora-Minimal-28-1.1.aarch64.raw.xz) to the eMMC card and then tried to install u-boot according to these instructions https://wiki.odroid.com/odroid-c2/software/building_u-boot for the provided sd_fusing.sh. This should be adding the u-boot binaries to the beginning of the card; however, when I power the board on I simply get a solid blue kernel LED which seems to suggest that u-boot is starting but unable to boot the kernel. I was able to find an older fedora 25 image using a modified 3.14 kernel that boots so I'm attempting to go through the upgrade process for this currently. On 07/08/2018 08:05 AM, Peter Robinson wrote: > On Sat, Jul 7, 2018 at 10:49 PM, Dr. Zenzic <dr.zenzic@xxxxxxxxx> wrote: >> Hello All, >> >> Has anyone had any luck getting Fedora 28 to work on the Odroid C2? > I've had a number of reports it works just fine. I don't have a device > based on the same chipset to be able to confirm this though. > >> I've tried downloading the Fedora 28 Server aarch.raw.xz image which i >> put onto my sd card. I then moved the Archlinux aarch64 boot parition >> into boot along with the lib/modules and lib/firmware folders from >> Archlinux. This has been to no avail. I'm working on building the >> hardkernel kernel myself now but have never actually compiled a kernel >> myself so I'm not sure what I fully need to get the Fedora rootfs to >> boot with the kernel. > The Fedora kernel should work just fine so I have no idea why you > would even do anything you've attempted above. > >> If anyone has some guidance or a nice writeup on getting a bootable >> kernel recognized by Fedora on the Odroid C2 that would be greatly >> appreciated. > The only thing you should have to do is deal with the U-Boot side of > things, I believe that there's a need for a signed binary blob for the > early part of u-boot and you can use that in combination with the > Fedora build u-boot bit to boot the device but I've not got the exact > details. You shouldn't have to modify the kernel except possibly if > you want accelerated graphics but given you mention the Server image I > suspect that's not the case. > > Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx/message/ND2LJNO5RGU3SZL75LS3QUKONZUV5LH5/
