Arch Linux

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

[SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

Hi everyone,

I made a boot entry using the "UEFI shell"(Shell V2) method described in the wiki (https://wiki.archlinux.org/index.php/EFISTUB).

If I tried to add intel-ucode.img but I keep getting an error saying intel-ucode.img could not be found. I double checked the location of the .img it's under /boot on /dev/sda1

Here's what the fs1:\options.txt file looks like now:

   root=/dev/sda2 ro initrd=\intel-ucode.img
   root=/dev/sda2 ro initrd=\initramfs-linux.img

I also found an guide where they added the first entry with rw which also didn't work for me.

Thanks in advance.

Last edited by JohnyBeGood (2019-03-14 21:36:21)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,544

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

under /boot on /dev/sda1 doesn't tell us much. Where is it on the ESP?

miomio

Member

Registered: 2016-01-17

Posts: 167

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

Is ESP a location or a binary?

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

ESP is /dev/sda1
In the booted system it is mounted to /boot

[jbg@Arch boot]$ ls
initramfs-linux-fallback.img  intel-ucode.img  options.txt    vmlinuz-linux
initramfs-linux.img           optionsFB.txt    optionsUC.txt

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 1,975

Website

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

   root=/dev/sda2 ro initrd=\intel-ucode.img
   root=/dev/sda2 ro initrd=\initramfs-linux.img

Yeah, that's the problem. Try:

root=/dev/sda2 ro initrd=\intel-ucode.img initrd=\initramfs-linux.img

By the way: You are aware, that you are mounting / read-only this way?

Last edited by schard (2019-03-14 09:25:29)

---

macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

Thanks, I will try that later.
I was aware that it is read only and as I said in the initial post I also tried "rw" for intel-ucode.img.

Can you tell me what the proper way to mount the images is? rw?

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 1,975

Website

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

You don't "mount" the images.
You tell the kernel to load them in the specified order.
The "rw" or "ro" options apply to the mounting of the root file system you specify via "root=".
Having a "ro" (read only) filesystem is probably not what you want.
So you should also change "ro" to "rw".

Last edited by schard (2019-03-14 09:40:23)

---

macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

I seem to miss something. I do not think that root is ready only as I installed a DE and use it since a week or two.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

It's switched to rw later on in the boot process

There was  a time when root system was mounted read only to make fsck'ing root easier, but that hasn't been necessary for years.
recommendation now is to use rw or nothing.
I do think there was a news post about it back then, but can't find it.

Looks like efistub wiki page wasn't updated to reflect the change.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,544

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

   root=/dev/sda2 ro initrd=\intel-ucode.img
   root=/dev/sda2 ro initrd=\initramfs-linux.img

Yeah, that's the problem. Try:

root=/dev/sda2 ro initrd=\intel-ucode.img initrd=\initramfs-linux.img

Not only that, but if it's inside /boot on the ESP, the '\' path is obviously wrong.

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

   root=/dev/sda2 ro initrd=\intel-ucode.img
   root=/dev/sda2 ro initrd=\initramfs-linux.img

Yeah, that's the problem. Try:

root=/dev/sda2 ro initrd=\intel-ucode.img initrd=\initramfs-linux.img

By the way: You are aware, that you are mounting / read-only this way?

That actually was the problem. Thanks for helping me.

[SOLVED]

Though, l still can't see why to use rw instead of ro.

JohnyBeGood

Member

Registered: 2019-03-13

Posts: 6

Re: [SOLVED] EFISTUB does not recognise microcode (intel-ucode.img)

It's switched to rw later on in the boot process

There was  a time when root system was mounted read only to make fsck'ing root easier, but that hasn't been necessary for years.
recommendation now is to use rw or nothing.
I do think there was a news post about it back then, but can't find it.

Looks like efistub wiki page wasn't updated to reflect the change.

Sorry Lone_Wolf I overlooked your post. Changed to rw now as well.

Thanks everyone!