If you’re on Bazzite you have to add a couple to the silverblue command. Once enabled, the copr, make sure to do:
sudo rpm-ostree override remove kernel kernel-devel-matched kernel-devel kernel-core kernel-modules kernel-modules-core kernel-modules-extra --install kernel-cachyos-rt
You add kernel-devel-matched and kernel-devel or you get an error instead.
@bieszczaders you can add these instructions if you want not really necessary if they check the comments
You can enable support for Secure Boot by self-signing the kernel with a key added as a MOK.
I wrote a guide for it here: CachyOS Kernel for Fedora with Secure Boot · GitHub
Hello there.
I can’t boot into graphical mode with kernel 6.15.1. With 6.14.8 works fine. Tried reinstalling NVIDIA driver 575.57.08 and the new kernel, ran akmod --rebuild and dracut regenerate, but still not able to fully boot. It gets stuck (after pressing ESC) in gdm.sevice, but plymouth only shows a frozen loading image (pressing ESC again)
[Edit]
Removing completely Negativo17’s drivers and using kernel-cachyos-nvidia-open it works, but with for games until now, the performance is not good and some crash when trying to open.
[Edit]
Definetely a bug, only after removing all driver related files; restarting and installing the driver again I was able to use my system again with kernel 6.15.1 with the proprietary driver.
Dealing with NVIDIA is tiresome 
6.15.1 works fine for me with an Intel GPU.
How could I do the same secureboot type signing on Bluefin/Aurora?
It seems it’s slightly more complicated to self-sign 3rd party kernels in Silverblue/Bluefin/Aurora. According to what I found this might be what you’d have to do:
To install a custom kernel on Fedora Silverblue, you typically need to build an RPM with your changes and then use the command sudo rpm-ostree override replace ./your-kernel.rpm to apply it.
So you need to download the rpm, extract it, sign the kernel, create a new rpm and then install it. And you’d want to make it automatic for all updates. Perhaps one way to do it would be using a cron job that checks for an updated kernel every X hours.
We can only hope that the CachyOS kernel will get (self-)signed like Bluefin, so that you just need to import the key using mokutil.
Hi mister, I’d like to report a recurring issue that I’ve encountered since kernel version 6.15.1, which still persists in 6.15.2 — though it occurs intermittently.
My system sometimes fails to shut down or reboot properly due to a failure in unmounting ZRAM devices. However, systemd still reports that the shutdown process completes successfully. I check log from Plymouth’s verbose mode (accessed by pressing the Esc key) and I get this.
Any idea how to fix it? I report this on GitHub Issue too, and I forwarding here
