Bug#839595: flash-kernel: Please add support for SolidRun Clearfog
Hi!
Karsten Merker <merker@debian.org> writes:
> is this the environment from mainline u-boot or the environment
> from the original Marvell u-boot? I ask because there are a few
> things that look a bit uncommon to me:
This is a mainline 2016.9 u-boot (clearfog_defconfig)
> - The bootcmd loads the kernel as a zImage but the initrd as a
> uImage, which is a very unusual combination and I am unsure
> whether that could even work properly. The normal case is
> either loading the kernel as a zImage and the initrd as a plain
> initrd image and booting them with bootz, or loading both the
> kernel and the initrd as uImages and booting them with bootm.
Works fine:
| => ext4load mmc 0:2 0x100000 armada-388-clearfog.dtb ; ext4load mmc 0:2 0x800000 vmlinuz-4.7.0-1-armmp ; ext4load mmc 0:2 0x1800000 initrd.img-4.7.0-1-armmp.uimage ; bootz 0x800000 0x1800000 0x100000
| 18060 bytes read in 79 ms (222.7 KiB/s)
| 3699848 bytes read in 237 ms (14.9 MiB/s)
| 15982059 bytes read in 787 ms (19.4 MiB/s)
| ## Loading init Ramdisk from Legacy Image at 01800000 ...
| Image Name: initrd.img-4.7.0-1-armmp
| Image Type: ARM Linux RAMDisk Image (uncompressed)
| Data Size: 15981995 Bytes = 15.2 MiB
| Load Address: 00000000
| Entry Point: 00000000
| Verifying Checksum ... OK
| ## Flattened Device Tree blob at 00100000
| Booting using the fdt blob at 0x100000
| Loading Ramdisk to 0f0c2000, end 0ffffdab ... OK
| Loading Device Tree to 0f0ba000, end 0f0c168b ... OK
|
| Starting kernel ...
With plain initrd:
| => ext4load mmc 0:2 0x100000 armada-388-clearfog.dtb ; ext4load mmc 0:2 0x800000 vmlinuz-4.7.0-1-armmp ; ext4load mmc 0:2 0x1800000 initrd.img-4.7.0-1-armmp ; bootz 0x800000 0x1800000 0x100000
| 18060 bytes read in 79 ms (222.7 KiB/s)
| 3699848 bytes read in 237 ms (14.9 MiB/s)
| 15981995 bytes read in 796 ms (19.1 MiB/s)
| Wrong Ramdisk Image Format
| Ramdisk image is corrupt or invalid
> Is mmc0 an SD card or an EMMC chip? Have you upgraded the system
> from a marvell u-boot to a mainline u-boot or has it been set up
> from scratch with a mainline u-boot? I ask because mainline
> u-boot by default keeps the existing environment on upgrade, so
> if you have upgraded the system from a marvell u-boot to a
> mainline u-boot, you might still have an old non-mainline
> environment.
eMMC chip. as far as I know there was no u-boot shipped on the eMMC
(booting via UART works quite well)
> You could try running "env default -f -a" at the u-boot prompt,
> which would reset your active environment to the default
> environment of the u-boot version you are currently running.
| => env default -f -a
| ## Resetting to default environment
| => printenv
| baudrate=115200
| bootdelay=3
| fdt_high=0x10000000
| initrd_high=0x10000000
|
| Environment size: 80/65532 bytes
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
Reply to: