I’ve recently installed Fedora Jam on my laptop and followed the instructions on rpmfusion.org to install Nvidia drivers. They seem to have been properly installed, but does not seem to be active. When using blender for instance I cannot select the GPU.
You seem to have the drivers installed and loading properly.
You also seem to be running gnome on wayland.
With that config the nvidia dGPU is not normally active unless you explicitly select it when you open the app with a right-click and select to run the app with the discrete GPU.
Thank you. I followed the steps you linked to, but after rebooting after adding “PrimaryGPU” “yes” it just leads to a black screen. I entered my password just to try because I saw there was some hard drive activity and it seems to log me in, but only to a black screen. The only thing that’s visible is the mouse pointer and the corner indicator “light” when I move the mouse cursor there.
Actually, I found I could press Ctrl+alt+T and open a terminal. But the window was only partial. Lacking borders and such. Used it to edit the file and remove the references to PrimaryGPU and rebooted to a working desktop. But the Nvidia GPU isn’t active.
You had not previously mentioned kde. That is an oversight that may have helped get a correct answer.
The nvidia.conf file does help with using the nvidia drivers when xorg is in use, but your inxi output clearly showed that you are using wayland.
Thus you have either switched to using an xorg login or are misunderstanding what DE is in use.
To use xorg instead of wayland simply use the gear icon at the lower left corner of the screen where you enter your password to log in and select xorg. The default for fedora 36 is wayland.
How do you know it is not active? Your post with the lsmod command showed the drivers were installed, and the inxi output showed the nvidia driver is in use for the nvidia GPU. Both imply that the GPU is actually active and waiting to be tasked.
I did mention I had installed Fedora Jam which, I believe, is an official KDE spin- but I agree I should have been more specific, my apologies. I made sure I logged in to an Xorg session because I prefer using it at the moment. Besides when I tried Wayland it notified me the some Ibus thing wouldn’t work in Wayland. That notification didn’t appear in the xorg session. A recent update may have fixed that because when I tried logging in to Wayland now to double check that message didn’t appear anymore.
I “know” because when opening a project in the Godot game engine the debugger reports using the Intel chip. And blender runs slow and choppy on more complex scenes when I know it normally shouldn’t.
Thank you for taking the time to help me in any case.
ADDED: Oh, another indication is that the fan isn’t spinning up like it used to when under more demanding graphical processing. Trust me, this thing isn’t active.