[yocto] problems with Init

2014-08-12 Thread Chris Enrique
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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] problems with Init

2014-08-12 Thread Maciej Borzecki
On Tuesday 12 of August 2014 11:54:56 Chris Enrique wrote:
 
 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

Have you checked that /dev is mounted and udev is running?

 
 
 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?

--

Maciej Borzęcki
Senior Software Engineer Open-RnD Sp. z o.o.
www.open-rnd.pl, Facebook, Twitter
mobile: +48 telefon, fax: +48 42 657 9079
 
 
Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób,
do których została zaadresowana. Jeśli wiadomość została otrzymana
przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W
takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz
poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości
zwrotnej. Dziękujemy.
 
This message, including any attachments hereto, may contain privileged or
confidential information and is sent solely for the attention and use of
the intended addressee(s). If you are not an intended addressee, you may
neither use this message nor copy or deliver it to anyone. In such case,
you should immediately destroy this message and kindly notify the sender by
reply email. Thank you.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto