fanoush | # 11 | 2007-12-13, 22:48 | Report

There is also newer version of that - kernel based on MMC taken from N800 2.6.18 kernel which also has SDHC functionality but may (or may not) also work slightly better with MMC cards. http://fanoush.wz.cz/maemo/#sdhc This is newer code with many fixes but not so well tested as the older mmcplus kernel. There are only versions with multiblock writing enabled because this is enabled by default in 2.6.18 kernel.

PattiM | # 12 | 2007-12-14, 16:28 | Report

It seemed complicated, but was simple, actually. I now boot from both the mmc and internal memory, but as mentioned there doesn't seem to be any significant speed up. Still waiting for noob instructions for enabling multiblock read/write.
Patti

PS: I forgot to mention that if the user only uses Linux on their laptops/desktops, then we can dispense with the fat16 partition, can't we? And what're the advantages to using fsck as opposed to e2fsck, the latter of which I use on my SuSE systems...

PPS: In reference to the mmc wear associated with ext2/ext3 - I think mmc is so cheap that one could "clone" their mmc card to a backup mmc card periodically (with an mmc card reader and g4l) and use ext3 to avoid frustrating (unrecognized) file corruptions. With this in mind, could you indicate the command to format ext3?

PPPS: I also noticed that there doesn't seem to be a .bash-history file between boots - so I have to memorize the fsck disk check command and run it a LOT. I would be running fsck at least once a day...

---

Last edited by PattiM; 2007-12-14 at 16:52.

brian911 | # 13 | 2007-12-14, 21:26 | Report

Hi Patti:
Which MMC card are you using? To format to EXT3, it's the same mke2fs command, but with -j switch (since EXT3 is just EXT2 with journalling).

Bundyo | # 14 | 2007-12-14, 21:31 | Report

Or mkfs.ext3

norom | # 15 | 2007-12-18, 01:04 | Report

If the WLAN memory bug-fix was installed on flash and then copied to the mmc with everything else does it not need to be installed again onto the mmc?
thx.

brian911 | # 16 | 2007-12-18, 02:29 | Report

No, you don't have to. You are cloning the system to the MMC which already includes the patch to the OS.

dont | # 17 | 2008-01-29, 14:34 | Report

Brian:

I have just followed your recipe and it worked out fine for me.

I decided to go for an ext3 rather than an ext2 file system so I was a little worried about the following line (used 2x):

insmod /mnt/initfs/lib/modules/current/ext2.ko

I tried substituting ext3.ko with no luck so I went ahead and used the line as above. Everything seems to be working fine so far, but I wonder if I should have found an ext3.ko?

Finally, I have a Kingston 2GB. MMC card so I would like to try Fanoush's MMCPlus + Multiblock Writes experimental kernel. I think that you have been using this kernel on the same hardware. If so, any thoughts?

coffeedrinker | # 18 | 2008-01-29, 21:54 | Report

To use ext3 you need to use these:

insmod /mnt/initfs/lib/modules/2.6.21-omap1/mbcache.ko
insmod /mnt/initfs/lib/modules/2.6.21-omap1/jbd.ko
insmod /mnt/initfs/lib/modules/2.6.21-omap1/ext3.ko

YOU MUST ALSO change them in the boot menu.

dont | # 19 | 2008-01-29, 22:41 | Report

I have been running all day using ext2.ko on a ext3 file system with no apparent problems.

Should I start over again completely? Do I have to re-partition or re-format?

coffeedrinker | # 20 | 2008-01-29, 22:53 | Report

LOL I have no idea! I'm not that savvy about the filesystems. All I know is, the filesystems are the same except for the journal that ext3 uses, which you are not using. That's why it all works for you. There are some commands to enable the journal but I don't know them off hand.