https://bugzilla.novell.com/show_bug.cgi?id=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c8 --- Comment #8 from Thomas Renninger <trenn@suse.com> 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.