Bug 133920 - Can´t install bootloader to partition
Summary: Can´t install bootloader to partition
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: PC Other
: P4 - Low : Minor
Target Milestone: ---
Assignee: Olaf Dabrunz
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-15 21:26 UTC by Michael Stather
Modified: 2006-11-16 16:10 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
YaST2 logs (852.16 KB, application/x-compressed-tar)
2005-11-15 21:26 UTC, Michael Stather 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Stather 2005-11-15 21:26:17 UTC 
When I set YaST2 to install the bootloader (grub) into a partition instead of the MBR, if I exit the module the boot loader seems to be installed (no error messages are printed) but when I re-enter the module all the settings which I´ve made are lost, so the target is set to "MBR" again. Also the bootloader is installed in the MBR. I´ve attached the YaST2 logs.
Comment 1 Michael Stather 2005-11-15 21:26:45 UTC 
Created attachment 57422 [details]
YaST2 logs
Comment 2 Michael Gross 2005-11-17 13:58:30 UTC 
I was able to reproduce this. Jiri: Please look into it.
Comment 3 Jiri Srain 2005-12-15 12:08:54 UTC 
Reasigning to new maintainer
Comment 4 Torsten Duwe 2006-04-21 14:51:35 UTC 
According to the logs the boot loader _is_ installed into the partition, making this issue rather cosmetic. Did you verify the MBR contents?
Comment 5 Matej Horvath 2006-11-16 13:52:19 UTC 
The reporter isn't responding for a long time, marking as Invalid.
Comment 6 Michael Stather 2006-11-16 14:33:21 UTC 
And why? I reported this bug, nobody cares and now it´s closed.
Please fix(!) bugs instead of ignoring them
Comment 7 Andreas Jaeger 2006-11-16 16:10:59 UTC 
Michael, this bug was for six months in the state NEEDINFO and you did not answer the question raised by Torsten in comment #4.

It's you that ignored the question.  

According to #4: Looking at the logs files there does not seem such a bug as you reported.