On Tue, Oct 20, 2020 at 2:44 PM Michael Cronenworth <mike@xxxxxxxxxx> wrote:
There are four Vulkan driver options for AMD graphics chips at this time.
* Mesa RADV - LLVM (default up to version 20.1)
Original Vulkan driver produced by the Mesa team.
* Mesa RADV - ACO (default starting in version 20.2)
Newest Vulkan driver produced by Valve. Fedora 33 ships with this. Try
Only the ACO (shader compiler) is produced by Valve, the RADV Vulkan driver is still the same (a community effort).
'/RADV_DEBUG=llvm' to use the older backend to see if it fixes your visual bug./
* AMDVLK
Open source driver produced by AMD.
It's very unfortunate that we're in a situation where we have two open-source Vulkan drivers, and the one produced by the hardware vendor is actually not being used in most (any?) distributions. Dave Airlie can surely explain the reasons, I just read that AMDVLK is not great in being a first-class opensource citizen (allowing third-party pull requests, etc).
While both drivers should have a similar level of quality, there are of course bugs in both, as always. I think it would be quite helpful to have AMDVLK packaged as well in Fedora, so that users can install it and switch between AMDVLK and RADV when needed (Vulkan should support having both of them installed, and allow users to pick on of them before starting a program - not sure how, perhaps with an envvar). That would save some troubles to users who experience some bug like you do, and also it would help debugging (an easy check that it's not a hardware issue, for example).
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@xxxxxxxxxxxxxxxxxxxxxxx
