From: Tanstaafl <tanstaafl@libertytrek.org>
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 08:22:41 -0500 [thread overview]
Message-ID: <4B979D21.4040206@libertytrek.org> (raw)
In-Reply-To: <20100310013650.GA6034@waltdnes.org>
On 2010-03-09 8:36 PM, Walter Dnes 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 *never* use make oldconfig between major kernel versions...
I do as the kernel upgrade guide says - when going between major
versions (yes, even one), copy the old .config to the new kernel dir,
then run make menuconfig, and make sure all of your critical options are
set. This is much safer, though it does take more time.
I've been wondering though - how well does genkernel work now? I've
never used it...
--
Charles
next prev parent reply other threads:[~2010-03-10 13:23 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
2010-03-10 13:22 ` Tanstaafl [this message]
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=4B979D21.4040206@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--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