The guy can’t even read a name?

Last I checked this is Artix

I’ll have to check if EFISTUB causes any problems with microcode

We have the same grub dumbass.

And this is 4 chan, because a random idiot just said the “you don’t know shit about X”

what if you just put initrd=microcode.img to kernel command line

Chris random idiot confirmed

Yes, definitely. Maybe a troll too, will keep an eye

Maybe?

That might cause problems since microcode is firmware not a compressed rootfs

Yes, coming here to spread stupidity and lies to annoy others.

but it is the way to load microcode. grub literally does the same when you do “initrd ucode.img”

wiki:
These updates must be enabled by adding /boot/amd-ucode.img or /boot/intel-ucode.img as the first initrd in the bootloader configuration file. This is before the normal initrd file. See below for instructions for common bootloaders.

Look, let’s skip over the sweaty discussions where you claim to know more than I do, and I pretend that I’m impressed by your Arch-bro skills

And let’s move on to the part where you don’t spread your misinformation as facts

Considering I have packaged grub for artix, I know this hasn’t happened before. So shut the fuck up.

Oh! OK

So first of all, good job!

/warn no more trolling or you will be gone

I’m really scared now

It’s not meant to scare you. Behave like an adult and we won’t have any more problems.

OK. I will

For starters, since you’re the one who packages grub,

Can we get someone competent?

/ban bye bye troll

/unban @m3lcore

Nope, don’t need his toxic shit here.

Oh OK thanks

So I guess ELILO is usable

Yeah I’ll probably go with EFISTUB and skip bootloaders entirely

The guy can’t even read a name?

If you consider abandoned software a good idea… Sure why not.

I said I have packaged it, never said I am the current maintainer.

Ah xD

with this screenshot I just wanted to say that microcode can be loaded using initrd kernel option)