Wine works outstandingly well on every laptop where I tried it, even with dual graphics cards (Intel+AMD with the DRI_PRIME switch) etc.
However, on my main desktop with an nVidia GPU and the proprietary driver, most games show no graphics output at all. Sometimes the game windows flicker into view for a split second, so I know it loads them, but somehow the DirectX-to-Vulkan translation is not working correctly with the nv GPU driver. Even the "vkcube" demo shows the spinning cube in a window without decorations that I cannot grab/move/resize, so I guess it's an issue with the nv driver but I don't really want to switch to nouveau...
Might have to do with multiple monitors (one of which is connected to the onboard graphics), I got tired of trying to troubleshoot it after a fruitless 2 hour debugging session...
Interesting, I've never run into Wine-specific problems on my 1080 as far as I can remember (proprietary drivers). Plenty of other typical Nvidia crap, but nothing Wine. Multiple monitors and everything. Tested on Manjaro and Ubuntu 20.
One thing I remember having issues with at some point is not rebooting after a graphics driver update, causing the running programs that tried to use hardware acceleration to fail to communicate with the GPU. This was especially a problem with the 32 bit version of the driver and programs that I needed to install to get Wine installed (unless I only wanted to run 64 bit executables).
Another issue I've had with Nvidia drivers is that their Wayland support isn't as great as advertised, even with the new drivers. I can't plug in an external screen under Wayland on my laptop, for example, and with just one screen the Wayland compositor messes up the graphics state after a while. Perhaps you're (unknowingly) running Wayland and the compatibility problems come from there?
Either way, I hope you figure it out, seeing games and programs just work on Linux is kind of magical.
Hi, thanks for responding. I'm also running Manjaro (same as on my 2 laptops where everything Just Works(TM)...)
I'm running Xorg though, no Wayland, so that's definitely not it. I'll keep trying every now and then, of course, but I guess unless vkcube runs properly (like on my laptops...) things won't change
I have the opposite configurations of my machines (my desktop has an AMD GPU, but my laptop has an Nvidia), and my experience has been that the Nvidia stuff requires a lot more tinkering to get working. Because the laptop is an "Optimus" configuration (i.e. integrated graphics are used for most things, but the Nvidia card can be used for offloading), I need to use `nvidia-prime` (https://archlinux.org/packages/extra/any/nvidia-prime/) to launch things I want to run on the discrete GPU. I've had a lot of issues with the GPU overheating by default the past few driver versions, which I currently work around by disabling `nvidia-powerd` and then invoking `nvidia-smi -pl` with a custom power limit on boot. The power limit feature was only enabled one or two driver versions ago though; before that was enabled, the only setting I could find to try to mitigate the overheating when it first started happening was setting a custom max clock speed with `nvidia-smi -lgc`, which was somewhat less effective. Before the power limiting feature got enabled, I noticed a bizarre related issue during overheating where specific keys (the '1', 'a', and tab keys, but never any of the others around them) intermittently miss inputs. From googling, it seems like keyboard issues due to overheating isn't uncommon, but I couldn't find anyone with as specific issues as I was having. On a whim, I tried switching to using X11 instead of Wayland, and the keyboard issues confusingly didn't happen even when the GPU reached similar temperatures, but instead I started having issues where animations like opening a menu or inventory in games or alt tabbing between my game and something else would cause the screen to brightly flash different colors quickly. I wasn't able to figure out how to solve this, so I ended up swapping back to Wayland and using even more aggressive clock speed settings that tanked my frame rate but managed to keep the heat under control, until finally the update came that enabled the power level settings for my GPU model.
I don't know for certain that the issues were specifically due to Nvidia and not just trying to game on Linux with a powerful, insufficiently cooled GPU, but given how the AMD GPU worked for the same games with no need for any custom configuration, I'm definitely going to stick with AMD graphics whenever I end up getting a new laptop, even if I end up having to pay more to find a model that satisfies all my other constraints.
At the risk of inciting a flame war, I'll politely suggest that, while they're usually good enough, I'm not sure I'd say that AMD's drivers are quality. Not to belittle their engineers, only that I've seen enough issues to not prefer AMD for the quality of their drivers. The fact they're mainlined and FOSS is a big bonus, but that's regardless of their quality.
Beyond that, some of us need/want CUDA or other GPGPU support, which is a total nightmare with AMD GPUs, and other times the price/performance ratio leans in favor of nvidia, or some people just have nvidia cards and can't/don't want to buy new ones.
My experience with AMD (and ati before that) GPUs in the last 20 years were entirely negative. Even on Windows. nvidia has alway been a better experience.
Also, I mainly use Windows and only dual-boot to Linux on that system, so Windows driver quality is my primary concern.
Works for me. Using only AMD cards since 2009, without issues in either OS.
If you use Windows, remember to wipe it clean of NVIDIA drivers before attempting to install the AMD card, using DDU, as presence of NVIDIA drivers is well-known to cause issues.
However, on my main desktop with an nVidia GPU and the proprietary driver, most games show no graphics output at all. Sometimes the game windows flicker into view for a split second, so I know it loads them, but somehow the DirectX-to-Vulkan translation is not working correctly with the nv GPU driver. Even the "vkcube" demo shows the spinning cube in a window without decorations that I cannot grab/move/resize, so I guess it's an issue with the nv driver but I don't really want to switch to nouveau...
Might have to do with multiple monitors (one of which is connected to the onboard graphics), I got tired of trying to troubleshoot it after a fruitless 2 hour debugging session...