On Thu, May 23, 2019 at 12:55 AM Stephen Morris <samorris@xxxxxxxxxxxxxxx> wrote: > > I have upgraded from F29 to F30 via the recommenced dnf method. I > have Fedora running in a vm under vmware player. Grub2-mkconfig and > grub2-install no longer seem to generate the grub menu as they did > under F29, the menu seems to be that generated by grubby (it could > be that turning off the suppression of sub-menu creation is now > being ignored). Looking at /boot/grub2/grub.cfg I cannot see any > references in there to kernels, so I have attached the file for > reference. Am I missing something or is the functionality now > different, /boot/grub2/grub.cfg is where I have always written the > grub.cfg via this process? You have insmod blscfg blscfg on lines 128-129. So grub's setting up a generic BLS grub.cfg and you should have your kernel specifications in "/boot/loader/entries/*.conf". Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system? IIRC, the common bugs page recommends "configfile /boot/grub2/grub.cfg.rpmsave" or "configfile /grub2/grub.cfg.rpmsave" (depending on whether "/boot" is a separate filesystem) at the grub prompt to use the previous grub.cfg. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx