On 22/02/2016 16:47, Gordan Bobic wrote: [snip] > As mentioned, my accusation about the installer overwriting the >> onboard kernel was way off mark, although something (chainloading >> EFI?) does. > > The irony of that is killing me right now: > https://lists.fedoraproject.org/pipermail/users/2013-February/431095.html > > It is a long thread, but it does make for an entertaining (if also > at times depressing) read. > > Dumbing down and crippling the text installer was a retarded idea back > when it was done in F11 (and it filtered down into EL6). History > seemingly > hasn't shown it to be any less retarded than it seemed to many of us > back then. > I'll give it a read. >> Anyway, the install does in fact succeed, which is great. I probably >> should have stuck with the LVM partitioning scheme but hey ho, I can >> re run things now that I know UEFI is working. >> >> So, I have a minimal CentOS install with 4.2.0-0.21.el7.aarch64 >> kernel. Great start, thanks to all. >> >> There is no networking so I need to get the installer to recognise the >> nics at install time. > > So installer produces a bootable system, complete with a working kernel? Yes, and no. It produces a bootable kernel. > Does it use grub2 or does it do some magic to boot the kernel straight > from UEFI? > I haven't had the nerve to attempt to bun UEFI to SPI-NOR permanently, so following the install (and any subsequent ones) I've loaded it from u-boot manually and then booted directly from UEFI from there. I can of course automate that I suppose. -- Mike Howard