Package Details: linux-lts510-docs 5.10.174-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-lts510
Description: Documentation for the LTS 5.10 Linux kernel
Upstream URL:
Keywords: kernel linux
Licenses: GPL2
Submitter: jonathon
Maintainer: severach
Last Packager: severach
Votes: 10
Popularity: 0.102205
First Submitted: 2022-01-11 00:20 (UTC)
Last Updated: 2023-03-14 10:42 (UTC)

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:

A binary package is also available in my kernel-lts unofficial user repository.

Latest Comments

1 2 3 Next › Last »

ozz commented on 2022-12-13 15:46 (UTC) (edited on 2023-03-14 21:13 (UTC) by ozz)

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, verifies the signature, then builds this package.

Find the binary packages here:

ozz commented on 2022-12-05 23:37 (UTC)

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.

hugh commented on 2022-12-05 22:46 (UTC)

You alive @jonathon?

Hopefully just on holiday, but back eventually.

hugh commented on 2022-11-07 19:26 (UTC) (edited on 2022-11-07 19:27 (UTC) by hugh)

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: cannot open shared object file: No such file or directory

Openssl related I assume.

Linx, Linux-zen, Linux-lts repo packages all no probs.

ozz commented on 2022-10-16 02:22 (UTC) (edited on 2022-10-16 02:32 (UTC) by ozz)

The following patch can be applied to this package to make the build compatible with pahole 1.24

--- a/scripts/
+++ b/scripts/
@@ -161,7 +161,7 @@
    vmlinux_link ${1}

    info "BTF" ${2}
+   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.

ozz commented on 2022-10-16 01:15 (UTC)

@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.

0strodamus commented on 2022-10-15 23:33 (UTC)

@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).

ozz commented on 2022-10-15 21:40 (UTC)

@gnaggnoyil Same problem. Looks like resolve_btfids is returning EINVAL. Could this have something to do with the kernel 6 release or just a coincidence?

gnaggnoyil commented on 2022-10-15 13:12 (UTC)

I just encountered the following error when I ran extra-x86_64-build for this package:

  LD      vmlinux
  BTFIDS  vmlinux
FAILED: load BTF from vmlinux: Unknown error -22make: *** [Makefile:1189: vmlinux] Error 255
==> ERROR: A failure occurred in build().
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/gnaggnoyil/build

Is there anyone facing the same problem here? What could possibly go wrong?