My computer has both an iGPU and a NVIDIA 2060 dGPU combination. A couple months ago, my computer failed to boot and I’ve been having this issue ever since. I think this was at some point when the NVIDIA driver was updated, worked before, updated, and didn’t boot after. The NVIDIA driver was installed with the RPM-fusion repo through the terminal.
My computer continues to halt at “triggering uevents.”
I have asked on another forum and was shown the boot commands of rd.driver.blacklist and drm.modeset, with someone saying that they had an issue with the drm modeset command line entry and it needed to be removed. I was also asked if I had multiple displays, which I do, I have two, one over HDMI and the other over DP.
Each of the HDMI and DP monitor as solo display - hang on boot.
removing the drm modeset parameter - hang on boot.
Remove the rd.driver.blacklist=nouveau - boots fine.
Tried multiple distributions (other than Fedora). - Always hangs on “triggering uevents” ONLY after NVIDIA driver is installed.
Question 1) If I remove the rd.driver.blacklist for the nouveau driver, will it not allow the NVIDIA driver to function?
Question 2) Is there anyway to fix this? Is there an issue with the pass through for the dGPU and not working without the nouveau driver being available?
Question 3) Is this just an NVIDIA issue?
We do not know what you have installed as drivers, nor what is active. Since you have noted that the issue seems to be related to nvidia/nouveau, please post the following. dnf list installed *nvidia*, dmesg | grep -iE 'secure|nouveau|nvidia', lsmod | grep -iE 'nouveau|nvidia',
and finally inxi -Fzxx
Those details should give us enough info to make intelligent suggestions on how to resolve the problems.
Hi Jeff, Thank you very much for your response. I am pretty new to linux, so I am not the most savvy. At the moment, I removed the “nouveau” driver from blacklist in grub so I can load into fedora. I can give you those things though. Please see below.
All that looks good.
It shows you actually have the nvidia driver loaded and active.
The kernel command line looks similar to mine, but I have some additional things.
What do you have with cat /etc/default/grub?
Please post it in the </> preformatted text tags so it retains the formatting as seen on screen for you. Note that I edited your post above and added those tags so your data was more readable.
My line from that file that has the data of interest is
The options there that are missing from yours as seen with the dmesg output are initcall_blacklist=simpledrm_platform_driver_init and kvm.ignore_msrs=1
I don’t remember when or how those options were added but I seem to recall that it may have been nvidia related. I have that on my desktop daily driver as well as on my laptop.
I went and checked out the inticall_blacklist option, this does seem promising. I’ll be honest though, I am confused on how to make this option stick. My last attempt was to edit /etc/grub2.cfg and then grub2-mkconfig, but it seems that it didn’t save it??? Is this how I want to add these options, or is there a more permanent/easier way?
As of today, I’m not sure if my boot options were actually changed. I thought I had changed them, but they may have changed back. If that is the case, then my computer is booting just fine and I have had no issues as of today. I did install a new kernel version today iirc.
Thanks for your help Jeff V. You are fantastic and I appreciate your time.
That from lsmod shows the nvidia drivers are loaded and active, as does the dmesg output.
To add the suggested options to the kernel command line you could do so temporarily (for that boot only) edit the grub entry from the grub menu by pressing e with the kernel being booted displayed then enter the option into the line that begins with linux
To do it permanently you could edit the /etc/default/grub file and add the option to the GRUB_CMDLINE_LINUX line, then after saving it run sudo grub2-mkconfig -o /boot/grub2/grub.cfg which will recreate the entries for the next boot and it will remain for future updates. I hope that grub2-mkconfig line is exactly what you used before.
Thank you for your response and continued time and support. For the time being, my computer has begun to turn on with no issues. There was one time that when booting it said “nvidia drivers rolling back to Nouveau driver,” but when I rebooted, I did the lsmod command as you stated before and it showed the same thing about nvidia drivers being on and active.
I will continue to monitor the solution, especially as we head into F37 and try out your options if I hit a point at which I’m no longer booting.
Again, having the ability to check and know is something I learned along the way.