I Mounted A 2 Gig Sd Card!, Surprise, it's possible! :) Options

[cybersphinx]

However, I have further question: How could I replace the original sharp_mmcsd_m.o to the fixed one under /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/ ??

I guess that I may replace the original file by the following methods, please tell me which one is correct:

1. Delete the original sharp_mmcsd_m.o under /lib/modules/, and use Tree!Explorer copy and paste the fixed one to the same directory, reboot??

2. Using Terminal to replace the original file. But I do not know how to do it, could you tell me the method??

3. Should I re-link the fixed file to the original sharp_mmcsd_m.o under /lib/modules.rom/?? Or I have to create a new link?? If I have to create the new link, how to create the new link??

On the command line, something like the following should work:
cd /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/
mv sharp_mmcsd_m.o sharp_mmcsd_m.o.old [to make a backup, if you don't have one yet]
cp /mnt/card/new_module.o sharp_mmcsd_m.o [/mnt/card is the SD-Card, adjust to the path of the new module]

TreeExplorer probably also works. Linking is not necessary (things in /directory.rom/ are linked into /directory/, but not the other way around). Rebooting also isn't necessary, you can do "depmod -a; rmmod sharp_mmcsd_m; modprobe sharp_mmcsd_m" as root on the console.

[xamindar]

Thanks for your reply, it works!!! I have backup the original files!!

However, I have further question: How could I replace the original sharp_mmcsd_m.o to the fixed one under /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/ ??

Do you mean "put the original sharp rom module back in case this new one doesn't work?" All you need to do is re-link the one from the /lib/modiles.rom folders.

I guess that I may replace the original file by the following methods, please tell me which one is correct:

1. Delete the original sharp_mmcsd_m.o under /lib/modules/, and use Tree!Explorer copy and paste the fixed one to the same directory, reboot??

That will work just fine. There is a way to get it working without rebooting but the simplest way is to just reboot.

2. Using Terminal to replace the original file. But I do not know how to do it, could you tell me the method??

cd /lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block
--if the new module is on your sd card:
cp /mnt/card/sharp_mmcsd_m.o .
--if the module is on your cf card:
cp /mnt/cf/sharp_mmcsd_m.o .
--Of course, if you have the new module anywhere else just find out where (zaurus documents directory: /home/zaurus/Documents) and like cybersphinx said, just press the TAB key to see available folders or to autocomplete the name of a file or directory.
Then type "reboot" to restart the zaurus.

3. Should I re-link the fixed file to the original sharp_mmcsd_m.o under /lib/modules.rom/?? Or I have to create a new link?? If I have to create the new link, how to create the new link??

No relink needed. Think of all the .rom directories as "installation files". They are basically the whole original factory OS. If you are installing an updated or modified version of a file linked from these directories you don't need the original .rom version any more and can just ignore it.

If you were to totally screw up your zaurus to the point it is unusable or if you just wanted to restore it to its factory defaults, you would just run the format command in the zaurus' secret maintenance menu which would relink all those .rom files so you have a fresh insatall.

[qx773]

You can make the root folder writable by using:

su
mount / -o rw,remount

After you are done copying the new module into its proper location, you can make the root folder read-only again by typing:

mount / -o ro,remount

[enclose789]

Thanks again to Cyril92, Cybersphinx, Xamindar, and QX773, now my 6000L can recognize the 2GB SD card, and so far it works flawlessly!!

Thank you for teaching me how to use Console!!

Further thanks to pelrun for making it!! It's really amazing!!

[thanhnam2k]

Anyway, if you want to repeat my experiment, just download and install this ipk, and reboot the Zaurus:

http://c-guys.net/cgi-bin/download/passche...m.ipk&key=1

Could you please attached this file here?
I cannot connect to c-guys site.

Thanks so much

[speculatrix]

Anyway, if you want to repeat my experiment, just download and install this ipk, and reboot the Zaurus:

http://c-guys.net/cgi-bin/download/passche...m.ipk&key=1

Could you please attached this file here?
I cannot connect to c-guys site.

Thanks so much

just uploaded it for you - look on my website in downloads, in sharp directory, called sd-link11b_us_jpn_arm.ipk

[thanhnam2k]

just uploaded it for you - look on my website in downloads, in sharp directory, called sd-link11b_us_jpn_arm.ipk

You're so nice
I'm gonna to test it.

Thank you very very much

[xamindar]

Did anyone ever stick with this driver? I finally bought some 2gig cards and have been testing this driver. Looks like it will eventually lock up the zaurus until the SD card is removed if you attempt to do long file copies. And this is not just with 2 gig cards, it will do it with any of my SD cards. I guess it is ok if you don't just copy things straight from it for long periods of time. Looking through this thread many people said they will report back on their results but not many did. Did you guys stop using it? Is this just maybe an issue with the c3100 and this driver? But I'm using an eviljazz kernel so maybe something with that?

[cybersphinx]

Did anyone ever stick with this driver? I finally bought some 2gig cards and have been testing this driver. Looks like it will eventually lock up the zaurus until the SD card is removed if you attempt to do long file copies. And this is not just with 2 gig cards, it will do it with any of my SD cards. I guess it is ok if you don't just copy things straight from it for long periods of time. Looking through this thread many people said they will report back on their results but not many did. Did you guys stop using it? Is this just maybe an issue with the c3100 and this driver? But I'm using an eviljazz kernel so maybe something with that?

You mean pelrun's driver? I've been using it on my c760 since then, and didn't notice any problems I could attribute to the driver. But then I'm doing all my copying in a card reader and not on the Zaurus itself.

[speculatrix]

I had problems doing big file copies to the zaurus with cacko even before I put the new sd driver in place; I always assumed it was the usb networking as it was very inconsistent how long it'd last.

I guess to prove it one should copy files from host /dev/null, and on the zaurus to "dd if='/dev/urandom of=/mnt/card/junk bs=1024 count="1000000" etc, and then cat that random file back to /dev/null to force reading it.

[pelrun]

The c3100 uses the official c3200 sharp driver, not my hacked one

I too have had issues transferring large files directly to the SD card over usb networking; using scp to copy didn't help things as it increases the cpu load significantly. But I've never had any trouble transferring files of any size to or from the card to hd or nand.

[koan]

Hi

I have a 2 GB Sandisk SD card in my 750 and it works fine using these scripts,
except that when going to standby the card is unmounted and mounted
again at power on.

I want to use applications that have open files on the SD card, or
leave a shell in a working directory on the card when I go to standby.
If I leave open files then the card cannot be remounted and the
apps that had the file locks fail in various ways.

So I want to change it so that the card is not unmounted when going to
standby. Has anyone got that functionality working ?

My investigation using the logfile shows that
- suspend/power on cycle calls sdiomgr with "attach"
- manually inserting the card calls sdiomgr with "attach"
- selecting eject from SD icon does not call sdiomgr
- manually ejecting the card calls sdiomgr with "detach"

The modified sdiomgr script runs sdcontrol with "compeject" then "insert"
for "attach". I tried changing "compeject" to "eject" because it doesn't unmount
if there are open file locks however it didn't work - the card appears as
if it is mounted but I can't access anything on it.

If I try to simulate this sequence by change directory to card, su, run eject
and then insert the card remains mounted and visible. I'm guessing the
kernel driver resets open file locks when going to standby, but I am no expert.

By the way, the card is VFAT and I am using Sharp ROM.

Thanks