[yocto] problems with Init

Chris Enrique microdevel at googlemail.com
Tue Aug 12 02:54:56 PDT 2014


Hello,

i am currently working on a BSP for yocto in order to support a custom
PowerPC board. In the meantime, i have setup all the config to generate a
properly running 3.14 kernel and devicetree but still have some issues with
the rootfs that is produced by yocto. I chose cpio.gz as image format for
the rootfs which is converted via the u-boot mkimage-tool to a compatible
.uRamdisk image.

I already tested the kernel with a rootfs image which was not generated by
yocto and it works fine.

Unfortunately, the yocto generated image seems to have problems with Init
(target is core-image-minimal, my bsp doesn't modify anything except adding
support for the target board by specifying kernel config and devicetree).

Here you can see the kernel log at the point where init seems to fail:

console [netcon0] enabled
netconsole: network logging started
rtc-rx8581 0-0051: setting system clock to 2012-04-24 09:29:17 UTC
(1335259757)
Freeing unused kernel memory: 200K (c0525000 - c0557000)
Failed to execute /init (error -13)
INIT: version 2.88 booting
Starting
hwclock: can't open '/dev/misc/rtc': No such file or directory
Stopping syslogd/klogd: no syslogd found; none killed
Deconfiguring network interfaces... ifdown: interface lo not configured
ifdown: interface eth0 not configured
done.
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting remote filesystems...
Deactivating swap...
Unmounting local filesystems...
/etc/rc0.d/S40umountfs: line 22: can't create /dev/null: Read-only file
system
reboot: Power down
System Halted, OK to turn off power

I assume, if i am able to generate a working kernel using yocto, the rootfs
image automatically generated by yocto for target core-image-minimal is not
supposed to fail?


I appreciate any help with this issue!

kind regards,
chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20140812/80e4b3c6/attachment.html>


More information about the yocto mailing list