From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Do I need firmware for an integrated graphics unit?
Date: Wed, 21 Aug 2024 16:47:30 +0100 [thread overview]
Message-ID: <12495124.O9o76ZdvQC@cube> (raw)
In-Reply-To: <b10780bd-ff55-483a-9e9c-fc739da2740f@youngman.org.uk>
On Wednesday, 21 August 2024 16:22:18 BST Wol wrote:
> On 21/08/2024 14:49, Michael wrote:
> >> That would involve me learning how to make and handle a modular kernel,
> >> something I'd really rather not have to do.
> >
> > Well, there's nothing to it really. Just configure your kernel with the
> > drivers needed by your graphics card, but set them as modules. Then boot
> > with it and check dmesg. The kernel will load the modules and try to
> > fetch the requisite firmware.
>
> Just don't forget to "make modules" and "make modules_install". Then you
> need to make sure it's included in any initramfs, so no it's not quite
> as simple as "but set them as modules" if you don't have any other modules.
>
> That said, I've always had a modular kernel and there really isn't
> anything much to it - I just do my best (provided I can find them) to
> configure all the *required* drivers into the kernel, so if the module
> system fails the system still boots, or if only sometimes need them,
> modules aren't loaded until necessary to save ram.
>
> Knowing how to boot a modular kernel is a sensible skill to have. And
> booting the modular way (even if you don't actually have any modules) is
> an easy and sensible thing to do.
Someone said once that he builds-in everything necessary to start the system,
and all the less essential things as modules. That seems to make sense, and I
followed that advice for some years. I haven't been too particular more
recently, though.
--
Regards,
Peter.
next prev parent reply other threads:[~2024-08-21 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 20:05 [gentoo-user] Do I need firmware for an integrated graphics unit? Alan Mackenzie
2024-08-20 21:16 ` Peter Böhm
2024-08-21 10:32 ` Wol
2024-08-21 10:59 ` Alan Mackenzie
2024-08-21 13:03 ` [gentoo-user] " Grant Edwards
2024-08-21 11:15 ` [gentoo-user] " Alan Mackenzie
2024-08-21 11:37 ` Michael
2024-08-21 12:04 ` Alan Mackenzie
2024-08-21 13:49 ` Michael
2024-08-21 15:22 ` Wol
2024-08-21 15:47 ` Peter Humphrey [this message]
2024-08-21 15:49 ` [gentoo-user] " Grant Edwards
2024-08-21 14:43 ` Grant Edwards
2024-08-21 12:03 ` [gentoo-user] " Peter Böhm
2024-08-21 17:26 ` Alan Mackenzie
2024-08-21 18:10 ` Peter Böhm
2024-08-22 11:57 ` Alan Mackenzie
2024-08-22 14:46 ` Peter Humphrey
2024-08-22 15:05 ` Michael
2024-08-22 16:37 ` Alan Mackenzie
2024-08-22 23:22 ` Peter Humphrey
2024-08-23 9:42 ` Wol
2024-08-23 16:41 ` Alan Mackenzie
2024-08-21 0:30 ` [gentoo-user] " Grant Edwards
2024-08-21 11:39 ` Alan Mackenzie
2024-08-21 11:54 ` Michael
2024-08-21 13:02 ` Grant Edwards
2024-08-23 16:28 ` Alan Mackenzie
2024-08-23 21:28 ` Grant Edwards
2024-08-22 0:34 ` [gentoo-user] " corbin bird
2024-08-22 8:28 ` Michael
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=12495124.O9o76ZdvQC@cube \
--to=peter@prh.myzen.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