| Git Clone URL: | https://aur.archlinux.org/linux-lts510.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-lts510 |
| Description: | Headers and scripts for building modules for the LTS 5.10 Linux kernel |
| Upstream URL: | https://www.kernel.org/ |
| Keywords: | kernel linux |
| Licenses: | GPL2 |
| Submitter: | jonathon |
| Maintainer: | severach |
| Last Packager: | severach |
| Votes: | 10 |
| Popularity: | 0.000279 |
| First Submitted: | 2022-01-11 00:20 (UTC) |
| Last Updated: | 2025-05-02 23:14 (UTC) |
@severach Thanks! I modified and included it in my binary package build since it uses the latest GCC anyway and it seems to work fine. Of course if it gets patched upstream my build will break temporarily.
https://build.opensuse.org/package/binaries/home:curb:ArchLinux/linux-lts510/Arch
I already have a patch adapted from this for 179. I was waiting a version to see if they patch upstream. Looks like no.
It might be a while until 180 works. Recent updates to GCC or libc or the utilities or something recent has broken a whole bunch of packages. Apparently the 5.10 kernel as well.
I have set up an automated packaging system for this kernel using openSUSE's build system to create binary releases. I have been using these packages for a while and they seem to work fine. The process automatically checks and downloads the latest kernel source from kernel.org, verifies the signature, then builds this package.
Find the binary packages here: https://build.opensuse.org/package/binaries/home:curb:ArchLinux/linux-lts510/Arch
You can edit the PKGBUILD and change the version from 5.10.153 to 5.10.157 then change the first sha256sum to fc4cd7c0777ed53f1350e73877e9918df3c40d8e8abe93c6e1a0eb21556d327f and it should verify and compile. I've been too lazy to test the result though.
You alive @jonathon?
Hopefully just on holiday, but back eventually.
dkms install problem with linux-lts510 5.10.153 in kernel-lts.
No dkms modules install for linux-lts510 post package update.
/usr/lib/modules/5.10.153-1-lts510/build/scripts/sign-file: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
Openssl related I assume.
Linx, Linux-zen, Linux-lts repo packages all no probs.
The following patch can be applied to this package to make the build compatible with pahole 1.24
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -161,7 +161,7 @@
vmlinux_link ${1}
info "BTF" ${2}
- LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} -J ${1}
+ LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} --skip_encoding_btf_enum64 -J ${1}
# Create ${2} which contains just .BTF section but no symbols. Add
# SHF_ALLOC because .BTF will be part of the vmlinux image. --strip-all
Unfortunately the source uses tabs, those indents above are actually single tabs so you might not be able to cut/paste(?). Maybe use the -l option to patch. Save this to 0002-fix-pahole.patch and add it to the source and sha256sums in PKGBUILD. This patch could be improved by detecting the kernel version and such but I think they're already working on this for the upstream kernel tree.
@0strodamus Thanks! Indeed pahole was updated to 1.24 recently because it's a requirement for kernel 6. This is apparently a longstanding pahole bug and the developers themselves had to revert back to 1.23 but then kernel 6 requires 1.24 which reintroduced the bug. As stated, 1.23 works.
@gnaggnoyil @ozz I experienced the same issue. Downgrading pahole (1.24 => 1.23) enabled a successful build for me (leave $srcdir in place and re-run with "makepkg -e" to save time).
Pinned Comments
jonathon commented on 2022-01-11 19:25 (UTC) (edited on 2022-05-18 10:09 (UTC) by jonathon)
Please make sure you read the "How to use the AUR" wiki page before reporting issues: https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_and_upgrading_packages
A binary package is also available in my kernel-lts unofficial user repository.