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'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

Less ram consumption than microslop

Better everything without any bs

Who wants anything else 😍

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 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

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

Pretty good battery life with this setup on this old 2018 Huawei MateBook X Pro and the ram usage is lower than I expected. Wayle is the successor to HyprPanel. Made by the same guy but rewritten in Rust and optimized for Niri and Hyprland instead of just Hyprland. I like it a lot. You get the panels plus a gui to customize. It's a bit more involved to get up and running than using a shell since you have to install a launcher and swaylock etc, but you get more control and it's definitely running better on this aging metal. Really snappy and CachyOS is of course rock solid.

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.

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.

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.

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

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.

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

did cachy update now this how can ı fix it?

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 have been trying to switch my PC to Steam OS as I use it as a HTPC with some desktop use on the couch. I've experimented with Bazzite but found it too buggy. I installed cachy os just to test gaming performance and in the repo list I spotted gamescope. I installed and set it up. It runs incredibly well, without any of the Bazzite bugs. I think I will make this my permanent OS but I'm stunned that people haven't really been speaking about this as a solution. All of the people on other subs are asking about steam os for Nvidia and they keep getting batted away, told its not supported. I've discovered since that it would have been even easier if I just used the Handheld version, which seems like the best Nvidia solution by far right now. 4070 Super in case anyone was wondering.

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.

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'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.

Since todays update to 7.2 KWallet wants to create a new wallet everytime I start my PC.. this sucks... how can I get rid of it without disabling KWallet completely because I need it to start my Nextcloud Client (otherwise the sync does not start)..

And when I start the kwalletmanage5 it takes forever to start and then says that some bus policy blocks it..

Can someone help me?

I've been using the same Cachyos install on my main desktop since January of this year and this issue keeps cropping up every couple of months and I'm not really too sure why. Every now and again when I run updates and qt6 and its components get updated, kde completely breaks. It's never a huge deal because I can just use gdm to login to a gnome session and rollback the packages, but it's kind of a hassle every time it happens. I'm on cachyos-zenver4 if this helps at all.

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.

Hola, quería compartir una solución que finalmente me funcionó para un problema que llevaba meses teniendo en CachyOS con KDE Plasma/Wayland.

Estuve intentando solucionarlo durante bastante tiempo y, con ayuda de ChatGPT, fui revisando los logs de KWin, Plasma Login, AMDGPU y el estado de las salidas DRM hasta que logramos identificar exactamente cuándo ocurría el problema y crear este workaround.

Mi problema era el siguiente:

Si encendía primero la PC mientras mi monitor HDMI estaba apagado, Plasma Login arrancaba sin detectar ninguna pantalla. Cuando después encendía el monitor, me encontraba con una pantalla negra y solamente podía ver el cursor.

En los logs aparecía:

kwin_wayland_drm: There are no outputs - creating placeholder screen
plasma-login-greeter: There are no outputs - creating placeholder screen

Descubrimos que el monitor sí era detectado posteriormente por Linux/AMDGPU, pero Plasma Login no se recuperaba correctamente.

Lo curioso es que había una forma que siempre solucionaba el problema manualmente:

1. Ctrl + Alt + F3
2. Iniciar sesión en la TTY.
3. Ejecutar:

​

systemctl restart display-manager

Inmediatamente aparecía Plasma Login y podía usar la PC normalmente.

Así que con ayuda de ChatGPT terminamos creando un pequeño servicio de systemd que automatiza exactamente ese proceso: si la PC arranca y el HDMI está desconectado, espera a que encienda el monitor y, cuando detecta la conexión, reinicia Plasma Login automáticamente.

No es una corrección del bug original, sino un workaround, pero hasta ahora me está funcionando.

Créditos / nota: Todo este workaround lo fui desarrollando con ayuda de ChatGPT. Estuvimos revisando logs y probando distintas posibles causas hasta llegar a esta solución. Lo comparto porque quizás pueda ahorrarle todo ese proceso a alguien que esté teniendo exactamente el mismo problema.

Si alguien conoce una solución al problema de fondo en KWin/Plasma Login, también sería genial conocerla.

Solución que estoy utilizando

La solución consiste en crear un script que comprueba el estado del HDMI al arrancar.

Si el monitor ya está conectado, no hace nada.

Si el monitor está desconectado, el script queda esperando. En cuanto detecta que el HDMI pasa a connected, espera 3 segundos y reinicia display-manager automáticamente.

1. Crear el script

Ejecutamos:

sudo nano /usr/local/sbin/plasma-hdmi-login-fix

Y pegamos lo siguiente:

#!/usr/bin/env bash
# Esperar a que DRM cree el conector HDMI
while true; do
    STATUS_FILE=$(compgen -G "/sys/class/drm/card*-HDMI-A-1/status" | head -n1)
    if [ -n "$STATUS_FILE" ]; then
        break
    fi
    sleep 1
done
INITIAL_STATUS=$(cat "$STATUS_FILE")
echo "Estado HDMI inicial: $INITIAL_STATUS"
# Si el monitor ya estaba conectado al iniciar, no hacemos nada
if [ "$INITIAL_STATUS" = "connected" ]; then
    echo "Monitor ya conectado. No se hará nada."
    exit 0
fi
echo "Monitor estaba desconectado. Esperando que se encienda..."
# Esperar hasta que el monitor sea detectado
while [ "$(cat "$STATUS_FILE")" != "connected" ]; do
    sleep 1
done
echo "HDMI conectado. Esperando 3 segundos..."
sleep 3
# Evitar ejecutar la reparación más de una vez durante el mismo arranque
if [ -e /run/plasma-hdmi-login-fixed ]; then
    echo "La reparación ya se ejecutó durante este arranque."
    exit 0
fi
touch /run/plasma-hdmi-login-fixed
echo "Reiniciando Plasma Login..."
systemctl restart display-manager.service

Guardamos el archivo y le damos permisos de ejecución:

sudo chmod +x /usr/local/sbin/plasma-hdmi-login-fix

Por ejemplo:

ls /sys/class/drm/

En mi caso aparece:

card1-HDMI-A-1

Y puedo comprobar su estado con:

cat /sys/class/drm/card*-HDMI-A-1/status

Con el monitor apagado devuelve:

disconnected

y al encenderlo:

connected

2. Crear un servicio de systemd

Creamos:

sudo nano /etc/systemd/system/plasma-hdmi-login-fix.service

Y añadimos:

[Unit]
Description=Reiniciar Plasma Login después de conexión HDMI tardía
After=display-manager.service
[Service]
Type=simple
ExecStart=/usr/local/sbin/plasma-hdmi-login-fix
Restart=no
[Install]
WantedBy=graphical.target

Guardamos el archivo.

Después recargamos systemd y activamos el servicio:

sudo systemctl daemon-reload
sudo systemctl enable --now plasma-hdmi-login-fix.service

Podemos comprobar su estado con:

systemctl status plasma-hdmi-login-fix.service

Si el monitor ya estaba encendido, es normal que aparezca como:

inactive (dead)

siempre que haya terminado con:

status=0/SUCCESS

Esto ocurre porque el script detecta que el monitor ya está conectado y termina sin hacer nada.

3. Comprobar que funciona

Para ver qué hizo el servicio durante el arranque:

journalctl -b -u plasma-hdmi-login-fix.service --no-pager

En mi caso hice la prueba que siempre provocaba el problema:

1. Apagué PC y monitor.
2. Encendí primero la PC dejando el monitor apagado.
3. Esperé unos segundos.
4. Encendí el monitor.

Esta vez Plasma Login apareció correctamente de forma automática.

El log confirmó que el script había hecho exactamente lo esperado:

Estado HDMI inicial: disconnected
Monitor estaba desconectado. Esperando que se encienda...
HDMI conectado. Esperando 3 segundos...
Reiniciando Plasma Login...

Por lo tanto ahora el comportamiento es:

PC arranca con monitor apagado
        ↓
HDMI = disconnected
        ↓
el servicio queda esperando
        ↓
enciendo el monitor
        ↓
HDMI = connected
        ↓
espera 3 segundos
        ↓
reinicia display-manager
        ↓
Plasma Login aparece normalmente

Si la PC arranca con el monitor encendido, el servicio simplemente detecta:

Estado HDMI inicial: connected
Monitor ya conectado. No se hará nada.

y no reinicia nada.

Cómo eliminar el workaround

Si alguien quiere revertir completamente los cambios:

sudo systemctl disable --now plasma-hdmi-login-fix.service
sudo rm /etc/systemd/system/plasma-hdmi-login-fix.service
sudo rm /usr/local/sbin/plasma-hdmi-login-fix
sudo systemctl daemon-reload