From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side.
Date: Sat, 24 Aug 2024 11:08:44 +0100 [thread overview]
Message-ID: <3583233.iIbC2pHGDl@rogueboard> (raw)
In-Reply-To: <6f01d2bf-b29a-b517-f4a7-d599ddfc1858@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
On Friday, 23 August 2024 19:27:58 BST Dale wrote:
> I'm going to add a tidbit of info here. Might relate, might not. On my
> old system and my new system, I installed the sys-kernel/linux-firmware
> package. During the install of that package, a file magically appeared
> in /boot named amd-uc.img
This is the CPU microcode for AMD CPUs:
https://wiki.gentoo.org/wiki/AMD_microcode
> and when I run grub to create the config file,
> it sees and adds that the same as it does a init thingy and kernel for
> booting. I think a few months ago the way firmware works changed. I
> think there is a news item. Maybe.
>
> Even if you don't use init thingys, you might could use that file the
> linux-firmware package creates. Maybe you can put that in your kernel
> and include it inside the kernel. Then when you update your kernel,
> just include the newer file the package provides in /boot.
It can be built in the kernel, or added to the initramfs if you use one.
> If nothing else, that may give you a idea, about something I really
> don't understand completely. o_O LOL
>
> Dale
>
> :-) :-)
The CPU OEMs occasionally release microcode updates to address CPU instruction
bugs, but for modern CPUs you're more likely to obtain a timely microcode
patch by updating your MoBo's firmware.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-08-24 10:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:54 [gentoo-user] New machine: Contents of display are offset around 2 inches from the left hand side Alan Mackenzie
2024-08-22 21:44 ` Michael
2024-08-23 16:21 ` Alan Mackenzie
2024-08-23 18:27 ` Dale
2024-08-24 10:08 ` Michael [this message]
2024-08-23 18:33 ` Jack
2024-08-23 18:44 ` Dale
2024-08-23 19:09 ` Alan Mackenzie
2024-08-24 9:44 ` Michael
2024-08-24 13:25 ` Alan Mackenzie
2024-08-24 15:40 ` Michael
2024-08-24 20:36 ` Alan Mackenzie
2024-08-25 12:33 ` Alan Mackenzie
2024-08-25 13:53 ` Dale
2024-08-25 16:02 ` Michael
2024-08-25 16:28 ` Dale
2024-08-25 15:31 ` Michael
2024-08-25 17:47 ` Alan Mackenzie
2024-08-25 18:28 ` Dale
2024-08-25 19:12 ` Alan Mackenzie
2024-08-25 19:37 ` Dale
2024-08-25 21:04 ` Michael
2024-08-26 9:36 ` Peter Humphrey
2024-08-26 10:40 ` Alan Mackenzie
2024-08-26 11:54 ` Michael
2024-08-26 14:49 ` Alan Mackenzie
2024-08-27 16:05 ` Alan Mackenzie
2024-08-27 18:36 ` Michael
2024-08-27 20:50 ` Alan Mackenzie
2024-08-28 14:58 ` [gentoo-user] [Fixed] " Alan Mackenzie
2024-08-28 15:25 ` Dale
2024-08-25 21:07 ` [gentoo-user] " Alan Mackenzie
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=3583233.iIbC2pHGDl@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