Then I have mkinitcpio set to look for the kernel (and thereby determine the kernel version) at its new location of /boot/EFI/arch/vmlinuz-linux.efi. To make sure my kernels and initramfs' get to where i want them to be, I use a systemd.path/rvice to move the kernel when it is installed. I use gummiboot, which does not have this support, so I keep my kernels and initramfs' in \EFI\arch (which would be /boot/EFI/arch) on my machine. Many UEFI bootloaders and boot managers have support for reading them off certain partition formats, but some don't. The only reason not to do it that way is if you want to keep your kernels and initramfs' off of the ESP. I have been doing that since I migrated to UEFI as it seemed much more sane in my head. Of course that path is relative to the root of youe ESP, and not to your filesystem as a whole. Just keep the other configuration as is, and then additionally copy refind圆4.efi to \EFI\boot\boot圆4.efi. Otherwise, you can simply put rEFInd in that default position as well. So you can put the UEFI shell there to get things going. Obviously in those cases you will not have an efibootmgr entry, so it will default to whatever is in that postition. It is \EFI\boot\boot圆4.efi, and is typically for when you have a removable media you are booting off of. If your system did not come with a shell in the firmware, you can use the default spot for *.efi applications. I fall else fails, you can use the UEFI shell to create entries, though I do not know the syntax offhand. So it may be that you are doing everything right, but just being bitten by this bug. There have been some bugs with efibootmgr not actually creating entries on some machines/firmwares. Is your EFI System Partition of gdisk type ef00? After you use efibootmgr to make the entry, does it show up when you run efibootmgr w/o any arguments? If so, when you run efibootngr -v, what does it show for your refind entry?
0 Comments
Leave a Reply. |