> Am 14.05.2016 um 17:51 schrieb Thomas Bechtold <[email protected]>:
> 
> Hi,
> 
> I tried again the Cubox-i Tumbleweed image
> (openSUSE-Tumbleweed-ARM-JeOS-cuboxi.armv7l-2016.05.05-Build1.4.raw.xz )
> but it's broken again. This time, I get:
> 
> => run bootcmd
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found U-Boot script /boot.scr
> 2750 bytes read in 34 ms (78.1 KiB/s)
> ## Executing script at 12000000
> switch to partitions #0, OK
> mmc0 is current device
> 7420680 bytes read in 519 ms (13.6 MiB/s)
> 79608549 bytes read in 4776 ms (15.9 MiB/s)
> 38156 bytes read in 306 ms (121.1 KiB/s)
> Kernel image @ 0x10800100 [ 0x000000 - 0x713b08 ]
> ## Loading init Ramdisk from Legacy Image at 14800100 ...
>   Image Name:   Initrd
>   Image Type:   ARM Linux RAMDisk Image (uncompressed)
>   Data Size:    79608485 Bytes = 75.9 MiB
>   Load Address: 00000000
>   Entry Point:  00000000
>   Verifying Checksum ... OK
> ## Flattened Device Tree blob at 14700100
>   Booting using the fdt blob at 0x14700100
>   Using Device Tree in place at 14700100, end 1470c60b
> 
> Starting kernel ...
> 
> [    0.225135] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [    6.376159] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [    6.383309] sr_init: platform driver register failed for SR
> [    6.403448] Unable to find PPMU node
> setterm: cannot (un)set powersave mode: Inappropriate ioctl for device
> [   11.269077] systemd-udevd[247]: could not dup netlink fd: File exists
> [   11.275601] systemd-udevd[247]: could not listen on fds: File exists
> [  169.866174] reboot: Restarting system
> 
> 
> Any hints how to fix it?

I guess the first step would be to boot without the "quiet" option in the 
kernel command line. The system comes up, but reboots after a long time. Maybe 
kiwi couldn't find the rootfs?

Alex

> 
> Best,
> 
> Tom
> -- 
> To unsubscribe, e-mail: [email protected]
> To contact the owner, e-mail: [email protected]
> 

--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to