You are not logged in.
EDIT: After much frustration, I was able to find a solution. It seems that the recovery partition on this model of laptop is formatted in such a way as to make rEFInd's autoscanner crash. Disabling scanning for the recovery partition using the dont_scan_volumes option in refind.conf solves the issue.
I've tried installing rEFInd both using refind-install and manually as described on the wiki , and get the same result in both cases:
- When drivers_x64/ext4_x64 is present, rEFInd hangs on a screen with a white background and the rEFInd logo at the top (but OS logos or other symbols)
- Deleting the file results in rEFInd loading normally, but then (of course) it fails to detect Arch and shows only Windows
/boot/refind_linux.conf contains the following:
"Boot using default options" "root=PARTUUID=[relevant part of string returned from blkid /dev/nvme0n1p5] rw add_efi_memmap initrd=boot\intel-ucode.img initrd=boot\initramfs-linux.img" I also attempted to set up manual boot stanzas as described on the wiki page, but this has no effect - the boot manager still hangs on a blank screen.
The system in question is a HP EliteBook 840 G7.
Last edited by marcelgs (2021-07-01 21:00:34)
Offline
First, most common file system drivers are builtin rEFInd so it should work out without explicit driver install. Why do you need to explicitly install one?
Second, according to this, drivers also end with .efi extension. Where did you get your driver from?
My feeling is your issue is not with driver. Can you post your partition scheme i.e. lsblk? Also can you post your actual refind_linux.conf (not just that snippet) and refind.conf?
Offline