Re: Vulkan VK_ICD_FILENAMES and /dev/dri/renderD128 permissions

   Hi,

You need to log into the system, I guess.  The login process adds an
acl to give you access to /dev/dri/renderD128 when you log in, and
removes it when you log out (and probably change vt).  If direct
rendering works, then it works.  Did you try to do your tests remotely
with the system still on the login page? Been there, done that, got
the T-shirt.

Also, if the environment variable annoys you, the loader looks into
/etc/vulkan/icd.d for the json files, so you can symlink it there and
it'll just work.

Best,

  OG.


On Fri, Feb 19, 2016 at 3:48 AM, Cordell George Bloor
<[email protected]> wrote:
> Hello,
>
>
> I've been hacking away to try to get the vulkan branch working on Ubuntu
> 14.04 with kernel 4.2.
>
>
> I noticed that in the vulkan branch, README.intel-vulkan.txt suggests using
> `export VK_ICD_FILENAMES="$MESA_TOP/src/vulkan/anv_icd.json"` (link).
> However, there doesn't seem to be a anv_icd.json file anywhere in the
> repository. I tried `export
> VK_ICD_FILENAMES="$MESA_TOP/src/intel/vulkan/dev_icd.json"`, which seemed to
> work better. I presume somebody just forgot to update the readme after
> changing the name.
>
>
> Of course, vulkaninfo still fails. It just gets further than it did before.
> I'm a little stuck on the next error:
>
> anv_device.c:66: failed to open /dev/dri/renderD128: Permission denied
> (VK_ERROR_INITIALIZATION_FAILED)
>
>
> I haven't changed its permissions from the defaults it came with:
> 'crw-rw---- 1 root video 226, 128 Feb 18 16:18 /dev/dri/renderD128'.
>
>
> Any suggestions? Did I miss something I needed to do?
>
>
> Thanks,
>
> Cory Bloor
>
>
> _______________________________________________
> mesa-users mailing list
> [email protected]
> https://lists.freedesktop.org/mailman/listinfo/mesa-users
>
_______________________________________________
mesa-users mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-users