Kernel builds from linux-2.6.3-2.1.253.2.1

[Richard Ayer III]

Thomas Molina wrote:

>>Let me ask you a question or two. I was also trying to do a custom
>>2.6.3-2.1.253.2.1 kernel, and I was able to get it all to compile with the
>>changes I made (which were a lot). But when I try to boot it I get an error
>>like this:
>>    VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
>>    Please append a correct "root=" boot option
>>    Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
>>But the boot options are exactly the same as for every other kernel version;
>>so I must have turned off something critical, I'm just not sure what. My
>>root partition is on hda4, and it is ext3. Also, ever since I tried booting
>>my custom kernel that first time, rhgb doesn't start for any kernel I boot,
>>even though it is in all of the boot parameters. any thoughts?
>>    
>>
>
>That message is seen when a kernel is built with in initrd is made which 
>does not include the jbd module.  Did you include jbd support as modular 
>or builtin?  One way to handle this is make ext2, ext3, and jbd as 
>builtin.  I personally disagree with RedHat on this issue so I go the 
>other route.  I change all of my fstab entries to use device names 
>(/dev/hda1) rather than symbolic names like LABEL=/.  
>
>  
>
As it turns out, I had all of those built in and still saw the error. I 
may change my fstab entries, but I'd like to figure out what actually 
caused the problem. So I'm going to start over with the config file from 
the stock 2.6.3-2.1.253.2.1 kernel and try to slowly turn things off 
until I figure out just where it went wrong. If anyone else has any 
thoughts that might speed this process up for me, I'd be greatly 
appreciative to hear them.

Thanks,
Richard Ayer III