Hi,
the latest Tumbleweed update killed my cubox-i boot process. I get now:
## Error: "bootcmd_firstboot" not defined
## Error: "bootcmd_firstboot" not defined
## Error: "bootcmd_firstboot" not defined
=> printenv
[snipped]
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target};
done
boot_targets=mmc0 usb0 pxe dhcp
target=firstboot
[snipped]
Running manually "run mmc_boot" leads to:
=> run mmc_boot
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2756 bytes read in 35 ms (76.2 KiB/s)
## Executing script at 12000000
switch to partitions #0, OK
mmc0 is current device
7318304 bytes read in 515 ms (13.6 MiB/s)
ext4fs_devread read outside partition 2643393156
38144 bytes read in 173 ms (214.8 KiB/s)
Kernel image @ 0x10800100 [ 0x000000 - 0x6fab20 ]
## Loading init Ramdisk from Legacy Image at 14800100 ...
Image Name: Initrd
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 67347803 Bytes = 64.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...
Any hints how to solve this problem?
--
Tom
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
