CloD on Linux - (was : GPU process crashing)

[emmett]

hi 8~)

 

I'm getting persistent, multiple GPU process crashes in Mint 20.1 Ulyssa - wondered if there's value for you in me pursuing this..

 

[0420/221725.060758:ERROR:gl_surface_egl.cc(741)] EGL Driver message (Critical) eglMakeCurrent: Failed to make the GLX context current
[0420/221725.061166:ERROR:gpu_service_impl.cc(1124)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[0420/221725.064188:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[0420/221725.064650:WARNING:gpu_process_host.cc(1256)] The GPU process has crashed 2 time(s)
[0420/221725.065924:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[0420/221725.065934:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[0420/221725.067404:INFO:crash_reporting.cc(271)] Crash reporting enabled for process: gpu-process

 

Multiple errors / warnings on msg attachments, but nothin' that looks critical.

 

CloD in Win is running at ~120 fps with no issues yet encountered, but if I can get it running in linux (& Martinsyde's opentrack option works for me) then maybe I can finally ditch Redmond altogether.

 

One quirk so far - under Proton 7.0 and 'Soldier' runtime, I was getting the transparent 'IL*2Sturmovik' splash (sometimes with, sometimes without the Cliffs & Tobruk banners beneath).

 

By the time I got back for a second run at it, Proton 8.0 and 'Sniper' were available; now I get no banners at all, just 'Play' re-enabled in Steam after 15-20 secs.

 

cheers

 

Gigabyte X79-UD5; Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz; Mint 20.1 (64 bit) 5.4.0-147-generic; GTX 960/PCIe/SSE2 4.6.0 NVIDIA 470.182.03

Edited May 1, 2023 by emmett_grogan
forked

[Dawson]

Did you read about the successful running of CloD under Linux on the Atag forum? If no there might be something helpful there. I can't link to it right now.

 

I'm interested to hear any experience running the game under Linux so thanks for sharing.

[emmett]

Hi Dawson - yes, it was that post that got me excited.

 

I used Martinsyde's cod_fix shell script (reported all good, .dll symlinks ok) and his recommended prefix in Steam, but no luck yet.

 

cheers

 

[emmett]

k - still pushing on Martinsyde's suggested strategy re Proton (as per ATAG forum), now have CloD loading in both Mint 20.3 and recent Manjaro.

 

Manjaro (laptop) looks promising but no controllers connected as yet; menu functions & track playback verified, no issues.

 

Mint (desktop) is quirky, game loads mostly but nothing beyond initial menu screens; mouse-over or click on any function ('Open' in track playback, on/off radio buttons or volume sliders in Audio menu) causes game freeze. Still able to kill the process via Steam client but starting to wonder if there's some windowing or xserver issue here, I can find nothing in the Steam logs to suggest the cause. Tried (once) to open FMB, with expected results - blank screen, silence.

 

All controllers correctly ID'ed in logs but unable to test as 'Controls' menu functions cannot be accessed; one time last night, I fired up Steam on Mint & was offered the option to 'Connect' CloD; couldn't resist, clicked & found myself looking at the Manjaro desktop (Steam was running/connected, but pretty sure CloD wasn't running).

 

cheers

 

edit : interesting..

 

SteamOS version 1 'alchemist' and version 2 'brewmaster' have been discontinued. No further updates are planned.

The SteamOS 'clockwerk' prototype has also been discontinued and will not be released.

SteamOS version 3 'holo', as used on the Steam Deck, is a separate codebase based on Arch Linux packages and does not
 use this apt repository.

 

Edited May 1, 2023 by emmett_grogan

[emmett]

Trying to be a bit methodical now..

Several runs this week with Proton logging enabled, various runtime settings in Steam client + one test with Proton Experimental.

Behaviour still largely as described, tho' I sold the volume sliders short in the above - they actually work just fine _until_ I mouse-over or click on the radio buttons.

Manjaro on the same hardware shows identical issues with the menus, so I'm kinda ruling out the diff. in kernel version as a possible explanation for the variation wrt the laptop. What I suspect explains that, is a lack of access to the bumblebee daemon - seems Manjaro don' add yr user to the group at install, hoping to get some time on that machine over the w/end.

What I'm seeing consistently in the logs are these :

 

396.614:0140:0144:trace:loaddll:build_module Loaded L"Z:\\home\\emmett\\.local\\share\\Steam\\steamapps\\common\\IL-2 Sturmovik Cliffs of Dover Blitz\\parts\\core\\D3DCOMPILER_47.dll" at 0000000006AD0000: native
396.615:0140:0144:trace:loaddll:build_module Loaded L"Z:\\home\\emmett\\.local\\share\\Steam\\steamapps\\common\\IL-2 Sturmovik Cliffs of Dover Blitz\\parts\\core\\core.dll" at 0000000005B70000: native
396.799:0140:0144:trace:mscoree:_CorDllMain (0000000005B70000, 1, 0000000000000000)
396.799:0140:0144:err:mscoree:FixupVTableEntry unsupported vtable fixup flags 0

 

476.865:0140:01a8:err:d3d:wined3d_debug_callback 00000000180DE0B0: "GL_INVALID_FRAMEBUFFER_OPERATION error generated. Operation is not valid because a bound framebuffer is not framebuffer complete.".

 

and

 

603.216:0140:01c4:err:sync:RtlpWaitForCriticalSection section 0000000367707980 "../src-wine/dlls/wined3d/wined3d_main.c: wined3d_cs" wait timed out in thread 01c4, blocked by 0154, retrying (60 sec)

 

The latter does not appear, in the most recent run on Manjaro, but the framebuffer error appears twice (once only, on every Mint run); also had an odd 'ghost' screen visible when Alt-Tabbing, tho' unselectable (reverted to main CloD screen) - upper half blue sky 'n' clouds, lower half blank.

 

cheers

 

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.25-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-3820 CPU @ 3.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
======================
Proton: 1682713579 proton-8.0-2c
SteamGameId: 754530
Command: ['/home/emmett/.local/share/Steam/steamapps/common/IL-2 Sturmovik Cliffs of Dover Blitz/Launcher64.exe']
Options: {'forcelgadd', 'wined3d'}
depot: 0.20230405.47175
pressure-vessel: 0.20230405.0 scout
scripts: 0.20230405.0
sniper: 0.20230405.47175 sniper 0.20230405.47175
Kernel: Linux 6.1.25-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Apr 20 13:48:36 UTC 2023 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None

 

[emmett]

Possible candidate - "Multiple games trigger GL_INVALID_FRAMEBUFFER_OPERATION in wined3d"

 

https://bugs.winehq.org/show_bug.cgi?id=49002#c0

 

Fixed in wine dev 8.6, Proton currently on 8.0

 

*sigh*