Ni Qingliang | 22 Sep 03:56 2011
Picon

image_types_uboot

Hello, All:

when using "IMAGE_FSTYPES="ext2.gz.u-boot", I can't get what was
expected.

I can found it in "image_types_uboot.bbclass", but "image.bbclass" only
"inherit image_types", not "image_types_uboot".

what can I do? How about substitute the "inherit image_types" by
"inherit image_types_uboot" in "image.bbclass"?

Thanks!

--

-- 
Yi Qingliang
niqingliang@...
http://niqingliang2003.wordpress.com

McClintock Matthew-B29882 | 22 Sep 06:33 2011

Re: image_types_uboot

On Wed, Sep 21, 2011 at 8:56 PM, Ni Qingliang
<niqingliang@...> wrote:
> Hello, All:
>
> when using "IMAGE_FSTYPES="ext2.gz.u-boot", I can't get what was
> expected.
>
> I can found it in "image_types_uboot.bbclass", but "image.bbclass" only
> "inherit image_types", not "image_types_uboot".
>
> what can I do? How about substitute the "inherit image_types" by
> "inherit image_types_uboot" in "image.bbclass"?

You can add:

INHERIT += "image_types_uboot"

to your local.conf to enable these types. At some point it would be
good if we do this by default.

-M
Ni Qingliang | 22 Sep 07:09 2011
Picon

Re: image_types_uboot

THANKS!

On Thu, 2011-09-22 at 12:33 +0800, McClintock Matthew-B29882 wrote:
> On Wed, Sep 21, 2011 at 8:56 PM, Ni Qingliang
> <niqingliang@...> wrote:
> > Hello, All:
> >
> > when using "IMAGE_FSTYPES="ext2.gz.u-boot", I can't get what was
> > expected.
> >
> > I can found it in "image_types_uboot.bbclass", but "image.bbclass" only
> > "inherit image_types", not "image_types_uboot".
> >
> > what can I do? How about substitute the "inherit image_types" by
> > "inherit image_types_uboot" in "image.bbclass"?
> 
> You can add:
> 
> INHERIT += "image_types_uboot"
> 
> to your local.conf to enable these types. At some point it would be
> good if we do this by default.
> 
> -M

--

-- 
Yi Qingliang
niqingliang@...
http://niqingliang2003.wordpress.com

(Continue reading)

Ni Qingliang | 23 Sep 03:16 2011
Picon

Re: image_types_uboot

maybe somethings wrong, after add "INHERIT += image_types_uboot" in the
local.conf, I got that:
ERROR: cannot map 'allarch' to a linux kernel architecture

Any suggestion?

On Thu, 2011-09-22 at 13:09 +0800, 倪庆亮 wrote:
> THANKS!
> 
> On Thu, 2011-09-22 at 12:33 +0800, McClintock Matthew-B29882 wrote:
> > On Wed, Sep 21, 2011 at 8:56 PM, Ni Qingliang
> > <niqingliang <at> insigma.com.cn> wrote:
> > > Hello, All:
> > >
> > > when using "IMAGE_FSTYPES="ext2.gz.u-boot", I can't get what was
> > > expected.
> > >
> > > I can found it in "image_types_uboot.bbclass", but "image.bbclass" only
> > > "inherit image_types", not "image_types_uboot".
> > >
> > > what can I do? How about substitute the "inherit image_types" by
> > > "inherit image_types_uboot" in "image.bbclass"?
> >
> > You can add:
> >
> > INHERIT += "image_types_uboot"
> >
> > to your local.conf to enable these types. At some point it would be
> > good if we do this by default.
> >
(Continue reading)

McClintock Matthew-B29882 | 23 Sep 03:20 2011

Re: image_types_uboot

On Thu, Sep 22, 2011 at 8:16 PM, Ni Qingliang
<niqingliang@...> wrote:
> maybe somethings wrong, after add "INHERIT += image_types_uboot" in the
> local.conf, I got that:
> ERROR: cannot map 'allarch' to a linux kernel architecture
>
> Any suggestion?

Interesting. I have been seeing this same error and did not yet know
what was causing it. It has not caused any problems with the actual
build so far, but it's nice to know what is causing it. It's on my
list and I plan on looking into it.

-M
Ni Qingliang | 23 Sep 05:51 2011
Picon

Re: image_types_uboot

I had modified the "image.bbclass", and can generate ext2.gz.u-boot

and have new problem, when booting, I got that:

/etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
device

after login, I execute "echo -n > /etc/resolv.conf" success, and I can't
find file /var/log/messages, there is only "wtmp" in "/var/log".

On Fri, 2011-09-23 at 09:20 +0800, McClintock Matthew-B29882 wrote:
> On Thu, Sep 22, 2011 at 8:16 PM, Ni Qingliang
> <niqingliang@...> wrote:
> > maybe somethings wrong, after add "INHERIT += image_types_uboot" in the
> > local.conf, I got that:
> > ERROR: cannot map 'allarch' to a linux kernel architecture
> >
> > Any suggestion?
> 
> Interesting. I have been seeing this same error and did not yet know
> what was causing it. It has not caused any problems with the actual
> build so far, but it's nice to know what is causing it. It's on my
> list and I plan on looking into it.
> 
> -M

--

-- 
Yi Qingliang
niqingliang@...
http://niqingliang2003.wordpress.com
(Continue reading)

Ni Qingliang | 23 Sep 05:55 2011
Picon

Re: image_types_uboot

attachement is the bootlog on serial console.
I'm using mpc8314, I'm using the official kernel 3.0.4, and
linux-libc-headers also is 3.0.4, update the udev to 173.

On Fri, 2011-09-23 at 11:51 +0800, 倪庆亮 wrote:
> I had modified the "image.bbclass", and can generate ext2.gz.u-boot
> 
> and have new problem, when booting, I got that:
> 
> /etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
> device
> 
> after login, I execute "echo -n > /etc/resolv.conf" success, and I can't
> find file /var/log/messages, there is only "wtmp" in "/var/log".
> 
> On Fri, 2011-09-23 at 09:20 +0800, McClintock Matthew-B29882 wrote:
> > On Thu, Sep 22, 2011 at 8:16 PM, Ni Qingliang
> > <niqingliang@...> wrote:
> > > maybe somethings wrong, after add "INHERIT += image_types_uboot" in the
> > > local.conf, I got that:
> > > ERROR: cannot map 'allarch' to a linux kernel architecture
> > >
> > > Any suggestion?
> >
> > Interesting. I have been seeing this same error and did not yet know
> > what was causing it. It has not caused any problems with the actual
> > build so far, but it's nice to know what is causing it. It's on my
> > list and I plan on looking into it.
> >
> > -M
(Continue reading)

Ni Qingliang | 23 Sep 10:48 2011
Picon

Re: image_types_uboot

before "INIT: Entering runlevel: 5", the "echo -n > /etc/resolv.conf" in
udhcpc and "Running postinst /etc/rpm-postinsts/*.sh..." both failed.

it looks like the rootfs are not mounted, any ideas?

On Fri, 2011-09-23 at 11:55 +0800, 倪庆亮 wrote:
> attachement is the bootlog on serial console.
> I'm using mpc8314, I'm using the official kernel 3.0.4, and
> linux-libc-headers also is 3.0.4, update the udev to 173.
> 
> 
> On Fri, 2011-09-23 at 11:51 +0800, 倪庆亮 wrote:
> > I had modified the "image.bbclass", and can generate ext2.gz.u-boot
> >
> > and have new problem, when booting, I got that:
> >
> > /etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
> > device
> >
> > after login, I execute "echo -n > /etc/resolv.conf" success, and I can't
> > find file /var/log/messages, there is only "wtmp" in "/var/log".
> >
> > On Fri, 2011-09-23 at 09:20 +0800, McClintock Matthew-B29882 wrote:
> > > On Thu, Sep 22, 2011 at 8:16 PM, Ni Qingliang
> > > <niqingliang <at> insigma.com.cn> wrote:
> > > > maybe somethings wrong, after add "INHERIT += image_types_uboot" in the
> > > > local.conf, I got that:
> > > > ERROR: cannot map 'allarch' to a linux kernel architecture
> > > >
> > > > Any suggestion?
(Continue reading)

McClintock Matthew-B29882 | 23 Sep 17:55 2011

Re: image_types_uboot

On Fri, Sep 23, 2011 at 3:48 AM, Ni Qingliang
<niqingliang@...> wrote:
> before "INIT: Entering runlevel: 5", the "echo -n > /etc/resolv.conf" in
> udhcpc and "Running postinst /etc/rpm-postinsts/*.sh..." both failed.
>
> it looks like the rootfs are not mounted, any ideas?

I would probably start a new thread with a new subject so we get some
more eyes on this issue. Also, post what system you are building for.
Can you try mounting the ext2 rfs in loopback mode on your build
machine and seeing how much free space is left?

-M
Ni Qingliang | 26 Sep 03:41 2011
Picon

rootfs-ramdisk error

I'm using ramdisk, and get some error when booting, the udhcpc can't
write resolv.conf (No space left on device) and the rpm-postinsts fail.

my analysis:
	for the former, I only find some info in ./default/volatiles/00_core,
the /etc/resolv.conf is a link to /var/run/resolv.conf, but I have no
idea about udhcpd's error.

	for the latter, rpm-postinsts, the reason is: in rpm-postinsts, all sh
files have been executed, and moved to *.done,
(through /etc/rcS.d/S98configure), but /etc/rcS.d/S98configure have not
been deleted, so it is executed again when booting, but there is no any
*.sh file, so fail. ( as expected, if the /etc/rpm-postinsts/*.sh is
moved to *.sh.done, the /etc/rcS.d/S98configure should be deleted, but
it does exist in the rootfs)

the content of /etc/rcS.d/S98configure is:
for i in /etc/rpm-postinsts/*.sh; do
	echo "Running postinst $i..."
	if [ -f $i ] && sh $i; then
		# rm $i
		mv $i $i.done
	else
		echo "ERROR: postinst $i failed."
	fi
done
rm -f /etc/rcS.d/S98configure
I think the for sentence is not so robust as expected when no any *.sh
files.

(Continue reading)

Ni Qingliang | 26 Sep 03:45 2011
Picon

Re: rootfs-ramdisk error

for resolv.conf, maybe /etc/resolv.conf and /var/run/resolv.conf are
misordered.

in 00_core:
l root root 0644 /etc/resolv.conf /var/run/resolv.conf
f root root 0644 /var/run/resolv.conf none

if no /var/run/resolv.conf, does the first line can be success??

maybe we should change the order to:

f root root 0644 /var/run/resolv.conf none
l root root 0644 /etc/resolv.conf /var/run/resolv.conf

On Mon, 2011-09-26 at 09:41 +0800, 倪庆亮 wrote:
> I'm using ramdisk, and get some error when booting, the udhcpc can't
> write resolv.conf (No space left on device) and the rpm-postinsts fail.
> 
> my analysis:
>         for the former, I only find some info in ./default/volatiles/00_core,
> the /etc/resolv.conf is a link to /var/run/resolv.conf, but I have no
> idea about udhcpd's error.
> 
>         for the latter, rpm-postinsts, the reason is: in rpm-postinsts, all sh
> files have been executed, and moved to *.done,
> (through /etc/rcS.d/S98configure), but /etc/rcS.d/S98configure have not
> been deleted, so it is executed again when booting, but there is no any
> *.sh file, so fail. ( as expected, if the /etc/rpm-postinsts/*.sh is
> moved to *.sh.done, the /etc/rcS.d/S98configure should be deleted, but
> it does exist in the rootfs)
(Continue reading)

Ni Qingliang | 26 Sep 04:57 2011
Picon

Re: rootfs-ramdisk error

no luck, maybe it is not the order, problem still there.
and I can't find the /etc/resolv.conf after login.

the console log section:

Checking for -/etc/resolv.conf-.
Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
Checking for -/etc/resolv.conf-.
Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
Configuring network interfaces... udhcpc (v1.18.5) started
Sending discover...
PHY: mdio <at> e0024520:02 - Link is Up - 100/Full
Sending discover...
Sending select for 192.168.0.108...
Lease of 192.168.0.108 obtained, lease time 604800
/etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
device
adding dns 192.168.0.1
/etc/udhcpc.d/50default: line 67: /etc/resolv.conf: No space left on
device
done.

On Mon, 2011-09-26 at 09:45 +0800, 倪庆亮 wrote:
> for resolv.conf, maybe /etc/resolv.conf and /var/run/resolv.conf are
> misordered.
> 
> in 00_core:
> l root root 0644 /etc/resolv.conf /var/run/resolv.conf
> f root root 0644 /var/run/resolv.conf none
> 
(Continue reading)

Ni Qingliang | 26 Sep 07:03 2011
Picon

Re: rootfs-ramdisk error

If changed to jffs2, the resolv.conf error disappear.

On Mon, 2011-09-26 at 10:57 +0800, 倪庆亮 wrote:
> no luck, maybe it is not the order, problem still there.
> and I can't find the /etc/resolv.conf after login.
> 
> the console log section:
> 
> Checking for -/etc/resolv.conf-.
> Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
> Checking for -/etc/resolv.conf-.
> Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
> Configuring network interfaces... udhcpc (v1.18.5) started
> Sending discover...
> PHY: mdio <at> e0024520:02 - Link is Up - 100/Full
> Sending discover...
> Sending select for 192.168.0.108...
> Lease of 192.168.0.108 obtained, lease time 604800
> /etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
> device
> adding dns 192.168.0.1
> /etc/udhcpc.d/50default: line 67: /etc/resolv.conf: No space left on
> device
> done.
> 
> 
> 
> On Mon, 2011-09-26 at 09:45 +0800, 倪庆亮 wrote:
> > for resolv.conf, maybe /etc/resolv.conf and /var/run/resolv.conf are
> > misordered.
(Continue reading)

McClintock Matthew-B29882 | 26 Sep 18:03 2011

Re: rootfs-ramdisk error

Have you checked your rootfs itself to see how much free space is
left? You could mount it in loopback on your build machine to check.

There are some vars within poky that determine the rootfs size, grep
for IMAGE_ROOTFS_SIZE.

-M

On Mon, Sep 26, 2011 at 12:03 AM, Ni Qingliang
<niqingliang <at> insigma.com.cn> wrote:
> If changed to jffs2, the resolv.conf error disappear.
>
> On Mon, 2011-09-26 at 10:57 +0800, 倪庆亮 wrote:
>> no luck, maybe it is not the order, problem still there.
>> and I can't find the /etc/resolv.conf after login.
>>
>> the console log section:
>>
>> Checking for -/etc/resolv.conf-.
>> Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
>> Checking for -/etc/resolv.conf-.
>> Creating link -/etc/resolv.conf- pointing to -/var/run/resolv.conf-.
>> Configuring network interfaces... udhcpc (v1.18.5) started
>> Sending discover...
>> PHY: mdio <at> e0024520:02 - Link is Up - 100/Full
>> Sending discover...
>> Sending select for 192.168.0.108...
>> Lease of 192.168.0.108 obtained, lease time 604800
>> /etc/udhcpc.d/50default: line 63: /etc/resolv.conf: No space left on
>> device
(Continue reading)

McClintock Matthew-B29882 | 27 Sep 00:22 2011

Re: rootfs-ramdisk error

2011/9/26 Matthew McClintock <msm@...>:
> Have you checked your rootfs itself to see how much free space is
> left? You could mount it in loopback on your build machine to check.
>
> There are some vars within poky that determine the rootfs size, grep
> for IMAGE_ROOTFS_SIZE.

I'm actually seeing a similiar issue at the moment:

Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such
file or directory
bootlogd.
tar: can't open '/etc/dev.tar': No space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No
space left on device
/etc/rcS.d/S37populate-volatile.sh: line 52: /etc/volatile.cache: No
(Continue reading)

Ni Qingliang | 27 Sep 03:14 2011
Picon

Re: rootfs-ramdisk error

maybe not only similar, but same:)

curious, the issue disappeared, what I can remeber is reconfigured the
busybox.
maybe another thing is rebuilded all.

before that, I have added debug code in udhcpc's script, and found that:
mkdir /etc/AAAAA  will fail
but
cd /etc
mkdir ./AAAAA will success.
maybe that is a clue, but I can't reproduce the problem.:(

the IMAGE_ROOTFS_SIZE is 16M, only used about 11M.
I have looked the source code of the poky, it will use the bigger one in
(ROOTFS_SIZE and 1.3 * real_size) by default.

On Tue, 2011-09-27 at 06:22 +0800, McClintock Matthew-B29882 wrote:
> 2011/9/26 Matthew McClintock <msm@...>:
> > Have you checked your rootfs itself to see how much free space is
> > left? You could mount it in loopback on your build machine to check.
> >
> > There are some vars within poky that determine the rootfs size, grep
> > for IMAGE_ROOTFS_SIZE.
> 
> I'm actually seeing a similiar issue at the moment:
> 
> Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such
> file or directory
> bootlogd.
(Continue reading)

McClintock Matthew-B29882 | 27 Sep 17:06 2011

Re: rootfs-ramdisk error

On Mon, Sep 26, 2011 at 8:14 PM, Ni Qingliang
<niqingliang@...> wrote:
> maybe not only similar, but same:)
>
> curious, the issue disappeared, what I can remeber is reconfigured the
> busybox.
> maybe another thing is rebuilded all.
>
> before that, I have added debug code in udhcpc's script, and found that:
> mkdir /etc/AAAAA  will fail
> but
> cd /etc
> mkdir ./AAAAA will success.
> maybe that is a clue, but I can't reproduce the problem.:(
>
> the IMAGE_ROOTFS_SIZE is 16M, only used about 11M.
> I have looked the source code of the poky, it will use the bigger one in
> (ROOTFS_SIZE and 1.3 * real_size) by default.

Can you add a bug to bugzilla.yoctoproject.org to track this so we can
try to fix this for the 1.1 release?

-M
Ni Qingliang | 28 Sep 03:34 2011
Picon

Re: rootfs-ramdisk error

http://bugzilla.pokylinux.org/show_bug.cgi?id=1535

On Tue, 2011-09-27 at 23:06 +0800, McClintock Matthew-B29882 wrote:
> On Mon, Sep 26, 2011 at 8:14 PM, Ni Qingliang
> <niqingliang@...> wrote:
> > maybe not only similar, but same:)
> >
> > curious, the issue disappeared, what I can remeber is reconfigured the
> > busybox.
> > maybe another thing is rebuilded all.
> >
> > before that, I have added debug code in udhcpc's script, and found that:
> > mkdir /etc/AAAAA  will fail
> > but
> > cd /etc
> > mkdir ./AAAAA will success.
> > maybe that is a clue, but I can't reproduce the problem.:(
> >
> > the IMAGE_ROOTFS_SIZE is 16M, only used about 11M.
> > I have looked the source code of the poky, it will use the bigger one in
> > (ROOTFS_SIZE and 1.3 * real_size) by default.
> 
> Can you add a bug to bugzilla.yoctoproject.org to track this so we can
> try to fix this for the 1.1 release?
> 
> -M

--

-- 
Yi Qingliang
niqingliang@...
(Continue reading)


Gmane