https://bugzilla.novell.com/show_bug.cgi?id=812266
https://bugzilla.novell.com/show_bug.cgi?id=812266#c11
--- Comment #11 from Neil Rickert 2013-06-03 22:38:52 UTC ---
I have a whole other bug report related to that - bug 822770
I don't see how it could affect GRUB_DISTRIBUTOR, because that has to be set
before anything is written to NVRAM.
Related to that kernel bug -- it's an example of why its a bad idea to be
reinstalling grub for every "mkinitrd". Every reinstall could do some churning
and fragmenting of the NVRAM space. With frequent kernel updates in
Tumbleweed, I am seeing many unnecessary reinstalls of grub, when running
"grub2-mkconfig" would be sufficient.
Here's the typical sequence:
Tumbleweed kernel update messes with NVRAM
Next boot, the firmware deletes the Windows boot entry.
Next Windows boot (still possible from the grub menu), Windows puts its boot
entry back with highest priority.
I have to then get into the BIOS settings and change the boot order before I
can boot opensuse.
If, instead, "grub2-mkconfig" were run, none of those problems would arise.
The system would just keep working as before, but using the newer kernel.
There are similar problems caused for people who use Windows boot manager to
boot linux.
--
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.