I guess, they don’t answer to our question, because they are discussing this question now somewhere in hidden forum thread only for developers.
1 Like
…Or just not discussing about it yet. Doesn’t even matter, since this is clearly not gonna trickle beyond the Unstable branch in its current state.
Might be only Windows based systems. Who knows. So far there is a lot of talk and work regarding Wayland and other things for KDE. I don’t see R470 as a good driver and it won’t get those updates needed. R390 is a total different case. To maintain a driver Nvidia has to commit to fix their issues within their driver series and support newer kernel series. If we maintain a driver it has to work on all supported kernels on our end. If not we may think of adding a dkms packages for kernels supported by that, which may exclude newer kernel series. But as soon as Xorg-Server or any other component won’t work anymore, the driver is gone.
A dkms package should be fine for most users, there are nvidia dkms drivers in the aur but better to use official. Older hardware is fine on a lts kernel so that’s not an issue for most users.
“Stable” 495.44 driver released:
https://www.nvidia.com/download/driverResults.aspx/181274/en-us
I used quotes ("") because it has lead to several crashes and coredumps of some processes.
However, my laptop is an Optimus machine and I am a lame packager 
And I’m on Plasma 5.23.1 which hasn’t been patched to support Nvidia’s GBM implementation.
So let’s hope it will be sorted out by our wonderful maintainers.
470 series got an update as well:
https://www.nvidia.com/Download/driverResults.aspx/181278/en-us
No mention in the patch notes about GSYNC fix, whether it was actually fixed or not. Their notes are rarely complete anyway…
According to a Discord server I’m on, the 495.44 release didn’t fix the dbus spam.
This is not the case, see this: Current graphics driver releases - Linux - NVIDIA Developer Forums
R470 is supported on Linux, just as well as on Windows.
Also for the record, usually NVIDIA support is longer on Linux than on Windows. If you look at Fermi, on Windows only specific Quadro Fermi GPUs are supported with security updates, but on Linux all Fermi GPUs are supported.
Weird thing is I don’t have any dbus spam,maybe is not affecting to optimus laptops. (running 495 beta)
Hmm, that is not good. Maybe we should skip 495.44 for now and keep 470.xx? Wonder also about the Gsync fix not mentioned there …
I pushed 495.44 drivers to unstable without pre-compiled extramodules. Users might need to install nvidia-dkms package after removing any linuxXXX-nvidia package before. Pre-compiled packages may come later this week.
EDIT: Dont forget to run sudo mkinitcpio -P after. 
3 Likes
Hmm, maybe we should go then for that release series and wait a little longer for 495 and beyond. Let’s see.
Anyway, I think discarding 470 drivers when 495/latest drivers are pushed to Stable would be a mistake. That would mean people should use the 390 drivers, which are not really good at all, or not compatible at all with some currently working software (rendering, encoding, gaming, things important for users with Nvidia cards, most of the time).
I really think creating an additional video-nvidia-470xx driver for MHWD, when 495 hits Stable, would be a good move for all concerned people. It is not like recreating the nightmare when there was half a dozen drivers versions to maintain, it is keeping LTS drivers alive to keep proper support for all users.
At minimum Manjaro should provide a solution, like the DKMS package made for the 340 drivers, to not say 
to these concerned users.
PS: it is not even for me, I don’t care I don’t have old video card.
7 Likes
After removing linux514-nvidia and installing nvidia-dkms, the machine couldn’t boot my display manager. It got stuck before showing anything graphical except the useless short text about a filesystem scan, without telling me anything important about booting there. I had to manually switch to a TTY and look in the journal with journalctl -R and scroll down a few pages to find the error, which was an error about kernel module version mismatches. (I wish it would have just printed that error directly instead of requiring that.)
From my research about the error, I found that I had to type sudo mkinitcpio -P, wait for that to finish, then reboot again from a TTY (get there with Ctrl+Alt+F2) for booting to the display manager to succeed again. This short comment is to help anyone who had the same issue.
Edit: Phil’s updated this comment’s parent comment with this solution as well.
Currently we have this situation with Nvidia drivers:
:: Different overlay package(s) in repository community x86_64
-------------------------------------------------------------------------------
PACKAGE stable-staging unstable
-------------------------------------------------------------------------------
linux510-rt-nvidia 470.82.00-1 -
:: Different overlay package(s) in repository core x86_64
-------------------------------------------------------------------------------
PACKAGE stable-staging unstable
-------------------------------------------------------------------------------
mhwd-nvidia 470.82.00-1 495.44-1
:: Different overlay package(s) in repository extra x86_64
-------------------------------------------------------------------------------
PACKAGE stable-staging unstable
-------------------------------------------------------------------------------
gsettings-desktop-schemas 40.0-3 -
libxnvctrl 470.82.00-1 495.44-1
linux414-nvidia 470.82.00-1 -
linux419-nvidia 470.82.00-1 -
linux44-nvidia 470.82.00-1 -
linux49-nvidia 470.82.00-1 -
linux510-nvidia 470.82.00-1 -
linux513-nvidia 470.82.00-1 -
linux514-nvidia 470.82.00-1 -
linux515-nvidia 470.82.00-0.1 -
linux54-nvidia 470.82.00-1 -
nvidia-dkms 470.82.00-1 495.44-1
nvidia-utils 470.82.00-1 495.44-1
opencl-nvidia 470.82.00-1 495.44-1
:: Different sync package(s) in repository extra x86_64
-------------------------------------------------------------------------------
PACKAGE stable-staging unstable
-------------------------------------------------------------------------------
gsettings-desktop-schemas - 41.0-1
:: Different overlay package(s) in repository multilib x86_64
-------------------------------------------------------------------------------
PACKAGE stable-staging unstable
-------------------------------------------------------------------------------
lib32-nvidia-utils 470.82.00-1 495.44-1
lib32-opencl-nvidia 470.82.00-1 495.44-1
Yeah, I just hit this while trying to upgrade packages and removed my linux510 (had it as backup but never really needed ant it blocked upgrading to nvidia 495.44) but then ended up without linux514-nvidia installed. No biggie - was going to re-install that and bam - target not found…
So that’s a bit of a pickle…
Since the 495 driver has key Wayland support improvements, it would be good to have this available as a ‘normal’ kernel module on the unstable branch for those who want it.
Thanks to plilm and buju followed the info rebooted and on latest nvidia drivers.
1 Like