From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Using Gentoo as server and desktop
Date: Sat, 14 Dec 2024 15:05:00 +0100 [thread overview]
Message-ID: <Z12QjDv5te68tbkA@tp> (raw)
In-Reply-To: <viv2up$sph$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Am Fri, Dec 06, 2024 at 02:50:01PM -0000 schrieb Grant Edwards:
> >> All I've ever done for a kernel upgrades is to go into the new kernel
> >> source dir and do the following:
> >>
> >> # zcat /proc/zconfig >.config
> >> # make oldconfig
> >> # make
> >> # make install
> >> [..]
>
> > Also, don't forget 'make modules_install' for any modules not built in the
> > kernel.
>
> Good catch. I forgot to mention that. It's always the step after "make
> install". Every once in a while I do forget to do that step. For my
> systems that usually means that X won't start until I do the "make
> modules_install".
You can actually combine the two with
make install modules_install
:)
It may even be possible to do something like
make bzImage modules install modules_install
(I use sources from kernel.org and those four actions are what I use
regularly, though in two separate make runs).
--
Grüße | Greetings | Salut | Qapla’
Stop overpopulation, become gay!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-14 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 21:38 [gentoo-user] Using Gentoo as server and desktop Egoitz Aurrekoetxea
2024-12-05 22:02 ` Matt Connell
2024-12-06 9:14 ` egoitz
2024-12-05 23:01 ` [gentoo-user] " Grant Edwards
2024-12-05 23:20 ` Michael
2024-12-06 9:18 ` egoitz
2024-12-06 14:50 ` Grant Edwards
2024-12-14 14:05 ` Frank Steinmetzger [this message]
2024-12-06 9:18 ` egoitz
2024-12-06 0:25 ` [gentoo-user] " syscon edm
2024-12-06 9:20 ` egoitz
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=Z12QjDv5te68tbkA@tp \
--to=warp_7@gmx.de \
--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