This removes that “Failed to get adapters” error from the proton log but the behavior remains the same and the VK_ERROR_INITIALIZATION_FAILED still persists

Well, back at it again. Tried ProtonGE with the same results. But the vulkan logs are interesting!

cat ~/steam-220200.log | grep err

err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED

EDIT: more context

info:  Presenter: Actual swapchain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_SRGB
info:    Color space:  VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: no)
info:    Buffer size:  1920x1080
info:    Image count:  4
err:   Presenter: Failed to create Vulkan swapchain: VK_ERROR_INITIALIZATION_FAILED

It’s filled with this error. The entire log is massive I cant even upload it to pastebin. If you want me to search for something specific lmk or how I can supply the entire log.

EDIT2: also found:

99664.262:00d4:00d8:err:xrandr:xrandr14_get_adapters Failed to get adapters

99670.682:0180:0184:err:ole:com_get_class_object class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
99670.683:00e8:033c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_rpcrt4_io"
99670.683:0180:0184:err:ole:create_server class {82c5ab54-c92c-4d52-aac5-27e25e22604c} not registered
99670.684:0180:0184:fixme:ole:com_get_class_object CLSCTX_REMOTE_SERVER not supported
99670.684:0180:0184:err:ole:com_get_class_object no class object {82c5ab54-c92c-4d52-aac5-27e25e22604c} could be created for context 0x15

When I select proton-experimental as the version under force proton runtime, I actually see usage in rocm-smi, however I get a black screen or that weird “see behind my window effect I screenshotted” in another comment. When I let it choose, I can see the game but sit at 0% utilization.

What do you mean? There are the following:

Proton experimental Steam Linux runtime 1.0 Legacy runtime 1.0 Proton hotfix Proton 9.0-4 …

If you mean just the global checkbox, yes that’s on

Yeah I’ve tried several Steam Play options. I get different behavior from crashing to some wonky rendering of the windows behind it, but none work

Well I’ve installed BG3 just for the sake of testing and the DX11 launch results in a black screen. The Vulkan launch options crashing immediately…

Here is my steam logs when launching KSP I think the only thing of interest is this:

pressure-vessel-wrap[42106]: W: "opt/amdgpu/share/libdrm" is unlikely to appear in "/run/host"
pressure-vessel-wrap[42106]: W: "opt/amdgpu/share/drirc.d" is unlikely to appear in "/run/host"

Adding process 42106 for gameID 220200
Adding process 42107 for gameID 220200
pressure-vessel-wrap[42106]: I: pv_runtime_provide_container_access: Setting up runtime without using bwrap
pressure-vessel-wrap[42106]: I: EGL ICD #0 at /usr/share/glvnd/egl_vendor.d/50_mesa.json: libEGL_mesa.so.0
pressure-vessel-wrap[42106]: I: Vulkan ICD #0 at /usr/share/vulkan/icd.d/intel_hasvk_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #1 at /usr/share/vulkan/icd.d/radeon_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #2 at /usr/share/vulkan/icd.d/intel_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #3 at /usr/share/vulkan/icd.d/virtio_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #4 at /usr/share/vulkan/icd.d/intel_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #5 at /usr/share/vulkan/icd.d/radeon_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #6 at /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #7 at /usr/share/vulkan/icd.d/lvp_icd.i686.json: /usr/lib/i386-linux-gnu/libvulkan_lvp.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #8 at /usr/share/vulkan/icd.d/virtio_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Vulkan ICD #9 at /usr/share/vulkan/icd.d/lvp_icd.x86_64.json: /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so
pressure-vessel-wrap[42106]: I: Vulkan explicit layer #0 at /usr/share/vulkan/explicit_layer.d/VkLayer_INTEL_nullhw.json: libVkLayer_INTEL_nullhw.so
pressure-vessel-wrap[42106]: I: Vulkan explicit layer #1 at /usr/share/vulkan/explicit_layer.d/VkLayer_MESA_overlay.json: libVkLayer_MESA_overlay.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #0 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamfossilize_i386.json: /home/zamithal/.steam/debian-installation/ubuntu12_32/libVkLayer_steam_fossilize.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #1 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamfossilize_x86_64.json: /home/zamithal/.steam/debian-installation/ubuntu12_64/libVkLayer_steam_fossilize.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #2 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamoverlay_i386.json: /home/zamithal/.steam/debian-installation/ubuntu12_32/steamoverlayvulkanlayer.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #3 at /home/zamithal/.local/share/vulkan/implicit_layer.d/steamoverlay_x86_64.json: /home/zamithal/.steam/debian-installation/ubuntu12_64/steamoverlayvulkanlayer.so
pressure-vessel-wrap[42106]: I: Vulkan implicit layer #4 at /usr/share/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json: libVkLayer_MESA_device_select.so
pressure-vessel-wrap[42106]: I: Capturing glvnd loadable module #0: /usr/share/glvnd/egl_vendor.d/50_mesa.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: libEGL_mesa.so.0
pressure-vessel-wrap[42106]: I: Captured glvnd loadable module #0: /usr/share/glvnd/egl_vendor.d/50_mesa.json
pressure-vessel-wrap[42106]: I: Implementation on x86_64-linux-gnu: SONAME
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #0: /usr/share/vulkan/icd.d/intel_hasvk_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_intel_hasvk.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #1: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #2: /usr/share/vulkan/icd.d/intel_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #3: /usr/share/vulkan/icd.d/virtio_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_virtio.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #4: /usr/share/vulkan/icd.d/intel_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_intel.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #5: /usr/share/vulkan/icd.d/radeon_icd.i686.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/i386-linux-gnu/libvulkan_radeon.so
pressure-vessel-wrap[42106]: I: Capturing vulkan loadable module #6: /usr/share/vulkan/icd.d/intel_hasvk_icd.x86_64.json
pressure-vessel-wrap[42106]: I: Checking for implementation on x86_64-linux-gnu: /usr/lib/x86_64-linux-gnu/libvulkan_intel_hasvk.so

So steam play was already enabled, it looks like it defaults to "steam Linux runtime 1.0 (scout). When I select different versions of proton runtime I get different behavior dependig on which one I select.

Proton 9 says that it cannot switch to my monitors resolution,

Proton experimental and hot fix launch the game (I can hear it!), but things are … Weird. It only renders the windows behind it and the custom game cursor. When I alt enter to bring it into Windows mode, it’s still just the windows/desktop that would be behind the game but now it’s scaled differently.

EDIT:

It’s hard to tell but the above screenshot is the game window

Gotcha, today is the first business day since filing my ticket. They’ve requested logs but no solutions yet.

I don’t appear to have this.

My goal for this system was to eject windows from my life prior to the launch of Windows recall. That and host a bunch of docker containers in an environment more reliable than windows. I got impatient waiting for cosmic to reach full support, but still wanted to go with the distro system76 ships as “theirs” as opposed to putting Ubuntu on their hardware. I haven’t checked if cosmic is officially out yet but will likely switch over when it is. I’m a novice with Linux btw. I can use it to host and run my software but wanted a prepackaged solution for my devbox so that I have a much lower chance of breaking it. Also things like my Wacom tablet just worked out of the box, which is all big plus.

It doesn’t appear to be set and additionally I don’t appear to have the libgl1-mesa-swx11 package mentioned in that post.

set|strings|grep LIBGL

apt list | grep libgl1-mesa

libgl1-mesa-dev/jammy 24.0.3-1pop1~1711635559~22.04~7a9f319 amd64
libgl1-mesa-dev/jammy 24.0.3-1pop1~1711635559~22.04~7a9f319 i386
libgl1-mesa-dri/jammy,now 24.0.3-1pop1~1711635559~22.04~7a9f319 amd64 [installed,automatic]
libgl1-mesa-dri/jammy,now 24.0.3-1pop1~1711635559~22.04~7a9f319 i386 [installed,automatic]
libgl1-mesa-glx/jammy-updates 23.0.4-0ubuntu1~22.04.1 amd64
libgl1-mesa-glx/jammy-updates 23.0.4-0ubuntu1~22.04.1 i386

This does remind me that while developing a webgl canvas based javascript app the other day I was forced to go into firefox’s about:config and set webgl.force-enabled = true. I should have dug deeper on that.

Yeah I’m pleasantly surprised by the unanimous responses that AMD seems to be the way to go in this space. At this point I know it’s not using my GPU at all, so you are right that nvidia wouldn’t be any different

This is Pop_Os, which is System76’s ‘ubuntu like’ distro that comes shipped with vendor maintained drivers. It comes preinstalled with steam and is intended to be able to use it right out of the box. I’ve opened a ticket with them to discuss it further

Now i’m starting to doubt since this these responses have been so ubiquitous, but it’s definitely not plugged into the motherboard’s gpu slot. The motherboard has a single hdmi and displayport port. It, like all the other motherboard ports have a matte-black finish that matches the case. The displays are plugged into the glossy silver PCIE aligned hdmi and display ports, which doesn’t match the rest of the case. The card is doublewide, occupying 2 pcie slots and is labeled “ASROCK”.

It’s definitely plugged into the GPU. I’ve had plenty of opportunity to get acquainted with the back of my machine at this point. :,)

Yeah it appears my card isn’t being used at all, which explains the poor performance. Honestly the fact the system runs as well as it does without it is impressive. I’m reaching out to system76 for their diagnostics on why this might be

Take a look in each game’s graphics settings. Not all of them show it, but some do. In Baldur’s Gate 3

KK will do.

I would expect System76 to be able to help with this more efficiently than we can, since they sold you the system for use with Linux.

I will certainly reach out to them, but it hadn’t occurred to me until this post ¯_(ツ)_/¯

uname -r

6.9.3-76060903-generic

I think this is the mesa version?

OpenGL version string: 4.5 (Compatibility Profile) Mesa 24.1.0-devel

cat /etc/os-release

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com/"
SUPPORT_URL="https://support.system76.com/"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

dpkg -l|grep radeon

ii  libdrm-amdgpu-radeon1:amd64             1:2.4.120.60103-1787201.22.04                                amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:amd64                    2.4.120-1pop1~1706792268~22.04~bfb54ee                       amd64        Userspace interface to radeon-specific kernel DRM services -- runtime
ii  libdrm-radeon1:i386                     2.4.120-1pop1~1706792268~22.04~bfb54ee                       i386         Userspace interface to radeon-specific kernel DRM services -- runtime
ii  radeontop                               1.4-1                                                        amd64        Utility to show Radeon GPU utilization
ii  xserver-xorg-video-radeon               1:19.1.0-2ubuntu1                                            amd64        X.Org X server -- AMD/ATI Radeon display driver

I don’t know exactly what i’m looking for in the xorg logs… cat /var/log/Xorg.*.log | grep “EE”

cat /var/log/Xorg.*.log | grep “WW”

[  5068.047] (WW) Falling back to old probe method for modesetting
[  5068.047] (WW) Falling back to old probe method for fbdev

cat /var/log/Xorg.*.log | grep “gpu”

[  5067.696] (II) Applying OutputClass "AMDgpu" to /dev/dri/card1
[  5067.696] 	loading driver: amdgpu
[  5067.696] (==) Matched amdgpu as autoconfigured driver 0
[  5067.696] (II) LoadModule: "amdgpu"
[  5067.696] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[  5067.696] (II) Module amdgpu: vendor="X.Org Foundation"
	All GPUs supported by the amdgpu kernel driver

sudo journalctl -kb | grep gpu

Feb 15 08:59:51 pop-os kernel: [drm] amdgpu kernel modesetting enabled.
Feb 15 08:59:51 pop-os kernel: amdgpu: Virtual CRAT table created for CPU
Feb 15 08:59:51 pop-os kernel: amdgpu: Topology: Add CPU node
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT
Feb 15 08:59:51 pop-os kernel: amdgpu: ATOM BIOS: 113-APM7199-002
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: CP RS64 enable
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_early_init [amdgpu]] JPEG decode is enabled in VM mode
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: vgaarb: deactivate vga console
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: MEM ECC is not presented.
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SRAM ECC is not presented.
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: VRAM: 16368M 0x0000008000000000 - 0x00000083FEFFFFFF (16368M used)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Feb 15 08:59:51 pop-os kernel: [drm] amdgpu: 16368M of VRAM memory ready
Feb 15 08:59:51 pop-os kernel: [drm] amdgpu: 64286M of GTT memory ready.
Feb 15 08:59:51 pop-os kernel: [drm] GART: num cpu pages 131072, num gpu pages 131072
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x83fc000000 for PSP TMR
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e7e00 (78.126.0)
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully!
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
Feb 15 08:59:51 pop-os kernel: amdgpu: HMM registered 16368MB device memory
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Feb 15 08:59:51 pop-os kernel: amdgpu: Virtual CRAT table created for GPU
Feb 15 08:59:51 pop-os kernel: amdgpu: Topology: Add dGPU node [0x744c:0x1002]
Feb 15 08:59:51 pop-os kernel: kfd kfd: amdgpu: added device 1002:744c
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: SE 6, SH per SE 2, CU per SH 8, active_cu_number 80
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: amdgpu: Using BACO for runtime pm
Feb 15 08:59:51 pop-os kernel: [drm] Initialized amdgpu 3.57.0 20150101 for 0000:03:00.0 on minor 2
Feb 15 08:59:51 pop-os kernel: fbcon: amdgpudrmfb (fb0) is primary device
Feb 15 08:59:51 pop-os kernel: amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Feb 15 08:59:52 pop-os kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Feb 15 08:59:52 pop-os kernel: snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
...