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