wayland: use linux-dmabuf instead of wl_drm

[emersion]

amdvlk relies on the wl_drm Wayland protocol to find the DRM device used by the compositor. However, wl_drm is a Mesa-private, legacy protocol, and compositors are starting to drop support. amdvlk should use the standard linux-dmabuf protocol from wayland-protocols instead.

[Flakebi]

Thanks for the heads-up. This is tracked in GPUOpen-Drivers/pal#96.

[CNR0706]

Would implementing linux-dmabuf also allow Tearing on Wayland? Or is this unrelated?

Not super experienced with this. Sorry if that's a dumb question.

[jinjianrong]

Done in 2024.Q4.1 release

[mikezackles]

In case anyone else comes across this and does a double-take, it's in the 2024.Q2.1 release notes, so I'm guessing Q4 was a typo. Anyway, thanks!

[jinjianrong]

Sorry, this is a typo. The work is done in 2024.Q2.1 release

[HurricanePootis]

I am running AMDVLK 2024.Q2.3 and I am still getting the following error whenever I try to run a wayland application using AMDVLK:

wl_drm#44: error 0: wl_drm.create_prime_buffer is not implemented

[jinjianrong]

Thanks for reporting the issue. We will check it further.

[lukelmy]

Hi @HurricanePootis, thanks for your report.
Could you please provide your wayland application or where I can download it?

[HurricanePootis]

@lukelmy

I am running vkcube-wayland, which is apart of the Vulkan-Tools repository.

Also, for more information, I am running the amdvlk driver with the following build process:

  cmake -H. -Bbuilds/Release64 \
    -DCMAKE_BUILD_TYPE=Release \
    -DBUILD_WAYLAND_SUPPORT=On \
    -G Ninja

And, according to the default.xml file in the tar soure code, it is built with PAL commit GPUOpen-Drivers/pal@695337a.

Edit:
Here is vulkaninfo for my system with the AMDVLK driver

[HurricanePootis]

Any update on this? Kind of inconvenient for amdvlk not to work with modern wayland apps.

[jinjianrong]

@HurricanePootis we can't reproduce the issue locally. But we do notice an issue that may be related with yours. A fix is under implementation

[HurricanePootis]

@jinjianrong Good to know. If you are curious, I installed amdvlk through archlinux and here is the PKBUILD build script they use to build amdvlk for arch.

[HurricanePootis]

I am looking at the files pulled by the archlinux amdvlk package during its build process of 2024.Q2.3, and at pal/src/core/os/amdgpu/wayland/waylandWindowSystem.h, zwp_linux_dmbauf does show up and pal/src/core/os/wayland/mesa/ does exist.

So then, I don't know why even though these files are present at build time, the ensuing amdvlk driver is trying to use wl_drm.

[olm52]

Same problem here with up to date Archlinux using

ENABLE_HDR_WSI=1 mpv --vo=gpu-next --target-colorspace-hint --gpu-api=vulkan --gpu-context=waylandvk '/home/audiolinux/Downloads/Temp/Life Untouched 4K Demo.mp4'

[audiolinux@archlinux ~]$ ENABLE_HDR_WSI=1 mpv --vo=gpu-next --target-colorspace-hint --gpu-api=vulkan --gpu-context=waylandvk '/home/audiolinux/Downloads/Temp/Life Untouched 4K Demo.mp4' (+) Video --vid=1 (*) (hevc 3840x2160 59.940fps) (+) Audio --aid=1 (*) (aac 2ch 48000Hz) [HDR Layer] Created HDR surface AO: [pipewire] 48000Hz stereo 2ch floatp VO: [gpu-next] 3840x2160 yuv420p10 [HDR Layer] Creating swapchain for id: 5 - format: VK_FORMAT_B8G8R8A8_UNORM - colorspace: VK_COLOR_SPACE_SRGB_NONLINEAR_KHR wl_drm#56: error 0: wl_drm.create_prime_buffer is not implemented [vo/gpu-next/wayland] Error occurred on the display fd Exiting... (Quit)

[HurricanePootis]

Sounds like an Arch Issue? I will make a gitlab issue on their tracker.

[olm52]

Ok, fine

[lf-]

https://gitlab.archlinux.org/archlinux/packaging/packages/amdvlk/-/issues/1 arch bug filed

[HurricanePootis]

awesome