On Tue, 9 Jun 2020 19:14:23 -0600 linux guy <linuxguy123@xxxxxxxxx> wrote: > Changed GRUB_ENABLE_BLSCFG=true to false. Some random suggestions. I don't run nvidia anymore so never have problems like this, but maybe one of these will at least give you some insight to what is happening. F32 should work with GRUB_ENABLE_BLSCFG=true since it is the default for new installs. Can you set it back to true and then run the mkconfig for efi again. Once you do that, can you show the output of cat /boot/loader/entries for the .conf file for the 5.6.16-300 kernel Then show the line in /boot/efi/EFI/fedora/grub.cfg that has kernelopts in it. If the kernel options you want aren't in that line, I don't see how they will get to your kernel. I know whether the system is booting efi or not because a message comes up during boot, before the selection menu, that says something like using efi secure boot I have rhgb and quiet turned off, though, so I see that message. I see you have them turned on. If you remove them, there might be a clue to what is happening in the kernel messages. Does anything show up as an issue if you do a journalctl -b and go to a boot that didn't have the parameters you want? Try reinstalling the nvidia packages from rpmfusion after you generate a new grub.cfg, and forget about the nvidia options, to see if it will install correctly the way it always has once you have a grub.cfg file (I think you said initially you didn't have one). What happens if you use the efi firmware boot menu to try to boot using efi? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
