Horrendous performance

I’ve been a cachyos us for a while now, at least a year or two. I never had any problems with performance and running games. I gave away my pc to my sister last year and recently built a new pc, so I’m completely unaware of any changes and updates that might’ve caused the issues I’m having.

I have the Ryzen 7 7700, RX 6650XT, with 16gb of ddr5.

Here are things I’ve tried:

Fresh install (I’ve reinstalled the os thrice, every instance resulted in low FPS and Bluetooth connection loop.) then I install cachy os gaming meta then steam (I remember steam native being a thing but I guess that’s gone?), proton ge, cachy proton, proton hotfix and experimental all yield the same results. (I get only 60fps in games like OW and ultrakill along with insane stutters even tho I easily hit 144+ on windows.)

I tried several launch options and even tho I actually got things running smoothly once it eventually got back to being running like garbage and stuttering.

I made sure my iGPU is disabled, LACT to make sure I’m running on highest clocks and I’ve tried lower clocks. Disabled EXPO as well

No matter what I do these issues persists. Basic desktop use is fine it’s specifically games. I’ve never encountered a problem like this.

Is the hardware at full utilization or throttled?

Are you using Gamescope as a compositor instead of the default?

That’s exactly why I’m so perplexed, it was neither throttling nor did it have low utilisation.

I’ve also tried gamescope. Made zero difference

I’m going to need more information.

Can you run a cachyos-bugreport.sh and provide the result so we can see exactly what we’re working with.

First off I’d undo all the clock and timing changes by setting your BIOS back to Optimized Defaults and then disabling the iGPU, turning off Secure Boot (if your BIOS doesn’t have the proper certs to secure boot CachyOS) and not doing any
other changes until there’s a baseline.

We can review the bugreport, but if you’re not attached to what you’ve got going on now, might be worthwhile to start from a fresh install so that anything that was done in an attempt to improve performance (but was unsuccessful) is undone, but whether you do that or not, we can definitely start from where you’re at now.

Have you check your power usage profile? Is it set to performance? Not Balanced or Power Saver?

Have you read the Gaming with CachyOS guide?

Bluetooth connectivity loop? input devices and controllers? audio output?
If it’s an bt audio problem, there’s a bug in bluez 5.86 that is affecting bt audio devices that support both sink and source. Downgrade to 5.85

OK - so you’re running Steam + Proton? Did you read about the latest patches applied to Proton-CachyOS version and how they have an effect on some issues (latency)? There have been threads about it in the forums here in the last few days.

Are you on a 4K display? KDE? Wayland? what Composer and Window Manager?

I don’t know what game “OW” is when was it made? what game engine does it use? Have you checked ProtonDB for how other people are getting that game working? If you launch the game borderless windowed at half or 3/4 of your native desktop resolution does the game run better or the same?

Run the game in a window or borderless window and less than full resolution and run amdgpu_top next to it and see if the GPU is maxing out or if it’s got room to run and something else is throttling the system.

You say you build a new system – provide the full system spec (we’ll get it from the bugreport) but maybe there’s something going on with the hardware in the custom build.

Thank you for replying.

I reinstalled cachyos, complete fresh install, reset my bios settings (also updated it), turned off the iGPU, turned off secure boot, and made sure power management was in performance. Still the same

As for the bluetooth problem, I’ve downgraded all the way to 5.83 the problem still persists.

Thanks for mentioning this but I do not have any latency problems, only framerates.

I’m on a basic 1080p 165hz display, KDE and wayland.

OW is overwatch, should’ve specified.

The game does in fact run better if I lower the settings and resolution, and GPU utilization does go down if I lower them.

Looks like your GPU is being bifurcated. Should not be much of a performance hit in games, but not ideal.

You are also running single channel RAM, which could be a bigger issue for game performance, but I also understand wanting to avoid going broke from insane memory prices when building a PC.

Yeah but, there’s no shot these particular issues would cause my performance to be less than 50% of what I get on windows.

just curious, have you try enabling sched-ext ?
because, i’ve noticed some of my games has micro stutter when using default (non enabled sched-ext) a while ago, now i’m enabled it, no issue sofar

Sorry, I did not mean to say these were your specific issues. Only wanted to highlight some hardware limitations present. I am not as well versed with the software side yet.

do you want to know something funny? this only kinda works. I mean that literally.

I boot up my PC, open a game and play for a few minutes, I reboot and or shut down, turn my pc on and enter the game again the problem occurs yet again. If I reboot my pc the next time the problem goes away.

I am genuinely so confused and quite frankly annoyed.

If “JimmyTwoTimes” replies and nothing works I think I’ll go back to windows for the mean time.

Thank you all of you for your time

Edit: the good news is, i think my frametimes are more stable now, so less stutters. also, before I was hitting sub 60fps and now I’m getting more than that. Nowhere near what I’m supposed to get but whatever

Edit 2: well after a few reboots it went back to performing like hot garbage. I think my computer is cursed

Are you sure gamescope was running? I don’t see it in the journalctl of your log, where it normally leaves entries.

From my experience, if it’s not paired with Mangohud then for whatever reason it doesn’t run, but the game still loads.

It’s true I forgot to enable it one that particular installation but I went and enabled it rn and it still made no difference

I wrote you a book about how to optimize OW and gamescope, but that will have to wait, but I can see you problem thanks to the bugreport:

Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:4 chip-ID: 0e8d:0616
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 7c0104

bluez 5.85 is the sweet spot for Bluetooth right now, upgrade up to that, stay away from 5.86
so:
sudo downgrade bluez and select the latest 5.85 package.
( normally you would restart bluetooth after this, but you don’t have to restart bluetooth right now because we’re going to make more changes.

You’ve got a MediaTek USB bluetooth adapter they have known issues with Linux apparently, but let’s see if we can fix it.

Let’s start by disabling LE Audio / ISO features as the MediaTek USB messes it up.

sudo nano /etc/bluetooth/main.conf

Add:

Experimental = false
Disable = LEAudio

and restart bluetooth:

sudo systemctl restart bluetooth

then let’s disable autosuspend for that USB device since you want it on all the time.

in the bugreport we got the Vendor and Product info:

[    1.850640] usb 1-8: new high-speed USB device number 4 using xhci_hcd
[    2.068349] usb 1-8: New USB device found, idVendor=0e8d, idProduct=0616, bcdDevice= 1.00
[    2.068355] usb 1-8: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[    2.068357] usb 1-8: Product: Wireless_Device
[    2.068359] usb 1-8: Manufacturer: MediaTek Inc.
[    2.068361] usb 1-8: SerialNumber: 000000000

create a file to put the rule to not suspend your bluetooth adapter.
sudo nano /etc/udev/rules.d/99-btusb-disable-autosuspend.rules
with the following:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", ATTR{idProduct}=="0616", TEST=="power/control", ATTR{power/control}="on"

then load the rules:

sudo udevadm control --reload-rules
sudo udevadm trigger

then verify it’s working by running this:

NOTE: the 1-8 you see here corresponds to the system log saying the device is 1-8:
usb 1-8: Manufacturer: MediaTek Inc.
if you change ports or something changes, these cat commands will need to be updated to the matching device.

cat /sys/bus/usb/devices/1-8/power/control

You should get the result of:
on

notauto

Give your system a restart and then run:

cat /sys/bus/usb/devices/1-8/power/control

to make sure the change stuck and you see a response of on not a response of auto

Then let’s check and make sure the bluetooth changes stuck as well.

run (after the restart):
journalctl -u bluetooth -b | grep -Ei "experimental|le audio|bap|iso"

and you should no longer see

bluetoothd[890]: profiles/audio/bap.c:bap_adapter_probe() BAP requires ISO Socket which is not enabled
bluetoothd[890]: bap: Operation not supported (95)

These messages should not appear anymore.

So give that a shot and report back.

Feel free to run another cachyos-bugreport.sh and post the new link after you do the the changes and restart.


Sidenote, I (vibe coded) wrote a debug tool to help figure this type of stuff out.

– DebugDeck –

I find it helpful to watch what’s going on with the system while you’re trying to troubleshoot problems and optimize features:


On to the fun stuff - Optimizing OW.

Are you running OW “full screen” or borderless? Run full screen* (and let gamescope manage it, it’ll perform better.

Don’t use PROTON_USE_NTSYNC=1 it’s for NVidia cards, it doesn’t help you.

Install gamemode:

sudo pacman -S gamemode

Try this for your launch arguments:
DXVK_ASYNC=1 DXVK_FRAME_RATE=165 DXVK_MAX_FRAME_LATENCY=1 __GL_GSYNC_ALLOWED=0 __GL_VRR_ALLOWED=0 gamemoderun gamescope -w 1920 -h 1080 -W 1920 -H 1080 -r 165 -f -- %command%

change the -w #### and -h #### (not -H and -W) to the resolution you have OW set to run at in-game, if you’re not getting 165fps in game at 1920x1080, then reduce the resolution in game, close OW, update the -w -h values in your Launch Options to the new in-game resolution and start OW again.

Keep stepping down the resolution until you’re getting 165 consistently while playing, then we can fine tune other things and bring it back up.

Also CachyOS KDE 6.6 defaults to Wayland.

People in other threads are reporting success with their multi-display setups by reverting to X11 session.

you’ll have to install the X11 server:

sudo pacman -S xorg-server

Supposedly after installing xorg-server and logging out you’ll see a “session selector” icon appears on the login screen and you can choose “Plasma (X11)” and log back in to your account with an X11 session rather than Wayland.

the game doesn’t even run with said command. also, i’ve noticed i don’t get more than 10% cpu utilization in game. no idea what causes that

well, x11 fixes my issue. but quite frankly id rather not use that at all, it’s archaic and quite frankly worse

I can install OW and see how it runs for me, it ran fine before. Recently I play mainly ARC Raiders and The Finals, but did notice some quick FPS drops every 10-15 seconds, but could also be the game specifically, as others on their discord have been complaining about very poor 1% lows on the games even on high end hardware.

bad news. it didn’t

ow tends to switch there graphic to ultra upon launch might be stupid but make sure in the ow menu you have it lowest and uncapped fps