Having troubles with current ~amd64 package 384.47: Initialisation fails with error code (VkResult == -7) which translates to ERROR_EXTENSION_NOT_PRESENT. Reverting back to 381.22-r1 fixes the problem.
The new package doesnt install any vulkan files anymore. hossie@powertux ~ $ equery f nvidia-drivers | grep -i vulkan hossie@powertux ~ $ vulkaninfo clearly states "VK_ERROR_INCOMPATIBLE_DRIVER" From the release notes: http://www.nvidia.de/download/driverResults.aspx/120397/de "Fixed a bug where nvidia-installer would install a wrong version of the Vulkan ICD configuration file when GLVND is disabled for the GLX client." Maybe the files have moved or something...
Created attachment 485154 [details] nvidia_icd.json
nvidia_icd.json is missing after unpack, only nvidia_icd.json.template does exist and is presumably used by nvidia installer: { "file_format_version" : "1.0.0", "ICD": { "library_path": "__NV_VK_ICD__", "api_version" : "1.0.46" } } Comment 2 containes dirty workaround that "works for me".
Comment on attachment 485154 [details] nvidia_icd.json Is that "clean" enough to include in a revision?
(In reply to Jeroen Roovers from comment #4) > Comment on attachment 485154 [details] > nvidia_icd.json > > Is that "clean" enough to include in a revision? I would think so but I would feel much more comfortable if somebody with optimus laptop tried it first and confirmed it doesn't break anything. Nevertheless, even were it broken, it's probably net positive over current situation (vulkan doesn't work for anybody).
Please try with 384.59.
(In reply to Jeroen Roovers from comment #6) > Please try with 384.59. Tried with current ebuild (renamed .47 to .59), ICD is not present upon unpacking. Arch does this: https://aur.archlinux.org/cgit/aur.git/commit/?h=nvidia-full-beta-all&id=3f9841295b6651f54c702f4eaae65d5409f2b481 I suggest doing the same thing (+rename followed by doins) in our ebuild, should require no aditional effort unless nvidia decides to change the file again.
Created attachment 486790 [details, diff] arch-like patch for ebuild This works for me just fine.
Nevermind, took a while for git mirror to update portage tree, your 384.59 works just fine.
(In reply to Tomáš "tpruzina" Pružina (amd64 [ex]AT) from comment #9) > Nevermind, took a while for git mirror to update portage tree, your 384.59 > works just fine. I committed a single new ebuild with no revisions or later commits, so I don't see what you are talking about. Assumed fixed.
It's still broken for me with 384.59. /etc/vulkan/icd.d/nvidia_icd.json is there now, but the contents is radically different from the version 381.22-r1 installs. It also doesn't reference libGLX_nvidia.so.0 anymore. No idea if that's correct now, though. But in either case, with 384.59, Vulkan doesn't work. vulkanCapsViewer says no extensions are available, just like with 384.47. Printing out the extensions list myself with a small program only shows "VK_EXT_debug_report", i.e. no presentation, no nothing.
Regex doesn't apply properly. { "file_format_version" : "1.0.0", "ICD": { "library_path": "__NV_VK_ICD__", "api_version" : "1.0.46" } }
> sed -e 's:__NV_VK_ICD__:libGLX_nvidia.so.0:g' nvidia_icd.json missing inplace parameter "-i".
(In reply to Tomáš "tpruzina" Pružina (amd64 [ex]AT) from comment #13) > > sed -e 's:__NV_VK_ICD__:libGLX_nvidia.so.0:g' nvidia_icd.json > > missing inplace parameter "-i". Right.
Should be fixed in -r1.
Marking fixed, sorry for crappy testing.
Yup, works now. Thanks! :)
