I started daily driving sway during the transition from wlc to wlroots back in early 2019 (sway 1.0), so it’s been 5 years.
Note that’s since I got an HiDPI laptop in 2015, I have been looking at Wayland progress from the GNOME side for a long time, but not completly daily driving it because of some annoyances.
If you launch mullvad from the app icon, try you add to PrefersNonDefaultGPU=true (or false) in mullvad-vpn.desktop (cp /usr/share/applications/mullvad-vpn.desktop ~/.local/share/applications
If it is autostarted add it in .config/autostart/mullvad-vpn.desktop
Or add --disable-gpu to the in Exec : Exec="/opt/Mullvad VPN/mullvad-vpn" --disable-gpu %U
optimus/bumblebee is NVIDIA only, with AMD only setup everything should work ootb except some specific bugs (looking at you rocm)
Hello OP, on this kind of system GNOME should use the igpu by default and the dGPU only when an App “launched with dedicated graphics” from the menu, or with DRI_PRIME=1 from the command line. (Also some vulkan game can also select the dgpu)
If that is not the case this is a bug.
Are you using x11 or wayland, can you see what is using the dgpu with nvtop ?
Qt has native support of fractional scaling both on X11 and wayland (wp-fractional-scale)
On the other hand GTK3/4 only support integer scaling. So on wayland it’s they are basically rendered at x2 and downscaled to your fractional scale factor.
I got a gen 3, basically what is not working are :
SP4 owner here, you should avoid the pro 4, one of its revision (with the samsung display) is very prone to touch screen defects, see this issue.
I’m avoiding surface in general now, after using linux-surface for a year, I finally gave up and got myself a thinkpad x1 tablet. Even without the touchscreen issues, my experience with my SP4 was never good, the cameras needs libcamera and are awful, audio input randomly stopped working after sleep,I had blackscreen issues after login, and random freeze.
As @holland@lemmy.ml said I shouldn’t have set default.clock.rate.
I have 96000 and 192000 in allowed-rates beacause some of my flac are at this sample rate and it avoid resampling them and losing quality (or using CPU in this case because at resample.quality 10 it should not be hearable)
Former gentoo user here. Compiling everything yourself does not magically improve performance. You have to use keep track of USEFLAGS, ideally cherry picking for some package because some can cause bugs or performance regressions.
It can be really time consuming both compiling gentoo and trying different configurations. (But you’ll learn a lot of compilation/ build system knowledge along the way)
My advise is that if you have time and want to experiment and learn, sure go with gentoo. If not and performance is absolutely critical then go with Clear Linux, otherwise take your popular distro of choice, package availability and ease of use are more important than a couple of % in performance improvement IMHO.
By default audio is often configured to run properly on the crappiest sound card and CPU. Since you used easyeffect I assume you use pipeWire. Here some of my config : In pipewire.conf :
default.clock.rate = 96000
default.clock.allowed-rates = [ 44100 48000 96000 192000 ]
In pipewire-pulse.conf
stream.properties = {
resample.quality = 10
}
We’re talking about Qualcomm here, the company that made a deal with Microsoft to make Windows on ARM exclusive to Qualcomm SoC.