• 2 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle





  • You’re correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they’re slower code paths.

    The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.

    I’ve tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.









  • Yes, vulkan-radeon and the 32-bit equivalent of it, lib32-vulkan-radeon, provide Vulkan API support. They should definitely be installed if you plan on doing any gaming. I believe Steam depends on vulkan-driver and lib32-vulkan-driver, which vulkan-radeon and lib32-vulkan-radeon provide respectively. There’s also amdvlk which also provides vulkan-driver and is AMD’s proprietary Vulkan implementation. The general advice is to use vulkan-radeon though for the open source RADV implementation, although some games have been known to work better with AMDVLK.

    If I were you though, I’d just wait until some package you install requires them. The fact that they weren’t already installed just means you weren’t using any Vulkan applications to begin with. The only caveat to this statement is if you’re installing a game manually or via something like Flatpak, in which case it may be useful to install ahead of time. Up to you.

    Another thing you might consider is installing the libraries necessary for compute. You aren’t going to be doing many compute tasks on that underpowered 5700G APU, but when you do get your desktop GPU, you may want to install either ROCm, AMD’s open-source compute stack that provides things like HIP and their slightly buggy open-source OpenCL implementation, or opencl-amd, which is their tried and true, proprietary OpenCL implementation.