After booting up to Fedora 38 spin Plasma, logging in, and then logging back out, I am met with severe lag, and sometimes doubled keystrokes. This will usually clear up if only one monitor is connected and I click on a different user account badge than whatever is highlighted (can switch back to the original one afterward without issue). If there is another monitor connected, the problem often does not clear up until once I am logged in, and can occur even at first boot. I described the problem in this bug report on KDE, and someone there said that from drm_info it appears that simpledrm and the nvidia driver are trying to control the single monitor at the same time.
What is going on here, and can I do anything about it?
Potentially the comment is correct.
Please post the output of dnf list installed '*nvidia*' and cat /proc/cmdline. Use the </> button on the toolbar or use triple backquotes before and after the text to retain the formatting seen on screen when you copy & paste the text.
With this comment and what you have posted it may help to try editing the command line from the grub menu during boot for testing.
My command line contains 2 additional options that yours does not have. (I have an RTX 3050)
Maybe try pressing the e at the grub menu and then adding to the line that begins with linux one or both of the following to see if it helps. initcall_blacklist=simpledrm_platform_driver_init
and nvidia-drm.modeset=1
Note that editing the command line during boot is only temporary for that one boot.
If that helps then it is relatively simple to make the change permanent so it will always be there for each boot.
Now one may edit the file /etc/default/grub and add that option into the line that begins with GRUB_CMDLINE_LINUX. One would need to use sudo to edit that file.
Once the file has been edited and saved then run sudo grub2-mkconfig -o /boot/grub2/grub.cfg.
This command will update grub so the next boot uses that option in the command line.
Just booting up, and I noticed a longer than usual splash screen before a text error that said something like “Failed to load NVidia…” something, before a working login screen was displayed. IDK if this just started happening, or it’s because of a new bugfix, but either way, I suspect that the extra boot option is now causing the NVidia login display manager to hang for a bit and crash before the default one takes over, thus inadvertently effecting the same fix. I’ll try no modifoed options and the other one you suggested, and see what happens now.
Is there any way to avoid having to re-add initcall_blacklist=simpledrm_platform_driver_init to GRUB every time there’s a kernel update? I have this in /etc/default/grub and applied it with the grub2-mkconfig command, but it seems like when the kernel last updated it did not include this line when adding the new grub entry for some reason.
Please post the output of cat /etc/default/grub so we can see how that is structured.
Include cat /proc/cmdline with that so we can evaluate any differences.
Also please post exactly the command line used when you used grub2-mkconfig.
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.
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.
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.
