<html><head><style id="axi-htmleditor-style" type="text/css">p { margin: 0px; }</style></head><body style="font-size: 10pt; font-family: Arial; background-image: none; background-repeat: repeat; background-attachment: fixed;"><P>Hi,</P>
<P> </P>
<P>I have tried quite a few more things here, still with no luck. It really does seem that OpenEmbedded does not properly / fully build an image that works on (real?) embedded systems ... :-(. I am out of things to try, but let me pass this info along in the hope that it will save others some time / grief if they try to do similar things.</P>
<P> </P>
<P>I have tried several different formats / approaches to the rootfs, none of which work (except for the legacy Familiar Linux file system that I found). I cannot load the OpenEmbedded rootfs as an initrd, or when extracted to an SD card (as a "normal" file system, either copied from the ext2 file, or extracted from tar.gz). While this seems to be a rootfs issue, it still could be the build of init, as replacing the Familiar Linux init.sysvinit with the one generated by OpenEmbedded does in fact break the working file system. I tried reducing the size of generated rootfs (by setting <SPAN class=term>IMAGE_ROOTFS_SIZE), but that doesn't seem to be working either (so I cannot use the OpenEmbedded rootfs as an initrd, as it is 64 MB, which seems to cause problems on the target system). BTW, the OpenEmbedded generated linuxrc file is just a link to /bin/busybox, which seems a bit strange - so perhaps this is the issue?</SPAN></P>
<P><SPAN class=term></SPAN> </P>
<P>Hopefully this helps other folks - by not trying these same things.</P>
<P> </P>
<P>... Russell</P>
<P> </P>
<P> </P>
<P><BR><BR>On Wed, Dec 22, 2010 11:28 PM, <openembedded@rkmorris.us> wrote:<BR></P>
<BLOCKQUOTE style="BORDER-LEFT: rgb(0,0,204) 2px solid; PADDING-LEFT: 4px; MARGIN-LEFT: 16px">
<DIV style="FONT-FAMILY: Arial; FONT-SIZE: 10pt">Hi,<BR><BR>I have been strugging with this for quite some now, and really am stuck - so I really would appreciate any thoughts or pointers anyone has! Let me try to explain my problem.<BR><BR>I have been able to build OpenEmbedded on my machine, with a target of either h1940 or qemuarm - and for the console-image both build just fine. I can use the kernel for both of these (on the appropriate target), but my issue is with the rootfs. If I use the OpenEmbedded built rootfs in qemuarm, targeted for either qemuarm or the h1940 (but always using the qemuarm kernel) everything works just fine.<BR><BR>My issue arises when trying to use the rootfs on the h1940 - I cannot get my system to boot, and actually INIT is never launched (but the kernel seems fine). If I take an old file system that I was able to find (from Familiar Linux, ~ 2004-2005 vintage), it works fine on my h1940 (with the kernel from OpenEmbedded!) ... so the issue seems to be the rootfs. If I just replace /sbin/init.sysvinit in the Familiar Linux file system with the one from OpenEmbedded - then I get kernel panic (and no init found it says ... :-(). Oddly enough, if I use the Familiar LInux file system with qemuarm - it doesn't work, I have file system errors (and kernel panic), but the OpenEmbedded built file system (even for the h1940) works just great).<BR><BR>So it seems that I have some sort of filesystem incompatibility ... or am I wrong? BTW, I can load the above mentioned filesystems as ext2 or ext3 in (OpenSUSE) Linux, no issues there.<BR><BR>Again, any suggestions of how to fix this would be greatly appreciated!<BR><BR>Thanks!<BR><BR>... Russell<BR><BR><BR>_______________________________________________<BR>Openembedded-users mailing list<BR><A href="mailto:Openembedded-users@linuxtogo.org" target=_blank>Openembedded-users@linuxtogo.org</A><BR><A href="http://server.home:8080/redir.hsp?url=%68%74%74%70%3A%2F%2F%6C%69%73%74%73%2E%6C%69%6E%75%78%74%6F%67%6F%2E%6F%72%67%2F%63%67%69%2D%62%69%6E%2F%6D%61%69%6C%6D%61%6E%2F%6C%69%73%74%69%6E%66%6F%2F%6F%70%65%6E%65%6D%62%65%64%64%65%64%2D%75%73%65%72%73" target=_blank>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users</A><BR></DIV></BLOCKQUOTE></body></html>