You are not logged in.
Hi, I am trying to use rEFInd as my bootloader but my custom configuration isn't able to successfully boot the system.
My kernel options:
menuentry "Arch Linux Zen" {
icon /EFI/refind/icons/os_arch.png
volume "Arch Linux"
loader /boot/vmlinuz-linux-zen
initrd /boot/initramfs-linux-zen.img
options "root=PARTUUID=xxxxxxx rw initrd=boot\intel-ucode.img"
submenuentry "Boot with IMMOU and Nvidia VIFO Stub" {
add_options "intel_iommu=on iommu=pt vfio-pci.ids=10de:1c8c"
}
submenuentry "Boot using fallback initramfs" {
initrd /boot/initramfs-linux-zen-fallback.img
}
submenuentry "Boot to terminal" {
add_options "systemd.unit=multi-user.target"
}
}systemd-modules-load.service log:
Feb 12 22:29:54 arch systemd[1]: Starting Load Kernel Modules...
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'crypto_user': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'sg': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'nvidia-uvm': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'v4l2loopback': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'vboxdrv': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'vboxnetadp': Function not implemented
Feb 12 22:29:54 arch systemd-modules-load[541]: Failed to look up module alias 'vboxnetflt': Function not implemented
Feb 12 22:29:54 arch systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 22:29:54 arch systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Feb 12 22:29:54 arch systemd[1]: Failed to start Load Kernel Modules.
Feb 12 22:29:58 arch systemd[1]: Starting Load Kernel Modules...
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'crypto_user': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'sg': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'nvidia-uvm': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'v4l2loopback': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'vboxdrv': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'vboxnetadp': Function not implemented
Feb 12 22:29:58 arch systemd-modules-load[566]: Failed to look up module alias 'vboxnetflt': Function not implemented
Feb 12 22:29:58 arch systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 22:29:58 arch systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Feb 12 22:29:58 arch systemd[1]: Failed to start Load Kernel Modules.I am not sure what's wrong with my configuration. I am able to boot with the exact same kernel with GRUB so a misconfigured kernel can be ruled out.
Last edited by TheDcoder (2022-02-13 17:37:49)
Offline
It turns out it was an incredible series of coincidences that lead to the issue:
1. I adapted the sample rEFInd config which uses labels to identify the partition containing the kernel
2. The example uses "Arch Linux" and my label for the root partition is also the same
3. I also have a older copy of the same partition on a different drive (from the time I switched from a HDD to SSD)
As a result, rEFInd was loading my old backup partition containing an ancient version of the same kernel, and obviously some modules were missing.
The fix is simple, just use a proper UUID to identify your partition with the kernel and set it to the "volume" option in the config. I also renamed my backup partition to "Arch Linux Old" as a safety precaution to prevent incidents like this in the future.
Offline
You should edit your original post to indicate it's solved
Offline
How do I do that? I can't find the option to mark it as solved.
Offline
Edit the first post in the thread. That first post (only) has the ability to edit the title. Prepend [SOLVED] to the title.
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 for the info. Seems to be a very primitive way to do it though, would be nice if there was a button or option to do that. Also I can't prepend [SOLVED] to the title due to the character limit :-/
Subjects cannot be longer than 70 characters.
Last edited by TheDcoder (2022-02-13 15:47:57)
Offline
Seems to be a very primitive way to do it though, would be nice if there was a button or option to do that.
I think Arch uses the default configuration so perhaps submit a feature request upstream.
I can't prepend [SOLVED] to the title due to the character limit
Remove the superfluous "bootloader custom config" bit then.
Jin, Jîyan, Azadî
Offline
Done.
The [SOLVED] title hack does seem to be somewhat integrated into the forum already as it has the ability to list "unanswered" questions: https://bbs.archlinux.org/search.php?ac … unanswered
If this is implemented then I don't think it's much of a hassle to add a button. I am not the right person to report this upstream, I'll leave that up to the forum maintainers ![]()
Offline
The [SOLVED] title hack does seem to be somewhat integrated into the forum already as it has the ability to list "unanswered" questions: https://bbs.archlinux.org/search.php?ac … unanswered
Unanswered and unsolved are entirely different things.
An unanswered thread is simply one with 0 replies.
Offline