On Mon, 26 Jan 2015 10:19:09 +0100
Oscar C <oscar-listas(a)naiandei.net> wrote:
El 2015-01-25 11:44, Stefan Botter escribió:
I am trying to run the cubietruck JeOS image from
d.o.o://ports/armv7hl/factory/images/, but so far without success.
I have the image on a sd card, and put both partitions also on a
connected sata disk. As far as I can see the kernel starts, but
everything comes to a sudden stop where - I believe - the
process should take over.
I also tried the 13.2 image, but that did not work either, for
because of the uboot version (mentioned here on
the list earlier).
Is there any magic to perform? Can I help?
Could you attach the output of the serial console?
The attached file is the log from reset of the board until the system
is stuck, and after a reset I stoped the boot process and print the
Please tell me, if you need more information.
downloaded last Friday.
I have a cubieboard2 which is very similar to cubietruck (only dtb is
different) and the last lines before systemd is launched are more or
less similar to yours:
[ 3.556478] sunxi-rtc 1c20d00.rtc: setting system clock to
1970-01-01 00:00:09 UTC (9)
[ 3.564429] sr_init: No PMIC hook to init smartreflex
[ 3.569700] sr_init: platform driver register failed for SR
[ 3.580194] Unable to find PPMU node
[ 3.583804] exynos5-bus-int: probe of exynos5-bus-int failed with
[ 3.590814] PM: Checking hibernation image partition
[ 3.590832] PM: Hibernation image not present or could not be
[ 3.590848] usb2-vbus: disabling
[ 3.594078] usb1-vbus: disabling
[ 3.597330] ahci-5v: disabling
[ 3.600394] vcc3v3: disabling
[ 3.603358] vcc3v0: disabling
[ 3.607914] Freeing unused kernel memory: 1000K (c0d6a000 -
[ 3.627665] random: systemd urandom read with 0 bits of entropy
[ 3.638585] systemd: systemd 210 running in system mode. (+PAM
-LIBWRAP +AUDIT +SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
However, I see something weird in your u-boot script: the variables and
their values doesn't match what it should be. For example, the initial
ramdisk should load from address 0x4a000000 but in the u-boot
environment it seems to load from address 0x43300000. Could you post the
file boot.scr which is on the first partition of the sd card? Thanks!
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org