From: <openembedded@rkmorris.us>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Execution of Build Output Failing (Testing)
Date: Sat, 28 Aug 2010 08:42:46 -0500 [thread overview]
Message-ID: <1283002966187563500@rkmorris.us> (raw)
In-Reply-To: <1282944432199625500@rkmorris.us>
Hi,
It's all working now - thanks! I refreshed the source (via git), and did a complete new rebuild - and now it works.
Now back to my h1940. If anyone has any debugging suggestions I would definitely appreciate it. Unfortunately it seems to just hang, with no real debugging information (when "transferring" from the kernel to initrd, each of which has been confirmed on it's own). Of course I don't have a keyboard either, so it's even more fun ... :-(.
Thanks again,... Russell
On Fri, Aug 27, 2010 04:27 PM, <openembedded@rkmorris.us> wrote:
> OK, I checked - and my kernel file actually has 2.6.34 in it's name, so it seems right.
> Hmmm ... where the heck is 2.6.17-rc3 coming from?
> ... Russell
>
>
> On Fri, Aug 27, 2010 03:26 PM, <openembedded@rkmorris.us> wrote:
> > Yep, this makes complete sense - but I haven't tried to change versions (at least not on purpose ... :-)). Rather, these are what seem to happen by default. Let me look at the config files a bit more, to see if I can force this (or if you know, but all means yell about what I'm missing!).
> > BTW, on the PREFERRED_VERSION items below - likely a dumb question, but how is someone to know about this?
> > Thanks!
> > ... Russell
> >
> >
> >
> > On Fri, Aug 27, 2010 03:16 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > > On Fri, Aug 27, 2010 at 12:37 PM, <openembedded@rkmorris.us> wrote:
> > > Hi,
> > > Thanks for the quick response!
> > > What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
> > > Thoughts?
> >
> > yes because the default kernel for qemuarm machine is 2.6.34 and hence
> > the modules which are part of rfs are for that kernel.
> > you should use same kernel to boot qemu for best results.
> >
> > > Thanks again,... Russell
> > >
> > >
> > > On Fri, Aug 27, 2010 12:41 PM, Khem Raj <raj.khem@gmail.com> wrote:
> > >> On Fri, Aug 27, 2010 at 6:46 AM, <openembedded@rkmorris.us> wrote:
> > >> > Hi,
> > >> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> > >> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> > >> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> > >> > Is this a known issue? Any proposed fixes or workarounds for this?
> > >>
> > >> oe.dev works well on qemuarm here with
> > >>
> > >> PREFERRED_VERSION_usbutils_local = "0.86"
> > >> PREFERRED_VERSION_udev_local = "151"
> > >>
> > >> in local.conf and minimal/angstrom distro last time I tried it booted
> > >> fine. you can also adapt
> > >> contrib/qemu/run-qemu.sh to run OE in qemu.
> > >>
> > >> > Thanks!
> > >> > ... Russell
> > >> > _______________________________________________
> > >> > Openembedded-devel mailing list
> > >> > Openembedded-devel@lists.openembedded.org
> > >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >> >
> > >>
> > >> _______________________________________________
> > >> Openembedded-devel mailing list
> > >> Openembedded-devel@lists.openembedded.org
> > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >>
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >
> >
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From kergoth@gmail.com Sat Aug 28 16:44:47 2010
Received: from mail-ww0-f43.google.com ([74.125.82.43])
by linuxtogo.org with esmtp (Exim 4.69)
(envelope-from <kergoth@gmail.com>) id 1OpMeB-0000r9-0x
for openembedded-devel@lists.openembedded.org;
Sat, 28 Aug 2010 16:44:47 +0200
Received: by wwb31 with SMTP id 31so4502677wwb.24
for <openembedded-devel@lists.openembedded.org>;
Sat, 28 Aug 2010 07:44:13 -0700 (PDT)
DKIM-Signature: v
next prev parent reply other threads:[~2010-08-28 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 20:26 Execution of Build Output Failing (Testing) openembedded
2010-08-27 21:27 ` openembedded
[not found] ` <1282944796856928500@rkmorris.us>
2010-08-27 21:42 ` Martin Jansa
2010-08-28 13:42 ` openembedded [this message]
2010-08-29 13:34 ` openembedded
-- strict thread matches above, loose matches on Subject: below --
2010-08-27 12:15 [RFC] review process Frans Meulenbroeks
2010-08-27 13:46 ` Execution of Build Output Failing (Testing) openembedded
2010-08-27 17:41 ` Khem Raj
2010-08-27 19:37 ` openembedded
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=1283002966187563500@rkmorris.us \
--to=openembedded@rkmorris.us \
--cc=openembedded-devel@lists.openembedded.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.