Version 0.11.0 of rEFInd is now out! This version adds several new features (thanks in part to work by CJ Vaughter and Pavel Venev), in addition to more mundane bug fixes. See the rEFInd revisions summary page for details. Features that an average user are likely to be most interested in are the new mouse support and the ability to hide loaders via a single keypress in the main menu.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are easy ways (from Linux and Windows, don't know about macOS) to add NVRAM entries.
rEFInd maintained by Roderick has, thanks to him, superb documentation on its homepage.
And btw. - upgrading could be easily executed by just copying new files to proper places on ESP.
No need to reinstall, reinstall and... reinstal ; )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Because verifying that an existing entry matches what should be used for a new installation or update is tricky, the refind-install script deletes the current entry and creates a new one. Unfortunately, sometimes EFIs get flaky in their handling of NVRAM variables, which can cause them to not be added properly when efibootmgr tries to do so. These two factors can combine to cause the problem you describe, biuro74. I'll take a look at the installation script; it may be possible for it to take a lighter touch on the delete-then-re-create approach, which should help minimize this type of problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hiding tags with rEFInd of main hard drive is causing that rEFInd of flashdrive hides them too.
This is not expected behaviour?
Where is information about hidden loaders kept?
(hiding for main hard drive is work day-day solution but when flashdrive is connected and booted then this is safety to have all the options shown - there are no manual stanzas defined there)
You wrote sth about UEFI entries here ("Note that this feature is very new, so please be careful with it, especially since it involves writing to NVRAM") but what I'm hiding are linux efi stub loaded kernels only.
Could you consider adding semi-automatic linux kernel boot options?
I mean what we have now is fully automatic discover (and boot options the same time) or manual stanzas - even if we want to add just one boot parameter.
I suspect this problem has been already discussed?
What I am proposing are stanzas of "linux load parameters" type. So for volume defined by filesystem label or UUID we have just one option: 'additional boot parameters'.
This way we can have / leave automatic discover on and add one or more parameters for linux kernel.
Last edit: Jsf 2017-09-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The new hiding feature stores information on what to hide in NVRAM, which means that the hiding options apply to all rEFInd instances, no matter how they're launched. Thus, what you're seeing is the expected and normal behavior. You can always unhide an option if you want to, provided the hidden_tags option to showtools is enabled.
If you want to change kernel options on a one-time basis, you can do so by hitting F2, Insert, or Tab twice. This will open a line editor in which you can enter any options you like. You can also customize the options passed to a kernel by using the refind_linux.conf file in the same directory as the kernel itself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, and in fact that is possibly better to have one centralized "hiding" database.
Then just some small notification that tags were hidden would be useful.
As for the refind_linux.conf is it possible to have initrd= specification as one of the option parameters and the same time pointer to the main initial RAM disk automatically added?
Problem occurs with "..... initrd=\boot\intel-ucode.img" parameter.
You have quite a lot of automation built-in here and there and with refind_linux.conf we have unfortunately decentralized options database. At least I treat my ESP as my control place and I'm not allowing any distribution to install grub or even mount it like it wants.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 0.11.0 of rEFInd is now out! This version adds several new features (thanks in part to work by CJ Vaughter and Pavel Venev), in addition to more mundane bug fixes. See the rEFInd revisions summary page for details. Features that an average user are likely to be most interested in are the new mouse support and the ability to hide loaders via a single keypress in the main menu.
Big Tnx Sir! Awesome.
del
Last edit: hova888 2017-08-17
Indeed, BOOT.CSV exists now, but what RPM install has done, was to ... remove rEFInd entry from my BIOS :/ Now I have to install it again, manually.
There are easy ways (from Linux and Windows, don't know about macOS) to add NVRAM entries.
rEFInd maintained by Roderick has, thanks to him, superb documentation on its homepage.
And btw. - upgrading could be easily executed by just copying new files to proper places on ESP.
No need to reinstall, reinstall and... reinstal ; )
Because verifying that an existing entry matches what should be used for a new installation or update is tricky, the
refind-installscript deletes the current entry and creates a new one. Unfortunately, sometimes EFIs get flaky in their handling of NVRAM variables, which can cause them to not be added properly whenefibootmgrtries to do so. These two factors can combine to cause the problem you describe, biuro74. I'll take a look at the installation script; it may be possible for it to take a lighter touch on the delete-then-re-create approach, which should help minimize this type of problem.Hiding tags with rEFInd of main hard drive is causing that rEFInd of flashdrive hides them too.
This is not expected behaviour?
Where is information about hidden loaders kept?
(hiding for main hard drive is work day-day solution but when flashdrive is connected and booted then this is safety to have all the options shown - there are no manual stanzas defined there)
You wrote sth about UEFI entries here ("Note that this feature is very new, so please be careful with it, especially since it involves writing to NVRAM") but what I'm hiding are linux efi stub loaded kernels only.
Could you consider adding semi-automatic linux kernel boot options?
I mean what we have now is fully automatic discover (and boot options the same time) or manual stanzas - even if we want to add just one boot parameter.
I suspect this problem has been already discussed?
What I am proposing are stanzas of "linux load parameters" type. So for volume defined by filesystem label or UUID we have just one option: 'additional boot parameters'.
This way we can have / leave automatic discover on and add one or more parameters for linux kernel.
Last edit: Jsf 2017-09-02
The new hiding feature stores information on what to hide in NVRAM, which means that the hiding options apply to all rEFInd instances, no matter how they're launched. Thus, what you're seeing is the expected and normal behavior. You can always unhide an option if you want to, provided the
hidden_tagsoption toshowtoolsis enabled.If you want to change kernel options on a one-time basis, you can do so by hitting F2, Insert, or Tab twice. This will open a line editor in which you can enter any options you like. You can also customize the options passed to a kernel by using the
refind_linux.conffile in the same directory as the kernel itself.Ok, and in fact that is possibly better to have one centralized "hiding" database.
Then just some small notification that tags were hidden would be useful.
As for the refind_linux.conf is it possible to have initrd= specification as one of the option parameters and the same time pointer to the main initial RAM disk automatically added?
Problem occurs with "..... initrd=\boot\intel-ucode.img" parameter.
You have quite a lot of automation built-in here and there and with refind_linux.conf we have unfortunately decentralized options database. At least I treat my ESP as my control place and I'm not allowing any distribution to install grub or even mount it like it wants.