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
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 ?
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.
Hi, this - and I suppose all your kernel RPMS - are not ready for Silverblue, installation fails with
sudo rpm-ostree install kernel-longterm
[…]
Downloading from ‘copr:copr.fedorainfracloud.org:kwizart:kernel-longterm-6.1’… done
Importing packages… done
Applying 5 overrides and 75 overlays
Processing packages… done
Running pre scripts… done
Running post scripts… done
Running posttrans scripts… done
error: Running %posttrans for kernel-longterm-core: bwrap(/bin/sh): Child process killed by signal 1; run journalctl -t 'rpm-ostree(kernel-longterm-core.posttrans)' for more information
Since the fedora live kernel is currently Oopsing again and it is mind-boggling why the LTS kernel is not part of standard fedora to begin with, what is the requirement to get this one running under Silverblue time/money wise or better yet get it into Fedora proper?
What is the output of journalctl -t 'rpm-ostree(kernel-longterm-core.posttrans) in your case ?
The kernel should behave like the normal fedora kernel package with respect to ostree. Now maybe there are changes in the ostree side that would not apply to the kernel-longterm package…
journalctl -t ‘rpm-ostree(kernel-longterm-core.posttrans)’
Nov 14 18:02:33 t470 rpm-ostree(kernel-longterm-core.posttrans)[12896]: Failed to chase ‘/boot’: No such file or directory
Nov 14 18:03:19 t470 rpm-ostree(kernel-longterm-core.posttrans)[13562]: Failed to chase ‘/boot’: No such file or directory
– Boot 4ba26ce60f6f4755b8638bf75dd7d1bc –
Nov 14 18:05:08 t470 rpm-ostree(kernel-longterm-core.posttrans)[5613]: Failed to chase ‘/boot’: No such file or directory
– Boot 366bc03942614feb820f8f2bf6e05c16 –
Nov 30 19:52:20 t470 rpm-ostree(kernel-longterm-core.posttrans)[64912]: Failed to chase ‘/boot’: No such file or directory
Because I tried the current 6.6 kernel - which still goes into panic - I noticed that the last stable version 6.4 was deleted from Koji when I tried to reinstall it. Left without a non-crashing kernel I tried installing kernel-longterm again today. Still fails but with a slightly different error than given above:
rt.posttrans)[21857]: /usr/bin/dracut: line 1056: /sys/module/firmware_class/parameters/path: No such file or directory
rt.posttrans)[21857]: dracut: No ‘/dev/log’ or ‘logger’ included for syslog logging
rt.posttrans)[21857]: dracut: Can’t write to /boot: Directory /boot does not exist or is not accessible.
rt.posttrans)[21822]: /usr/lib/kernel/install.d/50-dracut.install failed with exit status 1.