| Summary: | Installer didn't add other OS's grub2 to newly created grub1 configuration | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
| Component: | Installer | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | zen25000 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | report.bug | ||
|
Description
Piotr Mierzwinski
2015-06-22 12:15:33 CEST
Please attach the debug file /root/drakx/report.bug.xz that was created during installation so that we can investigate. I don't know if we detect grub2 bootloaders properly when using grub as a bootloader. Maybe in this case we should have selected grub2 by default. Keywords:
(none) =>
NEEDINFO Created attachment 6767 [details]
report.bug
Samuel Verschelde
2015-06-22 13:12:00 CEST
Keywords:
NEEDINFO =>
(none) (In reply to Samuel VERSCHELDE from comment #1) > Please attach the debug file /root/drakx/report.bug.xz that was created > during installation so that we can investigate. > > I don't know if we detect grub2 bootloaders properly when using grub as a > bootloader. Maybe in this case we should have selected grub2 by default. We have never added grub2 based systems to the legacy grub menu. I would recommend using "MCC->boot->Set Up Boot System" to change the bootloader to grub2 which should correctly detect and add the other operating systems to the grub2 boot menu. This used to be mentioned in the errata e.g. for Mageia 2 :- https://wiki.mageia.org/en/Mageia_2_Errata#Installing_Mageia_next_to_a_GRUB2_based_distribution AFAIK nothing has changed in this regard, except that we now have a fully integrated grub2 available. (In reply to Barry Jackson from comment #4) > This used to be mentioned in the errata e.g. for Mageia 2 :- > > https://wiki.mageia.org/en/ > Mageia_2_Errata#Installing_Mageia_next_to_a_GRUB2_based_distribution > > AFAIK nothing has changed in this regard, except that we now have a fully > integrated grub2 available. So we should propose grub2 as the default in such situations. (In reply to Samuel VERSCHELDE from comment #5) > So we should propose grub2 as the default in such situations. If that is possible, then yes that would be one solution. I've applied that solution (change boot loader from mcc) and now it works :). Kubuntu is visible in boot menu. And even all 3 Windows partitions. I'm not sure is this much usable (as I remember in grub1 was only one), and I think, this might be a bit confusing for beginners. I'm not sure is this configurable or not. Anyway "MCC->boot->Set Up Boot System" is definitely easiest way to grub2 based system were detected than way given in documentation linked in Errata (where is mentioned about manually way and use existing grub2). Big thanks. And one question on end. Why grub2 is not default boot manager in Mageia 5? Status:
NEW =>
RESOLVED (In reply to Piotr Mierzwinski from comment #7) >...And even all 3 Windows partitions. I'm not > sure is this much usable (as I remember in grub1 was only one), and I think, > this might be a bit confusing for beginners. I'm not sure is this > configurable or not. >..... To avoid displaying the unwanted Windows partitions you can add a line similar to this in /etc/default/grub :- GRUB_OS_PROBER_SKIP_LIST="84E06AADE49BED2A@/dev/sda1 1EE8AF3AE8AF0F59@/dev/sda3" Use your own UUIDs and devices of course. Run update-grub after making the change to /etc/default/grub. (In reply to Piotr Mierzwinski from comment #8) > And one question on end. Why grub2 is not default boot manager in Mageia 5? It was decided early on in the Mageia 5 development cycle that grub2 would not be the default bootloader, however it is default for UEFI installations. Re-opening for now as nothing has changed and this report is still valid. Status:
RESOLVED =>
REOPENED Thanks for hint. :). I've applied it and works fine (less mess in grub2 menu). BTW. Quite pretty font in menu. I think this (skipping hidden partition) should be implemented in installer grub2 program. Regular user don't want do this manually (and before dig in Internet, seeking for how to hide it) only would like to have one properly entry (referring to main Windows partition) in boot manger. Advanced user if will want see them then will cope with it. Windows hidden partition are properly marked (fdisk -l nicely show this), so I think there is no problem detect then. Of course this is only my suggestion with low priority, because Mageia 5 still is using grub in first version. > (In reply to Piotr Mierzwinski from comment #8) > > And one question on end. Why grub2 is not default boot manager in Mageia 5? > > It was decided early on in the Mageia 5 development cycle that grub2 would not > be the default bootloader, however it is default for UEFI installations. Was there any specific reason such decision? (unstable grub2?, not supporting something?) (In reply to Piotr Mierzwinski from comment #10) > Was there any specific reason such decision? (unstable grub2?, not > supporting something?) Yes, at that time grub2 was not properly supported by the Mageia installer or drak* tools - you can see the gradual integration develop right back from Mageia 2 by studying the tracker (bug #416) and it's dependant bugs. I've activated grub2 (using mcc) on my PC (previously I did it on my laptop), where I have legacy nvidia graphics card. And where I upgraded Mageia from version 5 rc to version 5 final release. I found some issue in integration of grub2. I had 3 kernels. Using rpmdrake I removed the oldest one (including devel, virtualbox and nvidia304 packages) after restart I noticed in advanced options of boot menu, that there persists entry referring to removed kernel. Why it has not removed? While in similar operation, if active was grub1 then boot menu was properly updated, which means removed entry referring to uninstalled kernel. I think, boot menu should not have no entries referring to removed kernels. (In reply to Piotr Mierzwinski from comment #12) > I've activated grub2 (using mcc) on my PC (previously I did it on my > laptop), where I have legacy nvidia graphics card. And where I upgraded > Mageia from version 5 rc to version 5 final release. > I found some issue in integration of grub2. > > I had 3 kernels. Using rpmdrake I removed the oldest one (including devel, > virtualbox and nvidia304 packages) after restart I noticed in advanced > options of boot menu, that there persists entry referring to removed kernel. > Why it has not removed? > While in similar operation, if active was grub1 then > boot menu was properly updated, which means removed entry referring to > uninstalled kernel. > I think, boot menu should not have no entries referring to removed kernels. Please open another bug report for this issue. Thanks for reporting. I think this should be closed as it was against grub legacy which has never supported automatic detection and inclusion of grub2 systems. So although valid from the reporters POV, it was easily resolved by the use of grub2. Closing as wontfix. Status:
REOPENED =>
RESOLVED |