I've installed rEFInd - very nice and helpful tool. Thanks for writing this piece of code.
But... but :) All of my changes made in refind.conf seem to be ignored. Doesn't matter if I change timeout (only), or banner picture - it looks always the same.
My only clue is: when I've tried to install rEFInd first time using Fedora 20, I've "done" it via RPM package - just by unpacking it. Then I couldn't find proper "trigger" to make PC bootable from it, so I've noticed:
df /boot/efi
has been mounted under '/' somewhere in sdb9 :==]
So I manually changed it to '/boot/efi', manually mounted EFI partition (which has not been mounted at all) and installed rEFInd one more time - but now it was manually.
It worked and rEFInd appeared in my UEFI BIOS boot options (this "trigger"), so I can boot directly from HDD.
df /boot/efi shows now:
System plików 1K-blocks użyte dostępne %uż. zamont. na
/dev/sdb1 126976 31651 95325 25% /boot/efi
Maybe it is problematic, but I'm using two drives: SSD (/dev/sda1 is ESP partition, too, but I didn't install rEFInd there) and HDD - each one is bootable (Windows boot manager) and GPTed to be UEFI-compatible. I wanted to check how rEFInd works @ HDD (I was booting from CD before that), but so far - I experience such issue as described.
Any thoughts ?
CHeers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Resolved.
RPM installation put refind directory by brute force to HDD's ESP (unmounted !) whether manual-done-installation has been pointed into SSD's ESP.
Last edit: biuro74 2014-09-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've installed rEFInd - very nice and helpful tool. Thanks for writing this piece of code.
But... but :) All of my changes made in refind.conf seem to be ignored. Doesn't matter if I change timeout (only), or banner picture - it looks always the same.
My only clue is: when I've tried to install rEFInd first time using Fedora 20, I've "done" it via RPM package - just by unpacking it. Then I couldn't find proper "trigger" to make PC bootable from it, so I've noticed:
df /boot/efi
has been mounted under '/' somewhere in sdb9 :==]
So I manually changed it to '/boot/efi', manually mounted EFI partition (which has not been mounted at all) and installed rEFInd one more time - but now it was manually.
It worked and rEFInd appeared in my UEFI BIOS boot options (this "trigger"), so I can boot directly from HDD.
df /boot/efi shows now:
System plików 1K-blocks użyte dostępne %uż. zamont. na
/dev/sdb1 126976 31651 95325 25% /boot/efi
Maybe it is problematic, but I'm using two drives: SSD (/dev/sda1 is ESP partition, too, but I didn't install rEFInd there) and HDD - each one is bootable (Windows boot manager) and GPTed to be UEFI-compatible. I wanted to check how rEFInd works @ HDD (I was booting from CD before that), but so far - I experience such issue as described.
Any thoughts ?
CHeers
Resolved.
RPM installation put refind directory by brute force to HDD's ESP (unmounted !) whether manual-done-installation has been pointed into SSD's ESP.
Last edit: biuro74 2014-09-26