You are not logged in.
Hi all,
I am trying to get the intel-ucode drivers going on my mbp. Reading the wiki here https://wiki.archlinux.org/index.php/microcode#rEFInd
and I added these lines to /boot/refind_linux.conf
"Boot with standard options" "root=UUID=<UUID> rw initrd=/intel-ucode.img initrd=/initramfs.img"when i boot, it fails and says it cannot find intel-ucode.img or initramfs.img. I've also tried
"Boot with standard options" "root=UUID=<UUID> rw initrd=intel-ucode.img initrd=initramfs.img"and
"Boot with standard options" "root=UUID=<UUID> rw initrd=/boot/intel-ucode.img initrd=/boot/initramfs.img"all of which give me the same error message.
I verified that intel-ucode is installed. The root=UUID matches the / mountpoint in my fstab. I do NOT have a separate boot partition.
help
thanks. . .
Last edited by shelbydz (2016-04-14 11:49:26)
Offline
I do NOT have a separate boot partition
care to elaborate on this?
uefi by definition requires a boot partition in the form of the ESP
Offline
shelbydz wrote:I do NOT have a separate boot partition
care to elaborate on this?
uefi by definition requires a boot partition in the form of the ESP
Sorry, yes to clarify. I have a seperate partition that is already in place by osx that contains the EFI information. That's /dev/sda1. I installed reFIND and not anything like grub or syslinux.
The linux kernel and intel-ucode.img live in /boot, but that's /dev/sda5, which is the / partition.
thx
Offline
I believe that the kernel and initrds need to be on the ESP.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I believe that the kernel and initrds need to be on the ESP.
It does with some systems, like systemd-boot, but it doesn't with rEFInd. You do need to make sure it's reading from the correct partition and that rEFInd has drivers for the filesystem.
Offline
Okay, I'll take your word on that. I installed eEFInd on my daughter's MBP using my standard approach of mounting the EFI partition on boot, so I know that works. I have not tried it the other way, but have no reason to suspect it won't work.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Thanks Scimmia,
that was it. I bypassed the refind_linux.conf, rebooted and looked at the boot options that reFIND uses by default. It was using root=/dev/sda5 instead of the root=UUID=<UUID>. I swapped over to that and all is well.
Thanks for the help.
Offline