On 2021-01-07 3:54 p.m., Witold Baryluk wrote:
That is weird. I have no issues at all. radv is loaded for me by default in essentially all apps.
The fundamental issue is that the Vulkan loader doesn't define any particular order in which it enumerates Vulkan devices; it currently at least partially depends on the order in which the filesystem enumerates the *_icd.<arch>.json files. This means that lavapipe may end up being enumerated before or after HW accelerated devices depending on the current state of the filesystem, which may change with modifications to the directory containing those files.
Applications generally just use the first enumerated device by default, without checking if it's HW accelerated or not.
On Thu, 7 Jan 2021 at 14:23, Timo Aaltonen <tjaalton@debian.org> wrote:On 7.1.2021 13.22, Witold Baryluk wrote:Hi Timo. Do you know what apps is this happening with that causes problems? lavapipe does expose itself as DEVICE_TYPE_CPU, but it is likely some apps don't inspect the type properly. Would be interesting know which these are to investigate it properly. Of course, it can be solve with the VK_LAYER_MESA_device_select but also obviously we can't make every user need to use it. Maybe a better option is to package swrast into a own package? mesa-vulkan-swrast-driver? Thanks.Hi, according to irc everything (starting from vkinfo, vkcube), so we can't ship it. And doing a separate package doesn't sound like a good idea, loader/mesa just need to be fixed. -- t
-- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer