search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.15k stars 1.06k forks source link

HELLDIVERS™ 2 (553850) #7486

Open NTMan opened 8 months ago

NTMan commented 8 months ago

Compatibility Report

System Information

I confirm:

steam-553850.log steam-553850.log

Symptoms

After selection language in the game, I observe black screen with freezed MangoHud counters and Gnome notification that "steam_app_553850" is not responding. Screenshot from 2024-02-08 14-16-27

UPD:

Now the game freeze after change Graphic settings. Screenshot from 2024-02-09 22-09-12

steam-553850.log

Reproduction

Always

LuxLucian commented 8 months ago

I can get in game but hitting esc to bring up the menu or opening the social menu crashes the game for me.

WhiteEyeDoll commented 8 months ago

Same issue than the initial one. Starts and hangs to a black screen.

WhiteEyeDoll commented 8 months ago

Got the game to launch with GE-Proton7-55. :tada:

caniko commented 8 months ago

Got the to launch with GE-Proton7-55. 🎉

How is it going? Game running well?

LiamDawe commented 8 months ago

Proton 8.0-5 worked just fine on desktop Kubuntu 23.10 here, no crash got into tutorial just fine.

Proton Log: steam-553850.log

For Steam Deck, GE-Proton7-55 worked (other versions did not) but you must launch it in Desktop Mode.

alosarjos commented 8 months ago

Has someone played a game "online"?

VladimirMrzv commented 8 months ago

on my system it works image

Yamy1020 commented 8 months ago

Running on proton 8.0-5 with -d3d11 and it's aight. 55-60+ frames pretty much all the time in a mission no craashes or weird artifacts (Running on lenovo laptop with arch/hyprland ryzen 75800h and nvidia 3060mobile) played 1 mission online no issues there

WhiteEyeDoll commented 8 months ago

Game is runnin good on GE-Proton7-55. Servers had some hickups early but no issues currently. Multiplayer works.

SchnozzleCat commented 8 months ago

Can confirm it works with GE-Proton7-55 on Nixos running Hyprland. I could play and finish mission.

Going into the main menu (ESC) crashes instantly for me however.

Edit: The menu crash was present on windows as well and has since been hotfixed.

zrooda commented 8 months ago

The 1.3 GB patch allowed me to play a full game in multiplayer on GE-7-55 and Esc didn't crash the game. That said the game crashed after loading back to the ship and now can't be run anymore without hanging on load (I have a feeling it's because I changed windowing to full-screen).

LuxLucian commented 8 months ago

New update now has me stuck in a black screen while booting.

stevebalk commented 8 months ago

Sadly, not working for me. Start video is running, then one female Soldier speaks to another and it freezes. Most times even before the soldier starts to speak. Sometimes opens the nProtect Gameguard FAQ Website by itself, maybe it could not be loaded?!

GPU: NVIDIA RTX 2070 Super Video driver version: NVIDIA 545.29.06 Kernel version: 6.6.10-76060610-generic Proton version: Proton Experimental / GE-Proton8-30 / GE-Proton7-55 / Proton 8.0-5

WhiteEyeDoll commented 8 months ago

Still working after update using GE-Proton7-55.

Found issues so far:

/<LIBRARY_DIR>/SteamLibrary/steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/user_settings.config

fullscreen = false
borderless_fullscreen = true
LuxLucian commented 8 months ago

New update now has me stuck in a black screen while booting.

I fixed it by modifying the config file and dropping the quality settings /steamapps/compatdata/553850/pfx/drive_c/users/steamuser/AppData/Roaming/Arrowhead/Helldivers2/user_settings.config

I went in and muddled a bunch of numbers until the game booted, then I used the menu to config my settings. Changing "graphics_preset" to 1 or 2 should also work too.

chookity-pokk commented 8 months ago

I fixed it by modifier the config file and dropping the quality settings

@LuxLucian Just a tip, if you've fixed it by modifying something then probably also put the location of the file and the modification that you made. Because that's the first thing someone is going to ask about a comment such as yours.

DomiStyle commented 8 months ago

On Steam Deck I was able to just download the game and run it now, didn't have to switch to desktop mode or switch Proton versions at all.

On desktop I still need to use GE-Proton7-55 but it runs fairly well with that. Proton Experimental and Proton 8 run into the blackscreen issue.

ESC menu works as well since the last game update.

WhiteEyeDoll commented 8 months ago

GE-Proton8-30 works now!

Seems that something has been updated with the GameGuard configuration server side as no patches have landed to the game nor Proton.

Also all of the issues I mentioned in my earlier comment got fixed with the newer Proton version.

zrooda commented 8 months ago

FYI game still hangs on launch with fullscreen even on GE-8-30

calvinbull commented 8 months ago

GE-Proton8-30 works now!

Seems that something has been updated with the GameGuard configuration server side as no patches have landed to the game nor Proton.

Also all of the issues I mentioned in my earlier comment got fixed with the newer Proton version.

I'm still seeing the white border even with GE 8-30.

Also, as of today the game is consistently crashing my system at random intervals (not just the game process). Hard to track down what might be causing it because all background processes that I can see also freeze/die alongside my keyboard and mouse - only way out is a manual reboot.

It might be the vague AMD issue floating around as I have 7800x3d CPU / 7800xt GPU but difficult to say. I implemented the 'fix' (for windows users at least) listed in some discussions of disabling anti-aliasing and global illuminations which had no impact. Getting the crashes on 8-30 as well as 7-55 despite not having these issues yesterday.

WhiteEyeDoll commented 8 months ago

FYI game still hangs on launch with fullscreen even on GE-8-30

Yes, seems it's 50/50 that the game launches or hangs to a black screen with fullscreen enabled.

alosarjos commented 8 months ago

Was there a proton Hotfix release for this game?

Voronsky commented 8 months ago

I am currently trying it out with GE-8-30. Unfortunately, I have been met with nothing but crashes during the initial menus. I can't get far along enough without it crashing. The game starts in full-screen mode, so I see the white border. I did notice a proton hotfix that came with the initial game download.

Update Switched to Proton Hotfix in the compatibility drop-down and re-validated the game. The game launched without crashes, but I only played with it after finishing the training zone. I switched back to GE-8-30, and I was able to run around on my deck. I did notice that changing the graphics setting makes it crash, however (e.g., Anti-aliasing), regardless of Proton version.

My system

Screenshot from 2024-02-09 23-13-33 Screenshot from 2024-02-09 23-14-46

zrooda commented 8 months ago

GE-8-31 just released, I'm seeing ~10% more fps but take it with a grain of salt

updated wine to latest bleeding edge, allows helldivers to run

mtorromeo commented 8 months ago

It might be the vague AMD issue floating around as I have 7800x3d CPU / 7800xt GPU but difficult to say. I implemented the 'fix' (for windows users at least) listed in some discussions of disabling anti-aliasing and global illuminations which had no impact. Getting the crashes on 8-30 as well as 7-55 despite not having these issues yesterday.

What helped me reduce the crashes (7900xt GPU) was generally reducing graphics settings. Disabling global illumination is just one of the possible settings but for example while having ultra texture details the crashes were extremely frequent and since I reduced it to medium and lowered a few other settings it did not crash yet, but I still have to test it a bit more.

This seems to point to a bug in amdgpu, and the same issue also happened to me 3 times while playing A Plague Tale Requiem, but a friend of mine was having similar crashes on Windows with the same GPU and reducing graphics settings also helped him.

This is what I logged while remotely connected to the system via SSH: ``` [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=1751122, emitted seq=1751125 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process helldivers2.exe pid 20850 thread vkd3d_queue pid 21005 amdgpu 0000:0d:00.0: amdgpu: GPU reset begin! amdgpu 0000:0d:00.0: amdgpu: IP block:gfx_v11_0 is hung! amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process pid 0 thread pid 0) amdgpu 0000:0d:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10 amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B53 amdgpu 0000:0d:00.0: amdgpu: Faulty UTCL2 client ID: CPC (0x5) amdgpu 0000:0d:00.0: amdgpu: MORE_FAULTS: 0x1 amdgpu 0000:0d:00.0: amdgpu: WALKER_ERROR: 0x1 amdgpu 0000:0d:00.0: amdgpu: PERMISSION_FAULTS: 0x5 amdgpu 0000:0d:00.0: amdgpu: MAPPING_ERROR: 0x1 amdgpu 0000:0d:00.0: amdgpu: RW: 0x1 amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process pid 0 thread pid 0) amdgpu 0000:0d:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10 amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 amdgpu 0000:0d:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) amdgpu 0000:0d:00.0: amdgpu: MORE_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: WALKER_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: PERMISSION_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: MAPPING_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: RW: 0x0 amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process pid 0 thread pid 0) amdgpu 0000:0d:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10 amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 amdgpu 0000:0d:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) amdgpu 0000:0d:00.0: amdgpu: MORE_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: WALKER_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: PERMISSION_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: MAPPING_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: RW: 0x0 amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:169 vmid:0 pasid:0, for process pid 0 thread pid 0) amdgpu 0000:0d:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10 amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 amdgpu 0000:0d:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) amdgpu 0000:0d:00.0: amdgpu: MORE_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: WALKER_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: PERMISSION_FAULTS: 0x0 amdgpu 0000:0d:00.0: amdgpu: MAPPING_ERROR: 0x0 amdgpu 0000:0d:00.0: amdgpu: RW: 0x0 Failed to wait all pipes clean amdgpu 0000:0d:00.0: amdgpu: soft reset failed, will fallback to full reset! [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx amdgpu 0000:0d:00.0: amdgpu: MODE1 reset amdgpu 0000:0d:00.0: amdgpu: GPU mode1 reset amdgpu 0000:0d:00.0: amdgpu: GPU smu mode1 reset amdgpu 0000:0d:00.0: amdgpu: GPU reset succeeded, trying to resume [drm] PCIE GART of 512M enabled (table at 0x00000084FEB00000). [drm] VRAM is lost due to GPU reset! [drm] PSP is resuming... [drm] reserve 0x1300000 from 0x84fc000000 for PSP TMR amdgpu 0000:0d:00.0: amdgpu: RAP: optional rap ta ucode is not available amdgpu 0000:0d:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available amdgpu 0000:0d:00.0: amdgpu: SMU is resuming... amdgpu 0000:0d:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x0000003f, smu fw program = 0, smu fw version = 0x004e6601 (78.102.1) amdgpu 0000:0d:00.0: amdgpu: SMU driver if version not matched amdgpu 0000:0d:00.0: amdgpu: SMU is resumed successfully! ```
jakswa commented 8 months ago

Still getting crashes after 30min-1hr on GE-8-31. AMD CPU/GPU. All graphics set to lowest, resolution reduced, scaling set to performance -- if this was medieval era, picture me at the alter bathed in blood, carcasses spread around me, dragging anything I can find up, red spurts appearing around me as I find another setting to reduce.

edit: joking aside, seems like these issues are on the game and seem cross-platform, only wanted to give a sample that GE-8-31 doesn't magically fix the crashes for AMD

zrooda commented 7 months ago

The GCVM_L2_PROTECTION_FAULT errors don't seem to be necessarily local to just Helldivers, you could try some of the fixes mentioned in the convos below. I seem to be having the same problem on my 5800X3D / 6700 XT, booted back to gdm after the driver hard resets, usually after ~2 hrs of playing.

https://bbs.archlinux.org/viewtopic.php?id=284076 https://gitlab.freedesktop.org/drm/amd/-/issues/2496 https://gitlab.freedesktop.org/mesa/mesa/-/issues/8241

kisak-valve commented 7 months ago

HELLDIVERS™ 2 (553850) No connection to server.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/7491. @19Topgun93 posted on 2024-02-11T12:20:15:

Compatibility Report

System Information

``

Symptoms

After a update from Helldivers 2. It starts with no problems. I have connect my Playstation account to Steam. But at the start screen, I cannot connect to servers. The attachment. Bildschirmfoto vom 2024-02-11 12-18-21

I have reinstall the game twice, but the Problem is still there. In Protondb, it has now Gold status. Can you help me please?

Reproduction

By me. I start the game and that's it.

steam-553850.log

alosarjos commented 7 months ago

Right now servers are down / having issues, not related to Linux / Proton.

19Topgun93 commented 7 months ago

@kisak-valve Aaaaah ok. Thanks kisak. I thought per problem. Thanks I know it now for the next time :)

Thanks for answering on sunday :D

HoroTW commented 7 months ago

hey hey, I just wanted to let you know that it worked for me after I switched to the Nvidia beta drivers in aur and disabled shader caching in Steam. :+1:

archnecro commented 7 months ago

Even on Proton GE 8-32 I can't get past the nProtect gameguard download. It tries to download it but can't connect and times out. Anyone have any experience with this? I feel like I am the only one who can't get into the game. On Arch Linux.

jakswa commented 7 months ago

for anyone else with AMD 7000 series GPUs experiencing GPU driver crashes (system lockup), I've been following a support thread on steam discussions for updates (and sadly it's been quiet): https://steamcommunity.com/app/553850/discussions/1/4206994023681197128/

An excerpt:

Critical problems for players using the AMD Radeon 7000 series of GPUs

The Problem: There are all sorts of significant problems players with these GPUs are experiencing, in total making the game nearly unplayable.

Why It Happens: We aren’t sure at the moment. We had tested with these GPUs previously and hadn’t encountered this in-house, but clearly there is something deep that is wrong.

Frequency: This is a constant issue for these users.

What We’ve Done / Are Doing: This one needs some investigation, and our team is looking at it in collaboration with AMD. Please watch this space: we will update when we have more details on this matter.

gabriele2000 commented 7 months ago

In my case, using:

The game freezes constantly after one or two minutes, changing everything to low doesn't help yet, also it doesn't help that this game cannot run in DX11 mode, such a shame.

Using Proton Hotfix BTW.

DanCanGit commented 7 months ago

Throwing my 2 cents into the hat, 5700x CPU, RTX 2070 on 535.133.1 running EndeavourOS, it seemingly gets past the gameguard install, boots, and gets to the start of the dropship/droppod cutscene before freezing on any versions of proton, GE or not.

Currently, the error which stands out is

:err:winstation:map_shared_memory_section failed to open section L"\KernelObjects\__wine_thread_mappings\00000148-input": c0000034

This is has been attempted with both default settings, and a config file shared by a windows user with all settings set to their lowest values, shader pre caching enabled/disabled.

proton log as gist: https://gist.github.com/DanCanGit/81d9becef663ca8f66bbbe00ea2f3b9c

kisak-valve commented 7 months ago

Helldivers 2 not launching on steamdeck after trying all the common fixes

Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/10498. @Binksbrew123 posted on 2024-02-13T00:04:13:

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist I have tried every Proton version that has been said to work Including the most recent 8-32 and trying without forcing compatibility. I have increased the VRAM and tried in both game and desktop mode. I deleted the compatdata folder. I moved the game from my microSD to and external hard drive (I have the 64 gb steamdeck). The game just launches to the steam logo and then crashes.

Steps for reproducing this issue:

Voronsky commented 7 months ago

Update If anyone sees this issue, it has something to do with the user-settings.json being corrupted and needing to be replaced in the AppData/Roaming/Helldivers2 folder.

There seems to have been an update that was rollbacked according to their discord announcements, and now whatever methods described here to work no longer work. I can launch the game, but then it crashes after a few seconds before it gets to the intro. I've had this happen with Proton Hotfix, Proton Experimental, GE-8-32, and GE-8-30

Video Card: Driver: AMD AMD Radeon RX 6750 XT (navi22, LLVM 15.0.7, DRM 3.57, 6.7.3-060703-generic)

Operating System Version: Ubuntu 23.10 (64 bit) Kernel Name: Linux Kernel Version: 6.7.3-060703-generic

My steam log is attached: steam-553850.log

Picture of the crash Screenshot from 2024-02-12 21-33-49

gabriele2000 commented 7 months ago

@DanCanGit shame on me, I couldn't even get a similar log out of proton, heh!

gabriele2000 commented 7 months ago

After the game locks itself, the gameguard FAQ opens, I don't know why.

M-Alonzo commented 7 months ago

My experience with this game so far has been: I spent over 3 hours on Sunday trying several things (proton versions, graphics settings, verifying, etc) to get past the tutorial due to constant crashing. It would lock up anywhere from the encrypted message bit, the cutscene on the dropship, or mid way through the tutorial mission, crash my desktop, and kick me out to GDM.

For reference I'm on Nobara 39, Gnome desktop Wayland session, Ryzen 5 1600AF, Radeon RX 6650 XT. Game is using Proton Hotfix. Borderless window because fullscreen was not working.

I nearly gave up but I decided to try the game on the Xorg session before I quit, and wouldn't you know it, I was able to make it past the tutorial on the first try. Made it onto the ship, dropped on a solo mission, exited the pod... and then it crashed. Okay, so I went back and lowered some settings like turning off Global Illumination, etc. I tried this before on Wayland in the tutorial (I tried the lowest settings) but this time I was able to play 4 or 5 solo missions without crashing.

On Monday I went back to the Wayland session and played around 10 missions on multiplayer. I haven't had any crashes since Sunday.

TL:DR: For some unknown reason, switching to Xorg stopped the constant crashing.

gabriele2000 commented 7 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/7486#issuecomment-1941986377

I've already tried the game using the X11 session, to no avail. The fact that the crash happened less then it's not happening anymore isn't exactly a fix, since it could mean other underlying issues.

ThisNekoGuy commented 7 months ago

Not sure why, but my primary issue seems to be that on every subsequent launch of the game (any launches after the 1st one), the game locks up on a black screen after the window initializes. The only solution I've found for it is to delete the proton prefix and re-launch the game, but it's a tedious and incredibly annoying process because it forces me to reconfigure game and graphics settings upon doing so.

zrooda commented 7 months ago

Not sure why, but my primary issue seems to be that on every subsequent launch of the game (any launches after the 1st one), the game locks up on a black screen after the window initializes. The only solution I've found for it is to delete the proton prefix and re-launch the game, but it's a tedious and incredibly annoying process because it forces me to reconfigure game and graphics settings upon doing so.

Sounds like you're setting the window to fullscreen.

ThisNekoGuy commented 7 months ago

I have been doing that because, if I don't, the borderless window leaves a distracting white line along the bottom of my screen.

zrooda commented 7 months ago

I have been doing that because, if I don't, the borderless window leaves a distracting white line along the bottom of my screen.

Yeah borderless window doesn't fully stretch but the game currently doesn't launch with fullscreen, as mentioned several times in this issue. It might work with gamescope, not sure anyone tried yet. Or you could set fullscreen while playing and change it back before exiting the game. Or just edit the config file so you don't have to delete the entire prefix.

DomiStyle commented 7 months ago

Set the game to borderless fullscreen before you exit and set it to fullscreen after launch.

That way you can play without border and still have the game launch.

If you messed up you can edit the config file for the game and disable fullscreen in there. No need to recreate the prefix.

No crashes here on the 6900 XT with Wayland either.

zrooda commented 7 months ago

Not sure if it's today's update or upgrading to 6.7.4 kernel and 23.3.5-1 mesa but I'm not crashing with GCVM_L2_PROTECTION_FAULT anymore 🥳

gabriele2000 commented 7 months ago

@kisak-valve sorry for the direct ping, this log might interest you, that's my error. steam-553850.log

kisak-valve commented 7 months ago

Not that it helps directly, but the log hints towards an access violation (c0000005) in a thread called winepulse_timer_loop, suggesting some kind of audio related snafu.

calvinbull commented 7 months ago

Not sure if it's today's update or upgrading to 6.7.4 kernel and 23.3.5-1 mesa but I'm not crashing with GCVM_L2_PROTECTION_FAULT anymore 🥳

@zrooda Today's update certainly didn't fix anything for me. I normally stay away from cutting edge kernel releases, but I'll give 6.7.4 a try tonight and update here if it helps. As of now I'm getting a 100% crash rate (full GPU driver crash) between 1-20 minutes of starting the game.

UPDATE: I updated to latest 6.7.4 kernel, my mesa was already at the latest for my distro. Managed ~20 minutes before full system crash, so this wasn't the fix for me. Specs:

OS: Pop!_OS 22.04 LTS x86_64 DE: GNOME 42.5 Host: A620I Lightning WiFi Kernel: 6.7.4-x64v4-xanmod1 CPU: AMD Ryzen 7 7800X3D (16) @ 5.050GHz GPU: AMD 7800XT OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.3.2-1pop0~1704238321~22.04~36f1d0e Proton: GE-Proton8-32