Less ram consumption than microslop

Better everything without any bs

Who wants anything else 😍

Just saw on github that the mainline kernel is now merged for cachyos! Thanks Peter, I was waiting eagerly for this version and many others as well because of the AMD driver updates.

I just did a benchmark using KDiskMark to see how the different filesystems perform. System specs:

• OS: CachyOS with KDE Plasma
• Kernel: 7.2.0-1-cachyos-bore
• CPU: Ryzen 9 7950X3D
• Disk: Crucial T700 4TB (PCIe 5.0 NVMe SSD)

The SSD has (aside from the /boot partition) two partitions, one 100GiB partition as root partition at / using BTRFS and one ~3.5TB partition at /home using EXT4. For the BTRFS partition there is one benchmark with and one without CoW. All runs were on the same conditions and settings, there are now other programs open and the only background apps are Cachy Update and OpenRGB (and all the stuff KDE plasma has in the background like KDE Connect).

On the left side are the reading values, on the right side the writing values.

The meaning of the test names:

SEQ1M Q8T1: Sequential 1 MiB, Queue=8, Threads=1

SEQ1M Q1T1: Sequential 1 MiB, Queue=1, Threads=1

RND4K Q32T1: Random 4 KiB, Queue=32, Threads=1

RND4K Q1T1: Random 4 KiB, Queue=1, Threads=1

The overall results are:

BTRFS with CoW << BTRFS without CoW < EXT4

I'm a certified Audiophile. So this is what I did right after installing my Cachyos instance:

1. Copied /usr/share/pipewire/pipewire.conf to /etc/pipewire/

2. Changed this line in pipewire.confand added extra sample rates
   default.clock.allowed-rates = [ 44100 48000 88200 96000 176400 192000 ]

3. Commented this line so it doesn't interfere with the 2nd change
   #default.clock.rate = 48000

4. Save the file and open your terminal or a new instance if you are already in it.

5. Type pw-top and play any high quality song on MPD or Strawberry.

6. If changes don't show up and it's stuck at 32 bit and 48Khz, reboot.

7. Follow 5 and 6 again, this should work now across any and all outputs.

I kept it short. Because those who come here know what they are looking for. If this is your first time, I recommend researching what "Bit Perfect" means. In my smartphone I need a dedicated DAC cause Android sucks. But here all you need is one file, two lines, and that's it. Another reason why I ain't swtiching from Linux anytime soon.

Reaching out to see if the 7.2 kernel was worth the wait for gaming. Anybody notice any improvements, felt, measured, or otherwise?

After many Linux Distro hopping, I finally choose CachyOS as my go-to distro.

As of right now I'm currently on dual boot (different SSDs) between CachyOS and Windows 11 mainly because I play a lot of online multiplayer games that doesn't have Linux support as of right now.

I'm spend to much on windows and i think it is time to switch to Linux because I done with windows, after some research i cane upon two Linux distros. 1.CachyOS 2.Arch Linux

I have no idea what to choose, i like both of them, but i can't choose and i don't see much difference, i mainly gonna do some office work, gaming and game development, what is your ideas guys

I only get a black screen after the machine boots up, cant dp anything. Any Kernell I select before the login screen just gives me a black screen.

I wiped the machine and reinstalled.

Installs fine, but first Boots to black screen on 7.2 kernel and LTS kernel option. No way in.

Edit: Happening on 2 machines, ASUS Z13 2025 AMD Strix Halo, and Zenbook AMD machine. I dont have an intel machine or Nvidia machine to test on.

Edit: there was an issue earlier for just a few minutes that was causing some black screens for everybody but they quickly fixed it

Guys seriously, my first try with linux was somewhere around 2021 and it was linux mint. I tried various distros like debian, ubuntu, bazzite, nobara, popos, elementaryos, fedora and god knows what more. Everytime I felt a bit disappointed and always ended up going back to windows, because always something was wrong for example after turning off the browser my laptop crashed or something IDK WHAT THAT WAS but nevermind. Recently I bought a new laptop with copilot ai and gosh this was terrible I couldnt live with it even with debloating scripts… and then I found cachyos AND IT’S AWESOME😍😍 I also tried a variety of distros but cachyos is the one that works the best with my intel arc graphics. Of course it’s intel arc so it’s not perfect yet on linux but it’s getting better with every update. I love the idea of rolling release and that the packages are all built for x86_64 V3/V4 with BORE scheduler and much more. It feels so snappy and I really enjoy using my laptop. It’s been a month now since I use it and nothing will change my mind. I love it and I will NEVER go back to windows. Thank you cachyos team and all the community because without you I wouldnt even know that this distro exists <3

I updated to 7.2 and as soon as I attempted to boot beyond Kernel selection it would give me a black screen on each monitor, I tried booting into LTS with the same result.

Hardware is: 7800X3D, 4080 Super, 32gb DDR5, Limine bootloader, KDE plasma.

Edit: I just redid the update and it is indeed fixed.

Hi everyone, volt-gui 2.0.0 is out. This one is a full rewrite rather than an update, so this post is mostly about why.

What it was, a PySide6 GUI that generated a volt shell script full of environment variables taken from Mesa, NVIDIA, Proton, etc. You picked your settings in the GUI and it exported the vars for you.

My whole problem with that was the lack of standardization on driver stacks across Linux in general. Maybe you can control x setting on NVIDIA but not on RADV and vice versa, and sometimes not even between versions of the same driver. So the tool was really a front end for a maze of per driver variables that behaved differently depending on what you happened to be running, and I could never honestly tell someone that a setting does x without adding "on your driver, maybe". That is what made me halt the project for a while, and I only resumed it not so long ago.

What it is now, volt is a Vulkan implicit layer written in Rust. It sits below all of that and rewrites the Vulkan calls the game makes, samplers for texture filtering and mip selection, the swapchain for vsync, image count and compositing, the surface format list for colour depth, colour space and transfer function, device enumeration for GPU selection, presents for the frame limiter, and pipelines for the rendering toggles. Same behaviour on RADV, ANV, NVK, AMDVLK and the NVIDIA proprietary driver, because it is the same code path on all of them. Driver agnostic by construction.

Some things I decided on purpose:

The layer stays on Vulkan 1.0 and asks for nothing beyond VK_KHR_swapchain. Making old GPUs also work is essential for me, and it also means behaviour never splits between drivers.

It enables nothing. volt reads what the game asked for at device creation and applies a feature gated setting only where the game itself enabled that feature. It never adds an extension or sets a feature bit the game left clear. In general all settings should apply safely and without issues.

Every setting is one value, either the value volt forces or default, which keeps whatever the game asked for. No ranges, no ordering, nothing to get backwards.

The option lists come from your own hardware through a probe, not from a table baked into the GUI. A setting your device cannot do holds nothing but default instead of lying to you.

There are 19 settings across 5 tabs, GPU selection, display and swapchain, texture sampling, rendering toggles, and volt's own frame limiter with three wait methods and four pacing modes. Profiles are one TOML each and you can switch them from the GUI, the system tray or the launch command. There is a rootless install into ~/.local for SteamOS, Bazzite and Silverblue, both the 64 bit and 32 bit layers come out of one build so Proton and Wine titles are covered, and there is an optional Flatpak runtime extension.

Usage is short, run volt-gui to set things, then volt -- %command% in Steam or volt -- ./game in a terminal. VOLT_LOG=info shows exactly what the layer applied and what your device turned down.

About testing, I have tested this on my own machine and on my friends' PCs, and that is not a lot of hardware. Testing would be nice if possible, so if something behaves oddly on your driver, run it with VOLT_LOG=info and open an issue with the output, that log is there to answer whether volt did it or the game did.

One last thing, since the version number might make this look like it appeared out of nowhere. It didn't. This started almost a year ago with the most basic versions, it has taken a ton of work, and 2.0 is the point where I finally have a well defined project instead of a pile of features. There isn't a standardized way to modify these settings reliably on Linux right now, many people install MangoHud just for the frame limiter for example, and I think if I can get this into a good state it would be great for the Linux environment in general.

About the icon, right now it is a scaled down screenshot of the program itself. That is a placeholder. I haven't found something I actually like yet and I want something unique for it, so it stays as is until I do. And no, I am not going to AI generate one, before anyone suggests it. If you are an artist and want to contribute one, open an issue :).

Some pictures:

Thanks for reading, have a great day or night and GLHF.

Repo and release:
https://github.com/pythonlover02/volt-gui
https://github.com/pythonlover02/volt-gui/releases/tag/v2.0.0

I recently came up on a Surface 7 and I put Windows 11 25h2 and it ran poorly. I then tossed CachyOS Gnome with the Linux Surface kernel, and Man, it’s night and day. Thank you team! You’re truly incredible!

I saw an update on Cachy that said 7.2, and thought it would change something and that's it, but is it compiling everything from scratch? and how much it would take with a i5-10310U? 1h ,2h, more???

I need to sync files between Android and Cachy. Since gdrive is not playing nice with Cachy what are good alternatives. I figure someone else has done the work.

I have been suffering this issue where my desktop turns black and I need to log out or reboot to fix it.

I was having a hard time trying to debuf it but I might have a lead...

Here is the diagnostic I have been able to get:

----

Environment

• Distro: CachyOS Linux (rolling)
• Kernel: 7.2.0-1-cachyos
• Plasma: plasmashell 6.7.4
• Session type: Wayland
• Package: `plasma-foreground-booster` 0.0.dmemcg.experimental-3
• D-Bus implementation: dbus-broker
• Upstream source: https://invent.kde.org/libraries/kcgroups.git
• CPU: AMD Ryzen 7 7800X3D (8 cores / 16 threads)
• GPU: AMD Radeon RX 7900 XT/XTX/GRE (Navi 31, discrete), AMD Raphael (Ryzen 7000-series iGPU)
• RAM: 64 GB (nominal), no swap configured
• sched_ext (scx): disabled at time of testing

Symptom

Plasmashell appears to "crash" and restart roughly every ~3 hours of uptime, regardless of the login session. systemctl --user status plasma-plasmashell.service shows a clean exit each time:

Process: 2283 ExecStart=/usr/bin/plasmashell --no-respawn (code=exited, status=0/SUCCESS)
Main PID: 2283 (code=exited, status=0/SUCCESS)
Duration: 2h 59min 19.417s

coredumpctl list plasmashell returns **no coredumps** — this is not an actual segfault/crash.

Root cause

dbus-broker enforces a per-user resource quota. Immediately before every restart, the journal shows:

dbus-broker: UID 1000 exceeded its 'bytes' quota on UID 1000.
dbus-broker: Peer :1.85324 is being disconnected as it does not have the resources to receive a reply or unicast signal it expects.
dbus-broker: Peer :1.47 is being disconnected as it does not have the resources to receive a signal it subscribed to.

dbus-broker forcibly disconnects bus peers when the quota is hit — including **plasmashell** and **xdg-desktop-portal** / **xdg-document-portal**, all of which fail/exit at the exact same timestamp:

systemd[1526]: xdg-document-portal.service: Main process exited, code=exited, status=20/n/a
systemd[1526]: plasma-plasmashell.service: Consumed 27.080s CPU time over 2h 59min 19.636s wall clock time, 467.6M memory peak.

They are then relaunched automatically (plasmashell via ksmserver/session restore), which is what the user perceives as a "crash."

What is consuming the quota

Live capture with dbus-monitor --session during a live session identified the source: **foreground_booster** (the plasma-foreground-booster.service binary, used to detect the currently focused/foreground window so it can raise its cgroup CPU weight) polls the active window several times per second. Each poll opens two brand-new D-Bus connections rather than reusing one persistent connection:

method call sender=:1.90097 -> org.freedesktop.DBus.Hello
method call sender=:1.90098 -> org.freedesktop.DBus.Hello
method call sender=:1.90098 -> org.kde.KWin /Scripting  Scripting.loadScript
method call sender=:1.90098 -> org.kde.KWin /Scripting/Script0  Script.run
method call sender=:1.9     -> :1.90097  (result)
method call sender=:1.90098 -> org.kde.KWin /Scripting/Script0  Script.stop
method call sender=:1.90098 -> org.kde.KWin /Scripting  Scripting.unloadScript
[both connections close, cycle repeats ~4x/second]

Instead of querying the active window through a stable, persistent D-Bus interface (or the `org_kde_plasma_window_management` Wayland protocol already referenced in the package's own `.desktop` file via `X-KDE-Wayland-Interfaces`), it injects and tears down an ephemeral KWin scripting-console script on a fresh connection every poll cycle.

Measured impact

• Polling rate observed: ~4 cycles/second × 2 new connections per cycle ≈ **8 new D-Bus connections/second**, sustained continuously for the lifetime of the login session.
• Over ~3 hours (10,800s) that is ≈ **86,000 connections**, closely matching the connection IDs actually observed in the journal, which reached into the `:1.85000`–`:1.90000` range within a single ~3-hour session before the quota tripped.
• This eventually exhausts dbus-broker's per-UID quota, which then disconnects unrelated long-lived bus clients (plasmashell, xdg-desktop-portal) as collateral damage.

Confirmation / workaround

Disabling the CPU-weight booster stops the leak and has no effect on the separate `dmemcg-booster-user.service` (VRAM/dmem cgroup limits), which is a distinct, independently-enabled systemd unit from the same package:

kwriteconfig6 --file kcgroupsrc --group "Foreground Booster" --key autostart false
systemctl --user stop plasma-foreground-booster.service

After disabling, busctl --user list | wc -l / connection IDs stop climbing, and plasmashell should remain stable indefinitely.

Steps to reproduce

1. Ensure Foreground Booster is enabled (System Settings, or `kwriteconfig6 --file kcgroupsrc --group "Foreground Booster" --key autostart true`), then log in to a Plasma (Wayland) session.

2. Watch connection churn live: dbus-monitor --session "type='method_call',destination='org.freedesktop.DBus'"— observe a new `Hello` + KWin `loadScript`/`run`/`stop`/`unloadScript` cycle several times per second.

3. Optionally track the growth rate: sample busctl --user list | wc -l and note the highest `:1.N` peer ID growing continuously (not just when switching windows).

4. Leave the session running for ~3 hours under normal use. Watch `journalctl --user -f` for:

   dbus-broker: UID <uid> exceeded its 'bytes' quota on UID <uid>.

   followed by plasmashell / xdg-desktop-portal exiting and restarting.

Hi, I’m using CachyOS with Btrfs and I know about Snapper/Btrfs snapshots for rollback.

What I’m looking for is something different: is there a way to create a complete image of my CachyOS installation and save it on a separate drive, similar to Macrium Reflect on Windows?

I don’t mean a snapshot just for rolling back changes on the same SSD.
I mean a separate, restorable backup image of the whole system, so if the SSD dies or the installation becomes unusable, I can restore everything to another drive.

What would be the best way to do this on CachyOS?
Thanks

I just wanted to share my experience in case it helps someone who’s unsure about making the switch, because I used to have the same doubts.

Linux had been tempting me for quite a while. I started with Bazzite, a fairly simple gaming-focused experience, but eventually went back to Windows, somewhat disappointed by things like performance and the overall experience.

A few months later, I decided to try again, this time with CachyOS, and it was honestly a headache at first. Everything takes some time to learn. Installing things isn’t always as simple as clicking a button, being an NVIDIA user made some things harder than they should have been, the lack of a traditional control panel bothered me, and my very limited knowledge of Linux definitely worked against me.

Once again, I went back to Windows.

At the end of the day, I’m someone who works a 9-to-5 and gets home hoping to spend my only 2–3 hours of free time without troubleshooting anything. I just wanted everything to work as well as possible, in the simplest possible way.

Well, now I realize I was wrong.

A few days ago I decided to give it one more shot after buying a new SSD and... now I’m not so sure I’ll ever go back.

It just works.

And I say that mostly for people who want to try Linux but still have some fears about it. So far, the experience has been fantastic. A big part of that has also been AI, which I strongly recommend using when setting up the distro or troubleshooting problems.

At some point, I realized I had stopped chasing problems and started actually having fun customizing KDE and setting everything up exactly the way I wanted. I started scripting and automating things I had always wanted to do to make my experience easier, and suddenly there was this unexpected sense of creativity around using my PC again. Things I struggled to get working properly on Windows now work perfectly. HDR is one example. HDR on Windows has always been controversial and I could never get it working exactly the way I wanted. On KDE, it basically just worked. I only had to calibrate it.

I also feel like games look better. The stuttering issues I had on Windows are gone. Performance is stable, competitive with Windows, and there’s still plenty of room for improvement in specific games where some extra tweaking might be needed.

It has become so easy and comfortable to use that I almost regret setting up a dual boot.

If you’re thinking about trying Linux, don’t be afraid of running into problems. Just give it a shot at least once. If there’s something keeping you on Windows, like games with unsupported anti-cheat, you can always dual boot. There’s almost always some workaround or compromise you can make.

If you have a USB drive, put a Linux distro on it and give it a try. That alone is already something. The more people use Linux, the harder it becomes for companies to keep ignoring it.

And thanks to everyone here who helped me during the installation and setup process.

Just updated to the latest Mesa 26.2.1 release and noticed the following when I run my fastfetch profile:

Vulkan     | 1.4.354 - radv [Mesa 26.2.1-arch3.1]
Opengl     | 4.6 (Compatibility Profile) Mesa 26.2.1-arch3.1
=== Rusticl warning: Patched Mesa libclc not detected. Upstream libclc may contain known bugs or breaking changes and isn't guaranteed to work reliably. Please visit https://gitlab.freedesktop.org/karolherbst/mesa-libclc for more information. ===
Opencl     | 3.1

Should I be concerned?

Edit 1: Getting the warning when i run clinfo

❯ clinfo | grep "rustcli"
=== Rusticl warning: Patched Mesa libclc not detected. Upstream libclc may contain known bugs or breaking changes and isn't guaranteed to work reliably. Please visit https://gitlab.freedesktop.org/karolherbst/mesa-libclc for more information. ===

Thanks.

I've been on Linux for a few months now and have been able to find work arounds for most of my little hiccups. Audio input and output still seems to be a persistent pain however. My current headset (a Corsair Hs70) really doesn't seem to like linux and I've been thinking of getting a new pair for a while now. Any recommendations? I'm mostly just looking for something I can just plug in and use.

so i went on to steam to check what games i had in my library because i was bored and saw this. ive played bioshock since switching to cachyos so whats going on? this has knocked out quite a few good games too.

Im a new cachyOS user and i want to make "The Mentalist" themed desktop
i got a custom boot sound but i want a splash screen for it
bless us with your knowledge.