Description of problem: booting up older kernel (vmlinuz) requires "nokmsboot" to enable booting whereas booting up latest kernel (vmlinuz-desktop) does not require "nokmsboot" Version-Release number of selected component (if applicable): How reproducible: modifying grub or grub2 menu entry in the kernel/linux and initrd lines to include/exclude "nokmsboot" will illustrate the issue. Steps to Reproduce: 1. 2. 3.
are both grub2 and grub installed ? seems a dups see https://bugs.mageia.org/show_bug.cgi?id=8463#c9
Keywords: (none) => NEEDINFO
Only grub2 is installed. Doesn't appear to be a duplicate of 8463 (s-link not pointing to latest kernel). This report (8545) is about requiring "nokmsboot" when booting to older kernel. Follow up 2 further points o labelling of s-links (vmlinuz, vmlinuz-desktop) is misleading. (vmlinuz-desktop as opposed to vmlinuz-server?) why not just use vmlinuz and vmlinuz-old? o why have 2 folders (grub and grub2)? only one instance of grub can/should be installed.
well the other bug updates simlink and grub (and so the options) if you use grub2 ok. but please add more details, I don't see where is the issue. for your question, I guess it's historical choice for vmlinuz and packaging choice for grub2
/boot/grub is for legacy grub /boot/grub2 is for grub2 the symlinks in /boot is for those that want to have both -desktop* and -server kernels installed and keeping both selectable and pointing on latest installed one at all time.
CC: (none) => tmb
The main issue... <quote>the symlinks in /boot is for those that want to have both -desktop* and -server kernels installed and keeping both selectable and pointing .....</quote> Ah...does it mean that vmlinuz-3.7.1-desktop-1.mga3 and vmlinuz-3.7.0-desktop-1.mga3 are exactly the same kernel except that one is for desktop and the other for server (not needing dkms modules)? If that is not the case, the issue remains that dkms modules do not apply for older kernel (and should). Not the issue..but... <quote> /boot/grub is for legacy grub /boot/grub2 is for grub2 </quote> Understand. Just saying there should/can be only one instance of grub, hence only one /grub directory, just like one command should apply, not update-grub2, mkconfig2, grub2-install, etc...and one 'consistent' simlink labelling convention (if that applies). Thanks, Manuel and Thomas. I am happy Mageia finally uses grub2. Hope I can help more - and not be a hindrance.. :) Happy New Year!
we will likely not yet grub2, but this should be fixed. if not please reopen
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME