woops. i screwed up on the first ipk. made a new one and someone is testing it.
update...i added the new ipk. Some problems i came accross was going between modules.rom and modules. reason being is that modules.rom has the original driver while the modules carries a symlink-looks like one. so what the installer does is overwrites the symlink. the original driver stays as is in the modules.rom directory. Not sure if the file system is the same on all handhelds. But that was really my dilema.
papadon tested a few ipk's and now his sandisk 2gb works fine. he used the ipk installer.
So there you have it folks. ipk is at the start of this thread.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120894\"][{POST_SNAPBACK}][/a][/div]
Cresho and anyone else interested in this,
All the C3x00/C1000 Zauri use 2.4.20 linux kernel (unless you install OZ which use 2.6.15 or BSD)
They are all the same, except some have extra updated patches (ie tetsu special kernel)
The kernel sources are available from Sharp, except for the sd module which is binary only so nobody can update the driver except Sharp.
Sashz has compiled an opensource replacement for pdaXrom which, because it is opensource. we have the source code for it. And because pdaXrom is also using 2.4.20 kernel, the modules can be compiled for Sharp ROM or even copied over.
Now with the 3200 sd module, you can remove the symlink from /lib/modules/2.4.20/kernel/drivers/block/sharp_mmcsd_m.o and replace it with the new module, or you can replace the one under /lib/modules.rom/2.4.20/kernel/block/sharp_mmcsd_m.o directly, you you will need to remount / as rw before you can do that. On a C3000, that would be preferrable, because of the limited size of the NAND, but it is also dangerous because, if the NAND gets full during the replacement, you will not be able to update nor delete files from the NAND anymore unless you reflash the kernel. Same is with /home which is an another NAND partition, but it is not as crammed full as the / partition on the other NAND partition.
Also, it would be a good idea to unmount /mnt/card first and then shut down the SD manager by running /etc/rc.d/init.d/sd stop. Once you replace the module, you can start the SD manager again /etc/rc.d/init.d/sd start and you should be able to mount your SD card again without requiring a reboot.