From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What are common SSDs does and don'ts.
Date: Wed, 2 Apr 2025 00:46:47 +0200 [thread overview]
Message-ID: <Z-xs1_t9t8vV6O59@q> (raw)
In-Reply-To: <f0969b1c-28a6-7a30-c448-088a356c58d1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]
Am Tue, Apr 01, 2025 at 08:03:06AM -0500 schrieb Dale:
> > The microcode blobs are not in /usr, but in /lib/firmware; e.g.:
> >
> > $ ls /lib/firmware/amd-ucode/
> > microcode_amd.bin microcode_amd_fam16h.bin microcode_amd_fam19h.bin
> > microcode_amd_fam15h.bin microcode_amd_fam17h.bin README
> >
> > You either include the microcode required by your CPU in an initrd, or build
> > it in your kernel by specifying it - along with any firmware needed by your
> > graphics, etc. - in your kernel (CONFIG_EXTRA_FIRMWARE).
>
>
> I have these.
>
>
> root@Gentoo-1 / # ls /lib/firmware/amd-ucode/
> total 184
> drwxr-xr-x 2 root root 4096 Dec 16 12:28 .
> drwxr-xr-x 104 root root 20480 Mar 22 07:36 ..
> -rw-r--r-- 1 root root 12684 Mar 22 04:52 microcode_amd.bin
> -rw-r--r-- 1 root root 7876 Mar 22 04:52 microcode_amd_fam15h.bin
> -rw-r--r-- 1 root root 3510 Mar 22 04:52 microcode_amd_fam16h.bin
> -rw-r--r-- 1 root root 22596 Mar 22 04:52 microcode_amd_fam17h.bin
> -rw-r--r-- 1 root root 100684 Mar 22 04:52 microcode_amd_fam19h.bin
> -rw-r--r-- 1 root root 4662 Mar 22 04:52 README
> root@Gentoo-1 / #
>
>
> I'm family 25 so not sure if those apply.
Look at the readme in the same directory.
rour 25 (mine, too) is 0x19 in hex notation.
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
Electronically yours,
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-01 22:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 18:50 [gentoo-user] What are common SSDs does and don'ts Dale
2025-03-22 19:29 ` Mark Knecht
2025-03-22 21:37 ` Michael
2025-03-23 1:48 ` Dale
2025-03-23 9:00 ` Michael
2025-03-23 21:41 ` Dale
2025-03-23 22:15 ` Nate Eldredge
2025-03-23 22:32 ` Frank Steinmetzger
2025-03-23 23:24 ` Dale
2025-03-31 21:27 ` Frank Steinmetzger
2025-04-01 0:44 ` Dale
2025-04-01 10:01 ` Peter Humphrey
2025-04-01 10:12 ` Dale
2025-04-01 10:24 ` Peter Humphrey
2025-04-01 12:56 ` Dale
2025-04-01 13:13 ` Peter Humphrey
2025-04-02 3:33 ` Dale
2025-04-02 11:13 ` Peter Humphrey
2025-04-01 11:04 ` Michael
2025-04-01 13:03 ` Dale
2025-04-01 15:44 ` Michael
2025-04-02 4:04 ` Dale
2025-04-02 8:29 ` Michael
2025-04-07 18:28 ` Dale
2025-04-01 22:46 ` Frank Steinmetzger [this message]
2025-04-01 23:08 ` Frank Steinmetzger
2025-04-02 4:03 ` Dale
2025-03-23 4:34 ` Matt Jolly
2025-03-23 6:56 ` netfab
2025-03-23 7:01 ` Dale
2025-03-23 7:03 ` netfab
2025-03-23 22:46 ` Frank Steinmetzger
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=Z-xs1_t9t8vV6O59@q \
--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