Re: initrd and grub

[Susumu Takuwa]

>>>>> On Thu, 21 Jun 2001 12:37:13 +0900
        OKUJI Yoshinori writes:

OY> Then, mention what the result was more precisely. You haven't written
OY> what commands you executed, what was displayed by GRUB, the
OY> configuration of your system, etc.

excuse me:-) 

First, I installed Vine Linux 2.1, default kernel is 2.2.17
as /boot/vmlinuz-2.2.17-0vl10, to /dev/hda8. Second, I made
some initd images like this, 

# mkinitrd initrd.img 2.2.17-0vl10
# dd if=/dev/zero of=ramdiskX bs=1024k count=X
# losetup /dev/loop0 initrd.img
# losetup /dev/loop1 ramdiskX
# mke2fs /dev/loop1
# mount /dev/loop0 /loop0
# mount /dev/loop1 /loop1
# cp -a /loop0/* /loop1/
        [...]
# umount /loop(0|1)
# losetup -d /dev/loop(0|1)     
# gzip -c9 ramdiskX > /boot/ramdiskX.img

Well, I booted that kernel and initrd images with GRUB of
some different versions. The menu.lst is following, 

kernel (hd0,7)/boot/vmlinuz-2.2.17-0vl10 ramdisk_size=Y
initrd (hd0,7)/boot/ramdiskX.img

I tried the size of initrd images, that is X = 4, 48, 64, 96,
128, 192, 196. And I set ramdisk_size parameter Y as over
initrd image size. 

The results on each X: -------------------------------------
4       no problem
48      no problem
64      RAMDISK: could not determine device size
96      RAMDISK: Loading 98304 blocks [3 disk] into ram disk...
        done disk #1
        Please insert disk #2 and press ENTER
128     RAMDISK: could not determine device size
192     RAMDISK: could not determine device size
196     RAMDISK: Loading 200704 blocks [49 disk] into ram disk...
        done disk #1
        Please insert disk #2 and press ENTER   
------------------------------------------------------------

According ``linux/drivers/block/rd.c'', ramdisk driver failed
to determine the size of initrd images. Do you need any more?


        Susumu Takuwa