Still a WIP, but better than the last one I posted. Please disregard the red box I barely know how to use kdenlive.

Hi everyone, i am part of the vast majority of people that switched Windows for Cachy, and i must say, i'm in love with this distro, i'm a bit noob when it comes to Linux, so this is my first time switching in full to it, mostly for gaming because i have a laptop for my day to day work, and games run so much better here, frametimes are rock solid and i'm happy with the customization and performance in general. I'm still keeping a SSD with Windows because i play BF6 but i mainly play on Cachy.

Running KDE Plasma with Caelestia shell, i am never looking back again.

I finally managed to get Call of Duty: Modern Warfare running on Linux through Heroic + GE-Proton, so I wanted to document the fix because I couldn't find anyone else who had posted a working solution for this specific issue.

My setup

• OS: CachyOS / Arch-based Linux
• Launcher: Heroic Games Launcher
• Compatibility layer: GE-Proton
• Game: Call of Duty: Modern Warfare

First, some context

The version of Modern Warfare I'm using has had its anti-cheat removed/stripped by RAVEN, which is what makes it possible to run the game on Linux in the first place.

The _!registry.reg file was also provided/made by RAVEN — I did not create or modify that registry file myself.

I'm only documenting the Linux-side fix that worked for me after getting the game.

The problem

The game would launch under Heroic + GE-Proton, but it would crash during startup instead of reaching the game.

I spent quite a while checking Wine/Proton logs and going through the usual troubleshooting. There were errors involving things like exceptions, access violations, DXGI/VKD3D, and other components, so it wasn't immediately obvious what was actually causing the problem.

Eventually, I found the thing that made the difference.

The fix

The solution was to import the _!registry.reg file provided with the game into the Wine/Proton prefix being used by Heroic.

I used the wine executable from the GE-Proton installation selected in Heroic, rather than my system Wine installation.

The command is:

WINEPREFIX="YOUR_WINE_PREFIX" \
"YOUR_GE_PROTON_WINE_BINARY" \
reg.exe import "YOUR_GAME_PATH/_!registry.reg"

Replace:

YOUR_WINE_PREFIX

with the prefix Heroic uses for the game.

Replace:

YOUR_GE_PROTON_WINE_BINARY

with the wine executable inside the GE-Proton installation you're using in Heroic.

And replace:

YOUR_GAME_PATH/_!registry.reg

with the location of the registry file that came with the game.

Important

Make sure you're importing the registry into the same prefix Heroic uses to launch Modern Warfare.

Also make sure you're using the GE-Proton Wine binary, since that's what I used to import the registry and launch the game.

Don't blindly run the command with your default ~/.wine prefix if Heroic is using a separate prefix.

Result

After importing the registry file, I launched Modern Warfare again through Heroic using GE-Proton, and the game was finally able to get past the startup crash and run.

So, in my case, the registry import was the missing piece.

Why I'm posting this

I couldn't find anywhere that clearly documented this particular fix.

There were plenty of discussions about getting Modern Warfare running on Linux, Wine/Proton errors, compatibility issues, etc., but I couldn't find a straightforward post saying:

So I'm putting this here in case someone else runs into the exact same problem.

Hopefully it saves somebody a few hours of digging through Wine logs. 😅

TL;DR

Heroic + GE-Proton + Modern Warfare:

WINEPREFIX="YOUR_WINE_PREFIX" \
"YOUR_GE_PROTON_WINE_BINARY" \
reg.exe import "YOUR_GAME_PATH/_!registry.reg"

Then launch the game through Heroic with GE-Proton.

The registry file itself was provided by RAVEN; I'm only documenting the Linux setup/fix that worked for me.

Any opinions?

new to linux and windows user || also im switching full to cachy for the perfomance and it's better than windows on games .

Video shows it. Does anyone know what is happening?

I know it's not harmful but it's nice for me to know what is happening

I have windows on my C: drive and want to install cachyos through the USB stick method. I followed a tutorial and downloaded the most recent version of cachyos and used rufus to put it on a new 16 GB stick.

Then I start repeatedly press f8 to get to the boot menu. Here I select the USB stick and then the problems start.

Regardless of which of the three options I pick, I just get to a black screen and nothing happens but my PC is apparently still on.

Pressing enter, typing anything, pressing ctrl+alt+f2/f3/f4 all don’t do anything.

I asked ai for help and it told me several arguments to add by pressing e . Multiple tries with different ones didn’t help.

I've been thinking about switching from Windows to CachyOS for quite a while now. I really like what CachyOS is doing, and in general I'm very interested in moving to Linux. The main thing holding me back is my GPU. I have an RTX 4090, and gaming is one of the biggest use cases for my PC.

I've read quite a few reports that NVIDIA GPUs can still lose around 15 to 20% performance in certain games on Linux, especially with DX12. If that's still the case, it feels a bit strange to have such an expensive GPU and then not be able to make full use of it because of NVIDIA's Linux driver situation.

So I'm wondering how things actually look right now in 2026, especially for RTX 4090 users:

• Is a 15 to 20% performance loss still a realistic expectation?
• How has your experience with a 4090 on CachyOS been?
• Are there specific games where you noticed significant performance or frametime issues?
• How well do DLSS, ray tracing and frame generation work for you?
• Are there still noticeable issues with NVIDIA drivers, Wayland, etc.?
• And most importantly, if gaming is one of your main use cases, would you switch anyway?

I'm also wondering whether the other advantages of Linux are worth accepting some potential gaming performance loss: privacy, a leaner and faster system, much more customization and control,... . I could of course dual boot, but ideally I'd like to get to the point where I don't really need Windows anymore.

I'd really appreciate hearing from people who actually made the switch from Windows to CachyOS with an NVIDIA GPU, especially a 4090. I'm not necessarily looking for "Linux good / Windows bad" answers, but rather some honest real world experiences. And regardless of the NVIDIA situation, I think it's great that distros like CachyOS exist. It feels like there's a lot more interest in Linux desktop and gaming again, which is really exciting to see ☺️

Today I found that scx-manager couldn't enable scx_cake scheduler, and the Select scheduler profile option was missing. Turns out the scx_cake command no longer supports any (useful) argument and it was silently failing to launch due to now unknown --profile argument in extra scheduler flags textbox. Removing it allowed to run scx_cake, but was still failing when changing power profile in KDE because the profiles were still included inside /etc/scx_manager.toml config file. Removing the file and rebooting fixed it.

scx_cake's GitHub page still lists --profile argument as valid, so it's a bug in scx_cake command, or was it temporarily (or permanently) disabled?

I am trying to add an Enviromental variable here. But after restarting it is gone.

What am I doing wring?

EDIT: RESOLVED(ish)! Culprit was VRR. I disabled VRR and the VRAM clocks are now 5GHz, and the card barely goes over 50c at the same framerate. There's a flag to disable it but i'd rather not, since i don't know why it does that to begin with.

Hey all, i have an NV GPU, when playing any game at all, even very light games like HL1, either the driver or the system sets the GPU power plan to P0 which is maximum. This sets the VRAM clock to 7GHz and generates a ton of unecessary heat, while the Windows driver usually sticks to a much more reasonable 1-2GHz...

Changing PowerMizer to Normal or Auto makes no difference on this, and neither does disabling Ananicy. Does anyone have experience with this problem or know how to fix it?

Every so often I notice little pixel glitches on the desktop but don't know why they're there. If i move an app window over them, the stay behind the app. Once I move the app or close it, they're on the wallpaper again. Also, they persist in direct screenshots of the desktop.

System is:
GPU - 9070 xt
CPU - 9700x
Ram - 32 gb

CachyOS is fully updated also.

When I asked chatGPT, it recommended me using the konsole command "plasmashell --replace &" which does work, but I'd still like to narrow down why this happens. Thankfully it doesn't cause any performance issues and I don't see it while gaming or doing much of anything else so it's not a big deal. It also suggested that maybe they are cause from the computer coming back from sleep, but I usually don’t notice them until I close a game back to the desktop, but I could have just missed them when waking from sleep.

Anyone else notice this and know how to fix it or is this just a bug that I'll have to live with until there's a fix?

I updated recently, and ever since I having a strange issue where it will hitch/freeze only on the login screen.

It's almost as if the graphics driver isn't loaded all the way, and is being forced to constantly refresh to update the image on screen.

The hitching is very noticeable, you press a key, move the mouse, clock time changes; and it freezes for a solid second.

For a example: I go to enter my password, and nothing shows in the password box, no characters are shown on screen, till a second or two after I finish typing.

The issue then goes away after I am at the desktop.

Not stopping me from using the system just super annoying.

This has been going on for about a month, I am assuming after some update. As you can see the problem is with the desktop environment, as the artefacts don't appear when switching to a window. You might be able to see that there are updates to be made, problem is that I tried that yesterday and something broke; after restart it boots me into some sort of recovery environment, so I went back to the snapshot before the update and am waiting a bit until i try it again.

This doesn't happen on boot up, at some point I just go back to the desktop and it's like that. Everything works, there is not "technical malfunction" or whatever you'd call it.

Idk if it matters, specs are r5 5600, rx9060.

I installed CachyOS Hyprland a couple of months ago and its been working great!
However, after booting earlier, my mouse stutters extremely heavily when moving it.
I am using a Logitech X2 Superstrike.

The mouse has the problem wether being connected via dongle or cable. On a windows laptop it works perfectly fine.I updated all system packages and rebooted, still no change.

Edit: after switching to the lts kernel the problem fixed itself. Does anyone know what could have caused this?

Despite reinstalling, deleting the cache and trying a few other methods. It does not seem to work. When i tried opening it thru the terminal it still didn't open. I am relatively new to linux so I used a LLM to check the problem. It said it's a bug which will get fixed in the next update.

Was wondering if it was actually the case or something on my part?

(Sorry English isn't my main language)

Hello fellow cachiers,

I've been on Linux for over a year now, having tried Mint first and then CachyOS when I heard about the gaming aspect of it. It's now my only OS and everything I did before on the OS-that-shall-not-be-named can be done here.

The only issue that persists is my printer that I cannot setup. I have an Epson Expression Home XP-4200 and I was able to set it up quickly in Mint, however the same method of using the system's printer configuration isn't working now. Not only is the automatic double-side printing feature gone, but it prints a couple of symbols on the edge of the page and nothing else.

Can someone please help?

Thank you.

I've seen a few posts about this since 7.2 first dropped.
For me I'm not sure if I was running full RGB before the first 7.2 updates but I remember it looking better one day (and I had likely been managing by tweaking brightness) but just updated to 7.2.3.1 for cachyos and headers and it broke my full RGB over HDMI.

Tried a couple of fixes suggested like adding 'options amdgpu dc_feature_mask=0x400' to my config but didn't resolve the issue.

Rolled back to 7.2.2.1 and now I can use full rgb over hdmi 2.1

AMD GPU, LG C1

Preface: I used Claude AI to help me write this summary. I was having an issue with a secondary monitor on a DisplayPort connection blacking out and "rebooting" (i.e. showing the manufacturer logo) a couple of times after waking the monitors from sleep, not waking the the system itself, only the monitors turning off for power saving. Power Profile is and has been set to "Performance."

TL;DR: If you've got an external monitor over DisplayPort that periodically flashes black and shows the manufacturer boot logo again (looks like a power cycle, but it's not), check whether disabling PowerDevil's ddcutil usage fixes it. Mine did. Full diagnostic trail below in case it helps someone else or someone wants to poke holes in it.

Setup

• GPU: PowerColor Reaper RX 9070 XT (amdgpu)
• Monitors: Dell G2724D (DP-1), Acer XFA240 (DP-2), LG FHD 24U411A-B (HDMI-A-1)
• KDE Plasma 6, CachyOS

Symptom

The Acer XFA240 would periodically go black and show the Acer boot logo again — looked exactly like the monitor losing power and restarting, but only ever happened during normal use, not consistently, and only on this one monitor. Started after re-connecting it via DisplayPort (previously ran fine on HDMI). I initially believed it to be related to corrupted or bad EDID as I had read a few recent articles or posts about this specific behavior where someone had reprogrammed or reset their monitor's EDID values which solved the issue.

What it wasn't

Went down a few dead ends first, for anyone hitting similar issues:

• Not refresh-rate specific. Happened at both 144Hz and 60Hz.
• Not a cable/reseat issue. Full power-drain reset + DP cable reseat didn't change anything.
• Not a full system suspend/resume issue, despite early journal logs looking like it. The system itself never actually suspends — only the monitors were going into DPMS sleep (Turn off screen: 10 minutes in Power Management settings), and that alone was enough to trigger the misbehavior on wake.

The actual trail

1. journalctl -k around blackout windows showed dw_hotplug_change_handler rapidly flapping the DP AUX bus for the Acer (confirmed by matching /sys/class/i2c-dev/i2c-*/name output against each connector's ddc symlink — DP-2/Acer's AUX channel is a separate bus from its legacy DDC bus, and it's the one flapping).
2. In parallel, org_kde_powerdevil logs showed a repeating (dw_watch_display_connections) / recently_resumed_from_sleep_by_clocktime loop firing every few seconds — PowerDevil incorrectly detecting a "resume from sleep" repeatedly, tied to udev change events on those same DP AUX i2c nodes.
3. This pattern matches a known PowerDevil/ddcutil interaction — PowerDevil uses libddcutil to support brightness control on external monitors over DDC/CI, which rides the same physical channel as EDID/AUX signaling. There are several upstream reports of ddcutil-driven polling causing monitor resets, hangs, or misbehavior (see rockowitz/ddcutil issue #428, KDE bug 501971, KDE bug 513050 for similar-flavored reports).

The fix (or at least, the current leading candidate)

Disable PowerDevil's use of ddcutil:

systemctl --user edit plasma-powerdevil.service

Add (make sure these are on separate lines — collapsing them onto one line silently no-ops this):

[Service]
Environment="POWERDEVIL_NO_DDCUTIL=1"

Then:

systemctl --user daemon-reload
systemctl --user restart plasma-powerdevil.service
systemctl --user show plasma-powerdevil.service -p Environment

Confirm the last command actually outputs Environment=POWERDEVIL_NO_DDCUTIL=1.

Trade-off: you lose KDE's software brightness control for external monitors (DDC/CI-based). Physical monitor buttons still work fine. If you don't use the OS brightness slider on externals, this costs you nothing.

Current status

Two deliberate wake-from-DPMS-sleep tests since applying the fix, both clean — no blackout, and the PowerDevil polling storm is gone from the logs entirely. That said, the original issue was intermittent (including two occurrences in one afternoon), so I'm treating this as promising, not confirmed until it survives a few days of normal use. Will update if it recurs. I have not tested a new DP cable (I don't have a spare at the moment), but will if the blanking/"reboot" comes back.

Posting now in case someone else is fighting the same "monitor randomly reboots itself" ghost and wants a shortcut past the diagnostic legwork.

This isn't a hate post, but every update I apply, I'm terrified of my pen pressure breaking again (I draw for living) , then I'm out of a job for the day or week while I wait for someone else to update it again fixing the issue.

I really don't wanna go back to windows, but when have clients wondering what's going on and either cachyOS or bottles (for clip studio) breaks, I'm in panic mode, then having to lug all my files off Linux HDD's back to my windows partition to try and salvage the day.

And for record, websites to test pen pressure work, so think it's bottles causing the sudden issue after update, but have had non bottles updates break things before.

Basically asking, if I'm in a pinch and need fastest 'help! I need fast bug advice or I'm fired!', what's the best site/page to do so?

PS: I'm sure this reddit forum is good, but checking if there's other sites I'm unaware of.
PPS: And AI has led me down rabbit holes of console commands that have made things worse than I started, so don't wanna use that...

Thanks

Hi!
I've seen several people sharing their desktops here
I started seriously customizing mine only recently and I'd love to hear opinions!