r/linux_gaming 6h ago

Today is the day I break Windows (all systems going to Linux).

Post image
268 Upvotes

Reupload because I didn't notice my license plate was in the picture.

Started 2 years ago when I upgraded my R7 2700 + 1080gt + 4x 8gb DDR gaming system, with a R7 5800X4D + 4070 Super + 2x 32gb DDR4. Then bought a super budget mATX board and a cheap case from Phantecs to make a bazzite powered Proto-Steam Box for my man-cave TV. Pre-RTX hardware and Bazzite wasn't jaw dropping, but it was a step up from the Steam Deck that I had been plugged into the dock for over a year, and it cemented for me that Linux was ready for full time use.

Getting laid off last year and then the RAM apocalypse set things back, but I finally put together an new Intel based system running Mint. After two weeks of settling in to make sure that Linux will do everything I need it to do (plus a shit load of data migration and cleanup to get everything off the Windows system); I pulled the trigger and ripped apart my Windows system & shuffled parts around into two new builds.

- Intel i9 12900kf + Arc B580 + 64gb of RAM is my productivity system. (mint)

- R7 5800X3D + 4070 Super + 16gb RAM is my Gaming system connected to the man cave TV. (Bazzite)

- R7 2700 + 1080gt + 16gb RAM + 8x 4tb HDD as a homebrew NAS. (Unraid)

Technically I do still have a Laptop running Win10, but it is a Samsung 2 in 1 from 2017 & don't have a lot of faith that the touch screen or fingerprint scanner would work correctly after implanting Linux ... Other than that, I am free from Microslop.


r/linux_gaming 16h ago

Perfect switch emulation

Post image
69 Upvotes

The emulation of both luigis mansion is perfect on linux with eden and yuzu


r/linux_gaming 10h ago

tech support wanted How do you enable HDR in steam games? Fedora 44 KDE Plasma 6.6.4

29 Upvotes

I’m very new to linux in general, so bear with me here. I chose this distro since it already had HDR support, and people seemed to say that fedora was pretty newbie friendly. It’s been working great so far, but none of my games that support HDR have the setting unlocked.

I’ve seen posts of people saying it’s as easy as adding PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command% to the launch options in steam, but that hasn’t worked for me. Something to note is that I’ve seen people saying this should disable the steam overlay, but mine still pops up. I have HDR enabled in the display config, but toggling it hasn’t done anything. I’ve also tried proton experimental, hotfix, 11, and 10 with no results.

Any suggestions? My PC is a R5 5600x/ Rx 9070 and my display is a LG C2 42”.


r/linux_gaming 50m ago

Cambiar a CachyOS fue lo mejor que he hecho en mi vida.

Enable HLS to view with audio, or disable this notification

Upvotes

r/linux_gaming 10h ago

tool/utility g7ctl v0.3.2 - Autodetection is here!

11 Upvotes

The major news for this release is I no longer need your exact PID to provide support!! g7ctl should detect your gamesir device and setup the connection automatically. The packaged udev rule has been changed to allow user access to any Gamesir controller. From this point forward please only file an issue report if the detection process fails for you or something in-app/protocol doesnt work for your device. I'll will investigate with you and determine if support can be added or your device needs to be added to the blacklist.

Found out something I believed since commit one was wrong (and fixed it), then caught a live reconnect bug in the same subsystem

This project's whole model of the G7 Pro's USB behavior was wrong. Since the very first version, the docs, the code, and the naming all treated the controller as having two "personalities" — a normal gamepad mode, and a separate "vendor mode" it switched into so the app could read/write settings. It doesn't. Confirmed on real hardware: both USB identities the controller can present are fully working gamepad identities. Which one shows up just tracks whether the active profile's bindings need a keyboard/mouse interface (or you've set 1000Hz report rate) — not a mode you enter for config access. Config reads/writes work identically on either one. The measurements along the way were all real; I'd just built the wrong mechanism to explain them. Rewrote the docs and renamed the public API to match reality once this was confirmed, rather than patch around it quietly — kept the enter-vendor CLI command string stable on purpose so nobody's scripts broke.

Second, a few days later: a live bug showed up in that exact same subsystem. The GUI could re-enumerate the controller extra times — sometimes with a visible disconnect — right after switching to a profile that needs the keyboard/mouse interface. Root-caused it live: a ~6-second warmup routine the connect sequence always ran first turned out to be exactly what was destabilizing the connection in that window — a read attempted after just a couple heartbeats succeeds instantly in the same scenario the full warmup doesn't. Confirmed across four back-to-back profile-switch cycles afterward: zero extra re-enumerations, versus roughly one per cycle before.

Also in this batch, everything else from v0.3.1/v0.3.2 so nobody has to go dig for it:

  • Detection no longer needs a hardcoded USB product ID — a new colorway should work the moment it's plugged in, no bug report needed first
  • Two real data-corruption bugs: a trigger curve/deadzone write crossing a byte-address boundary could silently drop data; declaring only one of Trigger Force/Sync could silently clobber the other back to "off"
  • A curve preset dropdown could silently save an all-zero curve instead of the shape actually shown on screen
  • Clicking Release Device right after Sync Now could leave the UI stuck disabled until an app restart
  • Editing a settings tab mid-sync could get silently discarded, or corrupt what was being written underneath it — every tab now locks for the duration of an in-flight job
  • Sticks' Deadzone Initial/Max writes were one byte too long
  • g7ctl enter-vendor exited 0 on a handshake failure that doesn't raise an exception
  • Trigger Force/Sync were completely unvalidated — a bad hand-edited value could silently write the opposite of what was declared
  • Dock LED Brightness fell back to 100% instead of the nearest preset for an off-scale value
  • Refocusing faster than the app's own poll cadence after an auto-release could permanently strand the controller released
  • A USB error during connect could leak a claimed session, needing a replug to recover
  • Shutdown now waits longer (2s → 10s) so an in-flight sync gets a fair chance to finish before the process tears down
  • -v/--verbose logging, a rotating GUI log, and a better g7ctl diag for anyone filing a bug report
  • A reject list for other GameSir Nexus-family devices confirmed NOT to be a compatible device, refused outright instead of failing confusingly. If your controller is not supported by Nexus support will not provided but there is enough protocol work and documentation in my repo that I am confident someone else could carry the torch and get it working.

As always the project can found Here. Please note a major repo restructure and maintenance pass was done this cycle. Those of you that have done a git-checkout on the repo will need to remove your current checkout copy and clone it again from scratch. Sorry for the inconvenience


r/linux_gaming 10h ago

tech support wanted Can someone explain how GOG gaming works with a controller?

12 Upvotes

I recently bought my first set of GOG games and was wondering, how does it work when it comes to controller inputs or mapping? Does it just automatically work with the Heroic Launcher? Or do I need to do something more? Is it easier to use Steam and launch it that way? Thanks for all of the assistance!


r/linux_gaming 18h ago

tech support wanted Genshin crashes kwin

5 Upvotes

So recently i have moved from linux mint to kubuntu for funsies, but after the switch genshin impact has been acting up. It either freezes forever while audio still plays and i can still preform attacks and stuff (to some extend) or it just outright crashes and restarts my entire desktop. I'm using xxmi on steam with proton cachyos and I have tried reinstalling steam but that didn't help. Also during gameplay I've noticed that when i open the map certain chunks of it seem to be missing

My hardware:

Processors: 12 x AMD Ryzen 5 3600 6-Core Processor

Memory: 16 GiB of RAM

Graphics Processor: NVIDIA GeForce RTX 2070 SUPER

I have also tried expanding my swap file but that did f all which is nice

Also also here is the kwin crash log if thats of any help

Application: KWin (kwin_wayland), signal: Segmentation fault

warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing

warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing
[New LWP 52140]
[New LWP 52143]
[New LWP 52162]
[New LWP 52160]
[New LWP 52161]
[New LWP 52177]
[New LWP 52163]
[New LWP 52156]
[New LWP 52158]
[New LWP 52181]
[New LWP 52184]
[New LWP 52182]
[New LWP 52178]
[New LWP 52180]
[New LWP 52185]
[New LWP 52186]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :0 --xwayland-xauthority /run/user/1000/xauth_RwnSlL --xwayland'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  __pthread_kill_implementation (threadid=<optimized out>, signo=11, no_tid=0) at ./nptl/pthread_kill.c:44

warning: 44./nptl/pthread_kill.c: No such file or directory
[Current thread is 1 (Thread 0x7b5059c2ee80 (LWP 52140))]
Using eu-unstrip to resolve modules.
add symbol table from file "/usr/lib/x86_64-linux-gnu/libc.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libKF6Crash.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libkwin.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libQt6Core.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libQt6Gui.so.6"
add symbol table from file "/usr/bin/kwin_wayland"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libQt6DBus.so.6"
add symbol table from file "/usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so"
[Current thread is 16 (Thread 0x7b501ffff6c0 (LWP 52186))]

Thread 16 (Thread 0x7b501ffff6c0 (LWP 52186)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09852030, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09852030) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b504554626d in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#8  0x00007b50455124dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#9  0x00007b50455461dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 15 (Thread 0x7b503cf506c0 (LWP 52185)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09852030, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09852030) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b504554626d in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#8  0x00007b50455124dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#9  0x00007b50455461dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 14 (Thread 0x7b5040dfd6c0 (LWP 52180)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c098450e8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c098450e8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 13 (Thread 0x7b5041dff6c0 (LWP 52178)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x7b5042f425a8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x7b5042f425a8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 12 (Thread 0x7b503e57d6c0 (LWP 52182)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a061c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:49
#2  __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:75
#3  0x00007b50607282f6 in __GI_ppoll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#4  0x00007b505fb342f1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007b505fb343c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007b506120513d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#7  0x00007b5060f98f5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#8  0x00007b5061082aae in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#9  0x00007b50611185a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 11 (Thread 0x7b503d7516c0 (LWP 52184)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09852030, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09852030) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b504554626d in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#8  0x00007b50455124dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#9  0x00007b50455461dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 10 (Thread 0x7b503ed7e6c0 (LWP 52181)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c098450e8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c098450e8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 9 (Thread 0x7b50475ff6c0 (LWP 52158)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09844c40, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09844c40) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 8 (Thread 0x7b503ffff6c0 (LWP 52156)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09852030, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09852030) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b504554626d in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#8  0x00007b50455124dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#9  0x00007b50455461dc in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_nouveau.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 7 (Thread 0x7b5043ffd6c0 (LWP 52163)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a061c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:49
#2  __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:75
#3  0x00007b50607282f6 in __GI_ppoll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#4  0x00007b505fb342f1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007b505fb343c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007b506120513d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#7  0x00007b5060f98f5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#8  0x00007b5061082aae in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#9  0x00007b50611185a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 6 (Thread 0x7b50437fc6c0 (LWP 52177)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x7b504847c5a8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x7b504847c5a8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 5 (Thread 0x7b5044fff6c0 (LWP 52161)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c09844ff8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c09844ff8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 4 (Thread 0x7b5046dfe6c0 (LWP 52160)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c098a2050, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c098a2050) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 3 (Thread 0x7b50447fe6c0 (LWP 52162)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a058c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=202) at ./nptl/cancellation.c:49
#2  0x00007b50606a0967 in __futex_abstimed_wait_common64 (private=<optimized out>, futex_word=<optimized out>, expected=<optimized out>, op=<optimized out>, abstime=<optimized out>, cancel=true) at ./nptl/futex-internal.c:57
#3  __futex_abstimed_wait_common (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>, cancel=true) at ./nptl/futex-internal.c:87
#4  __GI___futex_abstimed_wait_cancelable64 (futex_word=<optimized out>, expected=<optimized out>, clockid=<optimized out>, abstime=<optimized out>, private=<optimized out>) at ./nptl/futex-internal.c:139
#5  0x00007b50606a3347 in __pthread_cond_wait_common (cond=<optimized out>, mutex=0x5d8c098450e8, clockid=0, abstime=0x0) at ./nptl/pthread_cond_wait.c:421
#6  ___pthread_cond_wait (cond=<optimized out>, mutex=0x5d8c098450e8) at ./nptl/pthread_cond_wait.c:453
#7  0x00007b50512a3add in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b505125891c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50512a3a1c in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#11 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 2 (Thread 0x7b5058bff6c0 (LWP 52143)):
#0  __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
#1  0x00007b50606a061c in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:49
#2  __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=<optimized out>, a5=<optimized out>, a6=<optimized out>, nr=271) at ./nptl/cancellation.c:75
#3  0x00007b50607282f6 in __GI_ppoll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>, sigmask=<optimized out>) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#4  0x00007b505fb342f1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007b505fb343c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007b506120513d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#7  0x00007b5060f98f5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#8  0x00007b5061082aae in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#9  0x00007b506157904d in ?? () from /usr/lib/x86_64-linux-gnu/libQt6DBus.so.6
#10 0x00007b50611185a6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#11 0x00007b50606a407a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:454
#12 0x00007b506073772c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Thread 1 (Thread 0x7b5059c2ee80 (LWP 52140)):
[KCrash Handler]
#6  0x00007b50519f918e in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#7  0x00007b50519fa584 in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#8  0x00007b50514cd11b in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#9  0x00007b50514cd6a9 in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#10 0x00007b50514ce1ba in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#11 0x00007b5050e0af07 in ?? () from /usr/lib/x86_64-linux-gnu/libgallium-26.1.7 - kisak-mesa PPA.so
#12 0x00007b5063d27977 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.6
#13 0x00007b5063a07bac in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.6
#14 0x00007b5063a0bb44 in KWin::Compositor::composite(KWin::RenderLoop*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.6
#15 0x00007b5060fea525 in ?? () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#16 0x00007b5063a39f6a in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.6
#17 0x00007b5060fdb406 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#18 0x00007b50621a0b7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6
#19 0x00007b5060f90098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#20 0x00007b5061116319 in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#21 0x00007b5061118d84 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#22 0x00007b5061c826e2 in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Gui.so.6
#23 0x00007b5060f98f5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#24 0x00007b5060f92c87 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt6Core.so.6
#25 0x00005d8bfaa4b543 in ?? ()
#26 0x00007b506062a601 in __libc_start_call_main (main=main@entry=0x5d8bfaa491e0, argc=argc@entry=14, argv=argv@entry=0x7ffc0087e968) at ../sysdeps/nptl/libc_start_call_main.h:59
#27 0x00007b506062a718 in __libc_start_main_impl (main=0x5d8bfaa491e0, argc=14, argv=0x7ffc0087e968, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc0087e958) at ../csu/libc-start.c:360
#28 0x00005d8bfaa51985 in ?? ()

r/linux_gaming 6h ago

tech support wanted Green screen randomly when gaming on Radeon 5700 XT (CachyOS)

3 Upvotes

Hello!

I switched to Linux a few months back (CachyOS) and overall it has been a very smooth experience, but there are some games where my computer crashes. The game will launch, play very smooth, and then suddenly, after 5-90 mins, I will get a green screen, the computer will crash and restart, and I get the error message above.

The games where it crashes are both through steam: Mius Front & Avatar Legends.

Here's what I've tried so far:

- I ran Windows before and had the cards/ram overclocked so I reset my clock speeds

- replaced my entire CPU with a new one, since the temp readings were quite high, and I was due for an upgrade

- I've changed the PCI-E slot of the GPU to Gen 3

- I tried underpowering the GPU 20% (going from 195W max to 160W max)

- In LACT, I've lowered the P-state 2 mV, and I've increased the Pstate 1 mV

- I've ran memtest86+ with 3 complete passes and no errors

- I've ran Furmark both in it's normal and vulkan mode, with no errors

There was one fix that helped, and which has pushed the crashes to happen later, and that's increasing Performance Level to Highest Clocks. It does however not get rid of the random crashes completely, and it also causes my speakers to start picking up a high amount of static, so if I use the mouse wheel, for example, I get a very audible noise from the speakers. Either way setting it to Highest Clocks wasn't enough by itself.


r/linux_gaming 20h ago

hardware Switch Pro Controller drops packets and disconnects when paired alongside other devices

2 Upvotes

So I've been banging my head against this for months now. My Nintendo Switch Pro Controller works fine on Windows with a DualSense or basically any controller/bluetooth device connected at the same time, but on Linux it falls apart.

I'm on CachyOS but I've also tried Mint and Fedora, same issue everywhere. GNOME, Cinnamon, KDE, doesn't matter.

What happens:

When I connect the Pro Controller while a other controller / bluetooth device is already paired (or the other way around), the Pro Controller gets super laggy within seconds. After about 10-20s it just disconnects. Only fix is toggling bluetooth off and back on, then re-pairing from scratch. Sometimes it works fine on the next attempt, sometimes not.

There's also a second problem where even on its own, the Pro Controller slowly degrades during longer Dolphin Emulator sessions. After maybe 30 min it starts lagging and eventually drops. dmesg spams this when it's happening:

nintendo 0005:057E:2009.0009: compensating for 12 dropped IMU reports

nintendo 0005:057E:2009.0009: delta=215 avg_delta=15

When the DualSense connects, avg_delta jumps from 15 to 19, which looks like the adapter is reallocating time slots away from the Pro Controller.

I also blacklisted hid_nintendo and let hid-generic handle it instead. Same exact lag. So the problem is below the HID driver, somewhere in the bluetooth stack.

Stuff I already tried that didn't help:

- disable_ertm=1

- BlueZ main.conf tweaks (FastConnectable, JustWorksRepairing, Privacy, etc)

- Changing adapter alias to "Nintendo"

- Different connection order

- Disabling wifi (I use ethernet)

- Editing LinkKey Type in BlueZ device info

- Changing kernel params

USB works perfectly btw. Zero problems ever. DualSense never drops a packet either, it's always the Pro Controller that gets starved.

Built-in Intel bluetooth adapter on an Acer Aspire XC-1760, kernel 7.2.2-cachyos.

Has anyone gotten two controllers working stable over bluetooth where one of them is a Switch Pro?


r/linux_gaming 5h ago

tech support wanted Issue with Applications & Taskbar on [SteamMachine] desktop mode unresponsive

Thumbnail
youtu.be
2 Upvotes

Issue:
As you can see in the video,
Clicking anywhere on open applications or the taskbar acts as if the window/taskbar isn't there and clicks on the the layer behind it or doesn't register at all. This suddenly started happening at some point around 11-12 pm EST 9/3/2026, i was using it perfectly fine with no issue when this started happening and wouldn't stop.

What i've tried:
Doing some research on google i found that SteamOS comes with aggressive compositing settings to keep the UI smooth, but they can cause a rendering bug under AMD RADV drivers where the "blur" layer behind windows stops updating its hitboxes. it was suggested under System Settings > Workspace Behavior > Desktop Effects i uncheck Blur and Background Contrast settings. This did temporarily fix the issue but after an hour or so it came back and hasn't gone away.

System Specs:

Operating System: SteamOS 3.8.26 Build: 20260827.1
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.18.46-valve1-1-neptune-618-g2e13b4367b17 (64-bit)
Graphics Platform: Wayland
Partition: A
Processors: 12 × AMD Custom CPU 1772
Memory: 16 GiB of RAM (15.2 GiB usable)
Graphics Processor: AMD Steam Machine
Manufacturer: Valve
Product Name: Fremont
System Version: 1

If anything further is needed please let me know and ill update the post. I tried following the guide for posting the best i could with the limited knowledge i have.

At the time of posting it is past midnight and i have work so i wont be responding or checking this until tomorrow afternoon. Thank you in advance!


r/linux_gaming 14h ago

How does Crimson Desert perform for you?

2 Upvotes

I've been playing Crimson Desert Enhanced for about 2 hours now, and I'm curious to know how it's running for everyone else.

I'm on Fedora + Niri with an RTX 5060 laptop GPU, playing at 2560x1440 on an external 120Hz monitor.

Currently I'm getting roughly 80–90 FPS according to the in-game counter with:

- FSR 3.1 Quality

- 2x Frame Generation

- Ray Tracing off

- 1440p

- Proton-CachyOS 11 (x86_64_v3)

- NVIDIA driver 610.57.04

Even though the frame counter in the setting say I'm getting around 80fps, it still doesn't feel like it for some reason. It still feels a little choppy and I don't know if I'm imagining it or if it really does feel like that. The visuals also don't look as good as it does in YouTube videos by other creators, but that is my only point of reference.

My Windows partition is too small to download the game, so I can't test it on Windows and see what performance on Windows is like either. Whenever I turn the LSS on, regardless of whether it is 4.0, 4.5 or 4.5 l, the frames drop like crazy and there is some extreme shadowing going on as well. Therefore, I'm forced to play on FSR upscaling 3.1, because this is the smoothest experience I can get.

For anyone else playing on a similar setup, what kind of performance are you getting and what settings are you using? Particularly interested in NVIDIA users, but AMD/Linux and Windows comparisons would also be useful.

I'm mainly trying to figure out whether I should keep tweaking the in-game settings or just accept that this is what the game is going to look/feel like on my hardware.


r/linux_gaming 17h ago

Do unreal engine games have a bad crashing issue on Linux through the heroic games launcher?

1 Upvotes

I got The Blood of Dawnwalker on GOG. I'm 4 hours in and every 30 or 40 minutes my game closes, and I get a unreal engine crash error.


r/linux_gaming 22h ago

MangoHud started ignoring my configurations for flatpaks while it used to work before.

Thumbnail
2 Upvotes

r/linux_gaming 43m ago

I swear I've seen a post of a guy who built an open source virtual desktop streamer for linux and I can't find it anymore

Thumbnail
Upvotes

Please tell me one of you heard of this


r/linux_gaming 1h ago

tech support wanted Cannot start GTA5 (Epic Games) via Heroic, Rockstar Launcher shows 'buy now' instead of 'play now'

Thumbnail
Upvotes

r/linux_gaming 1h ago

tech support wanted [Assassin's Creed 2] Game runs OK, but a few issues with frame rate, draw distance, and general application behaviour

Upvotes
  • Distro version: Linux Mint 22.3 Xena
  • Kernel version: 7.0.0-31-generic
  • CPU: AMD Ryzen 5 7600X
  • GPU; driver: NVIDIA GeForce RTX 5060 Ti; 595.84
  • Mesa version: 25.2.8-0ubuntu0.24.04.2
  • Wayland/Xorg?: Not sure how to answer this question (Linux newb), but the most relevant-looking line from inxi -xxACGS says "server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6".
  • gamecope?: Not sure how to answer this question.
  • VRR?: If this means variable refresh rate, then VRR is available on my monitor (ASUS VZ27EHF) but I don't know if the game is using it (or if "the game choosing whether or not to use it" is a coherent concept).

I have several issues, none game-breaking, but they're enough to bring down my quality of life. In particular:

  • Every 10 minutes or so, my frame rate will maybe halve, stay halved for about 15 seconds, and then slowly recover over the course of 30 seconds. The nature of the decrease is such that it's the sort of thing I'd expect if I were going into a new area and rapidly trying to load a lot of stuff, but that doesn't appear to be what's actually happening. It's somewhat miserable because if it happens during, for example, a race, because AC2's races have pretty challenging parkour segments I can more or less expect to lose and have to redo.
  • Draw distance is lower than I'd expect my card to be able to handle, sometimes to the point of objects popping in 5 metres in front of me.
  • The game doesn't close when I close it; the game application closes, a Ubisoft Connect window comes up and indicates it's doing game-close housekeeping for a couple of seconds, but Steam still detects the game as running until I close it through Steam.

I'm using Steam with Proton. I haven't forced a different compatibility tool for AC2, so I assume it's using Proton Experimental, which is set as the default on my Steam installation. I have EaglePatch for AC2 installed. Other games generally work about as well as ProtonDB would lead one to expect they would. In particular, the only other AC game I've installed on Linux (AC1 Director's Cut) doesn't have the frame rate issue or the issue with not closing (it does, however, have the draw distance issue).

My current Steam launch options for this game are -USEALLAVAILABLECORES -high PROTON_LOG=1 %command%. The first two are from someone else's suggested solution; effects have been equivocal/insignificant. The last one is from this wiki but I haven't run it with that yet.

I am not a skilled enough general computer user to determine if anything in the Linux Mint documentation is helpful for this. My Firefox doesn't want to work with reddit search for some reason so I haven't been able to check reddit using its own search engine, only Google. General search engines (Google and Kagi) have turned up a couple of mentions of similar problems, but none of the ones I've read are detailed enough for me to determine whether we're having the same problem.


r/linux_gaming 2h ago

tech support wanted Marvel rivials lagging and I don't know why

1 Upvotes

I am on Cachyos and have been playing rivials for a while now but recently I have been getting hit with random frame drops from 200fps to 40 or 30fps and I don't know what is causing it.
My specs:
RTX 5070TI
9800x3d
32gb of ram
samsung ssd
Any suggestions on what's going on?


r/linux_gaming 7h ago

tech support wanted I'm a newbie and don't know exactly what to do

2 Upvotes

Hey, fellas, so... I'm a new linux mint user and i've noticed every time i open a game on my steam library it does "process vulkan shaders" and it takes too long; is there something i'm missing? For example, this same machine using windows used to run Deadlock and now that i'm on linux mint it ain't due to this (and if i try to skip processing those shaders it does stutter a lot).

And deadlock runs on Linux very well from my researchs on r/DeadlockTheGame


r/linux_gaming 8h ago

Steam remote play issues

1 Upvotes

I just switched my computer to debian 13, and I was trying to play rainworld co op with a friend but steam remote play would not allow my friend to use keyboard controls even though I had it enabled on the steam overlay. This previously worked on windows, but is now extremely finicky, does anyone have any tips for fixing this?

- also I am currently using proton experimental, is there a different version that would work better?


r/linux_gaming 11h ago

Gang, does Protonplus automatically update to the newest release with the ''Latest' model?

1 Upvotes

I'm using DW Proton on SteamOS i'm just keen on if it will automatically update to use the newest version of that proton or do i have use the app to manually install it?


r/linux_gaming 12h ago

tech support wanted Strange FPS problems

1 Upvotes

I recently got back to using cachy-os and i'm experiencing a strange issue; sometimes i have really low fps on games (using as example Hitman: WoA, i usually get 100+ fps, but when this happens it goes to ~30) until i restart my monitor, than it goes back to normal.

i'm running (Hitman in this example, but happens from other launcher / Wine / Proton versions too) using: proton-cachyos-11.0-20260703 (steam linux runtime)

this is the output of inxi -xxACGS:

System:
 Host: pc Kernel: 7.2.2-1-cachyos arch: x86_64 bits: 64 compiler: clang
   v: 22.1.8
 Desktop: KDE Plasma v: 6.7.4 tk: Qt v: N/A wm: kwin_wayland dm: N/A
   Distro: CachyOS base: Arch Linux
CPU:
 Info: 6-core model: AMD Ryzen 5 5600 bits: 64 type: MT MCP arch: Zen 3+
   rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 32 MiB
 Speed (MHz): avg: 3990 min/max: 566/4471 boost: enabled cores: 1: 3990
   2: 3990 3: 3990 4: 3990 5: 3990 6: 3990 7: 3990 8: 3990 9: 3990 10: 3990
   11: 3990 12: 3990 bogomips: 83843
 Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
   ssse3 svm
Graphics:
 Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
   XT/6600M] driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
   lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, Writeback-1
   bus-ID: 07:00.0 chip-ID: 1002:73ff
 Display: wayland server: Xwayland v: 24.1.13 compositor: kwin_wayland
   driver: gpu: amdgpu display-ID: 0
 Monitor-1: HDMI-A-1 model: LG (GoldStar) ULTRAGEAR res: 1920x1080 hz: 180
   dpi: 93 diag: 604mm (23.8")
 API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
   gbm: drv: radeonsi surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
   drv: radeonsi
 API: OpenGL v: 4.6 vendor: amd mesa v: 26.2.1-arch3.1 glx-v: 1.4
   direct-render: yes renderer: AMD Radeon RX 6600 XT (radeonsi navi23 ACO DRM
   3.64 7.2.2-1-cachyos) device-ID: 1002:73ff display-ID: :0.0
 API: Vulkan v: 1.4.357 surfaces: N/A device: 0 type: discrete-gpu
   driver: mesa radv device-ID: 1002:73ff
 Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
   de: kscreen-console,kscreen-doctor wl: wayland-info
   x11: xdpyinfo, xprop, xrandr
Audio:
 Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
   driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
   bus-ID: 07:00.1 chip-ID: 1002:ab28
 Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
   vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
   lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487
 Device-3: fifine Headset driver: hid-generic,snd-usb-audio,usbhid
   type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 3-4:4 chip-ID: 3142:0009
 API: ALSA v: k7.2.2-1-cachyos status: kernel-api
 Server-1: sndiod v: N/A status: off
 Server-2: JACK v: 1.9.22 status: off
 Server-3: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
   status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin

r/linux_gaming 16h ago

tech support wanted Steam jackify M02 link to run game not just MO2

1 Upvotes

I need to be able to launch the game from Steam, not just Mo2.

I used Jackify to intall a mod list and it added it to Steam.

When I launch, it launches M02 but not the game (I have to hit run). That's fine when I'm at home but I'm playing with Steam Link (working so far) but it won't show M02 so I can hit run.

Current launch options in steam are:

Skyrim NOrdic Souls

STEAM_COMPAT_MOUNTS="/home/markb/Games/Modlist_Downloads" %command%

Fallout 4 Magnum Opus

STEAM_COMPAT_MOUNTS="/home/markb/Games/Modlist_Downloads" %command%

I tried getting M02 to make a shortcut (which it does in C:\users\steamuser\Desktop) but I can't show the properties of that shortcut to add to launch options.


r/linux_gaming 16h ago

tech support wanted Ghost Of Tsushima - Weird ghosting on the tree's.

Enable HLS to view with audio, or disable this notification

1 Upvotes

Is there any way to fix this?
Distro: Nobara
Using latest ProtonGE


r/linux_gaming 18h ago

If you use an eGPU for gaming in any distro share anything useful here

1 Upvotes

I created a similar post for SteamOS, but I saw not many people use eGPUs in SteamOS and many are connected through Oculink that's basically like connecting it directly to the PCIe port and doesn't need a lot of TS compared to USB4/TB4. So now, I want to expand it to any distro.

I use a RX 7600M XT connected through USB4 in SteamOS and this is what makes it work perfect for me:

- Changing to the preview channel to change to SteamOS 3.9 and kernel 7.2.

- Use ewagner12's all-ways-egpu script.

- Using these kernel parameters:

thunderbolt.host_reset=0

pcie_port_pm=off

amdgpu.pcie_gen_cap=0x40000

amdgpu.cwsr_enable=0

But, I want to hear if anyone else has something useful to share about its experience using an eGPU for gaming in Linux


r/linux_gaming 18h ago

tech support wanted Bonelab Always Hangs

Thumbnail
1 Upvotes