On 27/11/12 23:38, Alexander Graf wrote:
On 27.11.2012, at 22:30, Ciaran Farrell wrote:
On 27.11.2012, at 21:45, Ciaran Farrell wrote:
On 27/11/12 21:42, Alexander Graf wrote:
On 27.11.2012, at 21:30, Ciaran Farrell wrote:
On 27/11/12 19:06, Cristian Rodríguez wrote: > El 26/11/12 18:32, Ciaran Farrell escribió: > >> 6547890 bytes read >> ## Booting kernel from Legacy Image at 02000000 ... >> Image Name: Linux-3.6.0-1.2-cubox >> Created: 2012-10-18 11:13:02 UTC >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 3927856 Bytes = 3.7 MB >> Load Address: 00008000 >> Entry Point: 00008000 >> Verifying Checksum ... OK >> ## Loading init Ramdisk from Legacy Image at 05000000 ... >> Image Name: Initrd >> Created: 2012-11-26 21:06:55 UTC >> Image Type: ARM Linux RAMDisk Image (uncompressed) >> Data Size: 26547826 Bytes = 25.3 MB >> Load Address: 00000000 >> Entry Point: 00000000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> >> And there it hangs... > Now I have the same issue.. wow.. what is going on here.. maybe > something else is needed to actually load this monster initrd.. I > wonder why it is so big... > > > This works for me:
#!/bin/bash
set -x
file=boot/boot.script
echo 'if itest 1$arcNumber == 13905; then' >> $file echo ' setenv kerneladdr 0x2000000' >> $file echo ' setenv ramdiskaddr 0x5000000' >> $file echo 'fi' >> $file echo 'ext2load mmc 0:1 ${kerneladdr} boot/linux.vmx' >> $file echo 'ext2load mmc 0:1 ${ramdiskaddr} boot/initrd.uboot' >> $file echo -n 'setenv bootargs "' >> $file echo 'console=ttyS0,115200 root=/dev/mmcblk0p2"' >> $file echo 'bootm ${kerneladdr} ${ramdiskaddr}' >> $file echo 'boot' >> $file mkopts="-A arm -O linux -a 0 -e 0 -T script -C none"; inputf="boot/boot.script"; result="boot/boot.scr"; if ! mkimage $mkopts -n 'Boot-Script' -d $inputf $result;then echo "Failed to create uboot script image" exit 1 fi
Though methinks agraf will want to belt me on the head for setenv bootargs line. In fairness though, at least the cubox specific stuff is back in its own if box... The setenv gets imported from the .kiwi file. Maybe something's bogus there? What does the actually built boot.script look like? I spoke too soon - it does get past the loading kernel stage where I was bogged down all the time. However, it runs into another problem when booting:
[ 22.782759] sdhci-pltfm: SDHCI platform and OF driver helper [ 22.788442] mmc0: no vmmc regulator found [ 22.792729] ata1: SATA link down (SStatus 0 SControl F300) [ 22.831999] mmc0: SDHCI controller on sdhci-dove.0 [sdhci-dove.0] using DMA [ 22.838965] mmc1: no vmmc regulator found [ 22.881992] mmc1: SDHCI controller on sdhci-dove.1 [sdhci-dove.1] using DMA [ 22.888988] zram: num_devices not specified. Using default: 1 [ 22.894721] zram: Creating 1 devices ... [ 22.899705] TCP: cubic registered [ 22.903062] NET: Registered protocol family 10 [ 22.908219] Key type dns_resolver registered [ 22.912543] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5 [ 22.920176] ThumbEE CPU extension supported. [ 22.924437] PJ4 iWMMXt coprocessor enabled. [ 22.929047] registered taskstats version 1 [ 22.933353] rtc-mv rtc-mv: setting system clock to 2012-11-27 20:44:00 UTC (1354049040) [ 22.941765] Freeing init memory: 264K [ 22.976707] mmc0: new high speed SDHC card at address aaaa [ 22.985304] mmcblk0: mmc0:aaaa SU04G 3.69 GiB [ 22.998024] mmcblk0: p1 p2 setterm: cannot (un)set powersave mode: Invalid argument /usr/sbin/klogconsole [ 0.831911] Including oem partition info file [ 0.926862] Searching for boot device... [ 18.296347] Failed to find boot device ! That means the MBR signature that the kiwi initrd searches for does not match the MBR signature of the SD card you have. Have you booted this system before with the kiwi initrd? Sure - this is the same SD card I have been playing around with all the time. I possibly reformatted at some stage along the way with the YaST
On 27/11/12 21:50, Alexander Graf wrote: partitioner. Would that have fscked it up? Well, the kiwi initrd only works the first time you boot an image. On first boot the MBR signature gets destroyed and a new initrd gets generated that doesn't check for the MBR signature.
[ 18.305829] rebootException: reboot in 120 sec...
The boot.script in the /boot section looks like this:
setenv ramdisk boot/initrd.uboot setenv kernel boot/linux.vmx setenv initrd_high "0xffffffff" setenv fdt_high "0xffffffff" setenv bootargs loader=uboot console=ttyS0,115200n8 showopts ${append} looks good, no? Is $append set? Do reckon the difference between "console=ttyS0,115200" that I'm setting as bootarg and "console=ttyS0,115200n8" that the .kiwi file is setting could be the issue? Hrm - maybe. How about you give it a try and change it in the .kiwi file accordingly? :) I could not believe this, but exactly that change in the Image.kiwi.in file seems to have fixed this for me. sr#143623 created (based on rev11).
It would be great if some other cubox users could test this to see if it works for them too (especially on older versions uboot)...
Alex
-- Ciaran Farrell, Attorney at Law SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org