https://bugzilla.novell.com/show_bug.cgi?id=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c4 --- Comment #4 from Michael Chang 2013-08-22 06:28:42 UTC --- It seems like was_proposed is *always* true for autoyast installation thus the proposed value is never processed .. 2013-08-14 14:08:46 <1> kimball.arch.suse.de(3689) [Ruby] modules/BootGRUB2.rb:159 calling Propose with was_proposed set is really bogus, clear it to force a re-propose The proposed value here is the imported autoyast settings. I don't know, as that was_proposed check is needed for DVD installation to protect custom settings from being overwritten by default proposed settings erroneously. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c6 --- Comment #6 from Michael Chang 2013-08-22 06:39:10 UTC --- Created an attachment (id=553628) --> (http://bugzilla.novell.com/attachment.cgi?id=553628) DUD with yast2 and perl bootloader to test Rick, please help to test this DUD to see if the problem persists. Thanks a lot. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c8 --- Comment #8 from Thomas Renninger 2013-08-22 11:26:27 UTC --- Unfortunately this did not work. The DUD was taken, serial output from first boot: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready Loading ftp://10.121.0.100/dud/bug-834854_ybl-pbl-bnc834854.dud - 100% Driver Update: perl-Bootloader-0.708-98.1.x86_64.rpm Driver Update: yast2-bootloader-3.0.2-4.1.x86_64.rpm Driver Updates added: perl-Bootloader-0.708-98.1.x86_64.rpm yast2-bootloader-3.0.2-4.1.x86_64.rpm ----------- But in 2nd stage the boot parameters were gone again. I double checked for the messages in the patch. I had to: cd /var/log/YaST2/ gunzip y2log-1.gz and there found that the + if Mode.autoinst code path has not been taken: grep "calling Propose with was_proposed" /var/log/YaST2/* /var/log/YaST2/y2log-1:2013-08-22 12:33:21 <1> haldus.arch.suse.de(6963) [Ruby] modules/BootGRUB2EFI.rb:128 calling Propose with was_proposed set is really bogus, clear it to force a re-propose The expected message: "autoinst mode we ignore meaningless was_proposed as it always set" did not show up. So either the patch was not in the rpm, for some reason the dud rpms were not taken or the patch does not work as expected. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c10 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com InfoProvider|mchang@suse.com |jreidinger@suse.com --- Comment #10 from Thomas Renninger 2013-08-22 14:31:36 UTC --- Ok, I got it...: There is: BootGRUB2.rb and BootGRUB2EFI.rb both have nearly the same code. At least these code parts are identical. I did an EFI installation... I adopted above patch to BootGRUB2EFI.rb and the boot parameters are saved and used in second stage as well. Josef: Would it be doable to merge BootGRUB2.rb and BootGRUB2EFI.rb files? That would avoid such issues in the future. I could imagine there were already other changes/fixes put into the one file, but were forgotten to be put into the other one as well. I will attach a diff between the files. Most is grub2 vs grub2efi strings, some comments and some code which looks like it should be double checked whether it should show up in the other file as well... -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c12 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|jreidinger@suse.com |snwint@suse.com --- Comment #12 from Josef Reidinger 2013-08-22 14:53:45 UTC --- Thomas - It can be possible to merge it, but maintainer of such code is Stephen Winterfeld, that should decide if it is better to split it or keep separated. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c14 --- Comment #14 from Michael Chang 2013-08-23 05:32:53 UTC --- Hi Thomas, Thanks a lot for heading this up. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c16 --- Comment #16 from Josef Reidinger 2013-08-23 08:16:53 UTC --- (In reply to comment #15)

I agree we should merge the code, because we might have to add power pc (open firmware) and s390 support, having separated source for each of them makes no sense for the idea of a unified loader.

I agree. Original idea is to have split for each bootloader type ( elili, zipl, grub, plilo etc.) because it have different features, different options and need different setup. But if we have one unified loader with unified config, then it doesn't make sense to have it separately. -- 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=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c23 Julian Wolf changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #23 from Julian Wolf 2013-09-02 09:22:19 UTC --- Tested with factory on ain and tyne and seems to work now. -- 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.