Derek Atkins
2016-03-03 20:51:16 UTC
Hi,
I'm trying to run F23 on a Wandboard Quad, but it's not booting. It
hangs after the "Starting kernel" output.
I followed the instructions at
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Wandboard_.28Freescale_i.MX6.29
starting from Fedora-Minimal-armhfp-23-10-sda.raw.xz I installed the
image, then copied in the SPL and u-boot.img. But when I try to boot my
wandboard I get:
U-Boot SPL 2015.07 (Sep 12 2015 - 11:53:19)
U-Boot 2015.07 (Sep 12 2015 - 11:53:19 +0000)
CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
Reset cause: POR
Board: Wandboard rev C1
I2C: ready
DRAM: 2 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
518 bytes read in 49 ms (9.8 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-23-10 Boot Options.
1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl)
Enter choice: 1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl)
Retrieving file: /initramfs-4.2.3-300.fc23.armv7hl.img
38958034 bytes read in 1833 ms (20.3 MiB/s)
Retrieving file: /vmlinuz-4.2.3-300.fc23.armv7hl
5811776 bytes read in 307 ms (18.1 MiB/s)
append: enforcing=0 ro root=UUID=b2c019d9-2401-4a22-9a40-36a92a00cdfe
Retrieving file: /dtb-4.2.3-300.fc23.armv7hl/imx6q-wandboard.dtb
30792 bytes read in 1235 ms (23.4 KiB/s)
Kernel image @ 0x11000000 [ 0x000000 - 0x58ae40 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Loading Ramdisk to 2dad8000, end 2ffff3d2 ... OK
Loading Device Tree to 2dacd000, end 2dad7847 ... OK
Starting kernel ...
And then the system just sits and hangs.. Is this a known problem?
I tried with two different SD cards and both fail.
I could certainly revert back to F22, but why start 6-months behind?
-derek
I'm trying to run F23 on a Wandboard Quad, but it's not booting. It
hangs after the "Starting kernel" output.
I followed the instructions at
https://fedoraproject.org/wiki/Architectures/ARM/F23/Installation#For_the_Wandboard_.28Freescale_i.MX6.29
starting from Fedora-Minimal-armhfp-23-10-sda.raw.xz I installed the
image, then copied in the SPL and u-boot.img. But when I try to boot my
wandboard I get:
U-Boot SPL 2015.07 (Sep 12 2015 - 11:53:19)
U-Boot 2015.07 (Sep 12 2015 - 11:53:19 +0000)
CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
Reset cause: POR
Board: Wandboard rev C1
I2C: ready
DRAM: 2 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
518 bytes read in 49 ms (9.8 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-23-10 Boot Options.
1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl)
Enter choice: 1: Fedora-Minimal-armhfp-23-10 (4.2.3-300.fc23.armv7hl)
Retrieving file: /initramfs-4.2.3-300.fc23.armv7hl.img
38958034 bytes read in 1833 ms (20.3 MiB/s)
Retrieving file: /vmlinuz-4.2.3-300.fc23.armv7hl
5811776 bytes read in 307 ms (18.1 MiB/s)
append: enforcing=0 ro root=UUID=b2c019d9-2401-4a22-9a40-36a92a00cdfe
Retrieving file: /dtb-4.2.3-300.fc23.armv7hl/imx6q-wandboard.dtb
30792 bytes read in 1235 ms (23.4 KiB/s)
Kernel image @ 0x11000000 [ 0x000000 - 0x58ae40 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Loading Ramdisk to 2dad8000, end 2ffff3d2 ... OK
Loading Device Tree to 2dacd000, end 2dad7847 ... OK
Starting kernel ...
And then the system just sits and hangs.. Is this a known problem?
I tried with two different SD cards and both fail.
I could certainly revert back to F22, but why start 6-months behind?
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
***@MIT.EDU PGP key available
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
***@MIT.EDU PGP key available