AMDVLK 2023.Q4.3 Released With Counter-Strike 2 Optimization, VKD3D Change

[phoronix]

Phoronix: AMDVLK 2023.Q4.3 Released With Counter-Strike 2 Optimization, VKD3D Change

While we are now into 2024, AMDVLK 2023.Q4.3 was released today as a final EOY2023 update to this open-source AMD Vulkan driver that was supposed to be out last week but presumably got delayed due to the holidays...

https://www.phoronix.com/news/AMDVLK-2023.Q4.3

[user1]

One thing I don't understand is that AMDVLK recently removed Polaris and Vega support, but according to the latest AMDGPU-pro release notes, which includes both AMDVLK-open and AMDVLK-pro, there is still support not just for Polaris and Vega, but also for some older GCN cards. The Windows driver dropped support for pre Polaris GCN cards already 2 years ago. Maybe someone from AMD can elaborate on that?

[skeevy420]

One thing I don't understand is that AMDVLK recently removed Polaris and Vega support, but according to the latest AMDGPU-pro release notes, which includes both AMDVLK-open and AMDVLK-pro, there is still support not just for Polaris and Vega, but also for some older GCN cards. The Windows driver dropped support for pre Polaris GCN cards already 2 years ago. Maybe someone from AMD can elaborate on that?

TIL: If you don't specify anything with AMDGPU-Pro, it uses Mesa

If --usecase option is not present, the default selection is
"dkms,graphics,opencl,hip"
Available use cases:
dkms            (to only install the kernel mode driver)
  - Kernel mode driver (included in all usecases)
graphics        (for users of graphics applications)
  - Open source Mesa 3D graphics and multimedia libraries
multimedia      (for users of open source multimedia)
  - Open source Mesa 3D graphics and multimedia libraries
workstation     (for users of legacy WS applications)
  - Open source multimedia libraries
  - Closed source (legacy) OpenGL​

That's line 119 of amdgpu-install

[aufkrawall]

Amazing, it's 75fps in Hogwarts Legacy vs. 148fps with RADV on 7800 XT...

[user1]

TIL: If you don't specify anything with AMDGPU-Pro, it uses Mesa

I know it mostly consists of Mesa, but I mean specifically the non Mesa / pro drivers. If you check repo.radeon.com, you'll see all the pro drivers with the 23.30 branch in their package name. For example, here is the latest AMDVLK-pro driver.

[qarium]

I know it mostly consists of Mesa, but I mean specifically the non Mesa / pro drivers. If you check repo.radeon.com, you'll see all the pro drivers with the 23.30 branch in their package name. For example, here is the latest AMDVLK-pro driver.

i have a theory about this... they can not drop it as people may want to believe because there are still notebooks realatively new in the market with APUs who use Vega as igpu
on linux as it is opensource anyway they plain and simple can not drop it its opensource you can reenable it in no time.
so all the fear porn of people like Avis/birdie is all bullshit... its opensource you can implement any feature or update you want.

this game of we disable your card after 6 years of support they can only play this game in the closed-source world of windows.

i have a vega64 in the system i use right now to write with you and i have ZERO fear that they drop any driver what so ever.
i use RADV/MESA anyway so they can not end support or disable anything.

this bullshit of we end your support is a closed source windows game they can not play in linux world.

[qarium]

Amazing, it's 75fps in Hogwarts Legacy vs. 148fps with RADV on 7800 XT...

i watch this news for like 10 years now and in 10 years i had never ever any reason to install this driver.

writen with vega64 on RADV/MESA---

[skeevy420]

I know it mostly consists of Mesa, but I mean specifically the non Mesa / pro drivers. If you check repo.radeon.com, you'll see all the pro drivers with the 23.30 branch in their package name. For example, here is the latest AMDVLK-pro driver.

The Ubuntu packages install AMDVLK-Pro into /opt so something would have to explicitly be ran calling AMDVLK in order to use it. RADV is still used by default so older GPUs would work just fine. The open AMDVLK package, however, installs itself to /usr and /etc in a manner that overrides Mesa/RADV which would prevent older GPUs from working.

What we need is someone running Ubuntu with a Polaris or Vega GPU and AMDGPU-Pro installed to run something with

VK_DRIVER_FILES=\opt\amdgpu-pro\etc\vulkan\icd.d\amd_icd32.json:\opt\amdgpu-pro\etc\vulkan\icd.d\amd_icd64.json

to see whether Pro Vulkan does or does not work with older GPUs.

[user1]

The Ubuntu packages install AMDVLK-Pro into /opt so something would have to explicitly be ran calling AMDVLK in order to use it. RADV is still used by default so older GPUs would work just fine. The open AMDVLK package, however, installs itself to /usr and /etc in a manner that overrides Mesa/RADV which would prevent older GPUs from working.

What we need is someone running Ubuntu with a Polaris or Vega GPU and AMDGPU-Pro installed to run something with

VK_DRIVER_FILES=\opt\amdgpu-pro\etc\vulkan\icd.d\amd_icd32.json:\opt\amdgpu-pro\etc\vulkan\icd.d\amd_icd64.json

to see whether Pro Vulkan does or does not work with older GPUs.

I know that both AMDVLK-pro and open have the AMD switchable graphics layer that overrides RADV by default, so I don't think the location of AMDVLK and its icd matters. Mesa drivers also have their icd's in /usr/share/vulkan, a location which afaik is not used by AMDVLK.

[skeevy420]

I know that both AMDVLK-pro and open have the AMD switchable graphics layer that overrides RADV by default, so I don't think the location of AMDVLK and its icd matters. Mesa drivers also have their icd's in /usr/share/vulkan, a location which afaik is not used by AMDVLK.

It does matter. The open AMDVLK adds the JSON files to /usr/share/vulkan/implicit_layer.d/ that force AMDVLK and disable RADV. That doesn't happen when it's installed to /opt.