public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Kernel upgrading and linux symlink
Date: Sat, 31 Oct 2009 20:50:38 +0000	[thread overview]
Message-ID: <20091031205038.3814ad13@majikthise> (raw)
In-Reply-To: <hchtvu$1et$1@ger.gmane.org>

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

On Sat, 31 Oct 2009 20:00:35 +0200, Nikos Chantziaras wrote:

> So, to sum it up, when you update to a new kernel, first update the 
> symlink (or let the ebuild take care of it), build the kernel, boot it, 
> *then* rebuild external modules (like ati-drivers).  If you know what 
> you're doing, you don't need to reboot before rebuilding external 
> modules, for example I do:
> 
> ebuild /usr/portage/x11-drivers/ati-drivers/ati-drivers-N.ebuild compile
> mkdir /lib/modules/KERNEL_VERSION/video
> cp 
> /var/tmp/portage/x11-drivers/ati-drivers-N/work/common/lib/modules/fglrx/build_mod/2.6.x/fglrx.ko 
> /lib/modules/KERNEL_VERSION/video/

I don't use ati, but with other modules, this is not necessary. As long
as /usr/srx/linux contains a valid .config, you can build modules against
that kernel without running or even compiling it.


-- 
Neil Bothwick

Thesaurus: ancient reptile with an excellent vocabulary

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-10-31 20:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31 16:52 [gentoo-user] Kernel upgrading and linux symlink Harry Putnam
2009-10-31 18:00 ` [gentoo-user] " Nikos Chantziaras
2009-10-31 18:09   ` Harry Putnam
2009-10-31 18:41     ` Nikos Chantziaras
2009-10-31 19:18     ` Alan McKinnon
2009-10-31 20:03       ` Nikos Chantziaras
2009-10-31 21:07         ` Alan McKinnon
2009-10-31 21:27           ` Nikos Chantziaras
2009-10-31 21:43             ` Mark Knecht
2009-10-31 22:17               ` Alan McKinnon
2009-10-31 20:06       ` Harry Putnam
2009-10-31 21:03         ` Alan McKinnon
2009-11-01  7:00           ` Dirk Heinrichs
2009-10-31 20:50   ` Neil Bothwick [this message]
2009-10-31 18:24 ` [gentoo-user] " Denis
2009-10-31 21:26   ` Dale
2009-10-31 22:20     ` Alan McKinnon
2009-10-31 22:52       ` Dale
2009-10-31 22:58         ` Alan McKinnon
2009-10-31 23:25       ` Neil Bothwick
2009-10-31 23:29       ` Mark Knecht
2009-10-31 23:40         ` [gentoo-user] " walt
2009-10-31 23:43           ` Mark Knecht
2009-10-31 23:41         ` [gentoo-user] " Alan McKinnon
2009-10-31 23:50           ` Mark Knecht
2009-10-31 23:43         ` Mike Edenfield
2009-11-01  6:55 ` Dirk Heinrichs

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=20091031205038.3814ad13@majikthise \
    --to=neil@digimed.co.uk \
    --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