https://bugzilla.novell.com/show_bug.cgi?id=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c1 --- Comment #1 from Stefan Dirsch 2008-09-02 09:26:23 MDT --- Created an attachment (id=236781) --> (https://bugzilla.novell.com/attachment.cgi?id=236781) yast.tar.bz2 -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c3 --- Comment #3 from Stefan Dirsch 2008-09-02 09:49:59 MDT --- # cat /etc/grub.conf setup --stage2=/boot/grub/stage2 --force-lba (hd0,1) (hd0,1) quit # fdisk -l Disk /dev/sda: 4034 MB, 4034838528 bytes 255 heads, 63 sectors/track, 490 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00010eca Device Boot Start End Blocks Id System /dev/sda1 1 64 514048+ 82 Linux swap / Solaris /dev/sda2 * 65 490 3421845 83 Linux The machine is currently available at 10.10.100.215. -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c5 --- Comment #5 from Stefan Dirsch 2008-09-03 02:21:38 MDT --- Created an attachment (id=237003) --> (https://bugzilla.novell.com/attachment.cgi?id=237003) menu.lst /boot/grub/menu.lst -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c7 --- Comment #7 from Stefan Dirsch 2008-09-04 08:53:53 MDT --- Unfortunately I needed to kill the 11.1 Alpha2 installation on this machine due to our Lenovo preload efforts. :-( -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c9 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |gekker@novell.com --- Comment #9 from Stefan Dirsch 2008-09-19 11:58:07 MDT --- Still the same issue with openSUSE 11.1 Beta1. :-( Gary, do you think this needs to be fixed for SLE11? -- 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=422157 User duwe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c10 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #10 from Torsten Duwe 2008-09-23 06:34:38 MDT --- What is supposed to be in the MBR? generic boot code -> autoyast problem special IBM/Lenovo voodoo -> Lenovo problem -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c12 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|duwe@novell.com |jsrain@novell.com Status|NEEDINFO |NEW Info Provider|sndirsch@novell.com | --- Comment #12 from Stefan Dirsch 2008-09-23 07:33:41 MDT --- Torsten figured out, that grub needs to be installed into MBR instead of active partition. So this is another IBM/Lenovo Thinkpad like exception. -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c14 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #14 from Jiri Srain 2008-09-24 02:49:54 MDT --- But if this is the way this bug can be solved, what prevents you from changing the bootloader location? How can we detect that we need to store GRUB to MBR? (sorry, I don't have such hardware available) -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c17 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical --- Comment #17 from Jiri Srain 2008-09-26 01:58:44 MDT --- According to the log, YaST found in MBR the generic code. As loader was installed to boot sector and proper partition activated, I don't see any reason why the system does not boot. Anyway, it is not a blocker, since workaround exists. -- 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=422157 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c20 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Alpha 2 |Beta 1 --- Comment #20 from Stefan Dirsch 2008-10-01 03:11:22 MDT --- This sounds like a WONTFIX to me. I won't complain if you resolve it with this resolution. -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c23 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |sndirsch@novell.com --- Comment #23 from Jiri Srain 2008-10-14 02:55:49 MDT --- I've looked at the logs once more, the only suspicious issue which I found was that YaST detected generic boot code in MBR (and thus didn't replace it with anything). This is correct behavior as long as the detection work properly (YaST checks for some strings, other parts of the sector could have been rewritten). Before first installation, was there any system installed? Would it be possible to retry installation and check that the "Put generic code to MBR" check-box is checked? -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c30 --- Comment #30 from Jiri Srain 2008-10-20 09:56:20 MDT --- Luckily it seems that the original MBR code kept backed-up by YaST. It looks like a valid MBR code, anyway, after putting it into MBR, the system stopped booting. A fresh installation with replacing MBR with generic code boots properly, but MBR is not detected as containing valid generic bootloader code then (the detection fails even on the code in /var/lib/boot/). We will need to figure out what the code which I got from the back-up is about to fix this issue IMO. -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c32 --- Comment #32 from Jiri Srain 2008-10-21 02:18:59 MDT --- Well, I see two possibilities: 1. Find out why the MBR code which was present didn't boot 2. Update the detection so that if the old code is detected, it is considered invalid/unbootable and replace it 1. is optimal solution IMO, but I'm not sure that it is doable. 2. should be pretty easy (we can even change the behavior to replace MBR contents if generic code is detected). I just cannot guess whether it has any impact on other operating systems :-/ -- 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=422157 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c34 --- Comment #34 from Jiri Srain 2008-10-21 02:21:58 MDT --- Created an attachment (id=246738) --> (https://bugzilla.novell.com/attachment.cgi?id=246738) MBR installed by YaST This one workd well, but the detection script does not recognize it as the generic bootloader code -- 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=422157 User duwe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c36 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|duwe@novell.com | --- Comment #36 from Torsten Duwe 2008-10-22 07:15:54 MDT --- Strange. The MBR code from #33 only differs from "our" MBR (at least the one I keep in my Export) only in one respect: it encodes "addr32 <sth> $0x<someval>,0x0(%e{s,d}i)" more efficiently into "addr32 <sth> $0x<someval>,(%e{s,d}i)", saving one byte of object code, twice. The rest of the binary diff results from that. In any case I see no additional functionality. Recommendation: since it does not work, just regard that code as invalid :-) -- 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=422157 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=422157#c38 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #38 from Jozef Uhliarik 2008-10-27 06:26:46 MDT --- done in yast2-bootloader 2.17.34 -- 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.