kwizart/kernel-longterm-6.1

Team Workflows Projects in Copr
1

Description

Kernel built of longterm 6.1 branch (WIP)

Installation Instructions

This repository is created in the hope it will be useful. But is provided without any warranty.

This kernel built of the longterm support 6.1 branch (LT) is derived from the fedora spec file adapted to build across RHEL/CentOS 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.

If you want to provide any donation, contributions are welcomed with paypal.me/kwizart

Switch to kernel longterm 6.1

sudo dnf copr enable kwizart/kernel-longterm-6.1
sudo dnf install kernel-longterm
sudo reboot

Install devel packages for external kernel modules needs

sudo dnf install kernel-longterm-devel

Active Releases

The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

* Total number of packages downloaded in the last seven days.

This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-6.1/
2

Is there any MOK key that I should have on my system (Fedora 38)? It’s a bit annoying to sign the kernel after each update.

3

Thanks for rising this point.

Best would be to automate this on end-users systems. AKA same as using the akmod for building dedicated kmod. But of course it’s moot if you expect to protect your key. (So you need to trust your system).

Would you help to contribute that approach to akmods ?

4

Site note: I should have fixed the aarch64 build for f39+.
Hopefully the build should be all green on the next update…

5

Sorry, I don’t know how to automate it even on my own machine. I expected that you have generated key for signing the kernels, that I have to import on my PC, like Ventoy do it.

6

If you follow akmods docs on secureboot (rpm -qd akmods).
you should generate an akmod key that should also work for kernel.
See also https://bugzilla.redhat.com/show_bug.cgi?id=2070866

7

Unfortunately, I had no success with akmods, so I create a postinst script for signing the kernels Automatically signing long term kernels with Machine Owner Key (MOK) using post-install script · GitHub