If these are correct then the kernel update should have properly worked, if not then by knowing where to start we should be able to fix the problem.
I’m not sure what I did wrong the first time, but I double checked everything and ran the grub2-mkconfig command again, and after the next kernel update the initcall_blacklist=simpledrm_platform_driver_init was preserved. I forgot to circle back here about it. Thank you!
Sadly, after switching back to Fedora from NixOS, the issue has returned, and the initcall_blacklist line suffix is not fixing it anymore. The other suggested line suffix no longer exists as a command, apparently.
This solution is still working for me, so that is odd. I’d suggest double checking to make sure that initcall_blacklist=simpledrm_platform_driver_init got added to the very end of the line that starts with “linux”. I accidentally put it on the wrong line the first time I did this and that made it not work. Otherwise, please reply with what Jeff V asked for so they can help.
Actually these comments were directed to @tsumeone and his question about having to re-add the option with every kernel update. No reply was received there.
However, my next post quoting that request was directed to @thelabcat as well. The same information will be helpful in diagnosing the problem there.
Umm, IDK if the problem is solved or not, because on the next reboot I also got software updates, and even after removing the line change my NVidia drivers are now broken. But, I think that’s not GRUB’s fault.
After making the update to fix the error please once again show us the output of cat /etc/default/grub and cat /proc/cmdline so we may confirm the change was done properly.
What update are you talking about, exactly? One I’ve already made, or one I need to make? If the latter, I’m not sure what you are talking about. Regardless, here are the files:
Thus the update I referred to was the change there. You made a change, but not the recommended change.
One may remove the duplicated portions if desired although they are not applied twice (or at least cause no harm that way). You may note that even though duplicated in the /etc/default/grub file they are not duplicated in the actual command line from /proc.
Yes and no. I did make the recommended change, and then I reverted all changes from the default to try and fix the broken NVidia drivers, but with no effect.
To find out if the option suggested for use may work, one may enter it at boot time for a temporary test by displaying the grub menu then pressing e to edit the grub commands there.
Adding the option suggested to the end of the line that begins with linux will activate that option for that boot only and allow testing. If it makes things better then it may be added to the file /etc/default/grub and made permanent with the grub2-mkconfig command.
This is one option that I use with my nvidia card because it seems to work better than without, so it still is related to the nvidia, even though it is an alteration to grub. It modifies the modules loaded into the kernel at boot. It certainly was required some time back for me.
The menu normally can be set to display all the time if one first does sudo grub2-editenv - list to see what options are already set.
If the option menu-auto-hide=1 is displayed that usually would be why the menu does not display.
That can be changed with sudo grub2-editenv - unset menu-auto-hide so the menu is displayed with every boot.
Nvidia drivers –
Please post the output of dnf list installed \*nvidia\* so we can see what is installed that may be related to the nvidia drivers.
