Re: [gentoo-user] kernel panic on manually built kernel

[dhk <dhkuhl@optonline.net>]

On 11/04/2010 12:52 PM, Alan McKinnon wrote:
> Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did 
> opine thusly:
> 
>> I've always used the genkernel, but now am trying to make a manual one.
>>  I think the kernel is alright since all the default setting seemed
>> reasonable and the build was easy enough.  However, when I boot to it I
>> get a kernel panic and it complains about the root device /dev/hda3. So
>> I think the problem has to do with my parameters or syntax in grub.conf.
>>  Below are three grub menu options.  The first two have the problem and
>> the third is the genkernel that works fine.  Is there something wrong
>> with the way the first two are?  Thanks.
> 
> Why did you think it a good idea to NOT post the *actual* error? 
> 
> Your grub entries are correct.
> 
> I'll bet money that you built one or more of your chipset drivers, libata, or 
> root filesystem driver as a module.
> 
> These must not be modules, they must be built-in (otherwise you need an 
> initrd)
> 
> 
> 
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
>>
>> # This is a Manually built kernel with default settings.  kernel panic
>> title Gentoo Linux x86 2.6.34-r12
>> root (hd0,0)
>> kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
>> splash=verbose video=vesafb:mtrr,ywrap udev
>> # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768-32@85
>>
>> # This a genkernel and works
>> title Gentoo Linux x86 2.6.34-r6
>> root (hd0,0)
>> kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
>> ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
>> video=vesafb:mtrr,ywrap udev
>> initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
>>
>> --dhk
> 

Thanks all, I check those suggestions and get back to you.

The reason I didn't include the exact error is that I can't capture it.
 I'd have to write it on paper and then reboot to the working kernel.
By then it doesn't seem to be in any of the logs.  I'll see what I can
do about that.

Thanks again.

--dhk