From: Russell Senior <russell@personaltelco.net>
To: Denys Dmytriyenko <denis@denix.org>
Cc: meta-ti@yoctoproject.org
Subject: Re: [Angstrom-devel] Can't build cloud9 image
Date: Sun, 01 Apr 2012 21:57:05 -0700 [thread overview]
Message-ID: <86iphivihq.fsf@coulee.tdb.com> (raw)
In-Reply-To: <20120329012237.GE32193@denix.org> (Denys Dmytriyenko's message of "Wed\, 28 Mar 2012 21\:22\:37 -0400")
>>>>> "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
next prev parent reply other threads:[~2012-04-02 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 7:17 [Angstrom-devel] Can't build cloud9 image Russell Senior
2012-03-29 1:22 ` Denys Dmytriyenko
2012-04-02 4:57 ` Russell Senior [this message]
[not found] <4F5213E8.50108@mlbassoc.com>
[not found] ` <89B59491-7BDB-4A5D-BDC0-D4E3863E417B@dominion.thruhere.net>
[not found] ` <4F5367ED.1060903@mlbassoc.com>
2012-03-04 13:09 ` Koen Kooi
2012-03-04 13:17 ` Gary Thomas
2012-03-04 13:55 ` Richard Purdie
2012-03-04 14:10 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86iphivihq.fsf@coulee.tdb.com \
--to=russell@personaltelco.net \
--cc=denis@denix.org \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.