From: Kaddeh <kaddeh@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31
Date: Wed, 10 Mar 2010 01:02:03 -0800 [thread overview]
Message-ID: <f921d62a1003100102g4bd54d2at8b899d8ded8c7f09@mail.gmail.com> (raw)
In-Reply-To: <20100310013650.GA6034@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 3416 bytes --]
Walter,
I'd advise going back through and running a "make menuconfig" on
2.6.31-r6/10 and verify that everything is in order.
The reason that I say this is that, in the event that your kernel -DID-
revert back to defaults, if you have a non-ext2/3 partition, it isn't going
t recognize it (EXT4, Reiserfs3.6/4, etc aren't "default" options).
As for the warnings that you are talking about, those have existed for a
while, they are obviously non-fatal and not really pertinent to your issue
at hand.
Cheers
Kad
On Tue, Mar 9, 2010 at 5:36 PM, 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. And there was a kernel panic because gentoo couldn't
> find the boot device.
>
> 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...
>
>
> [d531][root][/usr/src/linux] make oldconfig
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/basic/docproc
> HOSTCC scripts/basic/hash
> HOSTCC scripts/kconfig/conf.o
> scripts/kconfig/conf.c: In function 'conf_askvalue':
> scripts/kconfig/conf.c:105: warning: ignoring return value of 'fgets',
> declared with attribute warn_unused_result
> scripts/kconfig/conf.c: In function 'conf_choice':
> scripts/kconfig/conf.c:307: warning: ignoring return value of 'fgets',
> declared with attribute warn_unused_result
> HOSTCC scripts/kconfig/kxgettext.o
> SHIPPED scripts/kconfig/zconf.tab.c
> SHIPPED scripts/kconfig/lex.zconf.c
> SHIPPED scripts/kconfig/zconf.hash.c
> HOSTCC scripts/kconfig/zconf.tab.o
> In file included from scripts/kconfig/zconf.tab.c:2486:
> scripts/kconfig/confdata.c: In function 'conf_write':
> scripts/kconfig/confdata.c:508: warning: ignoring return value of 'fwrite',
> declared with attribute warn_unused_result
> scripts/kconfig/confdata.c: In function 'conf_write_autoconf':
> scripts/kconfig/confdata.c:745: warning: ignoring return value of 'fwrite',
> declared with attribute warn_unused_result
> scripts/kconfig/confdata.c:746: warning: ignoring return value of 'fwrite',
> declared with attribute warn_unused_result
> In file included from scripts/kconfig/zconf.tab.c:2487:
> scripts/kconfig/expr.c: In function 'expr_print_file_helper':
> scripts/kconfig/expr.c:1090: warning: ignoring return value of 'fwrite',
> declared with attribute warn_unused_result
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf -o arch/x86/Kconfig
> *
> * Restart config...
> *
> *
> * Performance Counters
> *
> Kernel Performance Counters (PERF_COUNTERS) [N/y/?] (NEW)
>
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
>
>
[-- Attachment #2: Type: text/html, Size: 4199 bytes --]
next prev parent reply other threads:[~2010-03-10 9:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 1:36 [gentoo-user] Problem with "make oldconfig" 2.6.30-8 ==> 2.6.31 Walter Dnes
2010-03-10 9:02 ` Kaddeh [this message]
2010-03-10 13:22 ` Tanstaafl
2010-03-10 13:38 ` Dale
2010-03-10 13:46 ` Tanstaafl
2010-03-10 14:07 ` Alan McKinnon
2010-03-10 14:19 ` Tanstaafl
2010-03-11 10:16 ` Alan McKinnon
2010-03-10 13:47 ` Neil Bothwick
2010-03-10 13:56 ` Tanstaafl
2010-03-10 14:09 ` Neil Bothwick
2010-03-10 14:27 ` Tanstaafl
2010-03-10 14:35 ` Neil Bothwick
2010-03-10 15:46 ` Tanstaafl
2010-03-10 15:53 ` Paul Hartman
2010-03-10 14:09 ` Mick
2010-03-10 14:37 ` Neil Bothwick
2010-03-10 14:03 ` Alan McKinnon
2010-03-10 13:55 ` Mick
2010-03-11 13:03 ` Walter Dnes
2010-03-11 13:20 ` Neil Bothwick
2010-03-11 13:23 ` Jonathan
2010-03-11 23:38 ` [gentoo-user] Re: [solved] " Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f921d62a1003100102g4bd54d2at8b899d8ded8c7f09@mail.gmail.com \
--to=kaddeh@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox