linux kernel 2.6.3 - Kernel panic: VFS: Unable to mount ro..

I am not sure if I am experiencing a silo problem, or a problem with a
kernel configuration. I have a couple of sparc machines that I am
attempting to build 2.6.3 kernels for. I have gotten one to build
now, but I am unable to get it to finish booting. At the bootprompt,
I have typed in the name of my image (from silo.conf) with the "-p"
argument so I can see the output. The boot process recognizes my
kernel image and starts in on the boot process, then ends at:
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)

I would normally figure I had misconfigured the kernel - not including
ext2 or ext3 filesystems or IDE drivers in the kernel. But I did
include them. Silo doesn't seem to have a verbose mode, and I am not
left with the feeling that silo actually did anything - althought upon
boot, it does find images by name.

Here is the contents of silo.conf, the output /proc/cpuinfo, uname -a,
and distribution details. Any help is appreciated.

cpu : TI UltraSparc IIi
fpu : UltraSparc IIi integrated FPU
promlib : Version 3 Revision 14
prom : 3.14.0
type : sun4u
ncpus probed : 1
ncpus active : 1
Cpu0Bogo : 599.65
Cpu0ClkTck : 0000000011e19072
MMU Type : Spitfire

cat /etc/debian_version
testing/unstable

Linux mysparc 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64 GNU/Linux


`cat /etc/debian_version `
testing/unstable

lhack.DeleteThis@wgeddes.com (lhack) wrote in message news:<9c859923.0402211246.177fca6.DeleteThis@posting.google.com>...
> I am not sure if I am experiencing a silo problem, or a problem with a
> kernel configuration. I have a couple of sparc machines that I am
> attempting to build 2.6.3 kernels for. I have gotten one to build
> now, but I am unable to get it to finish booting. At the bootprompt,
> I have typed in the name of my image (from silo.conf) with the "-p"
> argument so I can see the output. The boot process recognizes my
> kernel image and starts in on the boot process, then ends at:
> Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
>
> I would normally figure I had misconfigured the kernel - not including
> ext2 or ext3 filesystems or IDE drivers in the kernel. But I did
> include them. Silo doesn't seem to have a verbose mode, and I am not
> left with the feeling that silo actually did anything - althought upon
> boot, it does find images by name.
>
> Here is the contents of silo.conf, the output /proc/cpuinfo, uname -a,
> and distribution details. Any help is appreciated.
>
> cpu : TI UltraSparc IIi
> fpu : UltraSparc IIi integrated FPU
> promlib : Version 3 Revision 14
> prom : 3.14.0
> type : sun4u
> ncpus probed : 1
> ncpus active : 1
> Cpu0Bogo : 599.65
> Cpu0ClkTck : 0000000011e19072
> MMU Type : Spitfire
>
> cat /etc/debian_version
> testing/unstable
>
> Linux mysparc 2.4.18 #2 Thu Apr 11 14:37:17 EDT 2002 sparc64 GNU/Linux
>
>
> `cat /etc/debian_version `
> testing/unstable


It is interesting to note that when it boots, it is finding the right
device for the root device - /dev/hda1 in this case (the machine is
all IDE). However, the error notice says to append a correct 'root='
argument. I have, and the results are the same.

My silo.conf file looks like this:
-----------------------------
partition=1
root=/dev/hda1
timeout=100
read-only
default=linux

image=/vmlinuz.old
label=linux
read-only

image=/vmlinux-2.6.2
label=2.6.2
read-only

image=/vmlinux-2.6.3
label=Monday
read-only
---------------------------

silo picks up any changes automatically, and the image in the above
file named "linux" boots. /dev/hda1 gets mounted during that boot
sequence. I just do not understand why I cannot get the root disk to
mount with the new kernels.