Hi - new refind user. Just installed arch using refind to boot. All is well. I also make custom kernels called linux-custom. I installed that package and as usual the kernel and image file are in /boot.
i.e. it contains
s
total 45368
4 efi/ 15728 initramfs-linux-fallback.img 4 syslinux/
15896 initramfs-linux-custom-fallback.img 3048 initramfs-linux.img 3812 vmlinuz-linux
3052 initramfs-linux-custom.img 4 refind_linux.conf 3820 vmlinuz-linux-custom
The refind display finds both and displays an icon for each kernel - however only the baseline linux boots - the linux-custom kernel dies failing to find /lib/modules/xxx (or similar).
I wonder how to fix this? It almost seems like the initram being used is the wrong one - but I cannot tell.
Any suggestions?
thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
rEFInd is optimized to find and boot kernels with filenames that include a number that's matched against an initrd file that also contains a number. This works very well with the standard naming conventions on Fedora, Debian, Ubuntu, OpenSUSE, and most other distributions. Arch, though, doesn't follow this convention, and so rEFInd's kernel auto-detection mechanisms don't work as well with it. In particular, your case of having two different kernels, neither of which has a filename with a number in it, and each of which links to two initrd files, does poorly with rEFInd's auto-detection. The easiest solution is likely to be to create manual boot stanzas, as described in the rEFInd documentation. Alternatively, you could move each kernel to its own directory or rename them so that they include numbers, but either of these options will require doing this manually (or at best, via a script fired off as part of kernel updates).
Pattern matching for the default is very basic; there are no regular expressions, just straight matches. You can, however, include a space in such matches, as in:
default_selection "vmlinuz-linux "
Of course, if you use a manual boot stanza (or for that matter, move or rename the files), you can use names that are more easily disambiguated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi - new refind user. Just installed arch using refind to boot. All is well. I also make custom kernels called linux-custom. I installed that package and as usual the kernel and image file are in /boot.
i.e. it contains
s
total 45368
4 efi/ 15728 initramfs-linux-fallback.img 4 syslinux/
15896 initramfs-linux-custom-fallback.img 3048 initramfs-linux.img 3812 vmlinuz-linux
3052 initramfs-linux-custom.img 4 refind_linux.conf 3820 vmlinuz-linux-custom
The refind display finds both and displays an icon for each kernel - however only the baseline linux boots - the linux-custom kernel dies failing to find /lib/modules/xxx (or similar).
I wonder how to fix this? It almost seems like the initram being used is the wrong one - but I cannot tell.
Any suggestions?
thanks.
Forgot to ask - with both linux and linux-custom and
default_selection vmlinuz
it picks vmlinuz-linux-custom - which would be fine if it worked - what do I put to have it boot the arch standard kernel (vmlinuz-linux)
is there some regex I can use like
default_selection vmlinuz-linux$
thanks!
rEFInd is optimized to find and boot kernels with filenames that include a number that's matched against an initrd file that also contains a number. This works very well with the standard naming conventions on Fedora, Debian, Ubuntu, OpenSUSE, and most other distributions. Arch, though, doesn't follow this convention, and so rEFInd's kernel auto-detection mechanisms don't work as well with it. In particular, your case of having two different kernels, neither of which has a filename with a number in it, and each of which links to two initrd files, does poorly with rEFInd's auto-detection. The easiest solution is likely to be to create manual boot stanzas, as described in the rEFInd documentation. Alternatively, you could move each kernel to its own directory or rename them so that they include numbers, but either of these options will require doing this manually (or at best, via a script fired off as part of kernel updates).
Pattern matching for the default is very basic; there are no regular expressions, just straight matches. You can, however, include a space in such matches, as in:
Of course, if you use a manual boot stanza (or for that matter, move or rename the files), you can use names that are more easily disambiguated.
Thank you ... I'll try adding manual stanza as you suggest. Thanks for your good work on this and your prompt reply too!
tested and works fine ... thank you!