This repository is created in the hope it will be useful. But is provided without any warranty.
This kernel built of the long term (LT) support 6.12 branch is derived from the fedora spec file adapted to build across RHEL/CentOS Stream and current Fedora releases. This kernel should be useful for those using external kernel modules, but don't want to re-base their kernel too often and break their external modules compatibility. It should also be useful for "Enterprise Linux" users where their modified kernel might produce incompatibilities with external modules. Or even those of us who want to run closer to upstream kernel code. Last, but not least, it also allows to verify kernel regressions and helps bisect and identify them into LT branches, so they can be reported upstream.
If you want to provide any donation, contributions are welcomed with paypal.me/kwizart
error: Updating rpm-md repo 'copr:copr.fedorainfracloud.org:kwizart:kernel-longterm-6.12': Failed to download gpg key for repo 'copr:copr.fedorainfracloud.org:kwizart:kernel-longterm-6.12': Status code: 404 for https://download.copr.fedorainfracloud.org/results/kwizart/kernel-longterm-6.12/pubkey.gpg (IP: XXX.XXX.XX.XX)
I tested further with installing on atomic desktops
the kernel-install wrapper is still not found
What I did
1. Use a container based system
Not sure if this is needed, but you can use universal blue systems, or the unofficial Fedora OCI images (which are the base of the entirety of universal blue since forever)
error: Running %posttrans for kernel-longterm-core: bwrap(/bin/sh): Processo filho foi terminado pelo sinal 1; run `journalctl -t 'rpm-ostree(kernel-longterm-core.posttrans)'` for more information
Fedora officially includes Hyprland in its repositories, but the packaged version is often outdated and may have bugs. Solopasha maintains a more up-to-date and stable version via their COPR repository. To give you flexibility, I’ve included both versions in the build—so you can choose the one that best suits your needs.
During installation in Silverblue f43 cliwrap deprecation warning and posttrans error.
$ rpm-ostree cliwrap install-to-root
warning: cliwrap is deprecated; the replacement path is to get functionality into the relevant upstream projects.
error: Missing required argument: ROOTDIR
I get some errors with latest kernel (6.12.61-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Dec 7 11:59:15 UTC 2025):
journalctl -r --priority=err
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e75e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e76e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e76e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e77c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e77c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e76e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e76e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e75e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e75e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e774
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e77c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e77c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e75c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e76e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e766
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2013e77c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2014abdc
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c97e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c93c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x20034ece
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c9a6
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x201453a2
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2002d98e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c9fe
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c93c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2002db4c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2014544e
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x20140b32
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x20030efe
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2003c98c
Dec 09 13:31:18 maketopsite kernel: rtw89_8852ce 0000:62:00.0: [ERR]fw PC = 0x2014abc6
Dec 09 08:18:59 maketopsite kernel: microcode: CPU23: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU22: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU21: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU20: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU19: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU18: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU17: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU16: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU15: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU14: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU13: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU12: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU11: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU10: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU9: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU8: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU7: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU6: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU5: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU4: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU3: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU2: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
Dec 09 08:18:59 maketopsite kernel: microcode: CPU1: update failed for patch_level=0x0b204037
Dec 09 08:18:59 maketopsite kernel: microcode: No sha256 digest for patch ID: 0xb204037 found
You are supposed to report to upstream maintainer directly at bugzilla.kernel.org or else.
From a quick, looks, only 6.12.52 have changes related to this rtw89 driver ;
It would be interesting to see if you can reproduce with kernel-longterm-6.12.51. My guess is that it should start to fail with 6.12.52. Unless it’s a change in the kernel-firmware package…
Please reproduce with fedora kernel if you don’t know how to deal with such kind of issue.