Re: [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31

[Mick <michaelkintzios@gmail.com>]

On 10 March 2010 01:36, Walter Dnes <waltdnes@waltdnes.org> wrote:
>  Today is when running a lilo menu with "production" and "experimental"
> kernels saved me.  "production" is 2.6.30-r8.  "experimental" is
> 2.6.31-r6 or 2.6.31-r10 (same problems with either one).  I set
> /usr/src/linux to point at 2.6.31-r6 (or 10), copied .config from
> 2.6.30-r8 and ran "make oldconfig".  I got the warnings listed below
> before the config process started.  "make oldconfig" appears to have
> reset to default values, and it was showing me some settings totally the
> opposite of what I know I've set.  When I ran through "make oldconfig",
> compiled and rebooted, I got a framebuffer console, which I *KNOW* I
> haven't selected.

If you had not enabled framebuffer in your old kernel then I can't
think how it would show up as enabled in your new kernel (as far as I
know fb is not enabled by default on any kernels that I've ever built)

> And there was a kernel panic because gentoo couldn't
> find the boot device.

Hmm ... so it's not just framebuffer but different filesystems perhaps?

>  I'm enough of a bit-twiddler that I can set up the kernel manually.
> But I know from past experience that it's a long slow process.  Is
> there any trick to salvage "make oldconfig", before I resort to setting
> up the kernel "the hard way"?  Here's the output from "make oldconfig"
> up to where it starts asking questions...

The errors you show are not show stoppers (or the new kernel would not
build).  You may want to update your gcc and then check using
gcc-config that the latest is being used.

With regards to your kernel panic I suspect an error in the .config
file you copied over.  Do you keep a copy both in
/usr/src/linux-gentoo-XXX/ and in /boot?  If yes then copy over your
.config from a different location this time, otherwise you'll have to
go about it through the manual method.

PS.  Just checking the obvious:  you aren't manually patching your
kernels and forgot to do it this time, right?
-- 
Regards,
Mick