Hi, OK, unfortunately I've exhausted all my thoughts on getting my h1940 up and running - it still fails ... actually, stops, after a console output noting that it has found the compressed RAMDISK image at block 0. After that no more console output ... but it's not completely hung, as I do get a console message about the Ethernet gadget when plugging in the USB. A admit though, I'm not sure what to try next - as I have no console output after the RAMDISK message, have no keyboard (it's a touchscreen device), no logs (using a ramdisk or SD paritition), and I can't connect to the USB ethernet interface even though I do get a message about it (but can't ping it). Any debugging suggestions would be greatly appreciated!!! Thanks,... Russell
On Sat, Aug 28, 2010 08:42 AM, <[email protected]> wrote: > 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, <[email protected]> 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, <[email protected]> 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 <[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 > > > _______________________________________________ > 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
