From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LZk5l-0005cg-8i for garchives@archives.gentoo.org; Wed, 18 Feb 2009 10:55:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE1BFE045F; Wed, 18 Feb 2009 10:55:46 +0000 (UTC) Received: from mail-bw0-f205.google.com (mail-bw0-f205.google.com [209.85.218.205]) by pigeon.gentoo.org (Postfix) with ESMTP id 770E3E045F for ; Wed, 18 Feb 2009 10:55:46 +0000 (UTC) Received: by bwz1 with SMTP id 1so5378663bwz.10 for ; Wed, 18 Feb 2009 02:55:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Zq551sqXlIfDTC5KJEGU8sY3Vze8muQ62NXX87Vx2jU=; b=c73ptNjDLhSz9JMx4Vf5+Aps7zzWxpEHyk4NTH1H++V5RPMVLiEeMTn70xeg8O3fI/ hiW+rmDzujK9aREACfV73WwxuSAAMPlNsEkgWGrNzaVSsNIKfrUxxeFKZnuH+JkMa2mX jltHy7lsGP3fsbn9QaTu0YW177NUjdK5cBXps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Y9zY8cwDdXgY3O80NnIJQKrWxeKO+i5LBuQCFJKUCGluA6Nl/jfwtb5LTdibhFJ8Ws 3NzEj54ZxXiz3SvckmGfTEUu28CBTt+hzSCPOo9CWPcLbXJosn8iZH3cQVr1kKmtEtAI uYVhKJNLXoD9ZHl6BiKbPEVJ0fpMwlY67AHKQ= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.103.115.12 with SMTP id s12mr452457mum.89.1234954545661; Wed, 18 Feb 2009 02:55:45 -0800 (PST) In-Reply-To: <499BBFDD.6020405@gmail.com> References: <865773ce0902151331y6c694eecm8625993dd9bd32a5@mail.gmail.com> <3ac129340902170337u215c0570n882217195623dfdc@mail.gmail.com> <499BBFDD.6020405@gmail.com> Date: Wed, 18 Feb 2009 19:55:45 +0900 Message-ID: <3ac129340902180255h31d33b17x397ad792d7458634@mail.gmail.com> Subject: Re: [gentoo-user] NIC not detected after Kernel upgrade From: daid kahl To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0016364c76b102052204632f4393 X-Archives-Salt: c93cf506-654b-4a7e-9851-b4b699606366 X-Archives-Hash: 5efb289f922cac54276af4b0fdf58aa2 --0016364c76b102052204632f4393 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit > > Also, you should avoid using oldconfig except for really minor kernel > > upgrades. I know this is mentioned in documentation elsewhere, but > > just a useful reminder. > > > > ~daid > > This has been discussed on this list before. Running make oldconfig > works fine. I, and a lot of others, have said this many times. I > configed one kernel about 5 years ago and have used oldconfig ever > since. It is faster and less prone to problems than starting from scratch. > > If you are going from 2.4 to 2.6, then you should start fresh. I > recently went from 2.6.23 to a 2.6.28 with no problem, other than trying > to figure out that new group stuff. > > Dale > > Huh. I was going from 2.6.23 to 2.6.26 about 2 weeks ago and using oldconfig was giving me some major trouble as I recall. Not sure specifically now, but I know CONFIG_HPET_TIMER had to be turned off later during manual configuration, or my machine was hanging after some ACPI scripts. This behavior is replicated elsewhere for similar hardware, though the author claimed it was fixed after 2.6.25 which I found to clearly not be the case. I had also not manually configured my own kernel either, so I thought it's worth the experience. I could save my current configuration for 2.6.26 and try oldconfig again from 2.6.23.9 to make another 2.6.26 kernel and see what the problem was. ~daid --0016364c76b102052204632f4393 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
> Also, you should avoid using oldco= nfig except for really minor kernel
> upgrades.  I know this is mentioned in documentation elsewhere, b= ut
> just a useful reminder.
>
> ~daid

This has been discussed on this list before.  Running make oldco= nfig
works fine.  I, and a lot of others, have said this many times.  = I
configed one kernel about 5 years ago and have used oldconfig ever
since.  It is faster and less prone to problems than starting from scr= atch.

If you are going from 2.4 to 2.6, then you should start fresh.  I
recently went from 2.6.23 to a 2.6.28 with no problem, other than trying to figure out that new group stuff.

Dale


Huh.  I was going from 2.6.23 to 2.6.26 = about 2 weeks ago and using oldconfig was giving me some major trouble as I= recall.  Not sure specifically now, but I know CONFIG_HPET_TIMER had = to be turned off later during manual configuration, or my machine was hangi= ng after some ACPI scripts.  This behavior is replicated elsewhere for= similar hardware, though the author claimed it was fixed after 2.6.25 whic= h I found to clearly not be the case.  I had also not manually configu= red my own kernel either, so I thought it's worth the experience.

I could save my current configuration for 2.6.26 and try oldconfig agai= n from 2.6.23.9 to make another 2.6.26 kernel and see what the problem was.=

~daid
--0016364c76b102052204632f4393--