It seems a little odd that the installer would put the kernel somewhere other than the target installation disk. Having UEFI on-board I can understand, but shouldn't the boot sequence in this case be: 1) u-boot (on-board) 2) UEFI (wherever u-boot can fetch it from) 3) grub (off the UEFI FAT partition on the target disk) 4) Kernel (/boot partition) Is there a good reason for deviating from this? Gordan On 2016-02-22 10:42, Michael Howard wrote: > On 22/02/2016 05:02, Phong Vo wrote: >> Hi, >> >> The mp30ar0 U-boot has some special memory mapping to accommodate >> 32-bit >> DMA. >> Please download the tar ball again - I've updated the tianocore UHP >> for >> this. > > Ok, your changes have enabled the board's u-boot to chainload EFI > which is great, many thanks. > > The installer though did not install a bootable kernel. It overwrote > the original onboard kernel thus preventing the board booting to it's > default 'OpenLinux'. The kernel that the installer installed appears > to fail due to bad CRC. So, with no disks connected or sdcard inserted > I get ...... > > ramdisk_self=run usb_init; run sf_read_ramdisk && run ram_self > SF: 0:0 probed > ................................................................................ > ................................................................................ > ................................................................................ > ................ > SF: flash read success (16777216 bytes @ 0x1000000) > List of available devices: > vga 80000002 S.O > serial 80000003 SIO stdin stdout stderr > usbkbd0 80000001 SI. > ## Booting kernel from Legacy Image at 82000000 ... > Image Name: Linux-LE > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 13828112 Bytes = 13.2 MiB > Load Address: 00080000 > Entry Point: 00080000 > Verifying Checksum ... Bad Data CRC > ERROR: can't get kernel image! > > ...... instead of booting to onboard OpenLinux. No great loss I guess > :) Obviously, what should have happened at this point after the > install is booting centos on disk. > > Booting with the provided Ubuntu image on sdcard still works. I think > there are recovery instructions somewhere in the docs so I might be > able to recover the original kernel. If not, anybody any idea how to > burn the kernel from the sdcard to this board or better still, how to > get a working centos kernel? > > Cheers,