Package Details: linux-lts510-headers 5.10.238-1

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-06-08 15:29 (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: 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 5 Next › Last »

gnaggnoyil commented on 2023-08-19 16:52 (UTC)

I tried building this package in a clean chroot today and got the following error:

./include/linux/usb/ch9.h:1: warning: no structured comments found
./include/linux/spi/spi.h:673: warning: Function parameter or member 'devm_allocated' not described in 'spi_controller'
./include/linux/regulator/driver.h:385: warning: Function parameter or member 'ramp_reg' not described in 'regulator_desc'
./include/linux/regulator/driver.h:385: warning: Function parameter or member 'ramp_mask' not described in 'regulator_desc'
./include/linux/regulator/driver.h:385: warning: Function parameter or member 'ramp_delay_table' not described in 'regulator_desc'
./include/linux/regulator/driver.h:385: warning: Function parameter or member 'n_ramp_values' not described in 'regulator_desc'
./include/linux/gpio/driver.h:293: warning: Function parameter or member 'parent_handler_data_array' not described in 'gpio_irq_chip'
./include/linux/device.h:561: warning: Function parameter or member 'msi_lock' not described in 'device'
./drivers/gpu/host1x/bus.c:742: warning: Excess function parameter 'key' description in '__host1x_client_register'
/build/linux-lts510/src/linux-5.10.191/Documentation/arm64/tagged-address-abi.rst:52: ERROR: Unexpected indentation.
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 ./include/linux/blk-mq.h' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 ./block/blk-mq.c' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 ./include/linux/genhd.h' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 -function pci_driver ./include/linux/pci.h' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'
...
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 -export ./drivers/input/sparse-keymap.c' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'
WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 7.2.2 ./include/linux/interconnect-provider.h' processing failed with: unsupported operand type(s) for +: 'PosixPath' and 'str'

Sphinx parallel build error:
TypeError: object of type 'PosixPath' has no len()
make[1]: *** [Documentation/Makefile:91: htmldocs] Error 2
make: *** [Makefile:1688: htmldocs] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/gnaggnoyil/build

Does anyone know what was going wrong here?

xx777 commented on 2023-08-18 19:59 (UTC) (edited on 2023-08-18 21:32 (UTC) by xx777)

@ozz, thanks for your help, but it's hard for me to find the first SEQNUM device that blocked everything.

i tried some kernels from arch archive:

linux-lts-6.1.46-1-x86_64.pkg.tar.zst --> bootable

linux-6.0.12.arch1-1-x86_64.pkg.tar.zst --> bootable

linux-5.19.13.arch1-1-x86_64.pkg.tar.zst --> bootable

linux-5.19.arch1-1-x86_64.pkg.tar.zst --> bootable

linux-5.18.16.arch1-1-x86_64.pkg.tar.zst --> unable to boot

linux-5.17.9.arch1-1-x86_64.pkg.tar.zst --> unable to boot

linux-5.16.16.arch1-1-x86_64.pkg.tar.zst --> unable to boot

linux-lts-5.15.94-1-x86_64.pkg.tar.zst --> unable to boot

linux-lts-5.10.90-1-x86_64.pkg.tar.zst --> unable to boot

by the way, i installed arch in a usb3.0 pendrive, will it be the reason that my pc doesnt boot with older kernels?

Update:

installed a new Arch on local HDD and then got the complete same result:

kernel >= 5.19 ( bootable )

kernel <= 5.18 ( unable to boot )

ozz commented on 2023-08-18 19:13 (UTC)

@xx777 that udev debug looks good but it scrolled past what we need to see. On the screenshot everything is waiting for SEQNUM 1488 but we can't see what that is and there may be even more things before that one that 1488 is blocked on. What you're looking for is the first SEQNUM device startup that is causing everything after that to get blocked. I usually record video to see what is happening (or redirect the console to a serial port but that's a lot more work).

xx777 commented on 2023-08-18 17:53 (UTC)

@ozz, thanks for your response.

boot parameter "quiet" enabled

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

boot parameter "quiet" disabled

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

boot parameters "quiet" disabled and "udev.log-priority=debug" enabled

https://i.imgur.com/4MfXBlo.jpg

I have a LinuxMint on the another partition, and it can boot with kernel 5.10. and 5.15., so i think my gpu (AMD R7 240) is compatible with older kernels.

My Arch works fine with linux-lts 6.1.45-1.

ozz commented on 2023-08-18 17:09 (UTC)

@xx777 Do you have "quiet" enabled in your kernel boot parameters? If so, at the GRUB prompt push e and remove it to see if it will print any more information. You can also try adding "udev.log-priority=debug" to the boot parameters as well.

Another thing to try is disconnect every device you can from your system them try to boot. Sometimes the system is actually booting but the video is frozen so if you can, try a different video output.

Does booting a completely different kernel work? Like the stock one or LTS.

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.