amicose wrote:The only thing that worries me is Grub. When I switch the computer on or wake it form hibernate, 9 times out of 10 grub doesn't load properly. I see a portion of the full grub screen, which can by anything from just the text 'Linux M' to my full range of boot options and a fraction of the last sentence (something like 'Automatic boot in 7 seco') - in any case, the text is curtailed and I have to keep powering the computer off and on until it loads properly. Anyone had the same problem?
This might be a sign of flaky hardware; however, it could also be a GRUB bug. Although the 2.0 release seems to be more reliable than the earlier 1.9x releases (which were bug-fests), GRUB 2 can still be a bit flaky sometimes.
I recommend you try another EFI boot loader. The easiest to install is probably my rEFInd, which you can set up just by installing the Debian package, at least if your EFI works correctly. (On some computers, you may need to jump through some extra hoops.) If rEFInd isn't to your liking, check out ELILO or Fedora's patched GRUB Legacy -- see my page on EFI boot loaders for details.
amicose wrote:Thanks! Just got round to actually testing this out. Installing Refind was no problem at all, however in combination with the grub installed via the method on this thread, any option I select with Refind loads Grub 2! This might be because my EFI is on sda2. Could I avoid this by running the installation manually?
amicose wrote:Both Grub and Refind bring up the bkpbootmgfw.efi (or however it's called), which does boot straight into Windows. Selecting Mint however still boots into Grub- how can I get it to boot directly into Mint?
And will I need to reinstall Refind or will it automatically scan for all valid efi files?
Also it would be good to change the resolution of the Refind screen (it's in 800x600 or near enough, whch doesn't even display all the text) - where do I find the refind.conf file?
OK, I found the /boot/efi/EFI/Microsoft/Boot directory. But - I still don't know how to move/rename files in Linux for which I don't have permissions!
You've probably run Ubuntu's "Boot Repair" tool, which is a little over-enthusiastic about applying a hackish fix to a relatively rare problem. The solution is to look at the files in /boot/efi/EFI/Microsoft/Boot. One will be called bootmgfw.efi, which should be the Windows boot loader; but after running Boot Repair, it will probably be a copy of GRUB. The real Windows boot loader will be called something else -- probably bootmgfw.efi.bkp, bkpbootmgfw.efi, bootmgfw.efi.grb, or something similar. You need to rename the files so that the Windows boot loader is called bootmgfw.efi. You should then be able to launch Windows using the Windows icon in rEFInd.
Users browsing this forum: coffee412 and 10 guests