https://bugzilla.novell.com/show_bug.cgi?id=228806 ------- Comment #2 from admin@eregion.de 2006-12-16 03:36 MST ------- Created an attachment (id=109984) --> (https://bugzilla.novell.com/attachment.cgi?id=109984&action=view) yast logs -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #4 from admin@eregion.de 2006-12-17 14:36 MST ------- my guess is, the problem orginated in the fact that the upgrade abortet half way through, due to a faulty dvd (strange enough, k3b verify after burn AND media check in yast thought it was ok...), so i had to continue the upgrade by hand. I did a clean re-install today (thankfully i DO change the suse default partition layout, so i have every place where i keep stuff thats not in rpm packages on separate partitions), and the machine is running just fine. Much faster than 10.1, too (might be because i showed zen the way towards /dev/null...). That still doesn't change the fact that i was NOT able to fix the broken bootloader in any way available (see bug #228813), so i'm still interested if you guys manage to find the reason for the broken bootloader. -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |odabrunz@novell.com |screening@forge.provo.novell| |.com | Status|REOPENED |NEW -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 ------- Comment #7 from martin.ament@gmx.de 2007-01-07 07:02 MST ------- Hi, I think there is a problem with the Yastmodul for configuring grub. I have Opensuse 10.2 and Windows XP (Second master, second partition) If I configure with the Yastmodul the Config works for Linux. But if i boot one time into windows. The bootloader isn't working anymore from the mbr. If i use a disk for booting everything works fine. My Partitions: ---- /dev/hdc2 7,9G 3,8G 3,7G 51% / udev 506M 144K 506M 1% /dev /dev/hdc3 13G 3,6G 8,7G 29% /home /dev/hdd1 21G 16G 4,6G 78% /mnt/hdd1 /dev/hdc5 2,0G 65M 1,9G 4% /mnt/lin1 /dev/hdc6 2,0G 65M 1,9G 4% /mnt/lin2 /dev/sda2 149G 109G 40G 73% /mnt/sda2 /dev/hdc7 13G 11G 1,3G 90% /usr/local /dev/hdd2 14G 12G 2,3G 85% /windows/C -- Default by Yast, but not working for a windows on second hd -- menu.lst title WindowsXP rootnoverify (hd0,0) makeactive chainloader (hd1,1)+1 ---- Modified like described in Grubdocu, working, but only one time --- menu.lst title WindowsXP rootnoverify (hd0,0) map (hd0) (hd1) map (hd1) (hd0) makeactive chainloader (hd1,1)+1 ---- I checked this, and i changed the entry for root and chainloader and now everything is working fine. -- menu.lst title WindowsXP rootnoverify (hd1,1) -- Windows root map (hd0) (hd1) map (hd1) (hd0) makeactive chainloader +1 -- NO hd information ---- I think the problem is, that the yastmodul assumes windows being on the first partition of the first hd, even if i changed the hd to /dev/hdd2 Is it possible to change the modul so it a) make the right entry for the root-Part? (hd1,1) in my case b) checking if the first hd is used, if that is not the case adding the map entries? Thanks -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|admin@eregion.de |mhorvath@novell.com ------- Comment #8 from admin@eregion.de 2007-01-10 02:57 MST ------- WHICH info is needed from me? besides, the stuff in comment #7 does not apply to my systems, both have only one harddisk, both have more or less the same partition scheme (windows on first primary partition on first harddisk, linux partitions all logicals insode one secondary partition on first harddisk), and above all, my fault situation was not "windows doesnt boot anymore" but "grub doesnt work at all, instead it reboots". -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 ------- Comment #10 from stefan.fent@novell.com 2007-02-14 02:48 MST ------- Can you please try and disable the graphical stuff in the bootloader configuration? (Comment out gfxmenu.... in /boot/grub/menu.lst) To Comment #7: Martin, we'll try to integrate this mapping mechanism into 10.3. But this is an enhancement and completely unrelated here -- 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, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=228806 odabrunz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|mhorvath@novell.com | Resolution| |DUPLICATE ------- Comment #12 from odabrunz@novell.com 2007-02-15 11:23 MST ------- The original problem here is about grub looping during boot. The original commenter cannot reproducce it anymore, but comment #9 suggests it could be related to this bug: https://bugzilla.novell.com/show_bug.cgi?id=231104 Setting this bug as a duplicate of bug #231104. Comment #7 suggests to handle booting Windows from the second drive by remapping the drive with grub. Feature #301994 has been opened for this. *** This bug has been marked as a duplicate of bug 231104 *** -- 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, or are watching someone who is.