You are not logged in.
Pages: 1
Hi, on a new install I decided to try out rEFInd. I used the scripted installation but when I rebooted, there were no boot entries I could boot into. How it looks: https://ibb.co/jbqbyF Thanks for any help you can provide
Last edited by chraffx (2017-05-21 04:27:09)
Offline
Please post the contents of the system's /boot/refind_linux.conf
Offline
Also, what scripted installation did you use?
Matt
"It is very difficult to educate the educated."
Offline
Refind detects all installed bootloaders, here it seems there are none on the esp partition.
Have you done:
bootctl install from the chroot?
Offline
Refind detects all installed bootloaders, here it seems there are none on the esp partition.
Refind is a bootloader and if it is not installed on the ESP how would it being loaded and produce a blank screen?
Have you done:
bootctl install from the chroot?
Refind does not need any help from another bootloader to boot an OS. Adding an additional bootloader may confuse the issue and I do not see how it will diagnose the issue with refind and its configuration.
Offline
Maybe because refind disables arch default entry by default unless an efi file is found:
menuentry "Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "Arch Linux"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=PARTUUID=5028fa50-0079-4c40-b240-abfaf28693ea rw add_efi_memmap"
submenuentry "Boot using fallback initramfs" {
initrd /boot/initramfs-linux-fallback.img
}
submenuentry "Boot to terminal" {
add_options "systemd.unit=multi-user.target"
}
disabled
}
linux-lts is detected directly.
Offline
Loqs for your personal references a quote of Rod Smith:
Fundamentally, rEFIt and rEFInd are boot managers. I presume this is what motivated Christoph Pfisterer to create rEFIt. I forked rEFIt into rEFInd after rEFIt fell into disrepair.
A boot loader, by contrast, loads a kernel into memory and transfers control to it. A boot loader does not need to interact with the user directly (although it could). Neither rEFIt nor rEFInd is technically a boot loader, although the Linux kernel creates a blurred line, because it includes a feature (the EFI stub loader) that enables it to function as its own EFI boot loader.
Offline
If your post was the last post in the thread please edit that post rather than creating a new one.
This seems to be going off topic in that I am not sure how that distinction is relevant to issue outlined by chraffx.
Without knowing the contents of refind_linux.conf, refind.conf, the ESP and /boot if separate how can anything more than speculation be achieved?
Edit:
grammar change ? to .
Last edited by loqs (2017-05-20 15:58:36)
Offline
I redid the installation and an entry appeared now, I expect that it was an error in creating the /boot/refind_linux.conf correctly. My current /boot/refind_linux.conf looks like this:
"Boot with standard options" "archisobasedir=arch archisolabel=ARCH_201705"
"Boot to single-user mode" "archisobasedir=arch archisolabel=ARCH_201705 single"
"Boot with minimal options" "ro root=UUID=990b590b-20ff-4e13-abb5-359468c7ad6f"
I believe the third line was generated without a device. As I still have an issue with the install but it doesn't fit under the same title I'll mark this thread solved and make a new one for that.
Offline
Pages: 1