On Tuesday, 1 April 2025 11:12:44 British Summer Time Dale wrote:
Peter Humphrey wrote:
On Tuesday, 1 April 2025 01:44:18 British Summer Time Dale wrote:
... I have /usr on the same partition as / this time around.
Do I need a init thingy still or can I ditch that thing? I do have /var
on a separate partition, if that matters.
I have /var on a separate partition on some machines, and I only need an
initrd for microcode loading. I suppose I could include that in the
kernel,
but I haven't tried that.
I thought about the fact I have a merged /usr now which means everything
is in /usr. I hadn't thought of microcode being needed tho. How do I
find out if there is any microcode being loaded on my system? I do have
the package installed, read somewhere that it only loads something if it
is needed so no real harm in having it installed even if nothing is
being used today. It could prove helpful if something is being used
later on tho.
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?
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).