From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What are common SSDs does and don'ts.
Date: Wed, 02 Apr 2025 12:13:44 +0100 [thread overview]
Message-ID: <1936908.tdWV9SEqCh@cube> (raw)
In-Reply-To: <2646a52b-70e5-908f-5118-20789caa99fc@gmail.com>
On Wednesday, 2 April 2025 04:33:01 British Summer Time Dale wrote:
--->8
> >> 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?
I don't know your system well enough to predict what you can do, but I have
that arrangement.
> 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.
--->8
# ls -l /boot | grep -v rescue
total 78M
-rwxr-xr-x 1 root root 145K Apr 1 11:20 amd-uc.img
-rwxr-xr-x 1 root root 139K Apr 1 11:20 config-6.12.21-gentoo
-rwxr-xr-x 1 root root 136K Feb 21 10:43 config-6.6.74-gentoo
-rwxr-xr-x 1 root root 216K Dec 10 15:01 early_ucode.cpio
drwxr-xr-x 5 root root 16K May 28 2024 EFI
-rwxr-xr-x 1 root root 21M Apr 1 11:20 intel-uc.img
drwxr-xr-x 3 root root 16K Apr 1 11:22 loader
-rwxr-xr-x 1 root root 6.3M Apr 1 11:20 System.map-6.12.21-gentoo
-rwxr-xr-x 1 root root 5.9M Feb 21 10:43 System.map-6.6.74-gentoo
-rwxr-xr-x 1 root root 11M Apr 1 11:20 vmlinuz-6.12.21-gentoo
-rwxr-xr-x 1 root root 11M Feb 21 10:43 vmlinuz-6.6.74-gentoo
That's everything in /boot. Nothing about grub, because I don't use it, much
preferring bootctl from systemd-utils (that's the only systemd package here),
whence the loader/ directory. I keep a small rescue system on each machine,
though these days it's usually used only for routine backups of the main
system.
I don't know where the amd-uc.img comes from. It shouldn't exist in an Intel
system, but if I delete it it just reappears. I'll track it down one day.
> 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.
Good point, if your kernels become that old.
--
Regards,
Peter.
next prev parent reply other threads:[~2025-04-02 11:15 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 [this message]
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=1936908.tdWV9SEqCh@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