Re: [Angstrom-devel] Can't build cloud9 image

Re: [Angstrom-devel] Can't build cloud9 image

[Koen Kooi]

Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:

> On 2012-03-04 05:46, Koen Kooi wrote:
>> 
>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
>> 
>>> OE Build Configuration:
>>> BB_VERSION        = "1.15.1"
>>> TARGET_ARCH       = "arm"
>>> TARGET_OS         = "linux-gnueabi"
>>> MACHINE           = "beaglebone"
>>> DISTRO            = "angstrom"
>>> DISTRO_VERSION    = "v2012.03-core"
>>> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
>>> TARGET_FPU        = "vfp-neon"
>>> meta-angstrom     = "master:2129eed920364abcc4f3f72d395333a041634e26"
>>> meta-oe
>>> meta-efl
>>> meta-gpe
>>> meta-gnome
>>> meta-xfce
>>> meta-initramfs    = "master:fdff8697ea2db6254d26510adb7d11e6352d950f"
>>> meta-opie         = "master:efa3892b20a4ef80274e56e5633ebd62c16f9731"
>>> meta-java         = "master:d430de31c167cd264be74a1d82af4b732bb915dd"
>>> meta-mozilla      = "master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e"
>>> meta-ti           = "master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450"
>>> meta-efikamx      = "master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d"
>>> meta-nslu2        = "master:3d9fc951b05b4df476374b6fc3085ebac7f293ee"
>>> meta-htc
>>> meta-nokia
>>> meta-openmoko
>>> meta-palm         = "master:cda19686a2a3573ce50c86733c3469d926124995"
>>> meta-handheld     = "master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7"
>>> meta-intel
>>> meta-sugarbay
>>> meta-crownbay
>>> meta-emenlow
>>> meta-fishriver
>>> meta-jasperforest
>>> meta-n450         = "master:df18b721f86f0737c0f302e49b27ea232c70e683"
>>> meta              = "master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047"
>>> 
>>> Building of cloud9-image ends up with this error:
>>>  /etc/fstab entries need to be created with the user flag for the loop devices like:
>>>  /dev/loop2 /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/tmp-mnt-boot vfat user 0 0
>>> 
>>> My host is Fedora-16 (i386)
>>> 
>>> How do I solve this so I can build the full cloud9-image?
>> 
>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
> 
> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
> edit /etc/fstab?

Then you can't build this image.

>  Everything else builds with no special "root" style
> privileges, why does this one image need it?

Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
And genext2fs will likely OOM on a lot of buildmachines.

>  Also, what if I build
> in another tree/path?  Now, I have to edit /etc/fstab again?

Correct, it's the gift that keeps on giving :(

Anyway, why are you posting this to the angstrom list? The cloud9 recipe and offending bbclass live in meta-ti.

Re: [Angstrom-devel] Can't build cloud9 image

[Gary Thomas]

On 2012-03-04 06:09, Koen Kooi wrote:
>
> Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:
>
>> On 2012-03-04 05:46, Koen Kooi wrote:
>>>
>>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
>>>
>>>> OE Build Configuration:
>>>> BB_VERSION        = "1.15.1"
>>>> TARGET_ARCH       = "arm"
>>>> TARGET_OS         = "linux-gnueabi"
>>>> MACHINE           = "beaglebone"
>>>> DISTRO            = "angstrom"
>>>> DISTRO_VERSION    = "v2012.03-core"
>>>> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
>>>> TARGET_FPU        = "vfp-neon"
>>>> meta-angstrom     = "master:2129eed920364abcc4f3f72d395333a041634e26"
>>>> meta-oe
>>>> meta-efl
>>>> meta-gpe
>>>> meta-gnome
>>>> meta-xfce
>>>> meta-initramfs    = "master:fdff8697ea2db6254d26510adb7d11e6352d950f"
>>>> meta-opie         = "master:efa3892b20a4ef80274e56e5633ebd62c16f9731"
>>>> meta-java         = "master:d430de31c167cd264be74a1d82af4b732bb915dd"
>>>> meta-mozilla      = "master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e"
>>>> meta-ti           = "master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450"
>>>> meta-efikamx      = "master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d"
>>>> meta-nslu2        = "master:3d9fc951b05b4df476374b6fc3085ebac7f293ee"
>>>> meta-htc
>>>> meta-nokia
>>>> meta-openmoko
>>>> meta-palm         = "master:cda19686a2a3573ce50c86733c3469d926124995"
>>>> meta-handheld     = "master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7"
>>>> meta-intel
>>>> meta-sugarbay
>>>> meta-crownbay
>>>> meta-emenlow
>>>> meta-fishriver
>>>> meta-jasperforest
>>>> meta-n450         = "master:df18b721f86f0737c0f302e49b27ea232c70e683"
>>>> meta              = "master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047"
>>>>
>>>> Building of cloud9-image ends up with this error:
>>>>   /etc/fstab entries need to be created with the user flag for the loop devices like:
>>>>   /dev/loop2 /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/tmp-mnt-boot vfat user 0 0
>>>>
>>>> My host is Fedora-16 (i386)
>>>>
>>>> How do I solve this so I can build the full cloud9-image?
>>>
>>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
>>
>> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
>> edit /etc/fstab?
>
> Then you can't build this image.
>
>>   Everything else builds with no special "root" style
>> privileges, why does this one image need it?
>
> Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
> And genext2fs will likely OOM on a lot of buildmachines.

But this is just to be able to generate a packed image that can be
copied directly to media?  Maybe that should be a different image
type, like the .u-boot images?  Then it would be obvious what's
being done and why.  In my case, I'm more than happy running a script
to copy the appropriate files to my SD card, etc. and I don't care
(nor especially want) a packed image.

>
>>   Also, what if I build
>> in another tree/path?  Now, I have to edit /etc/fstab again?
>
> Correct, it's the gift that keeps on giving :(
>
> Anyway, why are you posting this to the angstrom list? The cloud9 recipe and offending bbclass live in meta-ti.

Fair enough, I'll try to keep the discussions where they are most relevant.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [Angstrom-devel] Can't build cloud9 image

[Richard Purdie]

On Sun, 2012-03-04 at 06:17 -0700, Gary Thomas wrote:
> On 2012-03-04 06:09, Koen Kooi wrote:
> > Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:
> >> On 2012-03-04 05:46, Koen Kooi wrote:
> >>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
> this so I can build the full cloud9-image?
> >>>
> >>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
> >>
> >> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
> >> edit /etc/fstab?
> >
> > Then you can't build this image.
> >
> >>   Everything else builds with no special "root" style
> >> privileges, why does this one image need it?
> >
> > Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
> > And genext2fs will likely OOM on a lot of buildmachines.
> 
> But this is just to be able to generate a packed image that can be
> copied directly to media?  Maybe that should be a different image
> type, like the .u-boot images?  Then it would be obvious what's
> being done and why.  In my case, I'm more than happy running a script
> to copy the appropriate files to my SD card, etc. and I don't care
> (nor especially want) a packed image.

Just for reference, the directdisk stuff that was in OE-Core did
something like this (create an MBR with a couple of partitions following
it). It was removed as having some minor bugs and being unneeded but the
code might prove an interesting starting point to addressing this
problem. To come back, it would need to be a proper IMAGE_FSTYPES entry.

Cheers,

Richard

Re: [Angstrom-devel] Can't build cloud9 image

[Koen Kooi]

Op 4 mrt. 2012, om 14:55 heeft Richard Purdie het volgende geschreven:

> On Sun, 2012-03-04 at 06:17 -0700, Gary Thomas wrote:
>> On 2012-03-04 06:09, Koen Kooi wrote:
>>> Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:
>>>> On 2012-03-04 05:46, Koen Kooi wrote:
>>>>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
>> this so I can build the full cloud9-image?
>>>>> 
>>>>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
>>>> 
>>>> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
>>>> edit /etc/fstab?
>>> 
>>> Then you can't build this image.
>>> 
>>>>  Everything else builds with no special "root" style
>>>> privileges, why does this one image need it?
>>> 
>>> Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
>>> And genext2fs will likely OOM on a lot of buildmachines.
>> 
>> But this is just to be able to generate a packed image that can be
>> copied directly to media?  Maybe that should be a different image
>> type, like the .u-boot images?  Then it would be obvious what's
>> being done and why.  In my case, I'm more than happy running a script
>> to copy the appropriate files to my SD card, etc. and I don't care
>> (nor especially want) a packed image.
> 
> Just for reference, the directdisk stuff that was in OE-Core did
> something like this (create an MBR with a couple of partitions following
> it). It was removed as having some minor bugs and being unneeded but the
> code might prove an interesting starting point to addressing this
> problem. To come back, it would need to be a proper IMAGE_FSTYPES entry.

When I last tried to use that code it created images incompatible with the boot ROM used in TI SoCs :(

regards,

Koen

[Angstrom-devel] Can't build cloud9 image

[Russell Senior]

>>> At the risk of responding to a practical joke: /etc/fstab entries
>>> need to be created with the user flag for the loop devices, the
>>> error message even includes the exact entry you need to add.
>> 
>> I see that, but what if I'm "Joe user" who can't (or doesn't want
>> to)
>> edit /etc/fstab?

> Then you can't build this image.

FWIW, I added the /etc/fstab entry provide (for /dev/loop2) but I
still get this at the end (from build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/temp/log.do_rootfs

[...]
./media/mmc1/
./media/union/
./media/realroot/
loop: can't delete device /dev/loop1: Permission denied
loop: can't delete device /dev/loop2: Permission denied
loop: can't delete device /dev/loop3: Permission denied
/dev/loop1: Permission denied

>>  Everything else builds with no special "root" style
>> privileges, why does this one image need it?

> Simply put: because the tools suck. A this point in time there is no
> tool (or tools plural) that allows creating 2 partitions (vfat and
> extX) and concatenating them into a valid image with an MBR. The
> biggest lack is something like 'genfatfs', mcopy is a step in the
> right direction but is too limited to work in this scenario.
> And genext2fs will likely OOM on a lot of buildmachines.

Are you familiar with makebootfat?

  http://linux.die.net/man/1/makebootfat


-- 
Russell Senior, President
russell@personaltelco.net

Re: [Angstrom-devel] Can't build cloud9 image

[Denys Dmytriyenko]

On Thu, Mar 15, 2012 at 12:17:37AM -0700, Russell Senior wrote:
> > Then you can't build this image.
> 
> FWIW, I added the /etc/fstab entry provide (for /dev/loop2) but I
> still get this at the end (from build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/temp/log.do_rootfs
> 
> [...]
> ./media/mmc1/
> ./media/union/
> ./media/realroot/
> loop: can't delete device /dev/loop1: Permission denied
> loop: can't delete device /dev/loop2: Permission denied
> loop: can't delete device /dev/loop3: Permission denied
> /dev/loop1: Permission denied

Well, mine gets further (although it's not my main focus now):

| ./bin/tinylogin
| ./boot/
| ./boot/uImage-3.2.11
| ./boot/uImage
| ./boot/uEnv.txt
| losetup: /dev/loop1: detach failed: No such device or address
| losetup: /dev/loop3: detach failed: No such device or address
| 1024+0 records in
| 1024+0 records out
| 1048576 bytes (1.0 MB) copied, 0.00349814 s, 300 MB/s
| Disk /dev/loop1 doesn't contain a valid partition table
| Checking that no-one is using this disk right now ...
| BLKRRPART: Invalid argument
| OK
| sfdisk: Disk /dev/loop1: cannot get geometry
| 
| 
| Disk /dev/loop1: 444 cylinders, 255 heads, 63 sectors/track
| 
| sfdisk: ERROR: sector 0 does not have an msdos signature
| sfdisk:  /dev/loop1: unrecognized partition table type
| 
| sfdisk: No partitions found
| 
| Old situation:
| New situation:
| Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
| 
|    Device Boot Start     End   #cyls    #blocks   Id  System
| /dev/loop1p1   *      0+      8       9-     72261    c  W95 FAT32 (LBA)
| /dev/loop1p2          9     443     435    3494137+  83  Linux
| /dev/loop1p3          0       -       0          0    0  Empty
| /dev/loop1p4          0       -       0          0    0  Empty
| Successfully wrote the new partition table
| 
| Re-reading the partition table ...
| BLKRRPART: Invalid argument
| 
| If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
| to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
| (See fdisk(8).)
| Warning: block count mismatch: found 3566398 but assuming 72261.
| mkfs.vfat 3.0.12 (29 Oct 2011)
| Loop device does not match a floppy size, using default hd params
| ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.
| mount: /dev/loop0: can't read superblock
NOTE: package cloud9-image-1.0-r0: task do_rootfs: Failed


> > Simply put: because the tools suck. A this point in time there is no
> > tool (or tools plural) that allows creating 2 partitions (vfat and
> > extX) and concatenating them into a valid image with an MBR. The
> > biggest lack is something like 'genfatfs', mcopy is a step in the
> > right direction but is too limited to work in this scenario.
> > And genext2fs will likely OOM on a lot of buildmachines.

FWIW, there's a new patchset published in OE-Core ML to address memory issues 
of genext2fs...


> Are you familiar with makebootfat?
> 
>   http://linux.die.net/man/1/makebootfat

Interesting... I think I looked at it before, just need time to try to 
integrate it, time permitting.

-- 
Denys

Re: [Angstrom-devel] Can't build cloud9 image

[Russell Senior]

>>>>> "Denys" == Denys Dmytriyenko <denis@denix.org> writes:

Denys> On Thu, Mar 15, 2012 at 12:17:37AM -0700, Russell Senior wrote:
>> > Then you can't build this image.
>> 
>> FWIW, I added the /etc/fstab entry provide (for /dev/loop2) but I
>> still get this at the end (from
>> build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/temp/log.do_rootfs
>> 
>> [...]  ./media/mmc1/ ./media/union/ ./media/realroot/ loop: can't
>> delete device /dev/loop1: Permission denied loop: can't delete
>> device /dev/loop2: Permission denied loop: can't delete device
>> /dev/loop3: Permission denied /dev/loop1: Permission denied

Denys> Well, mine gets further (although it's not my main focus now):

Yeah, that was just because i wasn't in the 'disk' group in
/etc/groups.  Thank you to the interwebs for digging that one up for
me.

The compile is finishing for me currently, but I still can't get it to
boot, built on debian/unstable.  The MLO I build doesn't seem to get
recognized by my A4 beaglebone.  The ROM code spits C's at me as if
the microSD card wasn't there.  The microSD card is okay though (an 8
gig Kingston class 10 thing), because I can /sbin/dd the online
angstrom cloud9 demo image[1] on it and that boots.

[1] http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz


-- 
Russell Senior, President
russell@personaltelco.net