Openzaurus Install On C1000

[omro]

Hi

Is it possible to install the latest RC of OpenZaurus on to the C1000?

I saw a directory for the Akita, but files there don't seem to relate to the instructions in the install notes. Sorry if this is obvious to you all, but the notes on how to install the C1000 seem a little out of date or incomplete for the C1000.

I have no idea what file is the equivalent of initrd.bin this isn't covered at all by the notes.
There is also a mention about the flash partitioning, but if you don't know what the original flash sizes were (or how to change them back) that warning is just not helpful.

If anyone could help me and/or update the install notes, that'd be great.

Thanks

[Hrw]

go to http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4...4/images/akita/

click 'image to flash' of your favorite flavour - this will push SOMETHING-initrd.bin - rename to initrd.bin
click 'update script'
click 'kernel'

save to sd or cf and flash

[lardman]

Is it possible to install the latest RC of OpenZaurus on to the C1000?

Yes.

I have no idea what file is the equivalent of initrd.bin this isn't covered at all by the notes.

Download one of the gpe-, opie-, e-, bootstrap-images. Choose the "Image to flash" link for the one you want. Rename the .bin file which you get to "initrd.bin".

There is also a mention about the flash partitioning, but if you don't know what the original flash sizes were (or how to change them back) that warning is just not helpful.

See if it works first.

Anyone know what the partition sizes are on a vanilla Akita? You'd change it in the same way you did before, presumably using either the cacko or pdaX installer tool.


Si

[omro]

Well...

The Opie one came down as:

opie-image-3.5.4.1-rc4-akita.rootfs.img

Which looks nothing like initrd.bin

Ok.... looked again, why is there a direct link option if that gives you the wrong file type? confused by the point of that.

Will try again. Thanks.

[omro]

ok

I redownloaded everything.

it does all the flashing and reboots and then lines of errors, this is the last line...

Code: [Select]

JFFS2 error: (1) jffs2_build_inode_pass1: child dir "pics" (ino #2215) of dir ino #1663 appears to be a hard link
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
No clue what I've done wrong this time.

[omro]

Ok...

A size of 53 was too small
A size of 60 worked

I guess the optimum size is somewhere in between. How much of a difference does this really make if the partition is a little too big?