i'm getting a similar thing with 2.6.2 it was telling me no UFS filesystem was found?!? and i just tried again with 2.6.3. and now it says UDF FS no partition found. which is wack because it's an ext3 filesystem. it works fine under 2.4.x but 2.6 can't seem to figure anything out.

i might go back to using 2.5.70, when that came out it worked fine with my filesystems.

this is with the following:

VIA KT266/A/333
Slackware current

I upgraded to 2.6.0 and 2.6.1 without any problem by using "make oldconfig" with my existing .config file from 2.4.24 (using Slackware 9.1). But then using "make oldconfig" with 2.6.2 resulted in the same inability to mount the filesystem that you describe. I then tried using a the default .config file with 2.6.2 but with the same result. I also find I cannot use make xconfig or make gconfig with 2.6.2, even though the necessary libraries are there.

I upgraded my computer at work to 2.6.2 using the old .config files without any problem. That computer is a Dell Pentium (2.2 gHz, I think) also using Slackware 9.1. The home computer (the problematic one) is a 850 MHz Duron in a Abit KT133A motherboard.

Can anyone shed any light on this? Any help would be greatly appreciated.

it seems like you dont add all needed modules in your kernel's config

I had this error after compiling a 2.6.5 kernel (going from 2.4.22)
I am using grub and the fix was luckily easy for me. I had to change my grub config from this:
----------------------
title Fedora Core (2.6.5)
root (hd1, 0)
kernel /2.6.5/bzImage ro root=LABEL=/ hdb=ide-scsi
---------------------------------------------------------
to this:
-----------------------
"""""""""""""""""""""""
root (hd1,0)
kernel /2.6.5/bzImage

------------------------------------------------------

Hope this helps someone like me, who didn't know what to do :)

Just came across this problem, and the fix.
Since I'm running on Ubuntu I added --initrd to my make-kpkg and that's all it took.
Basically I think it means that your set up needs an initrd - use mkinitrd.
Hope this helps,
Tim

Removal of this is what makes things work. You may also need to point it to the real root device ("root=/dev/hda4" for example).

This "thing" is, AFAIK, one of RedHat's worst ideas. Maybe it was thought of a way of simplifying fstab editing for newbies, but it sure messes up things. I really have no idea how they have done this, but, as long as using the old initrd doesn't fix the problem when updating kernel, I suppose the patched the kernel. Even if it worked without kernel patching, it would have meant that using an initrd was absolutely necessary. Maybe someone can provide more info on this.

The "ro" thing doesn't change the situation. It merely means that the kernel will mount the root as read-only, leaving read/write remounting to the distro's specific boot scripts. This is a good idea since a very very early fs-specific bug/crash/mumbo-jumbo won't damage the filesystem. The scripts can fsck the filesystem prior to remounting R/W.

if the grub is well and you have selected with * your file sistem suport (ext2, ext3, reiserfs..) probably you may to select whith * the:

ATA/ATAPI/MFM/RLL support --->
<*>generic/default IDE chipset support

its in my case that i have IDE and not SCSI or SATA

Hello! I reviewed most of the comments on trying to resolve the kernel panic issue. However, in my case it didn't work. I am wondering if I need to rebuild the MBR to move from Fedora Core 3 to Fedora Core 2.

I had this problem, but i used the software called SUPERGRUB, find it in google, i guess that this error is because certain software that we installed they make changes in the grub list, e.g, i used another type of boot in ubuntu grub, i set an image and colors in the grub list, and i think that it made that error.
Please, give a north in this case..... but SUPER GRUG could be a solution for u =)
cheers.... excuse my english.