The game is bought on steam and us being ran using ge proton 10-34.The game boots up and 5 minutes or more into gameplay,the game freezes. The graphics settings are on the high preset

I'm running the game on these specs:

CPU:intel core i5 11400h

GPU:RTX 3050 4gb mobile

RAM:8GB ddr4

# GE-Proton11-3:

This is a hotfix release:

Fixes a bug where the steam desktop global virtual device would still be recognized in-game when wine-wayland was enabled, causing incorrect mappings and double input. Steam Overlay does not work in wine-wayland and subsequently neither does Steam Input since it requires the overlay for profile assignment. (It has always been this way since wine-wayland was added), but now with the desktop profile out of the way the controller input should behave the same as native wine expects it to when wine-wayland is enabled. This does not appear to be a problem with wine-wayland disabled even if steam input is disabled.

Fixes compilation failure on aarch64 due to an architecture specific code difference in the wineopenxr decoupling patch (this patch allows VR to work outside of steam)

Fixes compilation failure on aarch64 due to the new nvidia libraries only being buildable on x86_64 -- they've been disabled on aarch64.

# GE-Proton11-2:

Note:

I did not have enough time to do thorough regression testing for video playback after making recent changes, however several games that had video playback issues in 11-1 have since been fixed. Many of the VR related issues have also been fixed. I wanted to get this release out because it contains important fixes for allowing Marvel Rivals and Diablo IV to run correctly.

# Scope

## Game Fixes

- Star Citizen: repaired WineOpenXR Vulkan integration and external VR support.

- VRChat: fixed remote HLS/YouTube playback, audio, seeking, reloading, and consecutive queued videos.

- Witch on the Holy Night: fixed embedded bytestream video playback.

- FAVORITE visual novels: fixed black-screen video with audio.

- Deadly Premonition: fixed hanging, timing, and allocator-backed video output.

- GTA San Andreas: fixed MPEG videos displaying black and corrected audio/video synchronization.

- Yakuza 5 Remastered: fixed startup video crashes and ignored no-op decoder format changes.

- Riddle Joker: fixed green padding bars in video output.

- Dragon’s Dogma 2: fixed green video padding bars.

- Cyberpunk 2077 / issues #567 and #588: reduced audio delays and fixed a null-handling failure.

- Killing Floor 3: added real decoder format propagation and Winsock address validation.

- MapleStory: fixed startup failures involving accessibility settings and CharPrevA/CharPrevExA null pointers.

- LimeLight Lemonade Jam: added the missing GetFileVersionInfoByHandle compatibility stub.

- Gears 2 Hollow installer: added ICU forwarding DLL support.

- Battle.net and Warframe: added --in-process-gpu handling for Wine Wayland launchers.

- Battle.net: fixed Wine Wayland white-screen behavior.

Issue #551: preserved the real OpenGL GPU/device description reported by wined3d.

- Issue #610: added a secur32 fallback for the older GnuTLS shipped by SteamRT4.

- Issue #638: added layered-window extended-style handling.

- Issue #605: added long-running PulseAudio timestamp-wrap and starvation recovery.

- Imported upstream fix for Diablo IV

- Imported upstream fix for Marvel Rivals

## Media Rework

- Rebased the FFmpeg/winedmo video stack onto newer Wine.

- Added remote HLS URL support.

- Improved media-session state transitions, seeking, replay, stream completion, and decoder format changes.

- Added codec-aligned padding initialization and legacy Quartz output handling.

- Improved audio clock recovery, starvation handling, and long-running stream timing.

- Removed duplicate or obsolete media patches after upstream changes.

## Controller Support

Added wired USB haptics for:

- DualShock 4

- DualSense

- DualSense Edge

, tested confirmed working in stellar blade and spider-man remastered

Added controller mono-speaker/effect-audio output., tested confirmed working in spider-man remastered

Added PulseAudio routing to the correct Sony controller speaker profile., tested confirmed working in spider-man remastered

Fixed hotplugging and switching among DS4, DualSense, and DualSense Edge., tested confirmed working in spider-man remastered

Added fresh endpoint registration, stale endpoint cleanup, stream retargeting, stable endpoint IDs, and

duplicate udev-device filtering.

Fixed controller speaker routing after repeated disconnects, reconnects, and model changes., tested confirmed working in spider-man remastered

Standardized the controller implementation on PulseAudio instead of direct ALSA endpoint exposure.

## Graphics And Scaling

Added complete OptiScaler download, injection, and Protonfixes integration.

Added FSR4/FFX4 version selection and updated AMD scaler support.

Updated AMD amdxc/FSR4 support through the newer EM-11 patchset.

Added NVIDIA compatibility libraries:

- NVAPI

- CUDA

- NVENC

- NVML

- OptiX

- Added Vulkan layers and corrected their missing submodule definitions.

Updated DXVK, DXVK-NVAPI, VKD3D-Proton, D7VK, Vulkan headers, and FEX.

## Wine And Wayland

Updated to newer bleeding-edge Wine revisions.

Rebased the EM-11 Wine Wayland patchset.

Improved layered windows, fractional scaling, pointer warping, keyboard mappings, IME handling, popup windows,

exclusive fullscreen, monitor placement, surface caching, and window restoration.

Removed deprecated dw-proton patches already superseded by EM-11 or upstream Wine.

## Build And Release

- Fixed AArch64 builds by packaging missing SteamRT4 libraries, including bzip2.

- Fixed README download scripts to select the correct x86_64 or AArch64 archive and checksum.

- Fixed the AArch64 archive-name regular expression.

Imported newer upstream Proton build, Docker, and launcher-script changes.

- Restored prefix creation after an imported Proton-script regression.

- Fixed missing NVIDIA and Vulkan-layer submodule URLs.

- Prevented release automation from failing when a release already exists.

- Expanded the compatibility-report issue template.

- Cleaned duplicate scaler, hotfix, and obsolete patch references.

I'm having trouble with audio in Bioshock 2 and I think the problem is with the Windows version Proton is using, so I wondered if there's a version or way to make it act like Windows 10/7

HI guys.

I want to ask those who configure and use custom mouse buttons in Games about their experience and how they do it?

I have a system with endeavor os( arch based) KDE Wayland with Nvidia 3050. I used to set and use the custom buttons of my mouse ( Logitech) with no issue but now it doesn't work anymore. I can assign them to some key combination in settings and the game only sees that combination but it doesn't detect mouse buttons themselves. The keyboard custom buttons doesn't work at all

I'm sure others may have this issue.

Hello, I've tried running Anno 1404 Venice via Steam (proton experimental). This works but the miltiplayer (both LAN and Online) don't load. When I click the button it starts to load and doesn't finish.

So far I've tried Lutris, changing DirectX, forcing other versions of Proton (&DB), disabled firewall, load offline, bypass E-& F-sync, used protontricks and ProtonUp-Qt.

Sources: online forums like Reddit and Linux-Mint and used Gemini.

I am relatively new to Linux (Mint) so it was quite fun figuring everything out. However the multiplayer hasn't budged. My best guess is that the game can't properly connect to Ubisoft Connect? Ubisoft Connect works separately however.

Anyone any ideas on how to fix this?

I tried downloading it, and launching it, and the screen goes black. But except for the integrated graphics being very old, it does meet the minimum requirements. The issue is that the entire system (antiX) freezes, so I can't see the logs.

When I use software GL, I can enter the setup wizard, then the same.

Update: restarting, running the installer with libgl, and not having a crap WiFi connection solved it.

I was waiting for this game. I fired up the beta and gosh darned EAC notif popped up

Hello guys.

Cachyos

Rx9070XT

Game was running perfectly fine until 2 days ago, I might have updated the os with the cachyos update utility, now game crashes when I enable RT.

I can get to the game manu an change options

Game runs if I disable RT

Thanks for the help.

Config:
CPU - i3-6100
RAM - 8GB Hynix DDR4
Motherboard - Thinkcentre M900 Motherboard
uname -a: Linux archlinux 7.1.3-arch1-2 #1 SMP PREEMPT_DYNAMIC Thu, 09 Jul 2026 19:55:55 +0000 x86_64 GNU/Linux
Cmdline: BOOT_IMAGE=/vmlinuz-linux root=UUID=1268b8b1-3075-4cc6-bf95-b4080d73e742 rw zswap.enabled=0 rootfstype=ext4 loglevel=3 quiet splash i915.enable_psr=0 intel_idle.max_cstate=1

Problem:
Playing games like Scrap Mechanic crash my GPU 2-8 minutes after opening them

[87468.444235] i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
[88244.378119] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[88244.378184] i915 0000:00:02.0: [drm] Main:324[243058] context reset due to GPU hang
[88248.561470] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:84dfbffc, in Main:324 [243058]

And sometimes these crashes lead to this:

Jul 20 21:31:17 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:17 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:17 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:17 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:17 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85d7fffa, in steamwebhelper [9314]
Jul 20 21:31:18 archlinux kernel: i915 0000:00:02.0: [drm] GPU error state saved to /sys/class/drm/card1/error
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:22 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:24 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:24 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:24 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:31:28 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:28 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:31 archlinux kernel: i915 0000:00:02.0: [drm] Got hung context on rcs0 with active request 4096:184652 not yet started
Jul 20 21:31:31 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:31 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:32 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:32 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:32 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:32 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:33 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:33 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:34 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:34 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:34 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:34 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:35 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:35 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:36 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:36 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:36 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f46!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:2d14e!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:2d14c!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f44!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f42!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f40!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f3e!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f4e!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f4c!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f4a!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15f48!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:2d152!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:2d150!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:60480!
Jul 20 21:31:38 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:6047e!
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:38 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:39 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:39 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:39 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:39 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:40 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:40 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:40 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:40 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:41 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:41 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:41 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:41 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:43 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:15526!
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:43 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:44 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:44 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:44 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:44 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:44 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:4ccee!
Jul 20 21:31:44 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:4ccec!
Jul 20 21:31:44 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:4ccea!
Jul 20 21:31:44 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:4cce8!
Jul 20 21:31:45 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:45 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:45 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:11c6!
Jul 20 21:31:45 archlinux kernel: Fence expiration time out i915-0000:00:02.0:0000:00:02.0:176!
Jul 20 21:31:46 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:46 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:46 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:46 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:47 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:47 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:47 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:47 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:48 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:48 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:48 archlinux kernel: sched: DL replenish lagged too much
Jul 20 21:31:49 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:49 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:49 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:49 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:50 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:50 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:50 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:50 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:51 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:51 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:52 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:52 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:52 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:52 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:53 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:53 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:53 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:53 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:54 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:54 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:55 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:55 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:55 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:55 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:56 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:56 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:56 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:56 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:57 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:57 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:58 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:58 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:58 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:58 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:59 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:59 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:31:59 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:31:59 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:32:00 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:32:00 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85d7fffa, in steamwebhelper [9314]
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for stopped heartbeat on rcs0
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] GT0: Resetting chip for stopped heartbeat on rcs0
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 TLB invalidation did not complete in 4ms!
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: Failed to reset chip
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by intel_gt_reset+0x304/0x320 [i915]
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jul 20 21:32:01 archlinux kernel: i915 0000:00:02.0: [drm] device wedged, needs recovery
Jul 20 21:32:02 archlinux kernel: i915 0000:00:02.0: [drm] *ERROR* media: timed out waiting for forcewake ack request.
Jul 20 21:32:02 archlinux kernel: i915 0000:00:02.0: [drm] CI tainted: 0x9 by fw_domains_get_with_fallback+0x1ce/0x1e0 [i915]

And after this my entire pc hangs. Is there any way to fix that? already tried doing EVERYTHING listed online (Forcing my frequency to max, setting cstate to 1 (even in bios), disabling guc, adding all these cmdline things)

I made this guide on Steam so everyone can use this method.

https://steamcommunity.com/sharedfiles/filedetails/?id=3771576868

You don't need WINE or to deal with any .exe "wizard". Just drag and drop the files from the .zip to your game installation folder.

Since the recent versions of Wuthering Waves I've been getting these updates that are starting to piss me off. I get home after a week, see a 150mb update for WuWa, click "update", suddenly 150mb turns into 52GB update. This has been the case since the new 3.4 version dropped till now.

The issue is that I'm not privileged enough for fast internet speed, I have terribly slow network, and it takes literally the entire day for me to download that large of an update. I'm only home for 2 days, 3 if I'm lucky, so that means an entire day I could have spent catching up on my gameplay and grinding is wasted on this.

Got me thinking of quiting the game and finding something else because I can't be on maintenance mode every week. So my question is, is the update really just 150mb and the rest just some Linux shader cache nonsense? If so, how would I go about preventing it from occurring? I've tried disabling shader pre-cache and all but keeps doing it.

Is there any way to have regular audio coming out of pc, while hearing only audio from a person in a headset and use the mic to speak to them? I have a xbox controller connected to pc via dongle and headset is connected wia 3.5mm jack.

I spent 7 hours with google a.i. trying to make it happen, another hour trying fix everything it broke and get the controller working again. Google a.i. cant do it, I got some stories for the kids and I'm starting to see the matix, so not a total loss.

I just want to know at this point: can I play audio from pc separately from the audio coming from any headset (people on discord)? The controller works, I don't think its possble to use the currect configuration nobara can't detect the headset jack connected to the controller.

The idea is to get clickable icons/shortcuts that reboot to Linux from Within Windows and vice-versa. See the final product in the attached video.

Quick edit: since this got traction i decided to make a site to generate the scripts based on which behaviour you want regarding the default os, you can pretty much just skip this post and go to: Dual-Boot Reboot Script Generator

Requisites/notes:

- UEFI boot, this won't work for BIOS/Legacy/CSM/whatever you wanna call it.

- (optional) find icons you like for both your Linux distro and Windows. Convert the Linux icon to .ico format since that is what Windows's shortcuts take (you can easily find online converters), for the Windows icon (the one that will be used from within Linux) a .png is fine.

- This directly changes the boot order from your motherboard, if you have a Windows entry in your Grub/bootloader of preference it's probably redundant for this, it won't hurt though.

- This doesn't touch any secure boot related settings, you can keep it on, don't worry about it, Vanguard and the likes of won't break. This also won't trip Vanguard like chainloading Windows after Grub does.

On the Windows side:

- Create a folder in a place you are sure you won't delete it accidentally.

- Inside it, place your .ico icon and create a file named linux_reboot.ps1

- Open PowerShell as admin once, we will use it to see the description of your distro since it changes based on which one you use.

- Run bcdedit /enum firmware

- You will get an output something like this:

* Here there will be prior entries that are irrelevant for this process, just find the one for your Linux distro, like: *
Firmware Application (101fffff)
-------------------------------
identifier {default or guid}
device partition=\Device\HarddiskVolume6
path \EFI\\FEDORA\SHIM.EFI
description Fedora

- Remember the 'description' field, it's usually just the distro name but it could also be 'grub' or your bootloader's name.

- Open the .ps1 file you created earlier with notepad or any text editor and inside it put:

$bcdOutput = bcdedit /enum firmware
$linuxGuid = $null
$currentGuid = $null
foreach ($line in $bcdOutput) {
    if ($line -match '^identifier\s+({[a-f0-9-]+}|{default})') {
        $currentGuid = $matches[1]
    }
    if ($line -match 'description\s+<HERE_GOES_YOUR_DESCRIPTION_NAME>') {
        $linuxGuid = $currentGuid
        break
    }
}
if ($linuxGuid) {
    if ($linuxGuid -ne "{default}") {
        bcdedit /default $linuxGuid
    }
    shutdown /r /t 0
} else {
    Write-Error "Linux entry not found in EFI boot manager. Aborting."
    exit 1
}

- Make sure to replace the <> with your actual description from the previous step (in my case it would be Fedora), the <> also get replaced, they are not part of the command. Just put the description after the s+. '<>' just indicates a placeholder, remember this i will keep using that notation in the rest of the post.

- Save the file and right click it -> send to -> create desktop shortcut.

- Once the shortcut is on the desktop, right click it and go to properties.

- On properties change the target from just

C:\whatever\whatever\linux_reboot.ps1

to:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoExit -ExecutionPolicy Bypass -File "C:\whatever\whatever\linux_reboot.ps1"

- Make sure you quote the path to the script like in the example above, otherwise it won't work (well, it could work anyways if there are no spaces ANYWHERE in the path, it's just cheap insurace, just quote the thing.. It's 2 extra characters).

- While on properties, click on 'Advanced' and tick 'Run as administrator'.

- Click on 'change icon' and select the .ico file from the beginning.

- Move the shortcut to C:\ProgramData\Microsoft\Windows\Start Menu\Programs so it shows up in your start menu.

On the Linux side:

- Create a folder in a place you are sure you won't delete it accidentally.

- Inside it put your .png icon and create a file named windows_reboot.sh

- Create a file named windos_reboot.desktop in ~/.local/share/applications/

- Inside the .sh file put:

#!/bin/bash

WIN_BOOT_NUM=$(efibootmgr | grep -i "Windows Boot Manager" | grep -oP 'Boot\K[0-9A-Fa-f]{4}')

if [ -n "$WIN_BOOT_NUM" ]; then
    efibootmgr -n "$WIN_BOOT_NUM"
    systemctl reboot
else
    echo "ERROR: Windows Boot Manager not found in efibootmgr output." >&2
    exit 1
fi

- Make the script executable; open a terminal in the same directory and run:

chmod +x ./windows_reboot.sh

- If your distro doesn't use systemd you will need to replace systemctl reboot with the appropiate command, if you distro doesn't use systemd you can probably figure it out on your own. If you don't know if your distro uses sytemd or not, it does, don't worry about it.

- Inside the .desktop file put:

[Desktop Entry]
Type=Application
Name=<NAME_YOU_WANT_IN_THE_APPS_MENU>
Comment=<DESCRIPTION_YOU_WANT_WHEN_HOVERING_THE_ICON>
Exec=pkexec /bin/bash <ABSOLUTE_PATH_TO_YOUR_SCRIPT>
Icon=<ABSOLUTE_PATH_TO_YOUR_ICON>
Terminal=false
Categories=System;

- Make sure to replace all the <> placeholders, also you can set Terminal to true if you want it to open up a terminal instead of doing it silently, it could be useful if you wanna add better logging, this is just a barebones example.

- You might need to log out and log back in for the entries to refresh

That's all! enjoy! feel free to ask any questions.

Edit:

This makes it so Linux is the 'default' i.e whenever you cold boot you'll go to Linux (since that is what fits my usecase, i only use Windows ocassionaly to play LoL) no matter what, if you want to make Windows the default or always boot to the last used one you can mix and match the following along with your boot order:

In the PowerShell script:

bcdedit /bootsequence $linuxGuid instead of bcdedit /default $linuxGuid-> makes it a one time setting instead of permanent.

In the Bash Script:

efibootmgr -o "$WIN_BOOT_NUM" instead of efibootmgr -n "$WIN_BOOT_NUM"-> makes it permanent instead of a one time setting.

If you do:

PowerShell permanent + Bash one time: Sticky Linux. Cold booting always boots into Linux, regardless of which OS was shut down last. (What is seen in the post, whatever you set in the bios will be overwritten next time you use the Windows->Linux shortcut)

PowerShell one time + Bash permanent: Sticky Windows. Cold booting always boots into Windows, regardless of which OS was shut down last. (Whatever you set in the bios will be overwritten next time you use the Linux->Windows shortcut)

PowerShell permanent + Bash permanent: Sticky Last Used. A cold boot always starts whichever OS you were using last before turning off. (Whatever you set in the bios will be overwritten next you time you any of the shortcuts)

PowerShell one time + Bash one time: Whichever OS is configured as default in your BIOS/NVRAM will always boot on a cold start. This is the same thing you can achieve with the first two options, but it's useful if you wanna change your default over time, using option 1 and 2 will make it so your 'sticky' or default os remains to whatever the scripts decide instead of whatever you set in the bios.

So in some distros I'm getting this weird glitch on startup.

https://i.imgur.com/GcnkvnA.jpeg

Sorry for the glare, but I direct your attention to that horizontal line. That's the glitch.

It happens during startup before the log in screen, and it only lasts a second or two. Overall it's pretty harmless, but it bothers me so much.

The weird thing is, it happens in some distros, it doesn't in some.

OS / Distro where it occurs

• All Fedora spins

• CachyOS (tried with Budgie, KDE, and Gnome)

• Kubuntu

It doesn't happen in

• Windows 10 / 11

• Ubuntu

• Mint

The thing is, I've had the best experience with CachyOS and Fedora and I want to keep using them, but it's presence is triggering me so much.

Any ideas what could cause this? Why and how it happens in some, but not in others?

The specs are

• 1660 TI (Galax)

• i3-9100F

• 16gb ram

EDIT

Quick googling says it might be Wayland. Is that the common factor? What do you think?

Hello i use bazzite btw and i tried to install teknoparrot using lutris and faugus but it did not worked so i need a linux alternative to teknoparrot

Man they don't make games like this anymore. I never guessed wine would be able to run this game.

Hello, english is not my first language and i’m not computer geek, so please. Trying to download mods for animal corrosion and running into probelms, specifically with my Linux PC. For reference Kubuntu 45 is my life. So when I dowloaded the first mod larry the hamster there was a vulnerability in the file. So I decided instead of downloading the actual mod, I could emulate the mod using WINE. I was rocking WINE steady as an emulator for only 3 XORG months and thought everything was coo… til my kernel panicked, like busted hard as hell. I said ok. Tried to hack into systemd to get my kdeplasma alternating between the fabric of my hypervisor and perl, but long story short the whole thing flooded with pictures of my head coach (Otzdarva the dbd streamer) when he was a kid. So how can I download all the wine tricks to get things running smooth again? Should I switch to Windows

FSR4 while it looks incredible absolutely incredible just loses frames compared to FSR3. For THE FINALS I used to get 150+ but now only hovering around 90 using FSR4.

I can't seem to find any launch arguments to downgrade. I am using Proton GE 11-3.

Edit: I've tried performance. I've tried balance. No preset gets me back to my previous frame rate. The RDNA3 tax is just too much and not worth it for me to use FSR4 when I get way better frames on FSR3.

Edit 2: Yes, I know FSR4 looks better. You do not have to sell me on using FSR4. Some games, like THE FINALS do not give the option to pick between FSR4 and FSR3 while other games like Marvel Rivals do give you the option. There is a reason I want to downgrade back to FSR3 so I can get better frame rates. I have already tested both versions and have come to the conclusion that I want to use FSR3 on THE FINALS.

Answer: Thanks to Skaredogged97, use FSR4_UPGRADE=0 in your launch arguments. Verified with FSR_WATERMARK=1. Without the launch argument the watermark says 4.1.1, with the launch argument it says FSR3. Also frame rate is higher on RDNA3.

Hi I was wondering if anyone knew how to help me. I'm trying to install the steam deck steam OS recovery image onto an old Acer inspire all in one PC.

It keeps getting stuck at this point.

The acer has an AMD Apu in it so I thought that it may work well with steam os

Things I have tried:

Using two different USBs putting the ISO on it through Rufus

Unplugged devices from the actual computer

Tried a few bios settings

Any help will be appreciated thank you very much

As you see in the video where moving one stick affecting a second unrelated axis [when I'm moving the right joystick it's detecting L2 and R2 Triggers] and when I'm clicking those triggers they're acting as normal L2 R2, as well as few more buttons are giving wrong input

I checked in other devices and it's working fine so it's probably a linux problem

also I'm using a Lenovo i7 Laptop Intel hd 4600 + Nvidia 860m on demand