After the latest update, like many others, my system no longer boots. I’ve read that this is due to nvidia drivers. After GRUB menu, screen stays black. I have followed all steps here [Fix] System doesn’t boot, boots to a black screen, or stops at a message but still fail to boot. Below are errors from startx:
(EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the system’s kernel log for additional error messages and consult the NVIDIA README for details.
(EE) No devices detected
(EE) no screens found
(EE) Server terminated with error (1). Closing log file.
I also tried nkpro’s comment in the same thread.
Step 1 sudo mhwd -r pci video-nvidia returns “Error: config 'video-nvidia' is not installed!”.
In steps 3 and 4 my mkinitcpio.conf file already has MODULES="".
Steps 6 completed successfully though I am using linux54.
Step 7 returns Skipping already installed config 'video-linux' for device: 0000:01:00.0 (0300:10de:06eb) Display controller nVidia Corporation G98M [Quadro NVS 160M].
blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm
I followed the post and removed blacklist nouveau and blacklist ttm, then ran sudo depmod -a. This command finished with no output. I rebooted, but unfortunately still continue to have the black screen.
@kisun I really appreciate you’re previous responses. I’ve been scouring through this forum for a week trying to resolve with no luck. I am really hoping that I don’t need to do a new install and I’m not even sure that would fix it.
There has been several topics during many months now - due to upstream changes - kernel wise and others - only a subset of the previous Nvidia drivers is maintained.
The maintained drivers is the latest drivers - currently 460xx and the older 390xx.
Essentially this means if your card is not supported by either of these packages you need to use one the opensource drivers. (xf86-video-nouveau - fbdev or vesa).
This may not be optimal - but it is how it is.
To come around to a working system you need to uninstall all nvidia packages. Doing so will - or should - remove the listings created by installing those packages which prevents loading the opensource drivers.
Start by listing installed nvidia packages
pacman -Qq | grep -e 'nvidia'
This will give you an idea of what packages to uninstall. You can use the above command - pipe the result to a text file
$ pacman -Qq | grep -e 'nvidia' > nvidia.txt
Edit the text file and remove reference to mhwd packages. Save the file and the pipe file into pacman
$ sudo pacman -R - < nvidia.txt
After running this command check if the following files still exist - if they do remove then
I successfully removed ‘lib32-nvidia-340xx-utils’, ‘linux419-nvidia-340xx’, and ‘nvidia-340xx-utils’.
I deleted the three files in the /etc/ directory and rebooted. On shutdown for the reboot, it froze with the message
[3675.239517] watchdog: watchdog0: watchdog did not stop!
I had to hold the power button to force the shutdown. But this watchdog issue seems like it is an error for another day. On power up, the screen now works!
@linux-aarhus thanks for the above solution! I appreciate you and @kisun’s help! Moving forward with Manjaro updates, do you suspect that this driver issue will happen with each update? Or should updates honor the opensource drivers and not attempt to install/use nvidia drivers? Basically I am wondering if this machine has seen the end of the road for itself as far as updates for it.
The system will not attempt to install any driver on its own - not even on updates.
The watchdog message - I think I saw disabling the watchdog as part of another script - maxperfwiz by members of the forum @cscs - and it can safely be disabled.
The opensource drivers should work reasonably with the hardware and if you are not having gaming requirements then I don’t think you will see much difference.
Thank you for the information @linux-aarhus. I am glad to hear that I can continue to update the system without ongoing driver problems. No gaming requirements for me, so I am happy with the opensource drivers.
Thanks for the tip on the watchdog error. I will look into how to disable it. Thanks again everyone!