I'm making my first attempts at getting a 2.6 kernel running on my
Debian (Sarge) box. Upon boot I get "Kernel Panic: Unable to mount
VFS "305" or /dev/hda5 root partition" or something similar.
/dev/hda5 is ext3 and ext3 has been selected to be built into the
kernel (via menuconfig).

The disk itself is fine: I reboot into my old 2.4.20 kernel w/o
problem.

gcc 3.3.2
tune2fs 1.35
module-init-tools 3.0-pre2

Any suggestions?

-j

JVarsoke uttered the immortal words:

> I'm making my first attempts at getting a 2.6 kernel running on my
> Debian (Sarge) box. Upon boot I get "Kernel Panic: Unable to mount
> VFS "305" or /dev/hda5 root partition" or something similar.
> /dev/hda5 is ext3 and ext3 has been selected to be built into the
> kernel (via menuconfig).

Adding append="ramdisk_size=8192" to lilo.conf did it for me.

I can't see the point of upgrading to 2.6 yet though. The system I tested
2.6.0 on ran a lot slower and the sound card, which works beautifully with
the 2.4 kernel, wouldn't work.

I'll wait until 2.6 gets to 2.6.4 or later before I try it in anger.

--
Andy.

Andy Fraser <andyfraser31@hotmail.com> wrote in message news:<uop8d1-481.ln1@news.linuxuser.org.uk>...
> JVarsoke uttered the immortal words:
>
> > I'm making my first attempts at getting a 2.6 kernel running on my
> > Debian (Sarge) box. Upon boot I get "Kernel Panic: Unable to mount
> > VFS "305" or /dev/hda5 root partition" or something similar.
> > /dev/hda5 is ext3 and ext3 has been selected to be built into the
> > kernel (via menuconfig).
>
> Adding append="ramdisk_size=8192" to lilo.conf did it for me.

Nope, same error.

I've also tried:
eliminating "lba32" from lilo.

mkinitrd -o /boot/initrd-2.6.1.img 2.6.1 w/
initrd=/boot/initrd-2.6.1.img in LILO
CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y

Don't know what else to try. Suggestions?

-j

Andy Fraser <andyfraser31@hotmail.com> schrieb:

>I can't see the point of upgrading to 2.6 yet though. The system I tested
>2.6.0 on ran a lot slower and the sound card, which works beautifully with
>the 2.4 kernel, wouldn't work.

I can tell other story. Since 2.6.0-test3 I tried all prereleases and
run 2.6.1 now. It is more responsive, particular on network
connections, and sound works great with the integrated alsa driver.
There seems to be some problems with USB memory devices, though.
Eggert

On Monday 12 Jan 2004 10:08 am, Eggert Ehmke uttered these immortal words:

>>I can't see the point of upgrading to 2.6 yet though. The system I tested
>>2.6.0 on ran a lot slower and the sound card, which works beautifully with
>>the 2.4 kernel, wouldn't work.
>
> I can tell other story. Since 2.6.0-test3 I tried all prereleases and
> run 2.6.1 now. It is more responsive, particular on network
> connections, and sound works great with the integrated alsa driver.
> There seems to be some problems with USB memory devices, though.

I've pretty much left the 2.6 kernel alone until now, too much other stuff
to do :-)

I can remember the move from 2.2 to 2.4 was painless. I think, for now at
least, the move to 2.6 isn't going to be so easy.

--
Andy.

usenet.9.jvarsoke@spamgourmet.com (JVarsoke) wrote in message news:<bfa58f21.0401112133.5553e0a4@posting.google. com>...
> Andy Fraser <andyfraser31@hotmail.com> wrote in message news:<uop8d1-481.ln1@news.linuxuser.org.uk>...
> > JVarsoke uttered the immortal words:
> >
> > > I'm making my first attempts at getting a 2.6 kernel running on my
> > > Debian (Sarge) box. Upon boot I get "Kernel Panic: Unable to mount
> > > VFS "305" or /dev/hda5 root partition" or something similar.
> > > /dev/hda5 is ext3 and ext3 has been selected to be built into the
> > > kernel (via menuconfig).
> >
> > Adding append="ramdisk_size=8192" to lilo.conf did it for me.
>
> Nope, same error.
>
> I've also tried:
> eliminating "lba32" from lilo.
>
> mkinitrd -o /boot/initrd-2.6.1.img 2.6.1 w/
> initrd=/boot/initrd-2.6.1.img in LILO
> CONFIG_EXT2_FS=y
> CONFIG_EXT3_FS=y
> CONFIG_EXT3_FS_XATTR=y
>
> Don't know what else to try. Suggestions?
>
> -j

Have you installed the DEVFSD package? I was getting tons of errors
like yours until I installed this package.

usenet.9.jvarsoke@spamgourmet.com (JVarsoke) wrote in message news:<bfa58f21.0401111230.63df5852@posting.google. com>...
> I'm making my first attempts at getting a 2.6 kernel running on my
> Debian (Sarge) box. Upon boot I get "Kernel Panic: Unable to mount
> VFS "305" or /dev/hda5 root partition" or something similar.
> /dev/hda5 is ext3 and ext3 has been selected to be built into the
> kernel (via menuconfig).
>
> The disk itself is fine: I reboot into my old 2.4.20 kernel w/o
> problem.
>
> gcc 3.3.2
> tune2fs 1.35
> module-init-tools 3.0-pre2
>
> Any suggestions?
>
> -j

I am successfully running kernel 2.6.1 on redhat 9. I faced the same
problem

"Kernel Panic: Unable to mount VFS "305" or /dev/hda5 root partition"

My root partition was ext3 and default option for kernel compilation
makes ext3 filesystem to load as module. I compiled ext3 filesystm
into my kernel and the root partition was mounted without an error
after that.