You are not logged in.
Pages: 1
This is my first introduction to the wacky wonderful world of EFI. First question: is there any chance of damaging my machine by booting into a kernel panic repeatedly?
I just installed Arch and it successfully boots using rEFInd, however, I'd like to directly boot the EFISTUB. My partition looks like this:
/dev/sda1 /boot vfat <---- ESP partition
/boot/EFI <--- where refind is installed
/boot/vmlinuz-linuz
/boot/initramfs-linux.img
so I added the entry using
efibootmgr -d /dev/sda -p 1 -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sda2 rw initrd=/initramfs-linux.img"
according to the wiki. When I try to boot using this entry, I get a kernel panic:
not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
so my question is, am I directing the boot manager to the proper file? some of the docs mention a vmlinuz-linux.efi file, but there are no *.efi files on my system other than those installed by rEFInd.
If I am pointing to the correct file, am I missing some kernel options that rEFInd is adding automatically?
Last edited by spotty (2015-02-26 05:23:07)
Offline
rEFInd is a UEFI Boot Manager which provides a graphical menu for booting EFISTUB kernels.
Note that it does not say "boot loader", but "boot manager". This means rEFInd already uses the EFISTUB functionality for booting your computer.
When you want to change kernel parameters you have to use efibootmgr again, instead of simply editing a text file. There is no benefit to using EFISTUB directly instead of rEFInd, you will not gain anything from this besides a little bit of knowledge about efibootmgr.
If you want a more minimal boot manager than rEFInd, gummiboot fits better.
Offline
My partition looks like this:
/dev/sda1 /boot vfat <---- ESP partition /boot/EFI <--- where refind is installed /boot/vmlinuz-linuz /boot/initramfs-linux.img
That is not very clear.
Please post the output of:
# gdisk /dev/sda
lsblk -f
# efibootmgr -v
Jin, Jîyan, Azadî
Offline
Pages: 1