Sorry to say, nope :( Midori and m4i seems to be collecting dust as well. I've tried m4i on mine, and had problems.. Jailbait was worse - it kept trying to use modprobe, but modprobe wasnt even installed (!!).
So.. I built a 2.6 kernel for the iopener. I have 2 choices here..
1.) Boot the 2.6 kernel from the sandisk, via dos, using loadlin, and set the root to be /dev/hda, which is a CF attached to a CF to IDE converter, which is then attached to the IDE header..
2.) Same setup as above, except i'll be running off the CF, rather than sandisk.
I'll most likely do #2, since I want to use grub and have a cute splashimage when grub loads, and cover up all the loading messages.. especially since I'm doing this for my brother, who knows how to use a computer, but doesnt know much more than that.
My setup will be pretty limited, but basically the way I'm doing it - others can do it in the same way.
I'm using gentoo. I'm building a basic system that uses a stage3 (read the gentoo doc at www.gentoo.org, you'll know what i mean) and then I just build a 2.6 kernel that doesnt use modules - that has yamaha support compiled in, via motherboard support compiled in, etc. etc. This way I dont have to worry about needing modules, and 2.6 supports most of the hardware that I need.
I'm building this system in vmware for windows - which is a virtual PC in a PC. you can also build it on another hard drive, or so.. do NOT do this on an existing CF. for one.. it will take over 1gb just for the basic stuff. it took 1.1gb for me. if you have a compact flash hard drive (i.e. a CF that is an actual hard drive, not a normal flash drive) - then its not an issue. but if you have a normal cf, you could kill it by building on it, due to the limited write life.
With gentoo, I can just "emerge" anything i need. emerge will download the source, build the source for the specific chip (i586 in my case) and then install it. that way I can keep track of whats there, and remove anything I dont need.
When I'm done, I'll mount my 512mb compactflash under my system. I'll then use grub to make the CF bootable, and then copy most of the stuff from my harddrive to the CF with some exceptions. I'm not copying the portage files, since those can be over 500mb total. I'm not going to use emerge on the iopener at all, which is a disadvantage. However, it does give me more free space.
To boot linux on anything, you need at least the kernel, the init program in /sbin, and you need /etc/inittab. You also need /etc/init.d. Dont forget to check any extra programs to make sure you have their dependencies (use ldd). Its a pain in the butt.
I'm still figuring out how I'll do linux on the CF. I know that the root will be mounted readonly, with /tmp being a ramdisk, and /home will be another partition. this way /home can be mounted as read-writable if the user has to save something, then it'll be remounted as read-only. I'll also probably use cramfs.
I'll keep you posted if you're interested in what I'm doing, or if anybody else is interested. I'm trying to use the latest kernels, and to outline a way that most people can build their own customized i-opener linux distros without getting into really complicated stuff.
1.) Setup a hard drive that you dont care about, format it and install gentoo. Or use vmware workstation in windows for this.
2.) Setup packages you want in your "system".
3.) Make partitions in your CF, and copy over the stuff you really want to use.
4.) Grub and make your CF bootable.
5.) Put your CF into your iopener and enjoy.
Note: I'm still putting stuff on my 'system' disk, I havent started on putting stuff in the CF and testing on the iopener, but the kernel does work. So bear with me, I'll probably change stuff around before finalizing it.