Skip to main content
Topic: should grub use both intel-ucode and amd-ucode? (Read 408 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

should grub use both intel-ucode and amd-ucode?

I notice that some distros seem to use both intel-ucode and amd-ucode ie

initrd   /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img

is that reasonable?

Re: should grub use both intel-ucode and amd-ucode?

Reply #1

Only if you have a mainboard with sockets for Intel and Amd CPU.
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

 

Re: should grub use both intel-ucode and amd-ucode?

Reply #3
..........
Perhaps on live medium? I'm not sure.

I think that's where I have seen it often, but I have a recently built artix VM (from artix-lxde-dinit-20230814-x86_64.iso) which has grub.cfg with

Code: [Select]
initrd   /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img

so it has been installed that way.

Re: should grub use both intel-ucode and amd-ucode?

Reply #4
I think that since microcode loading is automatic process that shouldn't harm anything. But maybe that redundancy slows down boot process, so you may want to change that to your-cpu-manufacturer-only line.

Re: should grub use both intel-ucode and amd-ucode?

Reply #5
If you check the situation with some older CPU's, support has ended so there will never be new ucode releases. If the latest ucode is in the latest BIOS release, and you are running the latest BIOS, then any cpu ucode package is pointless, but it's up to the user to determine if this is the case.