| Summary: | Grub2 menu options vanish in MCC, ergo uneditable | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | DariuszSki <linuxstuff> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | zen25000 |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
DariuszSki
2013-04-10 15:20:27 CEST
(In reply to DariuszSki from comment #0) > Description of problem: > > When you are doing anything with the MCC GUI to the boot, like adding or > changing the boot options for any kernel installed, on next reboot, the MCC > boot options are completely blank, although there is no problem with grub2 > itself as the options are saved. However, this means that if you need to > change options in MCC, you can't. You can only add a new entry, which will > be available on next reboot to grub2, but again, in MCC it will be > completely blank list of boot options / kernels. This is expected at the moment - see errata https://wiki.mageia.org/en/Mageia_3_Errata#Grub2 > > At the grub2 boot menu, you can press "e" to edit the command lines, but it > does not save anything. This is correct operation the 'e' option only applies to the current boot. You can install "grub_customizer" when in KDE, but > as there is nothing displayed in MCC for entries, the customizer also > displays nothing that can be saved (produces error) Please file a separate bug against grub customizer > so each boot needs to > edit the command line, (for me to add nokmsboot to stop Nouveau driver > loading). > This is not necessary - see errata and https://bugs.mageia.org/show_bug.cgi?id=8540 which is now fixed. > This is not similar to Bug 8871 (other than entries not displaying in MCC). > > > Version-Release number of selected component (if applicable): > Mageia 3, Beta4. > > Steps to Reproduce: > Update a kernel, or attemt to edit a boot menu entry in MCC. Please attach copies of /boot/grub2/grub.cfg made before and after a kernel update. Thanks for taking the time to report this. Keywords:
(none) =>
NEEDINFO I edited the file /boot.grub2/grub.cfg to add "nokmsboot" and the system now boots normally with the nVidia driver. For reference to others that may find this on online articles, don't run "update-grub" or the settings you just entered in grub.cfg will be wiped. Found that out after many reboots. Will look into grub-optimizer more for a seperate bug. And will look into Kernel updates / MCC entries problem for seperate bug report if I can find more information on it. Closing this bug report. Status:
NEW =>
RESOLVED (In reply to DariuszSki from comment #2) > I edited the file /boot.grub2/grub.cfg to add "nokmsboot" and the system now > boots normally with the nVidia driver. This is not the way to do it. Please read the errata as indicated above. The change should be made in /etc/default/grub followed by running update grub. > > For reference to others that may find this on online articles, don't run > "update-grub" or the settings you just entered in grub.cfg will be wiped. > Found that out after many reboots. Exactly why you should not edit /boot/grub2/grub.cfg > > Will look into grub-optimizer more for a seperate bug. And will look into > Kernel updates / MCC entries problem for seperate bug report if I can find > more information on it. There are no issues currently known with regard to kernel updates and grub2. Menu modifications via mcc are currently not supported, however there are various methods of doing this manually as indicated in the errata. > Closing this bug report. |