First I want to thank you Rod for all the pages you wrote and for rEFInd. with out your pages I wouldn't find my way in installing linux in uefi mode. I managed to dual boot windows 8 , debian and fedora.
my question:
I installed rEFInd from debian using the deb package, the package installed and is working perfectly.
but during installation the install script complained that I don't have the efi partition mounted. which it is.
it also complained that I am in secure boot mode where i certainly am not otherwise debian would not boot.
I ignored these two messages because it just works.
in the rEFInd menu there is also an entry to boot debian from the kernel image,other then debian grub. and it has the penguin icon. how did rEFInd discover that? reading rEFInd pages you say that rEFInd scans all the sub directories of the efi directory , and debian kernel is in debian's /boot folder. you also say that "The EFI stub loader
has been added as a feature to the 3.3.0 kernel." and debian wheezy is kernel 3.2.. something.
other then that rEFInd works great and is exactly what I wanted.
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The complaint about a non-mounted ESP can occur because of a bug in the install.sh script. I've fixed that locally and in git, and it will go out with the next update.
The notice about Secure Boot mode is because I don't know of a 100% reliable way to detect a boot in Secure Boot mode. I'm afraid that won't change unless/until I learn of such a test that I can implement in a bash script.
Current versions of rEFInd, or more precisely of its installation script, attempt to detect the filesystem used on /boot and install an EFI driver for that. They also generate a /boot/refind_linux.conf file with suitable boot options for directly booting the kernel. This is intended to simplify the setup on computers with kernels that include the EFI stub loader. This seems to have succeeded in your case. If the penguin-icon direct-boot options work in your case, then I expect that means that Debian has backported the EFI stub loader to its 3.2.x kernels. If those icons don't work, then it just means that the rEFInd features are working as intended, but your kernel lacks the EFI stub loader. You can remove those icons by deleting the EFI filesystem driver file or by commenting out the scan_all_linux_kernels options in refind.conf.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First I want to thank you Rod for all the pages you wrote and for rEFInd. with out your pages I wouldn't find my way in installing linux in uefi mode. I managed to dual boot windows 8 , debian and fedora.
my question:
I installed rEFInd from debian using the deb package, the package installed and is working perfectly.
but during installation the install script complained that I don't have the efi partition mounted. which it is.
it also complained that I am in secure boot mode where i certainly am not otherwise debian would not boot.
I ignored these two messages because it just works.
in the rEFInd menu there is also an entry to boot debian from the kernel image,other then debian grub. and it has the penguin icon. how did rEFInd discover that? reading rEFInd pages you say that rEFInd scans all the sub directories of the efi directory , and debian kernel is in debian's /boot folder. you also say that "The EFI stub loader
has been added as a feature to the 3.3.0 kernel." and debian wheezy is kernel 3.2.. something.
other then that rEFInd works great and is exactly what I wanted.
Thank you.
The complaint about a non-mounted ESP can occur because of a bug in the
install.sh
script. I've fixed that locally and in git, and it will go out with the next update.The notice about Secure Boot mode is because I don't know of a 100% reliable way to detect a boot in Secure Boot mode. I'm afraid that won't change unless/until I learn of such a test that I can implement in a bash script.
Current versions of rEFInd, or more precisely of its installation script, attempt to detect the filesystem used on
/boot
and install an EFI driver for that. They also generate a/boot/refind_linux.conf
file with suitable boot options for directly booting the kernel. This is intended to simplify the setup on computers with kernels that include the EFI stub loader. This seems to have succeeded in your case. If the penguin-icon direct-boot options work in your case, then I expect that means that Debian has backported the EFI stub loader to its 3.2.x kernels. If those icons don't work, then it just means that the rEFInd features are working as intended, but your kernel lacks the EFI stub loader. You can remove those icons by deleting the EFI filesystem driver file or by commenting out thescan_all_linux_kernels
options inrefind.conf
.