From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fwd: Creating a custom kernel from a -bin kernel
Date: Wed, 09 Oct 2024 23:08:46 +0100 [thread overview]
Message-ID: <2717394.BddDVKsqQX@rogueboard> (raw)
In-Reply-To: <bceac387-0b94-0723-d72e-dcc12781bf1a@wht.com.au>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
Hi Andrew,
On Sunday 6 October 2024 15:16:46 BST Andrew Lowe wrote:
> For some reason this didn't go through yesterday so, once again......
>
>
> -------- Forwarded Message --------
> Subject: Creating a custom kernel from a -bin kernel
> Date: Sat, 5 Oct 2024 18:55:50 +0800
> From: Andrew Lowe <agl@wht.com.au>
> Reply-To: agl@wht.com.au
> Organization: Wombat High Tech
> To: gentoo-user@lists.gentoo.org
>
> Dear all,
> I'm in the process of building a new machine. To get things up and
> running I've decided to go with the gentoo-sources-bin kernel initially,
> then once I get things basically working as I want I will go back to
> building my kernels manually.
>
> I've now reached that point, "hand rolling" the kernel, but it is a
> pain, the first time round, getting things right.
>
> I have a recollection of reading somewhere online mention of a
script
> that will take the .config file from the "-bin" kernel and then
> modprobe, I think, each listed module in turn to see if it is actually
> being used and subsequently writing a new .config file that now only
> contains the modules/options that the specific machine needs.
>
> Is this a mythical script that I have dreamt up after a long day and
> too much chocolate or does it actually exist and does anyone have a link.
>
> Thanks for any thoughts,
>
> Andrew
Have a look at this page:
https://wiki.gentoo.org/wiki/Kernel/Configuration
In particular, take notice of 'make localmodconfig'.
Once you have a customised kernel as you like it and it boots successfully,
you can copy your good /usr/src/linux/.config to any subsequently emerged new
gentoo-source kernel trees and run 'make oldconfig' thereafter, to only have
to deal with new kernel options.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-09 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <379cf455-3ff3-47ad-4d0e-7d4a38920e37@wht.com.au>
2024-10-06 14:16 ` [gentoo-user] Fwd: Creating a custom kernel from a -bin kernel Andrew Lowe
2024-10-09 22:08 ` Michael [this message]
2024-10-09 22:23 ` [gentoo-user] " Peter Böhm
2024-10-10 0:44 ` [gentoo-user] Fwd: " Eli Schwartz
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=2717394.BddDVKsqQX@rogueboard \
--to=confabulate@kintzios.com \
--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