tom_byrne wrote:I managed to get Mint 14 running from disk on my NP550P7-S05UK laptop (details below) however the boot procedure is rather convoluted.
Just to clarify: By "...from disk...", I presume you mean that you've installed Mint so that you can dual-boot, albeit via the convoluted method you describe. If not, please elaborate.
I disabled Fast Boot and Secure Boot to install from DVD however after a reboot, instead of the grub loader I get a message to select suitable media and re-boot. (I think all this is "secure-boot-dysfunctionality").
No, if Secure Boot is disabled, then any problems you're having are unrelated to Secure Boot. I'm not 100% positive, but I suspect that disabling Fast Boot on your computer also enables BIOS-mode (aka legacy-mode or CSM) booting and gives it priority over EFI booting, and you don't have a BIOS-mode boot loader installed, hence the error message. In your situation, you should probably turn Secure Boot off but enable Fast Boot.
I can boot to Windows 8 by resetting the original BIOS settings however I noticed that with Secure Boot off I can interupt a boot using F4 (recovery).
I then cancel the recovery and select restart and then get the grub loader.
Again, I'm not 100% positive, but based on the symptoms you've described, I suspect you've got a broken firmware that insists on booting the Windows boot loader even if something else is set as the default. To test this hypothesis, please enter the following command in Linux:
- Code: Select all
sudo efibootmgr -v
This will produce information on the configured boot loaders, plus the order in which they're called ("BootOrder"). If there's no entry for Mint's GRUB (referencing grubx64.efi, IIRC), then my hypothesis could be wrong, and you need to use efibootmgr to add such an entry. If there is an entry for GRUB, though, and if it appears at the head of the BootOrder list, then my hypothesis is correct.
If my hypothesis is correct, there are several possible solutions:
- Run Ubuntu's Boot Repair tool, which performs some brute-force changes that should get GRUB running as the default. Specifically, it moves/renames the Windows boot loader, installs a copy of GRUB in its place, and reconfigures GRUB to launch Windows via the moved copy of the Windows boot loader. This is likely to be the simplest solution, but it could cause confusion or problems down the road.
- In Mint, move/rename /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi to another name/location. I recommend pushing it down to /boot/EFI/Microsoft/bootmgfw.efi. Then copy /boot/efi/EFI/linuxmint/grubx64.efi to /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi. With this change in place, GRUB should launch as the default boot loader; but you'll need to adjust your Windows entries in grub.cfg to refer to bootmgfw.efi in its new location. It's possible that update-grub will pick it up automatically, but I'm not sure of that. This procedure is similar in effect to the previous one, but the on-disk changes are a little less extreme and it obviously takes more manual tweaking.
- In Mint, install my rEFInd boot manager by installing the Debian package. Once that's done, try to reboot. If rEFInd comes up immediately, you're done. If it doesn't come up immediately (which is more likely, given the problem), reboot into Mint in whatever way you can and type "sudo mvrefind.sh /boot/efi/EFI/refind /boot/efi/EFI/Microsoft/Boot". This does something conceptually similar to the previous two fixes, but it sets up rEFInd as the default boot manager rather than GRUB. You can then boot Mint via rEFInd, either bypassing GRUB entirely or using GRUB as an intermediary, as you see fit.
viking777 wrote:Imho, the only chance you have with secure boot is to switch it off for approximately the next two years. Then switch it on again and see if anybody has got it to work by then.
Secure Boot is a nuisance, but it's not as bad as that. Some distributions (Ubuntu 12.10, Fedora 18, and a few more obscure ones to date) work with Secure Boot enabled in its default mode already. Any distribution, including Mint, can be made to work with some extra effort. See my page on the topic
for more information. Currently the extra effort required is well outside the comfort zone for less technically-inclined users, but as distributions adopt Secure Boot support, and as the tools improve, that will change. If the Mint developers don't have Secure Boot working with their next release, then they've got their heads buried in the sand.
tom_byrne wrote:I suppose Windows 8 requires secure boot to be on, so turning off SB in the BIOS effectively turns off W8
Why do people think this? It isn't true -- or at least, I've seen numerous reports of people switching off Secure Boot and continuing to be able to boot Windows 8. (I don't have a computer that shipped with Windows 8 with which to test.) Thus, if there is such a requirement, it must apply to only some installations.