From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What are common SSDs does and don'ts.
Date: Tue, 1 Apr 2025 22:33:01 -0500 [thread overview]
Message-ID: <2646a52b-70e5-908f-5118-20789caa99fc@gmail.com> (raw)
In-Reply-To: <12657129.O9o76ZdvQC@cube>
Peter Humphrey wrote:
> On Tuesday, 1 April 2025 13:56:31 British Summer Time Dale wrote:
>> Peter Humphrey wrote:
>>> On Tuesday, 1 April 2025 11:12:44 British Summer Time Dale wrote:
>>>> Is there somewhere I can look or some command I can run to see if I load
>>>> any microcode that it needs to access while booting but before /var is
>>>> mounted? Why isn't the microcode put in /usr or something anyway?
>>> See https://wiki.gentoo.org/wiki/Microcode
>>>
>>> That's the guide I followed.
>> I followed the link to the AMD one. Then I remembered that I do have
>> microcode loading because I have a amd-uc.img file in /boot. I never
>> messed with it but when I update grub config, it finds that. I guess it
>> will need a init thingy since it has to have that to load the microcode
>> thing too. The devs have it so automatic, I forgot about the thing. It
>> only hit me when I read the wiki thing.
>>
>> I guess I'll have to keep the init thingy. Now I know.
> I don't see why, Dale. I don't use one and my case is similar to yours. When I
> said I used one for microcode loading, I meant that the microcode image /is/
> the initrd.
>
Ahhhh. I have both. I have the microcode image as well as a init
image. Are you saying I can have just the microcode image and no
initramfs image and it will still boot? If you don't mind, can you list
what is in your /boot, just the kernel and init stuff that grub uses to
boot is enough. As a example, this is mine, with the command I used.
You may name things differently tho so adjust if needed.
root@Gentoo-1 / # ls /boot/ | grep -E '.img|kernel'
-rw-r--r-- 1 root root 148480 Mar 22 04:53 amd-uc.img
-rw------- 1 root root 15606048 Apr 1 16:34 initramfs-6.14.0-1.img
-rw------- 1 root root 12206262 Jul 23 2024 initramfs-6.9.10-1.img
-rw------- 1 root root 12418411 Jul 13 2024 initramfs-6.9.4-1.img
-rw------- 1 root root 12418472 Jul 13 2024 initramfs-6.9.4-2.img
-rw------- 1 root root 12419262 Jul 17 2024 initramfs-6.9.4-3.img
-rw-r--r-- 1 root root 15897600 Apr 1 16:16 kernel-6.14.0-1
-rw-r--r-- 1 root root 15385600 Aug 25 2024 kernel-6.9.10-1
-rw-r--r-- 1 root root 14943232 Jul 13 2024 kernel-6.9.4-1
-rw-r--r-- 1 root root 15021056 Jul 13 2024 kernel-6.9.4-2
-rw-r--r-- 1 root root 15381504 Aug 25 2024 kernel-6.9.4-3
root@Gentoo-1 / #
It uses the same microcode image for them all but as you can see, I have
5 boot options. I just created a new kernel and friends but have not
rebooted yet. I'll clean those up and get down to two or three one of
these days. If I didn't have the init thingy at all for one or more of
those, it would still boot with just a microcode image and kernel?
I read a link on this and I may point the kernel to the directory for it
to be included into the kernel. The only downside of that, old kernels
will have old microcode whereas this way, that microcode image gets
updated and on each reboot, loads the new microcode. Given the
infrequent kernel updates, this image method is the most up to date
method. If it updates, the new one loads on the next reboot, whenever
that happens.
Thanks.
Dale
:-) :-)
next prev parent reply other threads:[~2025-04-02 3:35 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 [this message]
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
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=2646a52b-70e5-908f-5118-20789caa99fc@gmail.com \
--to=rdalek1967@gmail.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