Hi,
Just a heads up. An update to Mesa is a bit more pressing now. It will need to get updated to 22.0 or newer pretty soon. Proton Experimental has dropped.
Is there a plan to get it up to date (and ideally kernel also)?
Thanks a mill .
Hi,
Just a heads up. An update to Mesa is a bit more pressing now. It will need to get updated to 22.0 or newer pretty soon. Proton Experimental has dropped.
Is there a plan to get it up to date (and ideally kernel also)?
Thanks a mill .
I think the nvidia drivers would need to be updated too right? Although I don't know if it's the policy of Solus to update drivers whenever proton requires it.
Plan is to update mesa post-sync this week. We already have the nvidia-beta-driver-current
which is at 515.43.04 for those that need it. The reason nvidia-glx-driver-current
is still on the 470 series is because once again nvidia decided to drop support for some cards.
As is, if its updated users with cards that were dropped will just boot to a blank screen and would need to manually switch themselves to the 390 series driver before updating to avoid this. Which means they'll also lose a lot of improvements that have occurred since 390. The maintainer @Staudey wanted to avoid this and held back updating it to hopefully find a better solution, reality is there is not one. Nvidia have done this many times before and will do it again.
Kernel is unlikely to move off 5.15.x next week as it is being evaluated as a future LTS kernel for Solus.
No, Solus does not update drivers because proton experimental decides to update its requirements.
Harvey Thanks for the info. Man that really stinks that Nvidia is doing that. Guess I'll have to move to the beta driver if I wanna use newer versions of proton then. Oh well no biggie I guess.
I don't necessarily agree that there is no better solution; but it is true that there is no (clearly) better solution with our current tools, and without expending a lot of additional effort. Unfortunately I can't seem to find the time to work on a (theoretical) better solution, so I've been planning to finally push the driver-branch change one of these days. Probably this sync cycle. Just have to prepare a PSA on our socials to warn users of older cards
Thank you for the information, I was about to open a post like this!
Just a heads up, Mesa3D 22.1.0 is already released at the time of this post.
Not relevant we pretty much never take the .0 and as the new mesa has not landed already it is highly unlikely to make this sync.
When updating to a newer branch, one tends to update to whatever the latest non .0 version is at the time. Unless show stopper issues are found in testing. So IF the maintainer were to move it to a newer branch today, that would likely be the version they choose.