From: ohm u. <oun...@ya...> - 2005-12-28 22:01:18
|
Hi all, I gained a bit of insight while playing around with the mmc card and its associated tools in the buildroot. However, I am once again at a stopping point. I have made a ext2 filesystem on the mmc card using mke2fs, it mounts correctly and right now has a lost+found directory as opposed to what was on there before. So all is good up until there. What I wanted to do now is get Linux on there (mmc card). I did not find much info except for this tidbit from the wiki http://www.gumstix.org/tikiwiki/tiki-view_faq.php?faqId=7&highlight=native#q344 here's what i think i need to do: (please advise where necessary) 1. build whatever source I choose for the pxa2xx 2. load fs image on to the mmc card 3. change kernel arguments to point to the mmc as the default mount point As usual, I'll keep searching the wiki and the archives, but any help would be appreciated. Thanks again, everyone! Ohm. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: Chris D. <chr...@gm...> - 2005-12-28 22:18:56
|
SSdtIG5vdCBzdXJlIGlmIHRoaXMgd291bGQgd29yayBvciBub3QsIGJ1dCBpdCBzZWVtcyBsaWtl IHNpbmNlIHlvdSBjYW4KbW91bnQgeW91ciBNTUMgY2FyZCB5b3Ugc2hvdWxkIGJlIGFibGUgdG8g anVzdCBtb3ZlIHNvbWUgZmlsZXMgb250byBpdCBhbmQKc3ltbGluayB0aGVtIGluIHRoZSByZWd1 bGFyIGZsYXNoIHNwYWNlIHRvIHRoZSBmaWxlcyBvbiB0aGUgTU1DIGNhcmQuCgpTbyBpbiB0aGUg Y2FzZSB3aGVyZSB5b3Ugd2FudCB0byBhZGQgc29tZXRoaW5nIGxpa2UgdGlueXggdG8gdGhlIGJ1 aWxkcm9vdApidXQgZG9pbmcgc28gd291bGQgbWFrZSB0aGUgcm9vdF9mcyBpbWFnZSB0byBsYXJn ZSwgSSB3b3VsZCBndWVzcyB0aGF0IHlvdQp3b3VsZCBiZSBhYmxlIHRvIGRvIGEgYnVpbGQgb2Yg dGhlIGJ1bGRyb290IHdpdGhvdXQgdGlueXgsIGNvcHkgdGhhdCBvbnRvCnRoZSBndW1zdGl4IGZs YXNoLCBhbmQgYm9vdC4gIFRoZW4geW91IGNvdWxkIGVuYWJsZSB0aW55eCBpbiB0aGUgYnVpbGRy b290Cm1ha2VmaWxlIHNvIHRoYXQgaXQgd291bGQgY29tcGlsZSwgZXRjLiAgVGhlbiB5b3UgY291 bGQgdGFrZSBqdXN0IHRoZSB0aW55eApiaW5hcnkgdGhhdCB5b3UganVzdCBidWlsdCBhbmQgbW92 ZSB0aGF0IHRvIHNvbWV3aGVyZSBvbiB5b3VyIE1NQy4gIFRoZW4geW91CmNvdWxkIHN5bWxpbmsg dG8gdGhlIHRpbnl4IG9uIHRoZSBNTUMgZnJvbSB0aGUgcmVndWxhciBmbGFzaC4KCkxpa2UgSSBz YWlkLCBJIGhhdmUgbm8gY2x1ZSBpZiB0aGlzIHdpbGwgd29yaywgYnV0IGRvaW5nIHNvbWV0aGlu ZyBsaWtlIHRoYXQKbWlnaHQgYmUgZWFzaWVyIHRoYW4gdHJ5aW5nIHRvIGdldCB0aGUgZnMgdG8g bG9hZCBmcm9tIHRoZSBNTUMgZGlyZWN0bHk/Pz8KCkNocmlzCgpPbiAxMi8yOC8wNSwgb2htIHVu bW9uZ2tvbHRoYXZvbmcgPG91bm1vbmdrQHlhaG9vLmNvbT4gd3JvdGU6Cj4KPiBIaSBhbGwsCj4K PiBJIGdhaW5lZCBhIGJpdCBvZiBpbnNpZ2h0IHdoaWxlIHBsYXlpbmcgYXJvdW5kIHdpdGgKPiB0 aGUgbW1jIGNhcmQgYW5kIGl0cyBhc3NvY2lhdGVkIHRvb2xzIGluIHRoZQo+IGJ1aWxkcm9vdC4K Pgo+IEhvd2V2ZXIsIEkgYW0gb25jZSBhZ2FpbiBhdCBhIHN0b3BwaW5nIHBvaW50LiBJIGhhdmUK PiBtYWRlIGEgZXh0MiBmaWxlc3lzdGVtIG9uIHRoZSBtbWMgY2FyZCB1c2luZyBta2UyZnMsCj4g aXQgbW91bnRzIGNvcnJlY3RseSBhbmQgcmlnaHQgbm93IGhhcyBhIGxvc3QrZm91bmQKPiBkaXJl Y3RvcnkgYXMgb3Bwb3NlZCB0byB3aGF0IHdhcyBvbiB0aGVyZSBiZWZvcmUuIFNvCj4gYWxsIGlz IGdvb2QgdXAgdW50aWwgdGhlcmUuCj4KPiBXaGF0IEkgd2FudGVkIHRvIGRvIG5vdyBpcyBnZXQg TGludXggb24gdGhlcmUgKG1tYwo+IGNhcmQpLiBJIGRpZCBub3QgZmluZCBtdWNoIGluZm8gZXhj ZXB0IGZvciB0aGlzIHRpZGJpdAo+IGZyb20gdGhlIHdpa2kKPgo+IGh0dHA6Ly93d3cuZ3Vtc3Rp eC5vcmcvdGlraXdpa2kvdGlraS12aWV3X2ZhcS5waHA/ZmFxSWQ9NyZoaWdobGlnaHQ9bmF0aXZl I3EzNDQKPgo+IGhlcmUncyB3aGF0IGkgdGhpbmsgaSBuZWVkIHRvIGRvOiAocGxlYXNlIGFkdmlz ZSB3aGVyZQo+IG5lY2Vzc2FyeSkKPgo+IDEuIGJ1aWxkIHdoYXRldmVyIHNvdXJjZSBJIGNob29z ZSBmb3IgdGhlIHB4YTJ4eAo+IDIuIGxvYWQgZnMgaW1hZ2Ugb24gdG8gdGhlIG1tYyBjYXJkCj4g My4gY2hhbmdlIGtlcm5lbCBhcmd1bWVudHMgdG8gcG9pbnQgdG8gdGhlIG1tYyBhcyB0aGUKPiBk ZWZhdWx0IG1vdW50IHBvaW50Cj4KPiBBcyB1c3VhbCwgSSdsbCBrZWVwIHNlYXJjaGluZyB0aGUg d2lraSBhbmQgdGhlCj4gYXJjaGl2ZXMsIGJ1dCBhbnkgaGVscCB3b3VsZCBiZSBhcHByZWNpYXRl ZC4gVGhhbmtzCj4gYWdhaW4sIGV2ZXJ5b25lIQo+Cj4gT2htLgo+Cj4KPgo+Cj4gX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4gWWFob28hIERTTCCWIFNvbWV0aGlu ZyB0byB3cml0ZSBob21lIGFib3V0Lgo+IEp1c3QgJDE2Ljk5L21vLiBvciBsZXNzLgo+IGRzbC55 YWhvby5jb20KPgo+Cj4KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tCj4gVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OiBTcGx1 bmsgSW5jLiBEbyB5b3UgZ3JlcCB0aHJvdWdoIGxvZwo+IGZpbGVzCj4gZm9yIHByb2JsZW1zPyAg U3RvcCEgIERvd25sb2FkIHRoZSBuZXcgQUpBWCBzZWFyY2ggZW5naW5lIHRoYXQgbWFrZXMKPiBz ZWFyY2hpbmcgeW91ciBsb2cgZmlsZXMgYXMgZWFzeSBhcyBzdXJmaW5nIHRoZSAgd2ViLiAgRE9X TkxPQUQgU1BMVU5LIQo+IGh0dHA6Ly9hZHMub3Nkbi5jb20vP2FkX2lkPTc2MzcmYWxsb2NfaWQ9 MTY4NjUmb3A9Y2xpY2sKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXwo+IGd1bXN0aXgtdXNlcnMgbWFpbGluZyBsaXN0Cj4gZ3Vtc3RpeC11c2Vyc0BsaXN0 cy5zb3VyY2Vmb3JnZS5uZXQKPiBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9s aXN0aW5mby9ndW1zdGl4LXVzZXJzCj4K |
From: Alexandre P. N. <al...@om...> - 2005-12-28 22:25:06
|
ohm unmongkolthavong escreveu: >[cut] >1. build whatever source I choose for the pxa2xx >2. load fs image on to the mmc card >3. change kernel arguments to point to the mmc as the >default mount point > > > That should work, except that i think by default gumstix's kernel don't compile in support for ext2, you may have to double check that (if you're going to specify it as the root mount point then you need to have built-in support compiled into the kernel, i.e. not a module). |
From: Craig H. <cr...@gu...> - 2005-12-29 00:28:34
|
On Dec 28, 2005, at 2:24 PM, Alexandre Pereira Nunes wrote: > ohm unmongkolthavong escreveu: > >> [cut] >> 1. build whatever source I choose for the pxa2xx >> 2. load fs image on to the mmc card >> 3. change kernel arguments to point to the mmc as the >> default mount point >> >> >> > > That should work, except that i think by default gumstix's kernel > don't > compile in support for ext2, you may have to double check that (if > you're going to specify it as the root mount point then you need to > have > built-in support compiled into the kernel, i.e. not a module). You'll also need to compile in (as opposed to using modules) all the MMC/SD stuff too. Then you should be able to remove the "rootfstype=jffs2" argument on the kernel command line (just drop it since default is ext2/3), replace root=1f02 with root=fe00 (if your ext2 parition is the whole MMC device) or root=fe01 (if your ext2 partition is partition #1 on the device). You can also actually support loading the kernel from the MMC device if you compile ext2 support into *u-boot*. Then instead of having to load the kernel from the internal flash device, you can load the kernel from the MMC card instead using the "extload" command instead of the "fsload" command -- ie change the u-boot "bootcmd" variable. You'll still need u-boot in the on-board flash since you can't avoid booting from memory address 0, which is in the on-board flash. C |
From: ohm u. <oun...@ya...> - 2005-12-29 16:15:24
|
Wow, lots of great information! Thanks everyone! I have one last question before I get my hands super dirty: If ext2 is the default filesystem, would it be possible to put the default gumstix linux onto the mmc? I ask because I recall in an earlier post about how jffs2 requires an underlying flash layer which the mmc doesn't have. What will I have to change in order for the default gumstix fs to be in ext2 format? I guess the most obvious is this in the makefile: #TARGETS+=ext2root # Must mount cramfs with 'ramdisk_blocksize=4096' #TARGETS+=cramfsroot # You may need to edit make/jffs2root.mk to change target # endian-ness or similar, but this is sufficient for most # things as-is... TARGETS+=u-boot jffs2root anythign else? Thanks in advance! Ohm. --- Craig Hughes <cr...@gu...> wrote: > On Dec 28, 2005, at 2:24 PM, Alexandre Pereira Nunes > wrote: > > > ohm unmongkolthavong escreveu: > > > >> [cut] > >> 1. build whatever source I choose for the pxa2xx > >> 2. load fs image on to the mmc card > >> 3. change kernel arguments to point to the mmc as > the > >> default mount point > >> > >> > >> > > > > That should work, except that i think by default > gumstix's kernel > > don't > > compile in support for ext2, you may have to > double check that (if > > you're going to specify it as the root mount point > then you need to > > have > > built-in support compiled into the kernel, i.e. > not a module). > > You'll also need to compile in (as opposed to using > modules) all the > MMC/SD stuff too. Then you should be able to remove > the > "rootfstype=jffs2" argument on the kernel command > line (just drop it > since default is ext2/3), replace root=1f02 with > root=fe00 (if your > ext2 parition is the whole MMC device) or root=fe01 > (if your ext2 > partition is partition #1 on the device). > > You can also actually support loading the kernel > from the MMC device > if you compile ext2 support into *u-boot*. Then > instead of having to > load the kernel from the internal flash device, you > can load the > kernel from the MMC card instead using the "extload" > command instead > of the "fsload" command -- ie change the u-boot > "bootcmd" variable. > You'll still need u-boot in the on-board flash since > you can't avoid > booting from memory address 0, which is in the > on-board flash. > > C > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: David F. <dav...@ya...> - 2005-12-29 16:52:49
|
--- ohm unmongkolthavong <oun...@ya...> wrote: > I have one last question before I get my hands > super > dirty: If ext2 is the default filesystem, would > it be > possible to put the default gumstix linux onto > the > mmc? I have tried several variations (inluding what you are asking about, as Craig said, add ext2 to uboot), what works best for me is to mount the mmc as ext2 into the flash filesystem. I use multiple mmc partions replacing /opt and /var. I also leave a third small parition as fat so windows can still see what the card is. I had to be carefull about filesystem check issues on ext2 hanging the entire boot. Also be sure to use noatime. David |
From: Craig H. <cr...@gu...> - 2005-12-29 17:25:09
|
On Dec 29, 2005, at 8:15 AM, ohm unmongkolthavong wrote: > Wow, > lots of great information! Thanks everyone! > > I have one last question before I get my hands super > dirty: If ext2 is the default filesystem, would it be > possible to put the default gumstix linux onto the > mmc? > > I ask because I recall in an earlier post about how > jffs2 requires an underlying flash layer which the mmc > doesn't have. Yup, you'd have to modify the buildroot top-level Makefile to use "ext2root" instead of "jffs2root", or however "ext2root" needs to be spelled. I haven't ever done it, but I expect it'll then spit out an ext2 filesystem image as root_fs_arm_nofpu instead of a jffs2 one, and you can then dd that onto your MMC card or something. I don't know how you control the filesystem size though since ext2 needs to know how big it is; perhaps there's some option in there which will call resizeext2fs or however that app's spelled at the end... > What will I have to change in order for the default > gumstix fs to be in ext2 format? I guess the most > obvious is this in the makefile: > > #TARGETS+=ext2root > > # Must mount cramfs with 'ramdisk_blocksize=4096' > #TARGETS+=cramfsroot > > # You may need to edit make/jffs2root.mk to change > target > # endian-ness or similar, but this is sufficient for > most > # things as-is... > TARGETS+=u-boot jffs2root > > anythign else? Nope, I think that's it -- just remove jffs2root and add ext2root. Check the ext2root makefile to see how it's determining the size of the target filesystem, and edit to your needs (ie the size of your MMC card) C |
From: ohm u. <oun...@ya...> - 2005-12-29 19:50:29
|
Hi again, I am getting the error that David mentioned about the ext2 hanging the system boot. I enabled ext2 support on the buildroot for the flash and the mmc. The makefile was changed accordingly too. Also, in the kernel arguements I have root=fe01 to make it look at the mmc. Any takers? Also, I am trying to understand all the new information i'm getting on here. If I have a root_fs_arm_nofpu image and transfer that onto the mmc, will having root=fe01 make the mmc act as the new filesystem? How would I access stuff? would I use /mnt/mmc/usr/bin ? Is the root_fs_arm_nofpu like a .iso image for the gumstix? as usual, thanks! Ohm. --- Craig Hughes <cr...@gu...> wrote: > On Dec 29, 2005, at 8:15 AM, ohm unmongkolthavong > wrote: > > > Wow, > > lots of great information! Thanks everyone! > > > > I have one last question before I get my hands > super > > dirty: If ext2 is the default filesystem, would it > be > > possible to put the default gumstix linux onto the > > mmc? > > > > I ask because I recall in an earlier post about > how > > jffs2 requires an underlying flash layer which the > mmc > > doesn't have. > > Yup, you'd have to modify the buildroot top-level > Makefile to use > "ext2root" instead of "jffs2root", or however > "ext2root" needs to be > spelled. I haven't ever done it, but I expect it'll > then spit out an > ext2 filesystem image as root_fs_arm_nofpu instead > of a jffs2 one, > and you can then dd that onto your MMC card or > something. I don't > know how you control the filesystem size though > since ext2 needs to > know how big it is; perhaps there's some option in > there which will > call resizeext2fs or however that app's spelled at > the end... > > > What will I have to change in order for the > default > > gumstix fs to be in ext2 format? I guess the most > > obvious is this in the makefile: > > > > #TARGETS+=ext2root > > > > # Must mount cramfs with 'ramdisk_blocksize=4096' > > #TARGETS+=cramfsroot > > > > # You may need to edit make/jffs2root.mk to change > > target > > # endian-ness or similar, but this is sufficient > for > > most > > # things as-is... > > TARGETS+=u-boot jffs2root > > > > anythign else? > > Nope, I think that's it -- just remove jffs2root and > add ext2root. > Check the ext2root makefile to see how it's > determining the size of > the target filesystem, and edit to your needs (ie > the size of your > MMC card) > > C > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: David F. <dav...@ya...> - 2005-12-29 22:09:17
|
--- ohm unmongkolthavong <oun...@ya...> wrote: > /mnt/mmc/usr/bin ? Is the root_fs_arm_nofpu > like a > .iso image for the gumstix? > If you build it as ext2 then you should be able to loop mount the image. My initial test used an extra partition on my Fedora system. I used a 128MB partition then dd'd the root_fs image to it, extended the root_fs to fill the 128MB then when all fcsk'd ok I dd'd the parition to a mmc card partition of equal size. David. |
From: Craig H. <cr...@gu...> - 2005-12-29 22:30:48
|
On Dec 29, 2005, at 2:09 PM, David Farrell wrote: > > --- ohm unmongkolthavong <oun...@ya...> > wrote: > >> /mnt/mmc/usr/bin ? Is the root_fs_arm_nofpu >> like a >> .iso image for the gumstix? >> > > If you build it as ext2 then you should be > able to loop mount the image. > > My initial test used an extra partition on my > Fedora system. I used a 128MB partition then > dd'd the root_fs image to it, extended > the root_fs to fill the 128MB then when all > fcsk'd ok I dd'd the parition to a mmc card > partition of equal size. looking at make/ext2root.mk it looks a lot like you could just uncomment the GENEXT2_SIZE=100000 line and set it to be the number of blocks on your MMC card (normally blocks are 512 bytes, so the number of blocks will be drive_size_in_kb/2). That will make an ext2 "iso image" which you can then just dd directly to your MMC card. C |
From: Craig H. <cr...@gu...> - 2005-12-29 22:36:51
|
On Dec 29, 2005, at 11:50 AM, ohm unmongkolthavong wrote: > Hi again, > > I am getting the error that David mentioned about the > ext2 hanging the system boot. > > I enabled ext2 support on the buildroot for the flash > and the mmc. > > The makefile was changed accordingly too. > > Also, in the kernel arguements I have root=fe01 to > make it look at the mmc. > > Any takers? Ah, one other thing you'll need to change -- modify build_arm_nofpu/ root/etc/fstab to have the / filesystem mount itself from /dev/mmc/ mmc0/disc instead of from /dev/mtdblock2, and change its filesystem type. > Also, I am trying to understand all the new > information i'm getting on here. If I have a > root_fs_arm_nofpu image and transfer that onto the > mmc, will having root=fe01 make the mmc act as the new > filesystem? Yes -- the idea here is that (other than u-boot) you're basically just not using the gumstix internal flash. Your root filesystem will now be on the MMC card instead. "/" will be mounted from /dev/mmc/ mmc0/disc instead of from /dev/mtdblock2 > How would I access stuff? would I use > /mnt/mmc/usr/bin ? No -- your entire filesystem will be on the MMC card, not on the gumstix flash. An alternative to this strategy would be to put an overlay filesystem on the MMC card and then mount that on some subdirectory, but managing that is likely more tricky than just going whole-hog and having all the stuff on the MMC card. A third strategy for advanced students would be to use a root_fs on the gumstix flash, and then use unionfs to overlay the MMC card on top of that, with writes going to the mmc card. That'd actually be a really neat solution. > Is the root_fs_arm_nofpu like a > .iso image for the gumstix? Yup, pretty much. It's basically the entire contents of the "disk", just in a file. You could loop-mount the file, or you can just bitwise copy it to the physical disk. C |
From: ohm u. <oun...@ya...> - 2006-01-03 17:22:27
|
Hello everyone, Thanks for all the great information! I found all of it helpful, and I believe that I am close to achieving what I wantde to do with the mmc card. However, I am recieving a few errors. Check out this dmesg output // start dmesg output mmcblk0: mmc0:0001 AF RM 501760KiB mmcblk0: unknown partition table EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing init memory: 64K Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. //end dmesg output ALSO, to be sure (i'm a newb), I tried root=fe01 in the bootargs: //START mmcblk0: mmc0:0001 AF RM 501760KiB mmcblk0: unknown partition table VFS: Cannot open root device "fe01" or unknown-block(254,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,1) //END Here are my bootargs: console=ttyS0,115200n8 root=fe01 reboot=cold,hard video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19,lower:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 finally, the fstab: /dev/mmc/mmc0/disc / ext2 rw,noatime,auto 0 1 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /tmp tmpfs mode=1777 0 0 #/dev/mmc/mmc0/part1 /mnt/mmc ext2 noauto 0 0 Judging from my errors, I assume my ext2 filesystem that i made using the mke2fs program is incorrect, or at least not set up. May I run by you guys what i did with the mke2fs? once the mmc card was in the gumstix and the gumstix was booted into linux: 1) umount -a 2) mk2efs /dev/mmc/mmc0/disc Am I missing anything here? I didn't specify any specific ext2 file size. Would that be enough to cause the boot-up to hang? Thanks for all the help so far. My EE senior design group finally decided on using the gumstix for our senior project; this forum and the help it provided was a major selling point! I'll post some updates as we get the ball rolling! =p Ohm. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: Leonard S. <lsa...@co...> - 2006-01-03 17:35:56
|
Good day Ohm, It looks like there are two "issues" with one being a real problem and=20 the other just a complaint by the kernel: An actual problem: 1) The first dmesg output shows that Linux did in fact find and mount=20 your ext2 filesystem. The error is that it could not find a runnable=20 "init" program to run, so it appears that the filesystem is not=20 populated. The kernel looks in several places for an executable program=20 called "init": /bin/init, /usr/bin/init, /etc/init, and finally /init.=20 If it cannot find such an executable, then it complains and quits with=20 the message you see. It could be that you have the programs loaded but=20 without their executable permission bits set, or maybe the program=20 simply has not been placed where it is expected to be. The solution is=20 to check the contents of your root filesystem. A complaint that is not an error: 2) The complaints about unknown partition table result from your choice=20 to format the entire MMC card as a single partition, rather than using=20 the traditional partition table. You may want to consider formatting=20 your MMC card with a traditional partition table, even if you only have=20 a root partition on it. That will prevent the kernel from generating=20 complaints about the partition table. The traditional way of setting up=20 a mass storage device is using the "fdisk" program. I assume that you have used a workstation with an MMC reader/writer to=20 prepare the card? If so, you can always mount the MMC partition on the=20 workstation and investigate it from there. Good luck and good hunting! Len Samuelson ohm unmongkolthavong wrote: >Hello everyone,=20 > >Thanks for all the great information! I found all of >it helpful, and I believe that I am close to achieving >what I wantde to do with the mmc card. However, I am >recieving a few errors. Check out this dmesg output > >// start dmesg output >mmcblk0: mmc0:0001 AF RM 501760KiB > mmcblk0: unknown partition table >EXT2-fs warning: mounting unchecked fs, running e2fsck >is recommended >VFS: Mounted root (ext2 filesystem). >Freeing init memory: 64K >Warning: unable to open an initial console. >Kernel panic - not syncing: No init found. Try >passing init=3D option to kernel. >//end dmesg output > >ALSO, to be sure (i'm a newb), I tried root=3Dfe01 in >the bootargs: > >//START >mmcblk0: mmc0:0001 AF RM 501760KiB > mmcblk0: unknown partition table >VFS: Cannot open root device "fe01" or >unknown-block(254,1) >Please append a correct "root=3D" boot option >Kernel panic - not syncing: VFS: Unable to mount root >fs on unknown-block(254,1) >//END > >Here are my bootargs: >console=3DttyS0,115200n8 root=3Dfe01 reboot=3Dcold,hard >video=3Dpxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19= ,lower:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 > >finally, the fstab:=20 >/dev/mmc/mmc0/disc / ext2 =20 >rw,noatime,auto 0 1 >proc /proc proc defaults =20 > 0 0 >sysfs /sys sysfs defaults =20 > 0 0 >devpts /dev/pts devpts gid=3D5,mode=3D620 > 0 0 >tmpfs /tmp tmpfs mode=3D1777 =20 > 0 0 >#/dev/mmc/mmc0/part1 /mnt/mmc ext2 noauto > 0 0 > >Judging from my errors, I assume my ext2 filesystem >that i made using the mke2fs program is incorrect, or >at least not set up. May I run by you guys what i did >with the mke2fs?=20 > >once the mmc card was in the gumstix and the gumstix >was booted into linux:=20 >1) umount -a=20 >2) mk2efs /dev/mmc/mmc0/disc > >Am I missing anything here?=20 > >I didn't specify any specific ext2 file size. Would >that be enough to cause the boot-up to hang? > >Thanks for all the help so far. My EE senior design >group finally decided on using the gumstix for our >senior project; this forum and the help it provided >was a major selling point! I'll post some updates as >we get the ball rolling! =3Dp=20 > >Ohm. =20 > > > =09 >__________________________________________=20 >Yahoo! DSL =96 Something to write home about.=20 >Just $16.99/mo. or less.=20 >dsl.yahoo.com=20 > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log f= iles >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > > =20 > |
From: Leonard S. <lsa...@co...> - 2006-01-03 17:56:02
|
Correction on the last mail, I should have been more careful in=20 describing where the kernel looks for its "init" program. The file that=20 affects this is ".../init/main.c" in the kernel source tree. The part=20 that counts is near the end of the file, so it's easy to find. In the=20 snippet below, the "execute_command" string is initialized from the=20 "init=3D" parameter of the kernel command line. /* * We try each of these until one succeeds. * * The Bourne shell can be used instead of init if we are * trying to recover a really broken machine. */ if (execute_command) run_init_process(execute_command); run_init_process("/sbin/init"); run_init_process("/etc/init"); run_init_process("/bin/init"); run_init_process("/bin/sh"); panic("No init found. Try passing init=3D option to kernel."); } Leonard Samuelson wrote: > Good day Ohm, > > It looks like there are two "issues" with one being a real problem and=20 > the other just a complaint by the kernel: > > An actual problem: > > 1) The first dmesg output shows that Linux did in fact find and mount=20 > your ext2 filesystem. The error is that it could not find a runnable=20 > "init" program to run, so it appears that the filesystem is not=20 > populated. The kernel looks in several places for an executable=20 > program called "init": /bin/init, /usr/bin/init, /etc/init, and=20 > finally /init. If it cannot find such an executable, then it complains=20 > and quits with the message you see. It could be that you have the=20 > programs loaded but without their executable permission bits set, or=20 > maybe the program simply has not been placed where it is expected to=20 > be. The solution is to check the contents of your root filesystem. > > A complaint that is not an error: > > 2) The complaints about unknown partition table result from your=20 > choice to format the entire MMC card as a single partition, rather=20 > than using the traditional partition table. You may want to consider=20 > formatting your MMC card with a traditional partition table, even if=20 > you only have a root partition on it. That will prevent the kernel=20 > from generating complaints about the partition table. The traditional=20 > way of setting up a mass storage device is using the "fdisk" program. > > I assume that you have used a workstation with an MMC reader/writer to=20 > prepare the card? If so, you can always mount the MMC partition on the=20 > workstation and investigate it from there. > > Good luck and good hunting! > > Len Samuelson > > ohm unmongkolthavong wrote: > >> Hello everyone, >> Thanks for all the great information! I found all of >> it helpful, and I believe that I am close to achieving >> what I wantde to do with the mmc card. However, I am >> recieving a few errors. Check out this dmesg output >> >> // start dmesg output >> mmcblk0: mmc0:0001 AF RM 501760KiB >> mmcblk0: unknown partition table >> EXT2-fs warning: mounting unchecked fs, running e2fsck >> is recommended >> VFS: Mounted root (ext2 filesystem). >> Freeing init memory: 64K >> Warning: unable to open an initial console. >> Kernel panic - not syncing: No init found. Try >> passing init=3D option to kernel. >> //end dmesg output >> >> ALSO, to be sure (i'm a newb), I tried root=3Dfe01 in >> the bootargs: >> >> //START >> mmcblk0: mmc0:0001 AF RM 501760KiB >> mmcblk0: unknown partition table >> VFS: Cannot open root device "fe01" or >> unknown-block(254,1) >> Please append a correct "root=3D" boot option >> Kernel panic - not syncing: VFS: Unable to mount root >> fs on unknown-block(254,1) >> //END >> >> Here are my bootargs: >> console=3DttyS0,115200n8 root=3Dfe01 reboot=3Dcold,hard >> video=3Dpxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:= 19,lower:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363=20 >> >> >> finally, the fstab: /dev/mmc/mmc0/disc / ext2 =20 >> rw,noatime,auto 0 1 >> proc /proc proc defaults 0 = 0 >> sysfs /sys sysfs defaults 0 = 0 >> devpts /dev/pts devpts gid=3D5,mode=3D620 >> 0 0 >> tmpfs /tmp tmpfs mode=3D1777 0 = 0 >> #/dev/mmc/mmc0/part1 /mnt/mmc ext2 noauto >> 0 0 >> >> Judging from my errors, I assume my ext2 filesystem >> that i made using the mke2fs program is incorrect, or >> at least not set up. May I run by you guys what i did >> with the mke2fs? >> once the mmc card was in the gumstix and the gumstix >> was booted into linux: 1) umount -a 2) mk2efs /dev/mmc/mmc0/disc >> >> Am I missing anything here? >> I didn't specify any specific ext2 file size. Would >> that be enough to cause the boot-up to hang? >> >> Thanks for all the help so far. My EE senior design >> group finally decided on using the gumstix for our >> senior project; this forum and the help it provided >> was a major selling point! I'll post some updates as >> we get the ball rolling! =3Dp >> Ohm.=20 >> >> =20 >> __________________________________________ Yahoo! DSL =96 Something to= =20 >> write home about. Just $16.99/mo. or less. dsl.yahoo.com >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through=20 >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK= ! >> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> =20 >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log=20 > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: ohm u. <oun...@ya...> - 2006-01-03 19:41:55
|
Hi Len, thanks for the great info! I checked the build_arm_nofpu/root directory and checked if there was indeed an init program there. I saw it was in the /bin directory and that it's a link to busybox. Busybox was already set to be executble. To be absolutely certain, I recompiled and stuck it back onto the mmc card. Upon boot-up, I get the same error as before ("...try passing init=...). Is there anything else I should be looking at? Is linking to busybox going to hurt anything? Thanks again! Ohm. __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: Dave H. <dhy...@gm...> - 2006-01-03 20:33:17
|
Hi ohm, > I checked the build_arm_nofpu/root directory and > checked if there was indeed an init program there. I > saw it was in the /bin directory and that it's a link > to busybox. Busybox was already set to be executble. Since you can bootup using jffs2, I would create a traditional jffs2 image, but use a kernel that has ext2 built in. Getting that to boot should be straight-forward. The next to do is get to the point where you can mount the mmc card as an ext2 filesystem (or whatever filesystem you're trying to use). You should be able to browse the filesystem and see all of the files where you expect them to be. Until you can browse the filesystem like this, I wouldn't even bother worrying about booting into your file system. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Leonard S. <lsa...@co...> - 2006-01-03 21:07:22
|
Ohm, I'll answer as well as possible, though I cannot guarantee the answer... = :-) 1) Having /bin/init symlinked to busybox is OK, as long as the symlink=20 is really correct. I assume that you already know something about symlinks, on Linux workstations. First here are a few lines that I have copy/pasted from my workstation. I= 've set up the buildroot in an /opt/lcs/... directory, and the output from=20 "ls" shows that init is in the sbin directory, linked to busybox. When the unit=20 runs in the actual gumstix hardware, these directories should be in the root rather t= hen somewhere in /opt. > ls -l bin/init > pwd /opt/lcs/gumstix-buildroot/build_arm_nofpu/root > ls -l sbin/init lrwxrwxrwx 1 lcs users 14 2005-12-09 07:40 sbin/init -> ../bin/busybox > ls -l bin/busybox -rwxr-xr-x 1 lcs users 492020 2005-12-09 08:30 bin/busybox > I am surprised that you found init in .../bin rather than .../sbin. That=20 is not how my buildroot is setup. For now, I will assume that the symlinking is OK. 2) The next thing to look at is the basic system libraries. The ELF object/executable format is powerful but subtle, and has surprising dependencies. For example, on my gumstix: # ls -l /sbin/init lrwxrwxrwx 1 root root 14 Mar 4 2005 /sbin/init -> ../bin/busybox # ls -l /bin/busybox -rwxr-xr-x 1 root root 487924 Mar 4 2005 /bin/busybox # ldd /bin/busybox ldd: can't open cache '/etc/ld.so.cache' libcrypt.so.0 =3D> /lib/libcrypt.so.0 (0x4000d000) libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x40029000) libc.so.0 =3D> /lib/libc.so.0 (0x40038000) ld-uClibc.so.0 =3D> /lib/ld-uClibc.so.0 (0x40000000) In the example, /sbin/init is symlinked to /bin/busybox. /bin/busybox is an big executable file. Note, however, that it needs support from some dynamic libraries. This is why "ldd" is useful. In my system, if any of the libraries is missing or unavailable, then my "init" would not start u= p correctly. The kernel ELF executable program load function does not distinguish between being unable to start the executable program itself, such as /bin/busybox, and a missing (or improperly configured) critical startup library such as /lib/ld-uClibc.so.0. So you should check your library directory to make sure the supporting library files are present and correctly configured. Here is how my existing gumstix reports them: # ls -l /lib/ld* /lib/libuC* -rwxr-xr-x 1 root root 19968 Mar 4 2005 /lib/ld-uClibc-0.9.27.so lrwxrwxrwx 1 root root 19 Mar 4 2005 /lib/ld-uClibc.so.0 ->=20 ld-uClibc-0.9.27.so -rw-r--r-- 1 root root 272928 Mar 4 2005 /lib/libuClibc-0.9.27.so # I hope this helps. If not, then I may be able to find out a little bit mo= re by preparing my own MMC root setup and see if I can find out what else needs to be examined. Len Samuelson ohm unmongkolthavong wrote: >Hi Len,=20 >thanks for the great info!=20 > >I checked the build_arm_nofpu/root directory and >checked if there was indeed an init program there. I >saw it was in the /bin directory and that it's a link >to busybox. Busybox was already set to be executble.=20 > >To be absolutely certain, I recompiled and stuck it >back onto the mmc card.=20 > >Upon boot-up, I get the same error as before ("...try >passing init=3D...). Is there anything else I should be >looking at? Is linking to busybox going to hurt >anything?=20 > >Thanks again!=20 >Ohm. > > > > =09 >__________________________________________=20 >Yahoo! DSL =96 Something to write home about.=20 >Just $16.99/mo. or less.=20 >dsl.yahoo.com=20 > > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log f= iles >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > > =20 > |
From: David F. <dav...@ya...> - 2006-01-04 00:24:39
|
--- ohm unmongkolthavong <oun...@ya...> wrote: > //START > mmcblk0: mmc0:0001 AF RM 501760KiB > mmcblk0: unknown partition table > VFS: Cannot open root device "fe01" or > unknown-block(254,1) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to > mount root ... > finally, the fstab: > /dev/mmc/mmc0/disc / ext2 disc? Why is this not a parition? > rw,noatime,auto 0 1 > proc /proc proc > defaults > 0 0 > sysfs /sys sysfs > defaults > 0 0 > devpts /dev/pts devpts > gid=5,mode=620 > 0 0 > tmpfs /tmp tmpfs > mode=1777 > 0 0 > #/dev/mmc/mmc0/part1 /mnt/mmc ext2 > noauto > 0 0 > > Judging from my errors, I assume my ext2 > filesystem > that i made using the mke2fs program is > incorrect, or > at least not set up. May I run by you guys what > i did > with the mke2fs? > > once the mmc card was in the gumstix and the > gumstix > was booted into linux: > 1) umount -a > 2) mk2efs /dev/mmc/mmc0/disc > > Am I missing anything here? Again shouldn't this be a partion? How did you parition your mmc card? With Fdisk? David. |
From: ohm u. <oun...@ya...> - 2006-01-04 06:31:48
|
I used mke2fs to format the mmc. I was trying to make an ext2 filesystem on the mmc. I have been formatting the entire disc recently, but I get errors with /dev/mmc/mmc0/part1. I will post specifically what errors when I work on it in the morning. thanks again Ohm. --- David Farrell <dav...@ya...> wrote: > > > --- ohm unmongkolthavong <oun...@ya...> > wrote: > > > //START > > mmcblk0: mmc0:0001 AF RM 501760KiB > > mmcblk0: unknown partition table > > VFS: Cannot open root device "fe01" or > > unknown-block(254,1) > > Please append a correct "root=" boot option > > Kernel panic - not syncing: VFS: Unable to > > mount root > ... > > finally, the fstab: > > /dev/mmc/mmc0/disc / ext2 > > disc? Why is this not a parition? > > > rw,noatime,auto 0 1 > > proc /proc proc > > defaults > > 0 0 > > sysfs /sys sysfs > > defaults > > 0 0 > > devpts /dev/pts devpts > > gid=5,mode=620 > > 0 0 > > tmpfs /tmp tmpfs > > mode=1777 > > 0 0 > > #/dev/mmc/mmc0/part1 /mnt/mmc ext2 > > noauto > > 0 0 > > > > Judging from my errors, I assume my ext2 > > filesystem > > that i made using the mke2fs program is > > incorrect, or > > at least not set up. May I run by you guys what > > i did > > with the mke2fs? > > > > once the mmc card was in the gumstix and the > > gumstix > > was booted into linux: > > 1) umount -a > > 2) mk2efs /dev/mmc/mmc0/disc > > > > Am I missing anything here? > > Again shouldn't this be a partion? > > How did you parition your mmc card? > With Fdisk? > > David. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: David F. <dav...@ya...> - 2006-01-04 13:58:41
|
--- ohm unmongkolthavong <oun...@ya...> wrote: > I used mke2fs to format the mmc. I was trying > to make > an ext2 filesystem on the mmc. I have been > formatting > the entire disc recently, but I get errors with > /dev/mmc/mmc0/part1. I will post specifically > what > errors when I work on it in the morning. > It has been about a year since I did this (I'm typing from memory). From my Fedora (FC3) system I fdisk'd the mmc card to create 3 partitions. I created two ext2 paritions and one fat partition. I formatted the ext2 and fat partitions. I used tune2fs -i 0 option to disable time interval based (gumstix has no clock) fsck. I also believe I used -c 8 to force a check every 8 boots. (My system did not very often on). I then e2fsck'd both ext2 paritions. Only after all of the above did I move the card to the gumstix. In your case with the root fs, I would still run a e2fsck on a host system before using with the gumstix. David. |
From: ohm u. <oun...@ya...> - 2006-01-04 23:08:58
|
Hiya David, I am getting these errors after trying what you suggested: //boot up messages: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing init memory: 76K EXT2-fs error (device mmcblk0): ext2_check_page: bad entry in directory #2: directory entry across blocks - offset=0, inode=8420, rec_len=24804, name_len=0 Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. //end bootup messages at boot hangup did this on the gumstix using fdisk, since when I use fdisk on my workstation, it does not show /disc or /part1 and the gumstix does. I mounted /part1 and fdisk'ed two partitions on to them. I re-read the replies to this thread and there was mention of extending the size of the root_fs to fit the entire 128MB. I was wondering why this is needed, and how to do it. Thanks a lot! Ohm. --- David Farrell <dav...@ya...> wrote: > > > --- ohm unmongkolthavong <oun...@ya...> > wrote: > > > I used mke2fs to format the mmc. I was trying > > to make > > an ext2 filesystem on the mmc. I have been > > formatting > > the entire disc recently, but I get errors with > > /dev/mmc/mmc0/part1. I will post specifically > > what > > errors when I work on it in the morning. > > > > It has been about a year since I did > this (I'm typing from memory). > > From my Fedora (FC3) system I fdisk'd the > mmc card to create 3 partitions. I created > two ext2 paritions and one fat partition. > > I formatted the ext2 and fat partitions. > I used tune2fs -i 0 option to disable > time interval based (gumstix has no clock) > fsck. I also believe I used -c 8 to force > a check every 8 boots. (My system did not > very often on). > > I then e2fsck'd both ext2 paritions. > > Only after all of the above did I move the > card to the gumstix. > > In your case with the root fs, I would > still run a e2fsck on a host system before > using with the gumstix. > > David. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: David F. <dav...@ya...> - 2006-01-05 13:31:33
|
--- ohm unmongkolthavong <oun...@ya...> wrote: > Hiya David, > > I am getting these errors after trying what you > suggested: > > > //boot up messages: > EXT2-fs warning: mounting unchecked fs, running > e2fsck > is recommended > VFS: Mounted root (ext2 filesystem). > Freeing init memory: 76K > EXT2-fs error (device mmcblk0): > ext2_check_page: bad > entry in directory #2: directory entry across > blocks - > offset=0, inode=8420, rec_len=24804, name_len=0 > Warning: unable to open an initial console. > Kernel panic - not syncing: No init found. Try > passing init= option to kernel. > //end bootup messages at boot hangup > > did this on the gumstix using fdisk, since when > I use > fdisk on my workstation, it does not show > /disc or > /part1 and the gumstix does. I mounted /part1 > and > fdisk'ed two partitions on to them. I had problems with the gumstix native ext2 utilities, I did all the filesystem stuff on a Fedora box. Use dmesg to see that device to call your mmc when you plug it in. It is considered a scsi device, mine is sda so sda1 is the 1st part. > I re-read the replies to this thread and there > was > mention of extending the size of the root_fs to > fit > the entire 128MB. I was wondering why this is > needed, > and how to do it. Thanks a lot! I used resize2fs, see man resize2fs. If you need to resize the partition, you can usually delete the existing with fdisk and recreate it bigger and not lose anything (as long as you keep the same starting cylinder). David. |
From: ohm u. <oun...@ya...> - 2006-01-05 16:13:19
|
Hi all, I learned a lot during the course of this thread! Since I'm new to the gumstix, and Linux, even, knowing what to do next after all of your helpful suggestions was tough. Nonetheless, I'll point out my mistakes and what actually worked for the next newb who happens to want to do the same thing. dd did the trick, thanks a lot David! What I was doing before was simply plopping down the root_fs_arm_nofpu onto the mmc card using <cough> Konqueror. Since all I was doing was putting a file onto the mmc and trying to boot THAT, it kept panicing<sp> at boot-time. Using dd seems to put the exact image of what is in root_fs_arm_nofpu directly on the mmc, transforming it into a disk with an actual fs on it. I hadn't known about 'dd' until you guys mentioned it on here, so thank you very much for enlightening me. dd is such a powerful program! =p Also, the bootargs need to be changed such that the kernel looks to the mmc instead of to the defaul mtdblock2. here is my bootargs variable: console=ttyS0,115200n8 root=fe00 reboot=cold,hard (also some LCD stuff, but cut to save space) notice the root=fe00 the "fe" is the major number of the device you are looking at. Normally, root = 1f02. if you look at the major number of mtdblock2 on the gumstix, it's: # ls -l /dev/mtdblock2 brw-r----- 1 root root 31, 2 Jan 4 2006 /dev/mtdblock2 31 = 1f, the 02 in 1f02 is the actual device you are looking at, i.e. mtdblock 2. Correct me anywhere I'm wrong please. This thread will be helpful to other newbs like me! Thanks a lot, everyone. I learned a lot, and I hope it helped you guys stay sharp! =p Ohm. --- David Farrell <dav...@ya...> wrote: > > > --- ohm unmongkolthavong <oun...@ya...> > wrote: > > > Hiya David, > > > > I am getting these errors after trying what you > > suggested: > > > > > > //boot up messages: > > EXT2-fs warning: mounting unchecked fs, running > > e2fsck > > is recommended > > VFS: Mounted root (ext2 filesystem). > > Freeing init memory: 76K > > EXT2-fs error (device mmcblk0): > > ext2_check_page: bad > > entry in directory #2: directory entry across > > blocks - > > offset=0, inode=8420, rec_len=24804, name_len=0 > > Warning: unable to open an initial console. > > Kernel panic - not syncing: No init found. Try > > passing init= option to kernel. > > //end bootup messages at boot hangup > > > > did this on the gumstix using fdisk, since when > > I use > > fdisk on my workstation, it does not show > > /disc or > > /part1 and the gumstix does. I mounted /part1 > > and > > fdisk'ed two partitions on to them. > > I had problems with the gumstix native ext2 > utilities, I did all the filesystem stuff on > a Fedora box. > > Use dmesg to see that device to call your mmc > when you plug it in. It is considered a scsi > device, mine is sda so sda1 is the 1st part. > > > I re-read the replies to this thread and there > > was > > mention of extending the size of the root_fs to > > fit > > the entire 128MB. I was wondering why this is > > needed, > > and how to do it. Thanks a lot! > > I used resize2fs, see man resize2fs. If you need > to resize the partition, you can usually delete > the existing with fdisk and recreate it bigger > and not lose anything (as long as you keep the > same starting cylinder). > > David. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |