OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: Pyrates on January 17, 2004, 01:49:25 pm
-
Hi there!
I want to customize my rom, but I have a small problem... I can\'t get it :?
Now, the thing is, I found a description on http://docs.zaurus.com/index.php?id=buildi...ding_custom_rom (http://docs.zaurus.com/index.php?id=building_custom_rom) how to basically do it, but retrieving the filesystem isn\'t covered there. I mean, I have the initrd.bin, that\'s where it is, right? I can\'t mount it as a cramfs, but using losetup as described there doesn\'t work as well, the final mount give the usual \"wrong filesystem\" error message (if I use it with -t cramfs, without mount complains about unknown filesystem...). So, can anybody tell me how to actually retrieve the filesystem? Does OZ feature the build.sh skript to make back into an initrd.bin afterwards?
Thanks for any help, cheers
Philipp
-
The reason you can\'t mount it is that it\'s a jffs2 image. There is a way of mounting this (try a search of this forum and the www.zaurus.com/dev/board one for \'mount and jffs2\' or similar) but I can\'t remember it off the top of my head.
Si
-
Found it:
modprobe mtdblock
modprobe mtdram -o total_size=16384
modprobe jffs2
dd if=initrd.bin of=/dev/mtdblock/0
mount -t jffs2 /dev/mtdblock/0 mnt/initrd
Si
-
Thanks I\'ll have to recompile my kernel for that, maybe I\'ll switch to 2.6 today...
Cheers
Philipp
-
So, switch done Now, I\'m not getting anywhere, I have CONFIG_MTD_RAM=m set, but I don\'t get a mtdram module. Does anybody know about that, what do I have to configure?
Otoh, I don\'t know how to get /dev/mtdblock/0, because I don\'t have such a file.
If I did a dd if=/dev/mtdblock/0 of=/home/pips/initrd.bin after doing all you suggested, would I get a valid initrd that I could flash on my zaurs?
Man, I have a lot of questions Thanks for helping
Cheers
Philipp
-
Ummm... got it... Well, got the module (there actually is CONFIG_MTD_MTDRAM to be set).
And ... *more Ummm* didn\'t do my homework, a bit of googling showed me how to get my /dev/mtdblock/* ... sorry for that!
Still need help on the last issue, but I think I\'m just gonna try
Cheers
Philipp
-
If I did a dd if=/dev/mtdblock/0 of=/home/pips/initrd.bin after doing all you suggested, would I get a valid initrd that I could flash on my zaurs?
Hmm, you\'ll be able to access the files in the filesystem. I presume you can also write to the filesystem. Assuming you don\'t exceed the max size for the initrd.bin file (I don\'t know what it is) then yes, you should be able to flash the resultant image.
Si
-
I tried it, but it wouldn\'t work. But the initrd came out to big, I did just delete some files, but it came out a bit more than 16MB, that\'s too much, so I\'m not surprised flashing didn\'t work... I\'ll try it again tomorrow...
Cheer
Philipp