-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I select only Integrated, at boot I will get a message "Missing NVIDIA kernel module, defaulting to Nouveau" #121
Comments
Update: I have tried with multiple fresh installations, always at boot it will show the message of missing NVIDIA kernel module, the only way to get rid of it, is to switch from Integrated to Hybrid, the default mode, that is counter productive, because is the same as not having EnvyControl installed. If you need more information, please let me know, thank you |
It's a known problem with the RPM Fusion Nvidia driver, I think we need to add/modify some Fedora/RHEL specific boot params in addition to blacklisting the kernel modules via modprobe but haven't really looked into it. In the meanwhile, it's safe to ignore it. |
Disable the nvidia-fallback.service and this warning will no longer occur |
@logicito Write |
@Boria138 This is what I see:
I disabled and stopped the service but that did not seem to have effect. After reboot it is active again. And I still saw the message.
But note this:
Note on my other HD with the same exact system but without akmod-nvidia installed, I do not see that message. Must be built into the driver. Just double-checked the lsmod output above from both systems are identical. Observations:
I do not believe your change is needed. As a final test, on the system without akmod-nvidia installed, I executed
|
All the nvidia-fallback service does is to try to start nouveau via modprobe and display messages in plymouth, the changes are only cosmetic, it doesn't affect functionality, but I still think you should disable this service so people don't get confused, probably the best option is to mention this rule in the readme because I think even if you mask the service udev will still call it. |
I just checked it looks like if you mask the service then udev rule doesn't work and plymouth doesn't write anything, @klmcwhirter please check with yourself if this works and if it does I will update pr |
I have moved on to a different approach that seems to be working better for me. Please work with Victor.
On Thursday, March 7, 2024 at 12:18:46 AM PST, Boria138 ***@***.***> wrote:
I just checked it looks like if you mask the service then udev rule doesn't work and plymouth doesn't write anything, @klmcwhirter please check with yourself if this works and if it does I will update pr
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
What different approach ? |
@klmcwhirter is talking about this |
My use case is very specific. I am a developer - NOT a gamer that needs a dedicated GPU. So my goal since I had to buy a $700 laptop from a local sticks-and-bricks has been to turn off the dGPU and recover *some* battery life.
I do not want to have to install the nvidia driver. I did have it installed on the HD I was using to test with. But not in my production HD.
Here is the POC I put together. The first link in the README spells out the details of the approach.
https://github.com/klmcwhirter/nvidia-more-battery/ - Get battery time back by making usage of nvidia GPU optional for systems with Optimus
Note I am working with Victor on the side to potentially include some of this in envycontrol upon switch to integrated mode.
Also, note that with the rpmfusion nvidia driver installed you will still get the innocuous message about the fallback to nouveau.
There is no real panacea here - 3-1/2 hrs battery instead of ~2 hrs. BUT, it was nice to wake up this morning with 96% battery instead of 15%. Sleep / suspend battery time has been solved it seems. A definite step in the right direction.
The other major feature is that the GPU can be "turned back on" without a reboot. Simply tell the kernel to rescan the PCIe bus with:
echo 1 | sudo tee /sys/bus/pci/rescan
To turn it back off simply reboot.
I definitely would like to hear from others whether this works on their system or not. Let me create a separate issue so that we can collect some feedback for Victor.
I have created a new issue as promised - #157
|
I thought that almost after a year, this issue would have been resolved, tested it today, and the exact same problem |
The missing modules is a Fedora issue, it shouldn't try to load again and again once we're blacklisting them |
@bayasdev , actually I am pretty certain it is an intentional design element by the rpmfusion folks - NOT fedora. The nvidia-fallback.service (that issues that warning) is started from inside of the kernel driver code somewhere. And it is right! During the transition to integrated mode we (envycontrol) just blacklisted all those modules. So to me, the service is just stating the obvious; the surprise is the choice to (at least temporarily) fallback to nouveau. As you mentioned, it is completely harmless and can safely be ignored. My analysis of loaded modules across a matrix of scenarios shows that. I am referencing this comment: #121 (comment) Personally I think this knowledge should be captured in the FAQ and this issue closed. But that is just my opinion. I'll let you work that out with @Boria138 . |
@bayasdev I guess this error can be closed, as it is not really an error at all |
Describe the bug
Brand new Fedora 38 installation, using the NVIDIA drivers from Gnome Software (RPM), configured to ONLY Integrated iGPU Intel, and at boot I get the message: "Missing NVIDIA kernel module, defaulting to Nouveau"
To Reproduce
Install NVIDIA driver from Fedora RPM via Gnome Software
Using EnvyControl set it only for Integrated
Boot
Expected behavior
No error message at Boot
Screenshots
If applicable, add screenshots to help explain your problem.
System Information:
Additional context
Add any other context about the problem here. If possible try to reproduce the problem with
--verbose
flag and attach its output.The text was updated successfully, but these errors were encountered: