On Thu, 27 Aug 2015, Fernando Rodriguez wrote: > I use GRUB2 because my efi firmware (like most) is really buggy. > Changing the boot order doesn't work at all (neither on the menu nor > through efibootmgr), so I have to delete and recreate the entries in the > right order. What I did is create 2 efi entries, one for my main kernel > and one for grub2 and I added entries for all my secondary kernels and > windows on the grub2 menu.
I have a similar setup: an efi entry for my kernel and gummiboot instead of grub2. I would use the firmware boot selector for multibooting, but going there lengthens the boot by around 10 seconds (Lenovo notebook) which is too much for my liking. So instead I by default boot into gummiboot and from there I choose my kernel, separate grub2's from Fedora and Ubuntu, or FreeBSD. Everything is nice and fast that way. Fedora and Ubuntu manage their own grub configs on kernel updates and I don't have to mess with any boot loader configs myself. On Fri, 28 Aug 2015, Mick wrote: > Interesting ... here I had no such problems on an EUFI Asus MoBo. I > have a number of kernels (up to six last time I looked) and I can change > the boot order with 'efibootmgr -o <numberA>,<numberB>,...,<numberZ>' I have a MSI B85-G43 and I must say that thing is the worst when it comes to managing the UEFI boot order. It completely ignores the one set using `efibootmgr -o` and instead seems to keep track of the order in which entries are added. Half of the time it even ignores me selecting the EFI boot entry during boot and instead merrily continues to load what it considers to be the _first_ entry. So I just use grub2 there and everything is fine.