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 <[email protected]> wrote: > On Fri, Aug 27, 2010 at 12:37 PM, <[email protected]> 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 <[email protected]> wrote: > >> On Fri, Aug 27, 2010 at 6:46 AM, <[email protected]> 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 > >> > [email protected] > >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > >> > > >> > >> _______________________________________________ > >> Openembedded-devel mailing list > >> [email protected] > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > >> > > _______________________________________________ > > Openembedded-devel mailing list > > [email protected] > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > > > > _______________________________________________ > Openembedded-devel mailing list > [email protected] > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel > _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
