Dingoonity.org

With the card I had, I wasn't given the option for 32K block size unless I went through command prompt.  Windows only offered "Default" (4K).  Using Vista SP2 I am able to select 64K block size instead of 32K.  XP told me the card wasn't compatible with 64K block size.  Testing 64K block size now with the various zImages listed in this thread.  So far, backed up my dingux partition and tried tossing the zImage on and it failed to load.  I noticed this problem every time I went to change the zImage/rootfs I needed to format the SD card.  I am wondering if maybe dingux writes something to the start of the card when it is first run or something?  or do the rootfs and zImage have to be the first files on the disk?  If the latter is the case, that would explain why I always had issues updating to the new zImage (and probably solve the issues that others are having), but it doesn't explain why when I put the "working" zImage back on (without formatting) the dingux boots properly.
May need to grab a copy of the dingux source and read through the whole thing (large project that i don't currently have time for, but be good for in the future).
crossing my fingers...
Thanks for the new zImage and thanks for all the info that everyone posts... it keeps me motivated to keep poking at some projects (and testing).
The Gh0ce_>0

But I tried again with the 4-bit one and am getting corruption for sure.  Going back to the 1-bit with poweroff and going to do more testing.  Sucks that the corruption is still occuring... wonder what exactly is causing it and why it seems to occur a lot more often with lower block sizes?

Until the problem is solved (if it can be solved), I'd personally like to see a kernel with 4-bit reads and 1-bit writes (since I assume there's no corruption when reading).

Booboo's already said this wouldn't be straightforward, however.

Hey vimrc I tried to do insert the options of switching between IPU enabled and IPU disabled zImages. I followed your instructions but I can't get it to run. This is what it says when I try to use the IPU enable function from a IPU disabled zImage:

cp: cannot stat './zImage': no such file or directory

Any idea why this is showing? I followed your instructions with the scripts and all already. In fact, I opened the scripts and tried to change it from /boot/cp to /boot/local to see if it help. Instead, it shows some access denied thing.

Please help!

Let me have a look.

There's any zImage-enabled-poweroff for LCD 9938 available at this moment??

Yeah I know, I'm already using opendingux on another sd card but I'm waiting the third installment to make the total migration to OD  (Impressive work btw).  So there's no turn-off for dingux legacy with the new screen, good to know that.
Anyway, thanks Ayla.