Here is some more explanation about my problem and what I do:
* I create the image of my ramdisk on my PC like that:
dd if=/dev/zero of=myramdisk bs=1k count=8000
myramdisk is a normal file (not a special device) (NB: using a special device
like /dev/ram, I can't create a image bigger than 4MB). Then I create a
filesystem on it (mke2fs -vm0 myramdisk 8000), mount it (mount -o loop -t ext2
myramdisk /mnt) and put all the files I need.
* Then I create a file of 16MB made from the kernel and the image of the
ramdisk, with a gap of 8MB between the two files.
* I load this file in the RAM of my brutus-like board at 0xc0000000. So the the
kernel is at 0xc0000000 and the ramdisk at 0xc0800000.
That's all
So, in the setup_initrd function should be: setup_initrd ( 0xc0800000 ,
0x7d0000 )
where 7d0000 is the size of the image of my ramdisk ( 8000 * 1024 ).
Let me give you an example:
This the current state of the image of my ramdisk (using 'df')
1024 blocks: 7745
Used: 6023
Available: 1722
* If I used setup_initrd ( 0xc0800000 , 0x00500000 ) : At the end of the boot,
the kernel asks me for the enter initlevel and then chrashes : So that means
that the ramdisk and particularly the "/etc/inittab" file are damaged.
* For setup_initrd ( 0xc0800000 , 0x0060000): all works perfectly well (login:).
(except one file that I found damaged)
* For setup_initrd ( 0xc0800000 , 0x0070000): the kernel found the ramdisk, but
crashes when loading it.
I could let the 0x00600000, but I want to add some more files in the image
of my ramdisk. When I do it, it doesn't work any more, even when I edit one of
the existing files of the ramdisk image. I'm stuck !!!
Arnaud
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
