LinuxQuestions.org - Can't find a valid ram image

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Can't find a valid ram image (https://www.linuxquestions.org/questions/linux-newbie-8/cant-find-a-valid-ram-image-800874/)

Can't find a valid ram image

Hi
I've compiled the kernel 2.6.33, configured it and installed (make install)
When it boots up I get the following messages:
RAMDISK: I can't find a valid disk image at 0
VFS: Couldn't open root at /boot/vmlinuz-2.6.33mykerne1 or block (0,0)

Code:

My current system configuration is: 

Linux domenico-laptop 2.6.24-16-generic



/etc/boot/menu.lst

title                Ubuntu 8.04, kernel 2.6.24-16-generic

root                (hd0,2)

kernel                /boot/vmlinuz-2.6.24-16-generic root=UUID=e37512fd-eef1-4ae3-b9c

c-41eb2a645e56 ro quiet splash

initrd                /boot/initrd.img-2.6.24-16-generic

quiet



title                Ubuntu 8.04, kernel 2.6.24-16-generic (recovery mode)

root                (hd0,2)

kernel                /boot/vmlinuz-2.6.24-16-generic root=UUID=e37512fd-eef1-4ae3-b9c

c-41eb2a645e56 ro single

initrd                /boot/initrd.img-2.6.24-16-generic



title                Ubuntu 8.04, memtest86+

root                (hd0,2)

kernel                /boot/memtest86+.bin

quiet



#I've also assigned to root=/boot/vmlinuz-2.6.24-16-generic #root=UUID=e37512fd-eef1-4ae3-b9c but it didn't work

title                kernel1 2.6.33

root                (hd0,2) 

kernel                /boot/vmlinuz-2.6.33mykerne1 root=/boot/vmlinuz-2.6.33mykerne1

initrd                /boot/vmlinuz-2.6.33mykerne1

quiet

### END DEBIAN AUTOMAGIC KERNELS LIST



# This is a divider, added to separate the menu items below from the Debian

# ones.

title                Other operating systems:

root





# This entry automatically added by the Debian installer for a non-linux OS

# on /dev/sda1

title                Windows Xp

root                (hd0,0)

savedefault

makeactive

chainloader        +1





# This entry automatically added by the Debian installer for a non-linux OS

# on /dev/sda3

title                Vista Recovery

root                (hd0,3)

savedefault

makeactive

chainloader        +1



the df command prompts the following output: 

/dev/sda3            15619232  3955200  10876848  27% /

varrun                1037280      156  1037124  1% /var/run

varlock                1037280        0  1037280  0% /var/lock

udev                  1037280        64  1037216  1% /dev

devshm                1037280      152  1037128  1% /dev/shm

lrm                    1037280    38176    999104  4% /lib/modules/2.6.24-16-generic/volatile

/dev/sda7            10614880  6433796  3646124  64% /home

/dev/sda8            41471764  15327116  26144648  37% /media/disk

gvfs-fuse-daemon      15619232  3955200  10876848  27% /home/domenico/.gvfs







I've attached the file  /boot/config-2.6.33mykerne1

Thank you in advance

Quote:

Code:

kernel /boot/vmlinuz-2.6.33mykerne1 root=/boot/vmlinuz-2.6.33mykerne1

Ummm ... an initrd is NOT a root filesystem.

Assuming you've built everything properly, it should probably look like this.

Code:

title                kernel1 2.6.33

root                (hd0,2) 

kernel                /boot/vmlinuz-2.6.33mykerne1 root=UUID=e37512fd-eef1-4ae3-b9c

c-41eb2a645e56 ro single

initrd                /boot/initrd.img-2.6.33mykerne1

But "/boot/vmlinux-2.6.33mykerne1" doesn't look formed right to me. Please post the output of the following:

Code:

ls /boot

First of all, thank you both. I've started reading what initrd is right now... I want to learn how Linux works and avoid boring u with stupid questions. Anyway the output of ls /boot is

Code:

abi-2.6.24-16-generic            memtest86+.bin

config                            System.map

config-2.6.24-16-generic          System.map-2.6.24-16-generic

config-2.6.33mykerne1            System.map-2.6.33mykerne1

grub                              vmlinuz

initrd.img-2.6.24-16-generic      vmlinuz-2.6.24-16-generic

initrd.img-2.6.24-16-generic.bak  vmlinuz-2.6.33mykerne1

let me see, if I've understood how the initrd works.
At boot initird acts as a file-system that starts the actual file system.
In my /boot folder there is no initrd image for the kernel 2.6.33, for this reason I get the error message, doesn't it ?
Keep on guessing, I badly built my kernel, now how can I fix it?