You are not logged in.
Pages: 1
Hey fellows hope you're all doing great.
I just have some questions regarding refind boot manager which I use to dual boot arch and windows on my laptop.
Before I installed arch,I installed refind boot manager from windows 8 using the guide on the rodsmith website.
Then I went on and installed arch,and everything worked right away.
On the arch system I mounted the efi partition to the
boot folder using fstab.
UUID="502D-3405" /boot/efi vfat defaults 0 1¬
/dev/sda2: UUID="502D-3405" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="85674c9f-2484-4b3b-bb97-2205e8d9da1c"so what resides now in my boot folder next to the efi folder,are the files (initramfs-linux.img, initramfs-linux-fallback.img
and vmlinuz-linux)
to make a long story short,I'm trying to create a custom entry in refind to boot into the kernel with modified parameters.
I just added this stanza to the defualt refind.conf file in (/boot/efi/EFI/refind/)
#Custom.Kernel Test
menuentry "Arch Linux" {
icon /EFI/refind/icons/os_arch.icns
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=PARTUUID=5b772462-68e1-463c-b22f-8ff22625ec21 rw rootfstype=ext4 pcie_aspm=force i915.i915_enable_rc6=1"
}blkid
/dev/sdb1: LABEL="root" UUID="310f4bbc-0a2c-4667-a397-d020a7c94177" TYPE="ext4" PARTUUID="5b772462-68e1-463c-b22f-8ff22625ec21"The entry is there,but the the system won't boot.I also tried compiling a custom kernel the traditional way using the guide on the wiki,the kernel and the img are created another entry for the custom kernel which showed up on the refind menu,when I select it,error that the loader is not found while loading vmlinuz comes up although all the files are in the boot directory.
Is there any thing I'm missing to make the new kernel bootable ?
Last edited by Herbalist (2014-08-01 12:24:30)
Offline
It seems as if you have two drives: one containing the efi-partition (sda2) and one containing your system (sdb)
On which partition is your boot folder you put the kernel images in?
If your kernel files are NOT on the efi partition you need to specify that using the 'volume' token as described here because the paths for 'loader' and such are relative to the efi partition or the specified volume.
Last edited by dice (2014-07-31 15:59:24)
I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do. (Gune | Titan A.E.)
Offline
If your kernel files are NOT on the efi partition you need to specify that using the 'volume' token as described here because the paths for 'loader' and such are relative to the efi partition or the specified volume.
Thank you dice,that's what I was missing.I just added the volume token and it worked.
Offline
Pages: 1