Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Robert, On Friday 29 November 2013 15:28:28 Robert Yang wrote: > I can reproduce the similar problem now, I think that it should be a > bug of e2fsprogs, it seems the debugfs can't know the free space > correctly, and thus it appears no free blocks, I'm sorry to say that > I can't fix it in a s

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Todd, I can reproduce the similar problem now, I think that it should be a bug of e2fsprogs, it seems the debugfs can't know the free space correctly, and thus it appears no free blocks, I'm sorry to say that I can't fix it in a short while, but I will fix it in one or two weeks, maybe you ca

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Todd, I can't reproduce the problem, the rpm has more space than ipk is because of the IMAGE_ROOTFS_EXTRA_SPACE, which is 50M * 1.3 by default. Would you please try the following commands: 1) $ ls -stlh tmp/deploy/images/wandboard-dual/core-image-minimal-dev-wandboard-dual-*.ext3 2) $ fs

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Paul, Thanks, seems not enough space when ipk ? I will try a ipk build today. // Robert On 11/27/2013 06:57 PM, Paul Eggleton wrote: Robert, since I think you implemented this, any idea what might be going wrong here? Cheers, Paul On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrot

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Robert, since I think you implemented this, any idea what might be going wrong here? Cheers, Paul On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrote: > Tried creating a fresh build folder and giving the vm more ram but the > results are basically the same: > > Allocated inode: 15264 > c

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Tried creating a fresh build folder and giving the vm more ram but the results are basically the same: Allocated inode: 15264 copy_file: Could not allocate block in ext2 filesystem debugfs: sif "libgio-2.0.so.0.3800.1" mode 0x81ed It appears that using package_rpm successfully allocates something

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Thanks for the ideas. I'll try creating a new build folder. If that still shows the problem, I'm thinking this has something to do with the fact that I'm running the build inside a vm (inside an Ubuntu vm running on a Mac). It looks like the build is using debugfs...maybe it's running out of ram

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Nicolas / Todd, On Monday 25 November 2013 11:31:42 Nicolas Dechesne wrote: > On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova > wrote: > > It appears that copying the files to the ext3 / sdcard image is failing in > > *populate-extfs.sh* > > I see a series of these errors: > > > > *copy_file:

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

On Sun, Nov 24, 2013 at 3:51 AM, Todd Stellanova wrote: > It appears that copying the files to the ext3 / sdcard image is failing in > *populate-extfs.sh* > I see a series of these errors: > > *copy_file: Could not allocate block in ext2 filesystem* > > Any idea what might cause this? I've verifi

[yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hello, I'm following these directions for building with yocto for the wandboard: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard I'm building a bb recipe based on core-image-minimal-dev, to which I've added: IMAGE_FEATURES += "package-management" In my conf/local.conf

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

It appears that copying the files to the ext3 / sdcard image is failing in *populate-extfs.sh* I see a series of these errors: *copy_file: Could not allocate block in ext2 filesystem* Any idea what might cause this? I've verified that the initial .tar archive and the bz2 contain the right files.