Open MCC>Boot>Setupt boot system : No entry corresponding to the different kernel available in /boot is displayed. No boot option is displayed for each kernel
What is the output of rpm -qa | grep grub and of rpm -qa | grep drakxtools
Keywords: (none) => NEEDINFOCC: (none) => marja11, thierry.vignaud, zen25000
Are you using grub2? If yes that's expected as grub2 auto generates its menu, so we cannot alter it.
$ rpm -qa | grep grub grub2-2.02-0.git10457.10.mga6 grub2-common-2.02-0.git10457.10.mga6 grub2-mageia-theme-2.02-0.git10457.10.mga6 grub-doc-0.97-43.mga6 $ rpm -qa | grep drakxtools drakxtools-backend-17.51-1.mga6 drakxtools-curses-17.51-1.mga6 drakxtools-17.51-1.mga6 > If yes that's expected as grub2 auto generates its menu, so we cannot alter it It's a problem now as we can't add/remove the boot options.
commit fbc399721879746f2cc69208dba3a42b290b0a7d Author: Thierry Vignaud <thierry.vignaud@...> Date: Sun Jul 17 10:35:09 2016 +0200 grub2: fix not being able to edit default cmdline Keep default append value (aka /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT into {default_append} variable) Always use the value passed as now write_grub2_sysconfig() is only called after having offered to display the default cmdline value On first run (during installer) or when migrating from grub-legacy or lilo, we get the first entry's parameters Thus resolving mga#18952 --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=fbc399721879746f2cc69208dba3a42b290b0a7d
Fixed
Status: NEW => RESOLVEDBlocks: (none) => 416Resolution: (none) => FIXED
*** Bug 18975 has been marked as a duplicate of this bug. ***
CC: (none) => max.augsburg