unfortunately we cannot answer.
You have not provided the requested info so we only know what you have said and not what the system sees.
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.
They didn’t seem to be talking to me when they initially asked, but I’ll go ahead and do it then.
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.
/etc/default/grub:
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" initcall_blacklist=simpledrm_platform_driver_init
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
/proc/cmdline:
BOOT_IMAGE=(hd2,gpt1)/vmlinuz-6.4.8-200.fc38.x86_64 root=UUID=e5b702d1-48a7-4911-8989-aa7a8d22e52b ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUI D=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
Thanks.
In your /etc/default/grub, this line appears to be the problem:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" initcall_blacklist=simpledrm_platform_driver_init
The initcall_blacklist=simpledrm_platform_driver_init needs to be inside the double quotes.
That line should look like this:
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau initcall_blacklist=simpledrm_platform_driver_init"
Once that’s corrected, you should be able to run sudo grub2-mkconfig -o /boot/grub2/grub.cfg and have it fixed.
I see exactly the same issue with what was posted. 
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:
/etc/default/grub:
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61
-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
/proc/cmdline:
BOOT_IMAGE=(hd2,gpt1)/vmlinuz-6.4.9-200.fc38.x86_64 root=UUID=e5b702d1-48a7-4911-8989-aa7a8d22e52b ro resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
I notice the nouveau blacklist lines are duplicated…
Now those two lines match.
In your earlier post this was seen
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" initcall_blacklist=simpledrm_platform_driver_init
and the suggestion was made to change that to
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau resume=UUID=b68ae08f-1854-46c2-ac61-d83f6ded9ae6 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau initcall_blacklist=simpledrm_platform_driver_init "
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.
Thanks for confirming, yeah.
I felt this was a separate issue, so I posted it here: NVidia drivers and VirtualBox broken after update and GRUB2 config change, no GRUB2 menu - #6 by thelabcat If this was a mistake, let me know and I will flag that post for deletion.
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.
But, GRUB wasn’t showing a menu at all. I would have done that otherwise.
I have since re-added the initcall_blacklist bit, and (probably unrelated) I now have a GRUB menu, but drivers are still broken.
For a user that has a hidden grub menu, it is a fact that holding down the shift key while powering on is supposed to force the menu to appear.
Noted for reference, thanks. Regardless, I do have a normally visible GRUB menu now, bot no change of options has fixed the drivers.
Edit: Strike that, the menu is gone again.
Notably, the drm modeset clip is now added to the boot line by default, but only the initcall blacklist clip actually fixes the issue.
Lets work on this two different ways.
grub menu –
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.