Hello! I just installed fedora and it won’t start. This is the log after I turned off quiet splash. I just installed the proprietary Nvidia drivers and it won’t boot now.
Tell us your PC/laptop specs, tell us how exactly you installed Nvidia or show us a link to which tutorial you used to install the drivers, and tell us which version of Fedora you are using. The more information people have, the better they can try to help you.
I have a nvidia geforce gtx 1080 ti mobile graphics card and and intel core i5 CPU. My laptop also has hybrid graphics. I am using fedora 37
Ok, that info is great.
We still need to know how and from what source you installed the nvidia drivers.
Also, one can force the system to load the nouveau drivers during boot by accessing the grub menu then using the e key to edit the grub commands being used.
Once the edit screen is displayed navigate to the line that begins with linux and remove the 2 parts that show rd.driver.blacklist=nouveau modprobe.blacklist=nouveau and if one wishes also the rhgb quiet so the messages may be seen during boot.
I managed to fix it by adding this the boot options systemd.unit=multi-user.target
Now it boots and works great but the thing concerning me is that it still fails to start nvidia-powerd service when I boot it. Other then that everything seems to work fine
I used this guide. How to Install the NVIDIA Drivers on Fedora Workstation 38
The nvidia-powerd.service is only active on certain laptops and specific GPU models. For everyone else that is just a notification.
To eliminate the notification from the logs one may use
sudo systemctl disable nvidia-powerd.service which will then no longer attempt to start it and thus no longer give those ‘failed’ messages.
1 Like
I see. Thanks for the explanation! But why does systemd-userdbd also fail?
That question will need to be answered by someone more attuned to systemd than I.
That service is usually not essential. Running systemctl status systemd-userdbd may give some more information.
On my system, I have completely disabled that service, both the service and the associated socket unit, and nothing seems to miss it.
The Failed to start message tells you how to get more details. If you don’t understand them, post the details in a new thread with a title that mentions systemd-userdbd failed to start to get the attention of the right people.