Originally Posted By: uc50ic4more
- The Mint folks - a very small global team led by one dude who I do not think makes his living with this - are all volunteers and I don't think this project has much of a budget
- For *some* reason, the Mint admins have chosen not to, or are otherwise unable to employ Canonical's signing certificate for Secure Boot
Yes. Mint 15, I think it was, worked with Ubuntu's certificate. After that, no dice. That being said, they should try to play with secure boot updates as little as possible to avoid throwing a curveball at their users. I know what to do if my system comes up straight to Windows without a grub screen after a strange secure boot update. Others may not.
Sierra048: That's a fairly easy fix, if it's what I think it is. What are you seeing when you run:
Code:
sudo efibootmgr
I see this:
Code:
BootCurrent: 0003
Timeout: 2 seconds
BootOrder: 0003,0001,0002,000E,0009,000A,0000,000F,000B,000C
Boot0000* Windows Boot Manager
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0003* ubuntu
Boot0009* CD/DVD Drive
Boot000A* USB Floppy/CD
Boot000B* Hard Drive
Boot000C* Realtek PXE B03 D00
Boot000E* ATAPI CD-ROM Drive
Boot000F* ubuntu
Yes, it's says Ubuntu, but it's Mint. Basically, that's telling me that it starts with 0003 (Mint), then tries 0001 (CD), and so forth. The important thing is that 0003, in my case, is first, which brings up the Grub menu. If you're having the Windows Boot Manager (in my case 0000) as first in your BootOrder, it'll just go into Windows automatically. You can also use the efibootmgr command (type man efibootmgr for some assistance from a command line, or we can help you here, too) to change that order, if it's the problem.
As for running Mint straight and wiping out Windows, I've done it before, and quite happily, to be honest. If you have no need of Windows, it's a good solution. On occasion, I play some Windows games. If it wasn't for that, the Windows partition would have been long gone on this box.