Mailinglist Archive: opensuse-bugs (2746 mails)

< Previous Next >
[Bug 822770] Install of grub2-efi failed

https://bugzilla.novell.com/show_bug.cgi?id=822770

https://bugzilla.novell.com/show_bug.cgi?id=822770#c25


Neil Rickert <nrickert@xxxxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|nrickert@xxxxxxxxxxxxx |

--- Comment #25 from Neil Rickert <nrickert@xxxxxxxxxxxxx> 2013-06-03 13:50:24
UTC ---
Created an attachment (id=542383)
--> (http://bugzilla.novell.com/attachment.cgi?id=542383)
Transcript with modified "efibootmgr"

This time the command worked. So I guess you won't get the extra info.

I'm getting the impression that the problem is fragmentation in the NVRAM space
causing incorrect estimates of space allowed (See that link I provided in a
recent comment).

I renamed my other install -- the one using /dev/sdb1 for ESP -- so that it is
now called "tumbleweed-secureboot" instead of "opensuse-secureboot". That a
preemptive action to prevent name conflicts when a future install fails to
honor the Distributor definition. The effect of that, and other changes, may
have reorganize NVRAM, reducing the fragmentation.

You may also note that, after the install, I did:
efibootmgr -o 3,0
That's because those (tumbleweed and Windows) are the two entries I want to
keep. (If I don't keep Windows, then Windows will reinstall it and mess up my
boot order).

I followed that with
efibootmgr -n 4
which makes entry 4 (the new opensuse_alt-secureboot) the next boot target.
The effect on my BIOS is that it will not delete entry 4 (at least for now),
since it will next boot from that. Otherwise it would have deleted it on the
next boot.

Those are there mostly to illustrate how my BIOS behaves in limiting to one
boot entry per ESP. I guess this is better than what Will Honea is describing
for HP, with it overfilling NVRAM.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References