https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.novell.com | |/show_bug.cgi?id=775778 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c2 --- Comment #2 from Tim Hardeck 2013-04-02 14:23:46 UTC --- Sure, after installation some parts of the file, like the GRUB_DISTRIBUTOR tag, still seem to be updated/replaced but the theme stays the same. So from my part I would consider this resolved. Thanks for fixing the issue. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c4 --- Comment #4 from Tim Hardeck 2013-04-02 17:03:27 UTC --- Not at all, from the Studio site it is fine, I just wanted to mention it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c6 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #6 from Neil Rickert 2013-06-01 19:23:49 UTC --- I found this bug in a search. I was about to report a similar problem (also with 13.1M1). First install - 32-bit. I changed the boot options from "resume=/some/path" to "noresume". On the installed system, it was still the original "resume=...". Incidentally, the change was because I am using randomly encrypted swap, so the resume won't work. Second install - also 32-bit. The same problem. Okay, neither is vital. I could edit "/etc/default/grub" after install, then rebuild "initrd" to fix it. Third install - 64-bit on a UEFI box. I changed the Distributor field in the installer boot options (from "openSUSE 13.1" to "openSUSE_alt 13.1". That did not take. The installer tried to use "opensuse" rather than "opensuse_alt". And that conflicted with another NVRAM entry. I finished up with a system that was not bootable. (I was able to rescue it). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c8 --- Comment #8 from Michael Chang 2013-06-03 01:15:42 UTC --- Hi Neil, For #1 #2 .. Are they regression to 12.3 ? .. Hm .. if regression happens, this one indeed a related suspicious patch.. :( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c10 --- Comment #10 from Michael Chang 2013-06-03 22:04:57 UTC --- Neil, The GRUB_DISTRIBUTOR could be affected by a kernel bug [1], could you please help to check your kernel outputs any suspicious message like this ? [ 169.877879] efivars: maxsize=0 [ 169.877885] efivars: active_available=58354 [ 169.877888] efivars: size=112 [ 169.877890] efivars: storeage_size=65536 [ 170.210621] efivars: maxsize=0 [ 170.210622] efivars: active_available=58354 [ 170.210623] efivars: size=26 [ 170.210624] efivars: storeage_size=65536 [ 170.210647] efivars: set_variable() failed: status=8000000000000009 If you frequently update your boot variable, this bug could happen if garbage collecting not triggered somehow according to the criteria of firmware. [1] https://bugzilla.kernel.org/show_bug.cgi?id=55471 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c12 --- Comment #12 from Michael Chang 2013-06-04 00:45:47 UTC --- "update-bootloader --refresh" in it's man page --refresh activate the new config e.g. write boot loader to disk are come from the old age of lilo which requires reinstall bootloader each time you update a config. I did have a intention to fix that but the odd is that we cannot break lilo (although it's flagged as unsupported there's people still using it). We can proceed by introducing a new --refresh-config and we patch every package other than grub2 that calls "update-bootloader --refresh" in their scriplet to check the loader type and switch accordingly .. if grub2 update-bootloader --refresh-config else update-bootloader --refresh fi [ don't touch grub unless anyone complain about it ] Meanwhile, I'm downloading the 13.1 M1 image to check this regression or not. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c14 --- Comment #14 from Andrey Borzenkov 2013-06-04 00:59:14 UTC --- (In reply to comment #12)

We can proceed by introducing a new --refresh-config

Well, forcible reinstallation of bootloader was itself added as result of other bug reports Fri Apr 27 12:06:09 CEST 2012 - mchang@suse.de - fix after grub2 package update, the system become unbootable. (bnc#758570) And if (defined $oper{refresh}) { # Always set $avoid_init=0 to guarentee bootloader installed (bnc#759224) my $ret = UpdateBootloader(0); exit 1 if ( !$ret ); } So the first question is - are conditions in these bug reports still apply? Or was it just papering over real problems in the first place? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c16 --- Comment #16 from Michael Chang 2013-06-04 02:32:34 UTC --- Btw .. that change was actually an revert commit of my failure attempt .. that stupid comment is somehow reflects my bad mood but not the fact. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c18 --- Comment #18 from Michael Chang 2013-06-04 03:20:58 UTC --- Thanks. For grub2 we now change to --refresh (== --refresh-config) : only update config --refresh-config : only update config --reinstall : only install bootloader This way we can avoid to change many packages but only grub2 to call update-bootloader --reinstall in addition to --refresh. update-bootloader --refresh && update-bootloader --reinstall || true -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c20 --- Comment #20 from Neil Rickert 2013-06-04 16:54:28 UTC --- Michael Chang - comment 12

are come from the old age of lilo which requires reinstall bootloader each time you update a config.

I did use lilo for many years -- approx 1995-2006. And I had to frequently reinstall lilo for just about anything. However, since suse 10.1 through opensuse 12.1, I used grub legacy, which was never unnecessarily reinstalled. It seemed to work well without any reinstall (just an update of menu.lst). I have also experimented with Mint and Fedora, which seem to manage without a grub2 reinstall. Andrey mentioned that the change originated with bug 758570. However, I see that was for an update to grub2 itself. It makes sense to reinstall when grub2 is updated. And maybe updating the boot loader with Yast should reinstall, or at least have a reinstall option. But it does not make sense to reinstall grub whenever a kernel is updated or when some other software update requires initrd to be rebuilt - updating "grub.cfg" should be sufficient in those cases. I can manage either way. But my concern is for non-technical users who have trouble coping with the side-effects of grub reinstall. Many want to leave their system booting Windows by default, and accessing linux via the Windows boot manager. That breaks whenever grub is reinstalled. And then there are the problems of getting a good boot procedure for UEFI, and having to redo that for every update. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c22 --- Comment #22 from Michael Chang 2013-06-06 05:12:10 UTC --- (In reply to comment #19)

update-bootloader --refresh --reinstall || true?

When posting the command I'm a bit not certain update-bootloader could handle more than one command at a time, since it can do that I think yours is better. Now the problem is that I found no easy way to implement pure reinstall without touching refreshing config. The avoid_init=(0|1) will either update config only or performing both reinstall and renew the config. Therefore a naming like reinit could be more suitable. It now looks like --refresh : update config (avoid_init=1) --reinit : update config and reintall (avoid_init=0) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c24 --- Comment #24 from Andrey Borzenkov 2013-06-06 10:45:08 UTC --- (In reply to comment #23)

And the other patch to deal with the grub2 reintall problem

https://github.com/WenhuaChang/perl-bootloader/commit/7f907101c08eecb34594a0...

Please, update also POD ... --reinit is missing. --><-- operation is one of --add, --remove or --refresh. --><-- I think it needs clarification to explain difference between --refresh and --reinit. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c26 --- Comment #26 from Neil Rickert 2013-06-16 11:37:40 UTC --- Update for 13.1 Milestone 2. My change from "resume=/dev/mapper/cr_swap" to "noresume" worked. My change of Distributor from "openSUSE 13.1" to "openSUSE_alt 13.1" was ignored. Later, running the installed system, I used Yast --> Bootloader, and again tried to change the Distributor field. It was ignored again. Manually editing "/etc/default/grub" seems to be the only way to change it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=812266 https://bugzilla.novell.com/show_bug.cgi?id=812266#c27 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #27 from Michael Chang 2013-09-27 09:49:47 UTC --- This bug report is intended to fix the SUSE studio team's problem, that is be able to change the kernel append in it's most part. (And Tim has acked it in comment#4). As I mentioned in comment#3, to meet your requirement in last comment may have to bring more changes and is out of scope of my intention (wrt this bug ..). I set this one to be resolved fixed and you can open new one for your problem. Thanks for your help. -- 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.