Installing Nvidia 450.xx drivers after 2020-08-22 stable update

I don’t know but if you need cuda then reinstall it after changing the video drivers from 440 to 450.

1 Like

You will not be updated from 440 to 450 automatically. When running the 440 driver you will automatically receive updates within the same series, but when changing to 450 series this has to be initiated manually.

It is really easy, and you can use the Manjaro hardware settings to do it. No need for CLI. Right-click on the installed driver and remove it, then right-click on the wanted driver and install it. The rest is taken care of. Thereafter reboot and that’s about it.

At least here I have to admit, running GTX980 with 440 before, now 450, no issues.

Cuda 11.0 installed fine and works on my machine.

Sat Aug 22 18:01:00 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.57       Driver Version: 450.57       CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce GTX 1050    Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   46C    P8    N/A /  N/A |      5MiB /  4042MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2909      G   /usr/lib/Xorg                       4MiB |
+-----------------------------------------------------------------------------+
1 Like

This wasn’t the case for me. It complained about breaking dependencies and would not proceed. I had to manually uninstall from Pamac, after installing video-modesetting

I have no hybrid graphics system, only a single GTX980. That seems to be easier to handle.

I assume so.

I used to have only one file in the X11/xorg.conf.d/ folder, 95-mhwd.conf. Now, there is a 90-mhwd.conf there as well, but the old one is still there. Is it safe to remove the 95 file? How can I tell which one the driver is actually using? Sorry if these are stupid questions, but am still trying to figure out why HEVC decoding is not working. I ran the nvidia-modprobe command, no change.

I was getting an error trying to update my nvidia drivers from 440 to 450.

Waiting for user input...
Starting
> Installing video-nvidia-450xx...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/nvidia-450xx/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing linux54-nvidia-440xx breaks dependency 'linux54-nvidia-440xx' required by linux-lts-nvidia-440xx
Error: pacman failed!
Error: script failed!


Done ...

I currently have kernels 5.4 and 5.7 installed and i’m actively using 5.7. I tried to fix this issue by uninstalling 5.4 and got a message stating “Changes were made successfully”, but in the details I got

linux54

linux54-nvidia-440xx

linux54-virtualbox-host-modules

linux54-headers

Starting

checking dependencies...

:: removing linux54 breaks dependency 'linux54' required by linux-lts

:: removing linux54-headers breaks dependency 'linux54-headers' required by linux-lts-headers

:: removing linux54-nvidia-440xx breaks dependency 'linux54-nvidia-440xx' required by linux-lts-nvidia-440xx

:: removing linux54-virtualbox-host-modules breaks dependency 'linux54-virtualbox-host-modules' required by linux-lts-virtualbox-host-modules

Done ...

I manually removed those 4 linux-lts packages in pacman as I no longer use that kernel. After doing that, I was successfully able to uninstall 5.4 and return back to the hardware configuration and run the auto install proprietary to complete the upgrade. I initially intended this post to be a bug report but I solved it as I was writing lol. Bit of a specific situation, but if anyone has a similar issue it might be helpful to know.

Getting this error when trying to update to the the latest Nvidia proprietary drivers using “auto install proprietary” and mhwd install.

Starting
> Using config 'video-nvidia-450xx' for device: 0000:26:00.0 (0300:10de:1b80) Display controller nVidia Corporation GP104 [GeForce GTX 1080]
> Installing video-nvidia-450xx...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/nvidia-450xx/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
Processing classid: 0302
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing linux57-nvidia-440xx breaks dependency 'linux57-nvidia-440xx' required by linux-latest-nvidia-440xx
Error: pacman failed!
Error: script failed!


Done ...

This didn’t work for me as it still uses mhwd and throws up the same error.

This doesn’t work for me either. I’ve tried auto install and manually install of the free drivers. I’ve tried force uninstall and force reinstall for the nvidia 440xx driver too. Still the same error each time. Tried those on Kernel 5.8 and 5.7 but get identical errors on both.

Everything else about the update works fine.

EDIT: R7 2700X GTX1080 Founders

This is probably the third or 4th thread on the same issue.
But your answer still lies above …

Its like this…

sudo pacman -R linux-latest-nvidia-440xx
## note - depending on your system you may have another 'latest' package to remove
sudo mhwd -i pci video-modesetting
sudo mhwd -f -i pci video-hybrid-intel-nvidia-450xx-prime
3 Likes

Had to clean a bit the stable announcement and was almost impossible to chose a perfect place to put it without getting intrusive. :rofl:

1 Like

I think it now uses /etc/X11/mhwd.d/nvidia.conf.
I noticed I made a mistake. I deleted the old 90-mhwd.conf which was softlinked to /etc/X11/mhwd.d/nvidia.conf which I also deleted. Then I put my old 90-mhwd.conf (never seen it being named 95-mhwd.conf) in /etc/X11/mhwd.d/ and renamed it to nvidia.conf. But when I softlinked this new nvidia.conf to /etc/X11/xorg.conf.d/ I forgot to rename it to 90-mhwd.conf (hence it’s /etc/X11/xorg.conf.d/nvidia.conf but after the update the softlink was named 90-mhwd.conf). So basically /etc/X11/xorg.conf.d/ doesn’t to matter but /etc/X11/mhwd.d/nvidia.conf.
Also, you don’t need to remove your 95-mhwd.conf. Just rename it to 95-mhwd.conf.bak.

If both files set drivers for the same device, only the last one will be applied (95-mhwd.conf). The files are read by alphabetical order.

This is that have worked for me:

  1. sudo mhwd -i pci video-modesetting

  2. sudo pacman -Rs linux-latest-nvidia-440xx

  3. sudo mhwd -r pci video-hybrid-intel-nvidia-440xx-prime

  4. sudo mhwd -i pci video-hybrid-intel-nvidia-450xx-prime

  5. reboot

4 Likes

This worked for me too!

Thanks!

This worked for me (no integrated graphics, nvidia 1060)

sudo pacman -R linux-latest-nvidia-440xx
sudo mhwd -r pci video-nvidia-440xx
sudo mhwd -i pci video-nvidia-450xx

then reboot

+1 The gui wouldn’t work but did exact same as this

Theres even a guide …

The problem I had wasn’t a message about failed dependencies or anything it was the same as a few other users. The manjaro settings manager gui just stopped and wouldn’t let you select anything so I had to uninstall and then install 450 via the cli. It wasn’t an issue doing it that way but there must be a issue with the gui for it to freeze for quite a few people

And what does note #2 say on that post ?