piovrauz wrote:With MS "system file protection" I was referring to the fact that windows "protects" its system files from change.
So my point is: does it consider the efi partition part of that? Because if it does it may cause problem.
AFAIK, Windows doesn't do this as a matter of course, although I've heard of systems on which it's difficult to write to the ESP. At least some of these cases are probably caused by the new Windows 8 "fast startup" feature, which [url=http://www.eightforums.com/tutorials/6320-fast-startup-turn-off-windows-8-a.html]should be disabled in Windows 8[/url] when dual-booting with Linux (or any other OS). It's possible that a few of these cases have some other cause, but the problem reports I've seen are ambiguous enough that I can't really say for sure.
Secureboot is not a problem, this laptop can sign as secure the .efi one wants, so there's no need to turn it off, if you do that you lose win8.
The ability to register any .efi as a valid file sounds very handy, and is similar to what PreLoader does. (I suppose it's even possible that this feature is built on PreLoader, just built into the firmware.) Turning off Secure Boot should
not cause Windows to fail to boot. If that's the result, then chances are you've either accidentally changed another feature (like switched from EFI-mode to BIOS/CSM/legacy-mode booting) or some other factor is preventing Windows from booting (like a GRUB bug, if Windows is being booted via GRUB).
nobugs wrote:Regarding rEFInd, boots fine now I have changed the boot order, with options in order below. I don't know how to change their order though, as I would like Mint as the first option not Windows. Mint would then boot up unattended.
These are the options in order:-
MS logo: Boot Microsoft EFI boot (boot repair backup) from ESP.
MS logo: Boot supposed Microsoft EFI boot (probably GRUB) from ESP.
3colouredcubes: Boot EFI\boot\bkpbootx64.efi from ESP.
MintLogo: Boot EFI\linuxmint\grubx64.efi from ESP.
3colouredcubes: Boot fallback boot loader from ESP.
UbuntoLogo: Boot boot\vmlinuz-3.8.0-19-generic from 36 Gib Ext4 volume. (Mint15 install).
The presence of two MS logo items indicates that Boot Repair has been run with the option to backup and rename the Windows boot loader files. You can fix the duplication either by re-running Boot Repair and selecting the advanced option to restore the backups; or by typing "sudo mv /boot/efi/EFI/Microsoft/Boot/bkpbootmgfw.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi" in Linux.
The EFI\boot\bkpbootx64.efi option probably either does nothing or is a duplicate of something else. You can probably safely delete it by typing "sudo rm /boot/efi/EFI/boot/bkpbootx64.efi" in Linux. The "fallback boot loader" is EFI/boot/bootx64.efi on the ESP (/boot/efi/EFI/boot/bootx64.efi from Linux). It's usually a duplicate of something else, and when it is, rEFInd normally hides it from view. If it's not a duplicate and is not being hidden but you want to hide it, try editing /boot/efi/EFI/refind/refind.conf and adding the line "dont_scan_dirs ESP:/EFI/BOOT/bootx64.efi".
Your first (Mint logo) Linux entry boots GRUB. Your second (Ubuntu logo) Linux entry boots the Linux kernel directly. If they both work, I recommend keeping both of them, since that will provide you with a fallback in case one of them stops working in the future. You can, however, remove either of them by using the dont_scan_volumes, dont_scan_dirs, or dont_scan_files options in refind.conf; or you can comment out the scan_all_linux_kernels options to remove the direct-kernel option. If you want to change the Ubuntu logo to a Mint logo, you can type "sudo cp /boot/efi/EFI/refind/icons/os_linuxmint.icns /.VolumeIcon.icns". (Several other ways to alter the icon are covered in [url=http://www.rodsbooks.com/refind/configfile.html#hiding]the rEFInd documentation[/url].)
You can set whatever boot option you want as the default by using the "default_selection" item in refind.conf. Be sure that line is uncommented and add any unique string from the option description as its option, as in:
This example sets the first item found that contains the string "vmlinuz" as the default.
piovrauz wrote:mint 15 can be installed in efi mode, but for mint 13/14 you need to use legacy mode, and after that give it a efi bootloader (for dualboot).
Mint 13 and 14
should install just fine in EFI mode, although they don't have any Secure Boot support, so they'd need to have Secure Boot disabled in order to work. I've installed several versions of Mint, I believe including both 13 and 14, directly in EFI mode.
nobugs wrote:Having got my machine booting both OS's thru rEFInd, decided to start from a bootable USB stick. Boots straight into Win8 and ignores the stick. Need to once again change UEFI to legacyOS mode.
If the USB flash drive has an EFI boot loader, rEFInd
should detect it by default;
however, this will work only if the firmware initializes USB devices. Many EFIs now do truncated or no USB initialization by default to speed up the boot process, so you might want to check your firmware settings to see if there's anything about USB initialization or a "fast boot" setting. If so, play with those settings. Also, in some cases USB devices might not be fully ready when rEFInd scans them. If this is the case, hitting Esc in rEFInd will cause it to re-scan for boot loaders, which may detect the USB drive.
If the USB flash drive does not have an EFI boot loader, but does have a BIOS boot loader, you can get rEFInd to detect it by editing refind.conf: Uncomment the "scanfor" line and ensure that "biosexternal" is among the options. Thereafter, rEFInd should scan for and detect BIOS-bootable external devices. A caveat: This feature requires a type of CSM that's accessible from rEFInd, and it requires that your CSM be active. If either of these conditions is not true, rEFInd will complain when it start up and you won't see any BIOS-bootable devices.
You might want to skim the [url=http://www.rodsbooks.com/refind/configfile.html]rEFInd configuration file documentation[/url] to learn more about its options. The defaults work well, but you can do a lot of fine-tuning and customization by editing refind.conf.