[Bug]: Missing DRI3 Support

[flo-sem]

Describe the Bug

Certain games on steam ('Cult of the Lamb' for me) start and crash immediately. After tinkering around with the launch options, my best guess for this is an issue with Vulkan. (As PROTON_USE_WINED3D=1 %command% resolves this).
After installing lutris for testing, i encountered this Note in the terminal:
vulkan: No DRI3 support detected - required for presentation

After looking at Issue 52 , i tried setting the proton version to v7... This resulted in the game opening in a black screen, with a popup showing:

Switching to resolution 1920x1080 failed
Screen: DX11 could not switch resolution (1920x1080 fs=0 hz=0) 

Steps to Reproduce

1. Enable Steam Play support for all games in the steam settings.
2. Download Cult of the Lamb
3. Start the Game

The Lutris message is reproduced by

1. Installing lutris
2. running lutris from the terminal

Expected Behavior

The game should launch as expected. Maybe consider enabling DRI3 as shown here.

Screenshots

No response

Relevant Settings

• Running without a dedicated GPU

Version

Build: [2024-10-12 02:59:05] [master] [0241c9f]

Platform

• Distro: Ubuntu 22.04
• Kernel: 5.15.0-122-generic x86_64
• GPU Driver: None (integrated Intel UHD Graphic)
• Docker version: 24.0.7

Relevant log output

Proton Log (with launchoption: PROTON_LOG=1)
======================
Proton: 1727965900 experimental-9.0-20241003
SteamGameId: 1313140
Command: ['/home/default/.steam/debian-installation/steamapps/common/Cult of the Lamb/Cult Of The Lamb.exe']
Options: {'forcelgadd'}
depot: 0.20240916.101795
pressure-vessel: 0.20240916.0 scout
scripts: 0.20240916.0
sniper: 0.20240916.101795 sniper 0.20240916.101795
Kernel: Linux 5.15.0-122-generic #132-Ubuntu SMP Thu Aug 29 13:45:52 UTC 2024 x86_64
Language: LC_ALL en_US.UTF-8, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
WARNING: Low /proc/sys/vm/max_map_count: 65530 will prevent some games from working
======================
...
2000513.561:0128:01f0:warn:threadname:NtSetInformationThread Thread renamed to L"HIDInput"
2000513.561:0094:01f4:warn:threadname:NtSetInformationThread Thread renamed to L"wine_rpcrt4_io"
2000513.563:0094:01f8:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2000513.563:0128:012c:trace:seh:register_module_exception_directory count 47, max_count 512.
2000513.563:0128:012c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\xinput1_3.dll" at 00006FFFFAC40000: builtin
2000513.565:0128:012c:trace:seh:RtlGrowFunctionTable 00000000681CB5A0, 80
2000513.565:0128:012c:trace:seh:RtlGrowFunctionTable 00000000681CB5A0, 81
2000513.566:0128:012c:trace:seh:RtlGrowFunctionTable 00000000681CB5A0, 82
2000513.566:0128:012c:fixme:system:NtUserGetDisplayConfigBufferSizes only returning active paths
2000513.566:0128:012c:fixme:system:NtUserQueryDisplayConfig only returning active paths
2000513.566:0128:012c:fixme:system:NtUserQueryDisplayConfig setting toplogyid to DISPLAYCONFIG_TOPOLOGY_INTERNAL
info:  Intel(R) UHD Graphics (CML GT2):
info:    Driver : Intel open-source Mesa driver 22.3.6
info:    Memory Heap[0]: 
info:      Size: 11776 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0xf
info:  Presenter: Actual swap chain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Color space:  VK_COLOR_SPACE_SRGB_NONLINEAR_KHR
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR (dynamic: no)
info:    Buffer size:  1280x720
info:    Image count:  4
info:    Exclusive FS: 1
warn:  D3D11DXGIDevice::QueryInterface: Unknown interface query
warn:  0ec870a6-5d7e-4c22-8cfc-5baae07616ed
warn:  DXGI: MakeWindowAssociation: Ignoring flags
info:  Setting display mode: 1280x720@60
info:  Setting display mode: 1280x720@60
X connection to :55.0 broken (explicit kill or server shutdown).
2000513.637:0200:0204:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005.
2000513.637:0200:0204:trace:seh:install_bpf Seccomp filters already installed.
2000513.637:0134:0138:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FEB0
2000513.638:0200:0204:trace:seh:register_module_exception_directory count 1, max_count 512.
2000513.638:0200:0204:trace:loaddll:build_module Loaded L"Z:\\home\\default\\.steam\\debian-installation\\steamapps\\common\\Cult of the Lamb\\UnityCrashHandler64.exe" at 0000000140000000: native
2000513.638:0200:0204:trace:seh:register_module_exception_directory count 2, max_count 512.
2000513.639:0200:0204:trace:seh:register_module_exception_directory count 2, max_count 512.
2000513.639:0200:0204:trace:seh:register_module_exception_directory count 3, max_count 512.
2000513.639:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernelbase.dll" at 00006FFFFFC10000: builtin
2000513.639:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernel32.dll" at 00006FFFFFEC0000: builtin
2000513.641:0200:0204:trace:seh:register_module_exception_directory count 4, max_count 512.
2000513.642:0200:0204:trace:seh:register_module_exception_directory count 5, max_count 512.
2000513.643:0200:0204:trace:seh:register_module_exception_directory count 6, max_count 512.
2000513.643:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msvcrt.dll" at 00006FFFFFB00000: builtin
2000513.643:0200:0204:trace:seh:register_module_exception_directory count 7, max_count 512.
2000513.644:0200:0204:trace:seh:register_module_exception_directory count 8, max_count 512.
2000513.644:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ucrtbase.dll" at 00006FFFFF9E0000: builtin
2000513.644:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\sechost.dll" at 00006FFFFFAC0000: builtin
2000513.644:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\advapi32.dll" at 00006FFFFFBB0000: builtin
2000513.645:0200:0204:trace:seh:register_module_exception_directory count 9, max_count 512.
2000513.645:0200:0204:trace:seh:register_module_exception_directory count 10, max_count 512.
2000513.645:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\win32u.dll" at 00006FFFFF490000: builtin
2000513.645:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\gdi32.dll" at 00006FFFFF4E0000: builtin
2000513.645:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\USER32.dll" at 00006FFFFF570000: builtin
2000513.646:0200:0204:trace:seh:register_module_exception_directory count 11, max_count 512.
2000513.646:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\dbghelp.dll" at 00006FFFFEEA0000: builtin
2000513.647:0200:0204:trace:seh:register_module_exception_directory count 12, max_count 512.
2000513.647:0200:0204:trace:seh:register_module_exception_directory count 13, max_count 512.
2000513.648:0200:0204:trace:seh:register_module_exception_directory count 14, max_count 512.
2000513.648:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\shcore.dll" at 00006FFFFE1B0000: builtin
2000513.648:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\shlwapi.dll" at 00006FFFFE1E0000: builtin
2000513.648:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\SHELL32.dll" at 00006FFFFE240000: builtin
2000513.649:0200:0204:trace:seh:register_module_exception_directory count 15, max_count 512.
2000513.649:0200:0204:trace:seh:register_module_exception_directory count 16, max_count 512.
2000513.649:0200:0204:trace:seh:register_module_exception_directory count 17, max_count 512.
2000513.649:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 00006FFFFF910000: builtin
2000513.650:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\combase.dll" at 00006FFFFECD0000: builtin
2000513.650:0200:0204:trace:seh:register_module_exception_directory count 18, max_count 512.
2000513.650:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\coml2.dll" at 00006FFFFECA0000: builtin
2000513.650:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ole32.dll" at 00006FFFFED30000: builtin
2000513.651:0200:0204:trace:seh:register_module_exception_directory count 19, max_count 512.
2000513.651:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\PSAPI.DLL" at 00006FFFFDD00000: builtin
2000513.651:0200:0204:trace:seh:register_module_exception_directory count 20, max_count 512.
2000513.652:0200:0204:trace:seh:register_module_exception_directory count 21, max_count 512.
2000513.652:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\mpr.dll" at 00006FFFFE020000: builtin
2000513.652:0200:0204:trace:seh:register_module_exception_directory count 22, max_count 512.
2000513.652:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ws2_32.dll" at 00006FFFFF9A0000: builtin
2000513.652:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\WININET.dll" at 00006FFFFE050000: builtin
2000513.653:0200:0204:trace:seh:register_module_exception_directory count 23, max_count 512.
2000513.653:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\VERSION.dll" at 00006FFFFE000000: builtin
2000513.685:0200:0204:trace:seh:register_module_exception_directory count 24, max_count 512.
2000513.685:0200:0204:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\imm32.dll" at 00006FFFFF460000: builtin
2000513.687:0200:0204:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FEB0
2000513.709:0030:0208:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2000513.710:0030:020c:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
2000513.711:0030:0210:warn:threadname:NtSetInformationThread Thread renamed to L"wine_threadpool_worker"
pid 149025 != 149024, skipping destruction (fork without exec?)

[alansari]

Could you try creating a file in your init.d directory with these contents:

sudo sed -i '/^Section "Device"/a \
    Identifier "Intel Graphics"\
    Driver "intel"\
    Option "DRI" "3"' /etc/X11/xorg.conf

If this fixes it for you i'll see if i can patch it in.
You can also just edit the /etc/X11/xorg.conf if thats easier and restart the container, just be sure not to recreate the container as changes will be lost

[flo-sem]

Gave it a shot, however then the vnc website can't connect to the server anymore, logs below.

If I edit the xorg.conf file itself, it resets itself after the container reboot.

I also tried creating a new config files in /etc/X11/xorg.conf.d/ , that however didn't seem to have any effect, as running vkcube still results in:

Selected GPU 0: Intel(R) UHD Graphics (CML GT2), type: IntegratedGpu
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
Could not find both graphics and present queues

---

Container Logs

2024-10-16 03:20:28,550 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2024-10-16 03:20:28,551 INFO supervisord started with pid 1

2024-10-16 03:20:29,555 INFO spawned: 'dbus' with pid 255

2024-10-16 03:20:29,558 INFO spawned: 'udev' with pid 256

2024-10-16 03:20:29,559 INFO spawned: 'xorg' with pid 257

2024-10-16 03:20:29,561 INFO spawned: 'audiostream' with pid 258

2024-10-16 03:20:29,562 INFO spawned: 'frontend' with pid 260

2024-10-16 03:20:29,564 INFO spawned: 'pulseaudio' with pid 261

2024-10-16 03:20:29,566 INFO spawned: 'x11vnc' with pid 264

2024-10-16 03:20:29,567 INFO spawned: 'desktop' with pid 266

2024-10-16 03:20:29,569 INFO spawned: 'sunshine' with pid 269

PULSEAUDIO: Starting pulseaudio service

2024-10-16 03:20:29,574 WARN exited: xorg (exit status 1; not expected)

2024-10-16 03:20:29,586 INFO reaped unknown pid 285 (exit status 0)

2024-10-16 03:20:30,604 INFO success: dbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,605 INFO success: udev entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,606 INFO spawned: 'xorg' with pid 325

2024-10-16 03:20:30,607 INFO success: audiostream entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,607 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,607 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,607 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,607 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,607 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:20:30,629 WARN exited: xorg (exit status 1; not expected)

2024-10-16 03:20:33,626 INFO spawned: 'xorg' with pid 364

2024-10-16 03:20:33,644 WARN exited: xorg (exit status 1; not expected)

2024-10-16 03:20:37,613 INFO spawned: 'xorg' with pid 416

2024-10-16 03:20:37,652 WARN exited: xorg (exit status 1; not expected)

2024-10-16 03:20:38,654 INFO gave up: xorg entered FATAL state, too many start retries too quickly

2024-10-16 03:21:00,032 WARN exited: x11vnc (exit status 11; not expected)

2024-10-16 03:21:00,033 WARN exited: desktop (exit status 11; not expected)

2024-10-16 03:21:00,033 WARN exited: sunshine (exit status 11; not expected)

2024-10-16 03:21:00,037 INFO spawned: 'x11vnc' with pid 685

2024-10-16 03:21:00,041 INFO spawned: 'desktop' with pid 686

2024-10-16 03:21:00,045 INFO spawned: 'sunshine' with pid 687

2024-10-16 03:21:01,066 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:01,066 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:01,066 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:01,067 INFO reaped unknown pid 698 (exit status 0)

2024-10-16 03:21:30,516 WARN exited: x11vnc (exit status 11; not expected)

2024-10-16 03:21:30,517 WARN exited: sunshine (exit status 11; not expected)

2024-10-16 03:21:30,583 INFO spawned: 'x11vnc' with pid 1058

2024-10-16 03:21:30,585 INFO spawned: 'sunshine' with pid 1059

2024-10-16 03:21:30,586 WARN exited: desktop (exit status 11; not expected)

2024-10-16 03:21:30,587 INFO spawned: 'desktop' with pid 1060

2024-10-16 03:21:31,598 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:31,599 INFO success: desktop entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:31,599 INFO success: sunshine entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2024-10-16 03:21:31,599 INFO reaped unknown pid 1072 (exit status 0)

[1mthesun]

Are you able to check if it's even running off the igpu? I have the same issue, included --device=/dev/dri in extra parameters with intel pentium 8505 (intel_gpu_top installed on unraid).

When running any game that requires proton, they instantly crash and go back to the green play button. When including the Wine parameter you mentioned in launch options, the games launch but run extremely poorly. In the unraid homepage menu the iGPU also shows no activity (also have --device=/dev/dri in plex extra parameters and when transcoding gpu shows activity) suggesting the game running off purely the CPU.

vkcube shows:
[default@SteamHeadless ~]$ vkcube
Graphics Selected GPU 0: Intel(R) Graphics (ADL GT2), type: IntegratedGpu
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
Could not find both graphics and present queues

But steam system information shows:
Video Card:
Driver: Mesa/X.org lImpipe (LLVM 15.0.6, 256 bits)
Driver Version: 4.5 (Compatibility Profile) Mesa 22.3.6
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 50 Hz
VendorID: 0x8086
DevicelD: 0x46b3
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 2
Primary Display Resolution: 1920 × 1080
Desktop Resolution: 1920 × 1080
Primary Display Size: 20.00" x 11.22" (22.91" diag), 50.8cm x 28.5cm (58.2cm diag)
Primary VRAM Not Detected

I feel like there may be a config issue somewhere, but not sure how to fix this

[flo-sem]

I looked into @1mthesun 's comment, running "Cult of the Lamb" (Proton) and "Enter the Gungeon" (Native), i found that while the 4 bar graphs in intel_gpu_top (Render/3D, Blitter, Video, Video Enhance) did in fact not show any utilisation, The above "IMC reads/writes" section showed a drastic increase after launching a game, as well as the amount of Watts used by the CPU (for both games).

I dont think a lack of iGPU utilisation is causing this issue...

(Sorry for closing and reopening, must have pressed the button on accident)

[flo-sem]

Any activity on this issue?

[niawag]

Hi, I'm facing the same issue with Marvel's SNAP game, I can run it (with proton 7.0-6 and "PROTON_USE_WINED3D=1 %command%" launch option) but it's reaaaally slow.
vkcube command gives:

[default@SteamHeadless ~]$ vkcube
Selected GPU 0: Intel(R) UHD Graphics (TGL GT2), type: IntegratedGpu
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
Could not find both graphics and present queues

I tried playing with xorg.conf (get reseted on container restart) and xorg.conf.d/20-intel.conf that stick after restart but does nothing.
Steam information shows:

Computer Information:
Manufacturer: Intel Corporation
Model: NUC11TNBi3
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz
CPU Family: 0x6
CPU Model: 0x8c
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 4100 MHz
4 logical processors
2 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux 12 (bookworm) (64 bit)
Kernel Name: Linux
Kernel Version: 6.8.0-47-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12101007
X Window Manager: Xfwm4
Steam Runtime Version: steam-runtime_0.20240806.97925
Video Card:
Driver: Mesa/X.org llvmpipe (LLVM 15.0.6, 256 bits)
Driver Version: 4.5 (Compatibility Profile) Mesa 22.3.6
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x8086
DeviceID: 0x9a78
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1680 x 1050
Desktop Resolution: 1680 x 1050
Primary Display Size: 17.52" x 10.94" (20.63" diag), 44.5cm x 27.8cm (52.4cm diag)
Primary VRAM Not Detected

If I run without "PROTON_USE_WINE3D" it gives:

Switching to resolution 1680x1050 failed
Screen: DX11 could not switch resolution (1680x1050 fs=1 hz=0)

I'm not sure of how to get Proton logs or where ot find them, if you can help me I'll provide them !

Did you made any progress on your side ?

[flo-sem]

I followed @alansari s comment trying to modify the Xorg config, but it had no effect just as you are describing

[niawag]

I tried to mount the xorg.conf file directly (to force it's content) but the container won't start because of "70-configure_xorg.sh" that try to edit the file and fail.
So I edited "70-configure_xorg.sh" from inside the container by forcing it to copy my xorg.conf file:

    if ([ "X${monitor_connected}" = "X" ] || [ "${FORCE_X11_DUMMY_CONFIG}" = "true" ]); then 
        print_step_header "No monitors connected. Installing dummy xorg.conf"
        # Use a dummy display input
        # cp -f /templates/xorg/xorg.dummy.conf /etc/X11/xorg.conf --> original line replaced by mine hereafter
        cp -f /home/default/xorg.conf /etc/X11/xorg.conf
    fi

It's running as before with the same exact problem so enabling DRI 3 in xorg.conf does not seem to solve our problem.
Here is my xorg.conf file for reference:

Section "Device"
    Identifier      "Configured Video Device"
    Driver          "dummy"
    VideoRam        256000
EndSection

Section "Monitor"
    Identifier      "Configured Monitor"
    HorizSync       5.0 - 1000.0
    VertRefresh     5.0 - 200.0
    ModeLine        "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync +Vsync
EndSection

Section "Screen"
    Identifier      "Default Screen"
    Monitor         "Configured Monitor"
    Device          "Configured Video Device"
    DefaultDepth    24
    SubSection      "Display"
    Depth           24
    Modes           "1920x1080" "1280x800" "1024x768" "1920x1080" "1600x900" "1440x900"
    EndSubSection
EndSection

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "DRI" "3"
EndSection

Is there something I should change in it ? Are the two Device sections ok ? (I tried to remove the first Device section, xorg process is not starting)
I also tried with this xorg.conf with the same result (working but no DRI3 support):

Section "Device"
    Identifier      "Configured Video Device"
    Driver          "dummy"
    Option          "DRI" "3"
    VideoRam        256000
EndSection

Section "Monitor"
    Identifier      "Configured Monitor"
    HorizSync       5.0 - 1000.0
    VertRefresh     5.0 - 200.0
    ModeLine        "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +Hsync +Vsync
EndSection

Section "Screen"
    Identifier      "Default Screen"
    Monitor         "Configured Monitor"
    Device          "Configured Video Device"
    DefaultDepth    24
    SubSection      "Display"
    Depth           24
    Modes           "1920x1080" "1280x800" "1024x768" "1920x1080" "1600x900" "1440x900"
    EndSubSection
EndSection

[ntn888]

I'm also facing this crash at launch issue with efootball with compatibility layer. the suggested workaround PROTON_USE_WINED3D=1 helps to launch but choppy experience...

[ntn888]

okay it works for me now.. my problem was setting FORCE_X11_DUMMY_CONFIG=true. I had to instead set this to false and use the grub argument mentioned here somewhere to use dummy display..

[1mthesun]

okay it works for me now.. my problem was setting FORCE_X11_DUMMY_CONFIG=true. I had to instead set this to false and use the grub argument mentioned here somewhere to use dummy display..

Do you mind providing a quick walkthrough on how you made this fix? Do you see that it's using gpu + performance is what is expected? Thank you so much

[ntn888]

okay it works for me now.. my problem was setting FORCE_X11_DUMMY_CONFIG=true. I had to instead set this to false and use the grub argument mentioned here somewhere to use dummy display..

Do you mind providing a quick walkthrough on how you made this fix? Do you see that it's using gpu + performance is what is expected? Thank you so much

Note that I'm using an AMD card (an RX580 to be precise). Performance is good - no issues, it's using the GPU as I can hear the fans boosting when playing. This method is to use the software dummy display, as I won't be connecting any monitors physically to the PC..

So in the compose file don't change the FORCE_X11_DUMMY_CONFIG=false setting.

Edit the file /etc/default/grub. Add amdgpu.virtual_display=0000:03:00.0,1 to the line GRUB_CMDLINE_LINUX_DEFAULT. In my case:

GRUB_CMDLINE_LINUX_DEFAULT="quiet amdgpu.virtual_display=0000:03:00.0,1"

Then run sudo update-grub. And reboot.

[Josh5]

So am I right in hearing that we only need to patch this for intel gpus using the dummy driver?

[niawag]

It seems so, the only people affected by this problem are using an Intel integrated gpu.

[SantiagoSchez]

okay it works for me now.. my problem was setting FORCE_X11_DUMMY_CONFIG=true. I had to instead set this to false and use the grub argument mentioned here somewhere to use dummy display..

Do you mind providing a quick walkthrough on how you made this fix? Do you see that it's using gpu + performance is what is expected? Thank you so much

Note that I'm using an AMD card (an RX580 to be precise). Performance is good - no issues, it's using the GPU as I can hear the fans boosting when playing. This method is to use the software dummy display, as I won't be connecting any monitors physically to the PC..

So in the compose file don't change the FORCE_X11_DUMMY_CONFIG=false setting.

Edit the file /etc/default/grub. Add amdgpu.virtual_display=0000:03:00.0,1 to the line GRUB_CMDLINE_LINUX_DEFAULT. In my case:

GRUB_CMDLINE_LINUX_DEFAULT="quiet amdgpu.virtual_display=0000:03:00.0,1"

Then run sudo update-grub. And reboot.

Do you mean editing grub in the host machine? Asking because grub is not even installed in the container.

EDIT: Yes, indeed, it's in the host, as we are creating a virtual display. Just for anyone coming here, don't just copy/paste the previous lines in your grub, as you should modify the PCI address to match yours GPU. Use lspci -D for that