public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Evgeniy Bushkov <zhen@dotcomltd.ru>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] NIC not detected after Kernel upgrade
Date: Wed, 18 Feb 2009 17:26:36 +0300	[thread overview]
Message-ID: <499C1A9C.9090300@dotcomltd.ru> (raw)
In-Reply-To: <3ac129340902180255h31d33b17x397ad792d7458634@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]

daid kahl пишет:
>
>     > 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
Hm, may be it's off-topic but I've seen such behavior on one of my 
servers - some ACPI events were hanging server with last kernels. The 
only thing I had to be done is to turn off ACPI in BIOS. Now service 
local isn't working and CPU frequency is not scaling also. Is this 
normal or can this parameter (CONFIG_HPET_TIMER) help me?

Best regards,
Evgeniy B.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 5581 bytes --]

      reply	other threads:[~2009-02-18 14:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 21:31 [gentoo-user] NIC not detected after Kernel upgrade Guillermo Garron
2009-02-15 21:40 ` Dirk Heinrichs
2009-02-15 21:52   ` Guillermo Garron
2009-02-16 17:36     ` Dirk Heinrichs
2009-02-18  0:38       ` Guillermo Garron
2009-02-15 21:50 ` Kenneth Prugh
2009-02-15 21:54   ` Guillermo Garron
2009-02-15 21:57     ` Guillermo Garron
2009-02-15 22:09     ` [gentoo-user] " Nikos Chantziaras
2009-02-15 22:25       ` Guillermo Garron
2009-02-16  1:17 ` [gentoo-user] " Stroller
2009-02-16  2:07   ` Guillermo Garron
2009-02-16 17:40   ` Dirk Heinrichs
2009-02-18  0:40     ` Guillermo Garron
2009-02-18  1:06       ` Guillermo Garron
2009-02-18 10:59   ` daid kahl
2009-02-18 12:05     ` Neil Bothwick
2009-02-17 11:37 ` daid kahl
2009-02-18  0:36   ` Guillermo Garron
2009-02-18  7:59   ` Dale
2009-02-18 10:55     ` daid kahl
2009-02-18 14:26       ` Evgeniy Bushkov [this message]

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=499C1A9C.9090300@dotcomltd.ru \
    --to=zhen@dotcomltd.ru \
    --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