<div dir="ltr"><div dir="ltr"><div>More detailed log with VK_LOADER_DEBUG=1</div><div><br></div><div><span style="font-family:monospace">INFO: Found ICD manifest file /home/vivek/install/share/vulkan/icd.d/libresoc_icd.x86_64.json, version "1.0.0"<br>DEBUG: Searching for ICD drivers named /home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so<br>GetProcAddr called for: vkCreateInstance<br>GetProcAddr called for: vkEnumerateInstanceExtensionProperties<br>DEBUG: Build ICD instance extension list<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>DEBUG: Instance Extension: VK_KHR_surface (/home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so) version 0.0.25<br>DEBUG: Instance Extension: VK_KHR_display (/home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so) version 0.0.23<br>DEBUG: Instance Extension: VK_EXT_direct_mode_display (/home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so) version 0.0.1<br>DEBUG: Instance Extension: VK_EXT_display_surface_counter (/home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so) version 0.0.1<br>DEBUG: Instance Extension: VK_EXT_debug_report (/home/vivek/install/lib/x86_64-linux-gnu/libvulkan_libresoc.so) version 0.0.9<br>DEBUG: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /etc/xdg/xdg-ubuntu/vulkan/implicit_layer.d:/etc/xdg/vulkan/implicit_layer.d:/etc/vulkan/implicit_layer.d:/usr/share/ubuntu/vulkan/implicit_layer.d:/usr/local/share/vulkan/implicit_layer.d:/usr/share/vulkan/implicit_layer.d:/var/lib/snapd/desktop/vulkan/implicit_layer.d:/home/vivek/.local/share/vulkan/implicit_layer.d<br><br>DEBUG: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /etc/xdg/xdg-ubuntu/vulkan/implicit_layer.d:/etc/xdg/vulkan/implicit_layer.d:/etc/vulkan/implicit_layer.d:/usr/share/ubuntu/vulkan/implicit_layer.d:/usr/local/share/vulkan/implicit_layer.d:/usr/share/vulkan/implicit_layer.d:/var/lib/snapd/desktop/vulkan/implicit_layer.d:/home/vivek/.local/share/vulkan/implicit_layer.d<br><br>DEBUG: ReadDataFilesInSearchPaths: Searching the following paths for manifest files: /etc/xdg/xdg-ubuntu/vulkan/explicit_layer.d:/etc/xdg/vulkan/explicit_layer.d:/etc/vulkan/explicit_layer.d:/usr/share/ubuntu/vulkan/explicit_layer.d:/usr/local/share/vulkan/explicit_layer.d:/usr/share/vulkan/explicit_layer.d:/var/lib/snapd/desktop/vulkan/explicit_layer.d:/home/vivek/.local/share/vulkan/explicit_layer.d<br><br>INFO: Found manifest file /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json, version "1.0.0"<br>DEBUG: Adding VK_LAYER_LUNARG_standard_validation using the loader legacy path. This is not an error.<br>INFO: Meta-layer VK_LAYER_LUNARG_standard_validation all 0 component layers appear to be valid.</span><br></div><div><br></div><div>Is this version 0.0.25 and similar values look bad?<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 23, 2020 at 8:33 PM vivek pandya <<a href="mailto:vivekvpandya@gmail.com">vivekvpandya@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
crowd-funded eco-conscious hardware: <a href="https://www.crowdsupply.com/eoma68" rel="noreferrer" target="_blank">https://www.crowdsupply.com/eoma68</a><br>
<br>
On Sun, Aug 23, 2020 at 10:36 AM vivek pandya <<a href="mailto:vivekvpandya@gmail.com" target="_blank">vivekvpandya@gmail.com</a>> wrote:<br>
><br>
> Hello all,<br>
><br>
> I just cleanup a bit and commited code at :<br>
> <a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/commit/d1f29adf926eb44453db1255834575a6f7169d5f" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/commit/d1f29adf926eb44453db1255834575a6f7169d5f</a><br>
><br>
> However it is not working as per my expectation (or my expectations are<br>
> wrong)<br>
><br>
> I want to see that driver fail at<br>
> <a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/commit/d1f29adf926eb44453db1255834575a6f7169d5f#54a82819ff146aa01755bf951d797d55a0332a32_0_43" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/commit/d1f29adf926eb44453db1255834575a6f7169d5f#54a82819ff146aa01755bf951d797d55a0332a32_0_43</a><br>
> however in debugger control never reach there.<br>
<br>
hm does it reach here?<br>
<a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_device.c#L105" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_device.c#L105</a><br>
<br>
(can i recommend a #ifdef VERBOSE_DEBUG and some printfs: it's crude<br>
but effective and when restarting or when others try to replicate this<br>
they will not need to set large numbers of breakpoints. plus, the<br>
debug print statements become a discussion anchor / reference-point,<br>
and a form of documentation in themselves)<br>
<br>
about that: is there an "official" MESA macro for use to do verbose<br>
development-level debug output? i see the radv code checks an<br>
environment variable:<br>
<a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/amd/vulkan/radv_device.c#L2569" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/amd/vulkan/radv_device.c#L2569</a><br>
<br>
<br>
<br>
> I see that in<br>
> <a href="https://gitlab.freedesktop.org/apinheiro/mesa/-/commit/07d01ebf6aae2f9ae71a8bea13a5d8acccb6280e" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/apinheiro/mesa/-/commit/07d01ebf6aae2f9ae71a8bea13a5d8acccb6280e</a><br>
> CreateShaderModule() is defined<br>
<br>
hmm i don't see an equivalent createShaderModule in here:<br>
<a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_pipeline.c" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_pipeline.c</a><br>
<br>
also, enumerateInstanceDeviceProperties is empty:<br>
<a href="https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_device.c#L259" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/vivekvpandya/mesa/-/blob/d1f29adf926eb44453db1255834575a6f7169d5f/src/libre-soc/vulkan/libresoc_device.c#L259</a><br>
<br>
whereas it is not, here:<br>
<a href="https://gitlab.freedesktop.org/apinheiro/mesa/-/commit/07d01ebf6aae2f9ae71a8bea13a5d8acccb6280e#0b80c3a6757284417a6c75db460ee183cd5e80dd_0_35" rel="noreferrer" target="_blank">https://gitlab.freedesktop.org/apinheiro/mesa/-/commit/07d01ebf6aae2f9ae71a8bea13a5d8acccb6280e#0b80c3a6757284417a6c75db460ee183cd5e80dd_0_35</a><br>
<br>
i would recommend putting debug printfs at the top of<br>
libresoc_GetInstanceProcAddr, to get a handle (ha ha) on what<br>
functions are being looked for. ah: it *might* also be worthwhile<br>
actually checking out that very early version of the broadcom driver,<br>
liberally sprinkling it with debug printfs at least at the start of<br>
every function, and see what is called, and in which order.<br>
<br>
by doing the same thing in the libresoc driver that would give you an<br>
idea of what is missing.<br>
<br>
the other thought that occurred to me: it could just be that expecting<br>
createGraphicsPipelines to be called is too early, and that to trigger<br>
it, a little more of the infrastructure has to be in place, such as<br>
responding to vkinfo:<br>
<a href="https://gitlab.axiodl.com/AxioDL/mesa/-/blob/abd629eb3d4027b89c13158e90c6732b412e550e/src/intel/vulkan/anv_device.c#L782" rel="noreferrer" target="_blank">https://gitlab.axiodl.com/AxioDL/mesa/-/blob/abd629eb3d4027b89c13158e90c6732b412e550e/src/intel/vulkan/anv_device.c#L782</a><br>
<br></blockquote><div>I added few debug statements but still the same result:</div><div>Here is my debug log:</div><div><span style="font-family:monospace">vivek@vivek-VirtualBox:~/mesa/dbg$ vulkaninfo <br>GetProcAddr called for: vkCreateInstance <br>GetProcAddr called for: vkEnumerateInstanceExtensionProperties <br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>GetProcAddr called for: vkCreateInstance <br>GetProcAddr called for: vkEnumerateInstanceExtensionProperties <br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>GetProcAddr called for: vkCreateInstance <br>GetProcAddr called for: vkEnumerateInstanceExtensionProperties <br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>libreSoc_EnumerateInstanceExtensionProperties called for layer: (null)<br>GetProcAddr called for: vkEnumerateInstanceVersion <br>GetProcAddr called for: vkDestroyInstance <br>WARNING: <br>WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance and find entrypoints with ICD. Skipping ICD.<br>WARNING: terminator_CreateInstance: Failed to CreateInstance and find entrypoints with ICD. Skipping ICD.<br>Cannot create Vulkan instance.<br>This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.<br>/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:371: failed with ERROR_INCOMPATIBLE_DRIVER</span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace"><span style="font-family:arial,sans-serif">I hope this is not due to the VirtualBox environment.</span><br></span></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
just a thought.<br>
<br>
l
</blockquote></div></div>
</blockquote></div>