RE: Kernel for linuxbios

[Sagiv Yefet]

I did what you said.
New error:

RAMDISK: Couldn't find valid RAM disk image starting at 0.
Freeing initrd memory: 2624k freed
VFS: Cannot open root device "" or 03:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:00

Sagiv.

-----Original Message-----
From: Stefan Reinauer [mailto:[e-mail]] 
Sent: Wednesday, October 13, 2004 4:28 PM
To: Sagiv Yefet
Cc: Dave Aubin; [e-mail]
Subject: Re: Kernel for linuxbios

* Sagiv Yefet  [041013 16:11]:
> Actually, I am using 2.4.24. 
> Maybe I should upgrade to 2.6.*. 
> but in the meanwhile what could be the problem?
>
> The command is:
>
> ./objdir/sbin/mkelfImage -t bzImage-i386 --kernel=/home/sagivy/bzImage
> --command-line="rw console=ttyS0,115200 root=/dev/ram0"  
>    --initrd=/home/sagivy/initrd --output=/home/sagivy/bzImage.elf

leave root=/dev/ram0 away in the parameters and say initrd=initrd
instead. IIRC there was some check in Linux that it only looks for an
initrd if there is a parameter saying that there is one.

Stefan

Kernel for linuxbios

"Sagiv Yefet"  writes:
> I did what you said.
> New error:
>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> Freeing initrd memory: 2624k freed
> VFS: Cannot open root device "" or 03:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:00

I hate looking at things with the messages cropped, it can hide useful
information.

In any case the kernel line:
> Freeing initrd memory: 2624k freed.

Indicates that the initrd is being found, and there is data there.

The line:
> RAMDISK: Couldn't find valid RAM disk image starting at 0.

Indicates that your initrd is either corrupted or it is in a format
your kernel does not recognize.

Do you have the proper filesystem in your kernel.  Is your initrd
compressed?  In some cases filesystems are only recognized inside a
compressed initrd.

Eric

Kernel for linuxbios

[Ronald G. Minnich]

On Sun, 17 Oct 2004, Sagiv Yefet wrote:
> I did what you said.
> New error:
>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
> Freeing initrd memory: 2624k freed
> VFS: Cannot open root device "" or 03:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:00

3:00 is hda, which is not what you what, I guess.

ron