what is going on with the 2.6.8.xx kernel?

[greenmeanie]

When ever I try goto 2.6.8.xx I keep getting a kernel panick error.

I compiled without initrd and my boot param's in meni.lst are correct?

the error is this.

VFS:cannot open root device "hda1" or unknown block(0,0)
please append a correct "root=" boot option
kernel panic - not syncing:VFS: unable to mount root fs on unknown-block(0,0)

but if i compile a 2.4.6 kernel everything is fine? just when I try to goto a 2.6.8 kernel all hell breaks loose. I have googled and seen tons of people with the same problem but no real answers for the headache.

[dawgie]

When ever I try goto 2.6.8.xx I keep getting a kernel panick error.

I compiled without initrd and my boot param's in meni.lst are correct?

the error is this.

VFS:cannot open root device "hda1" or unknown block(0,0)
please append a correct "root=" boot option
kernel panic - not syncing:VFS: unable to mount root fs on unknown-block(0,0)

If you are not using an initrd then you need to make sure that support for IDE, ATA and ATAPI Block devices is compiled in the kernel.
Also the filesystem support.



In the device drivers section:
ATA/ATAPI/MFM/RLL support

In the filesystem section:
Reiserfs support
Ext3 journalling file system support
JFS filesystem support
Second extended fs support
XFS filesystem support
/proc file system support
Virtual memory file system support

[greenmeanie]

So by default is it loading ide atapi ETC ETC as a module? and I need to switch them to a *? after knocking out initrd.

You might of solved my problem here.

[greenmeanie]

OK got it.
I did have to change the M to a *.
Do I actually have to go threw all the things I need and change them to *'s when shutting off initrd?

[epostma]

Ah, the beautiful art of kernel configuration!

The rough test to know if something needs to be built in or if it can be a module, is the following: if the kernel needs to know about it in order to mount your root filesystem, then it needs to be built in (or in your initrd). Otherwise it's usually OK to let it be a module. However, there are exceptions. If you already know that you're going to use something, then making something a module does not give any advantages, so it's usually best to err on the side of caution.

HTH,