this post was submitted on 15 Dec 2025
25 points (100.0% liked)
technology
24139 readers
317 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can just say that I had a game that wouldnt work with new nvidia drivers but It worked with older drivers. (Im not talking about super old drivers ~ same year or something (Total Warhammer 3) I tried various proton versions 10,9,8 and experimental + the native Linux version and it would crash within seconds of starting a game. And I did try it dozens of times Works very well with the old drivers. Mind you afaik this isnt the fault of Mint but something that the devs bungled in the last update for linux and mac users but still. Thats all I can say on the topic (only thing I changed are the drivers)
The main reason why im considering to dual boot 2 different Linux distros is cause I wanna use 2 different Linux distros so I can test them against each other and see which I prefer over a longer time period. I might decide to keep both .... I might decide to switch to one of the 2 at some point.
Well it sounds like you tried the lower hanging fruit already. If you have it narrowed down to the driver then the options are basically waiting for Nvidia to fix it (could happen), or waiting for third parties to notice they're broken in this one case and creating a work-around.
Setting the whole "nvidia, boo" rant aside, the situation is complicated by the fact that you have the kernel doing one thing, the Nvidia driver doing another, and then Nvidia's bespoke implementations of OpenGL and Vulkan doing their own thing on top of it. It isn't just the driver, the whole graphics stack is essentially kind of siloed. When I used to have Nvidia hardware (a 970) it generally worked pretty well, but edge cases like this don't benefit from the kind of transparency which exists in implementations like Mesa3D.
Like I said, if having a second OS around works, don't let me stop you. If it works today, it is definitely faster than waiting around for somebody to maybe fix it one day. I'd amend my advice about sharing a
/homepartition up above though. Games using Vulkan (including ALL Windows games running through dxvk) pre-compile their shaders and store them in a cache to avoid intermittent stutters during gameplay. These shaders must be compiled for a specific piece of hardware and a specific driver version. If you are switching back and forth between driver versions on each distro, this shader cache will frequently become invalidated (depends on if the game / runtime retains versioned shader caches, or just deletes the old ones when the driver version changes). If you notice it is constantly recompiling shaders every time you launch a game, this might be why. I think it is still certainly worth sharing a home partition though.