Package Details: linux-lts510 5.10.214-1

Git Clone URL: https://aur.archlinux.org/linux-lts510.git (read-only, click to copy)
Package Base: linux-lts510
Description: The LTS 5.10 Linux kernel and modules
Upstream URL: https://www.kernel.org/
Keywords: kernel linux
Licenses: GPL2
Provides: VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: jonathon
Maintainer: severach
Last Packager: severach
Votes: 9
Popularity: 0.000054
First Submitted: 2022-01-11 00:20 (UTC)
Last Updated: 2024-03-27 21:16 (UTC)

Dependencies (19)

Required by (4)

Sources (5)

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.

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

xx777 commented on 2023-08-18 16:33 (UTC)

linux-lts510-5.10.191-1-x86_64.pkg.tar.zst

linux-lts-5.10.90-1-x86_64.pkg.tar.zst (from arch archive)

linux-lts-5.15.94-1-x86_64.pkg.tar.zst (from arch archive)

The three kernels above cannot boot on my pc.

But i tested linux-lts510-5.10.191-1-x86_64.pkg.tar.zst in a VM and it is bootable.

so maybe there is something wrong with my arch.

severach commented on 2023-08-18 15:06 (UTC) (edited on 2023-08-18 15:07 (UTC) by severach)

The kernel is often broken by the compiler, binutils, or the kernel team. I boot all kernels before updating. I am booted to 5.10.191 right now. There are many reasons old kernels are not compatible with your current environment. I don't get these boot failures from Arch much but I get them from Manjaro constantly. Note the output of pacman -Dk then reinstall all packages.

xx777 commented on 2023-08-18 05:47 (UTC) (edited on 2023-08-18 05:49 (UTC) by xx777)

unable to boot, it stuck here. I tried linux-lts-5.10.90-1-x86_64.pkg.tar.zst from arch archive and got the same result.

https://i.imgur.com/ka4XY9K.jpg

ozz commented on 2023-06-14 20:14 (UTC) (edited on 2023-06-15 13:24 (UTC) by ozz)

The GCC issue is now fixed upstream with version 184. Binary build available in the regular place.

ozz commented on 2023-05-18 00:00 (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

severach commented on 2023-05-17 19:43 (UTC) (edited on 2023-05-17 19:45 (UTC) by severach)

I already have a patch adapted from this for 179. I was waiting a version to see if they patch upstream. Looks like no.

ozz commented on 2023-05-17 14:56 (UTC)

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.

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

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.