Description of problem: grubby interacts with grub2-efi.cfg instead of grub2.cfg Version-Release number of selected component (if applicable): 8.3-1 How reproducible: Always Steps to Reproduce: 1. Install fedora-16 2. Install grub2-efi *just the package* 3. run "grubby --info=ALL" Actual results: kernels from grub2-efi.cfg Expected results: kernels from grub2.cfg Additional info: looks like the problem is here (unverified) http://git.fedorahosted.org/git?p=grubby.git;a=blob;f=grubby.c;h=f21a7f8969134bf49c6c91c1ab5747027872da2c;hb=f1e780b61fdf922b4d73b671c4c355650ee6e9fa#l207 I discovered this bug because pm-hibernate was not working as it uses grubby.
Grubby can operate on multiple kinds of boot loader configuration files. Like /sbin/new-kernel-pkg you will have to specify --grub2 -c /etc/grub2.cfg if you want that particular configuration file. Otherwise you will get the default.
Maybe the bug should be filed elsewhere, but still I don't understand what is the correct method in Fedora to understand the current bootloader. Script /usr/lib64/pm-utils/sleep.d/01grub calls grubby with no explicit configuration file to modify. Maybe the solution is to conflict grub2 vs grub2-efi, as installing both confuses grubby (or who assumes grubby is automagic enough). Feel free to move this bug to pm-utils or whatever package it belongs.
The core issue of pm-utils / grub2 integration is tracked on bug 732058. *** This bug has been marked as a duplicate of bug 732058 ***