[fedora-arm] Failure to retrieve kernel

Peter Robinson

2016-04-27 16:24:36 UTC

Post by David Jones
I am a little confused with the following, just tried
Fedora-Minimal-armhfp-24-20160422.n.0 on a Utilite-pro

I believe there's issues with the utilite in general. The upstream
support is truly terrible so it's quite possible it doesn't work
currently at all. The patches we have to try to support it at best
support 1 eth, mmc, SATA and serial console. I have one to try and
improve the situation but I've not had the time to do so.

Peter

Post by David Jones
Using U-Boot SPL 2016.03 (Apr 09 2016 - 14:33:27)
Trying to boot from MMC
U-Boot 2016.03 (Apr 09 2016 - 14:33:27 +0000)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: CM-FX6
I2C: ready
DRAM: 2 GiB
NAND: 0 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2
MiB
Display: HDMI (1024x768)
Distorted logo
Using
U-Boot SPL 2016.03 (Apr 19 2016 - 15:07:05)
Trying to boot from MMC
U-Boot 2016.03 (Apr 19 2016 - 15:07:05 +0000)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: CM-FX6
I2C: ready
DRAM: 2 GiB
NAND: 0 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2
MiB
Display: HDMI (1024x768)
In: serial
Out: vga
Err: vga
PCB: 1.0
Net: FEC
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1: USB EHCI 1.00
scanning bus 1 for devices... 2 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
mmc2 is current device
Scanning mmc 2:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
558 bytes read in 45 ms (11.7 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-24-20160422.n.0 Boot Options.
1: Fedora-Minimal-armhfp-24-20160422.n.0 (4.5.1-300.fc24.armv7hl)
Enter choice: 1: Fedora-Minimal-armhfp-24-20160422.n.0
(4.5.1-300.fc24.armv7hl)
Retrieving file: /initramfs-4.5.1-300.fc24.armv7hl.img
40016290 bytes read in 1984 ms (19.2 MiB/s)
Skipping Fedora-Minimal-armhfp-24-20160422.n.0 (4.5.1-300.fc24.armv7hl) for
failure retrieving kernel
SCRIPT FAILED: continuing...
Found U-Boot script /boot.scr
2 bytes read in 40 ms (0 Bytes/s)
## Executing script at 17e00000
Wrong image format for "source" command
SCRIPT FAILED: continuing...
FEC Waiting for PHY auto negotiation to complete.......user interrupt!
BOOTP broadcast 1
extlinux.conf contains
# extlinux.conf generated by appliance-creator
ui menu.c32
menu autoboot Welcome to Fedora-Minimal-armhfp-24-20160422.n.0. Automatic
boot in # second{,s}. Press a key for options.
menu title Fedora-Minimal-armhfp-24-20160422.n.0 Boot Options.
menu hidden
timeout 20
totaltimeout 600
label Fedora-Minimal-armhfp-24-20160422.n.0 (4.5.1-300.fc24.armv7hl)
kernel /vmlinuz-4.5.1-300.fc24.armv7hl
append ro root=UUID=2bd7ab38-4655-40a2-bbe0-f2f83feb2b4f
console=ttymxc3,115200
fdtdir /dtb-4.5.1-300.fc24.armv7hl/
initrd /initramfs-4.5.1-300.fc24.armv7hl.img
The boot partition does contain the vmlinuz-4.5.1-300.fc24.armv7hl
I tried the same on a cuboxi-4pro, the system boots and generates output on
the serial connection, no problems with ssh either.
Regards
David
_______________________________________________
arm mailing list