From nobody Wed Sep 8 12:11:45 2021 X-Original-To: freebsd-x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D449F17A12BC for ; Wed, 8 Sep 2021 12:11:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4H4LbW5n9Vz3Ght; Wed, 8 Sep 2021 12:11:51 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1631103111; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gX15vIXWUZD32pnonVt0EP57G70+RbPpiESWNCHgfDk=; b=YAq2oEX1kAHnhpgLhY3axqWdZ58r/iR+KIp6qLUbJoLCDKAtaLBu22fC0v6sadAUj/DITF Uc38AcueDALZvAbN+fvWg0KUwk9eqBv1h+RrxvqpSmwoJIY3DE/VJj0XcgPB4L4m5cfYiy DIaYd7fTURTkWWw/D5DtyAeBJoBPGwKMyb26/gQ1Qw3eF/WWbJSZFYLWb+K4aDwGOiCpuA p8v6S87KjpTpLR9qEsk6UDlzte2EQ//lLYSQoFWvLb5zyn0V2nVgug5Gx13v135fLRO2ce rrH2RuH6v5rqgOveLgKbFWizMfmBepDEkNCKNY6rg2BKnHSNK2hRyMbzXrbkuQ== Received: by freefall.freebsd.org (Postfix, from userid 1354) id B32FBA08B; Wed, 8 Sep 2021 12:11:51 +0000 (UTC) From: Jan Beich To: Pete Wright via freebsd-x11 Cc: pete@nomadlogic.org Subject: Re: Issues with Chromium/Vulkan after upgrading vulkan to 1.2.190 References: <8s09-zh1o-wny@FreeBSD.org> Date: Wed, 08 Sep 2021 14:11:45 +0200 In-Reply-To: (Pete Wright via freebsd-x's message of "Tue, 7 Sep 2021 14:20:45 -0700") Message-ID: <4kav-qnb2-wny@FreeBSD.org> List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org MIME-Version: 1.0 Content-Type: text/plain ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1631103111; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gX15vIXWUZD32pnonVt0EP57G70+RbPpiESWNCHgfDk=; b=CCvRla1ciGbq/Ce3jRMwm3PWgjY3/Q6eY92+F0foiPaM0Oe+8Gm1ymd/4kWFWmQ6/uWUFI 8yLEmEuvlZ8bM1YI7j2LR8LRRHPOJz1SRzmnjB+7/t1GNEa0mhCa3umqJPErer4AOHbqxs aLgZs4/R74NbXmLx7diGlY+KK8q9kB7HDfzgcWyt180rwjonU5Z6N8hdSGefBsNTLC0S+v WE04Xov8oqDG5DQzqYLh0LMUagADGgdOYL6iU4jH944NlFOqi1CYh2SxtGiIQJHzyyiUVP EoBuvfUW6p7F0vfaIkIZwm8399L/95G+RX/iv1REeJrG0ke1XymZZyKnCoaMDA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1631103111; a=rsa-sha256; cv=none; b=JMP5x+gzFMUi0Vh+cKbGK0O45Ebic6T3MCxVYORMCu6yJdtLwDBEUzl7elYvUP/gbwrhox gpszN+tCUZJGBVWSpGZE8mR3bnQS3CPgAbrK2cpQ+meIMkZb44Vuo4rtI4cCxJoWtywVD3 LXR8pwYAsNlBO92g7YdUgUWiN9+8zxT4A5nScJi6S1EnqhP02F3ASrOtWVxih202JFDzUn ZRA3rKV9iCnTbTCCuAnJWy84qdlcBJuKTRD1rKAwj/by7uVzfm3l2U0Rp/4YFekz0pbLGS 6KPeeiyDO+JpesRd0dgdhvYIo6FBnZJLwomxmEwFxfT3aHSgQt/bUWfcihYe8A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Pete Wright via freebsd-x11 writes: >>> $ vulkaninfo >>> ERROR at >>> /wrkdirs/usr/ports/graphics/vulkan-tools/work/Vulkan-Tools-1.2.190/vulkaninfo/vulkaninfo.h:248:vkGetPhysicalDeviceSurfacePresentModesKHR >>> failed with ERROR_UNKNOWN >> Did you try to reboot? Sometimes GPU is wedged without triggering >> GPU reset. >> Does vulkaninfo and vkcube-display work fine on KMS console (e.g., >> ttyv0)? > > after i verified disabling vulkan in chrome i quit X and verified > vulkaninfo works fine via a KMS console. i've attached the output of > that to this email. What did you use before console? If a Wayland compositor then NVIDIA GPU maybe selected by default because discrete GPUs are favored over integrated. As NVIDIA blob lacks KMS/GBM it cannot share buffers with Wayland compositor. However, NVIDIA GPU can still be used for headless (CUDA, NVENC, OpenGL offscreen, Vulkan Compute) or rendering to Xorg then forwarding to Wayland via VNC. As a workaround try selecting the desired GPU either from within Vulkan application or via vulkan-loader environ(7) variable e.g., $ vkcube-wayland --gpu_number 0 $ VK_ICD_FILENAMES=/usr/local/share/vulkan/icd.d/intel_icd.x86_64.json vkcube-wayland