Package Details: linux-slim-headers 5.12.v.10-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-slim
Description: Header files and scripts for building modules for the slimmed down linux kernel.
Upstream URL:
Licenses: GPL2
Submitter: eggz
Maintainer: eggz
Last Packager: eggz
Votes: 1
Popularity: 0.000000
First Submitted: 2019-05-31 15:23
Last Updated: 2021-06-10 12:32

Pinned Comments

eggz commented on 2019-05-31 15:54

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

Server =$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

1 2 3 Next › Last »

eggz commented on 2021-02-17 22:43

Oh, this kernel is just the kernel I run on my pc, it only supports amd/radeon modern desktop hardware. I just publish this kernel for debug purposes, since it autotests my build pipelines each build, and sends back useful info for feedback. For full feedback/test I need a full run, so this actually includes an AUR publish.

This is why it has "zero compatibility" in the description; its not really meant for the general public, but people are welcome to try it on (it really is a lightweight kernel!) .

This kernel has also been useful in the past for spotting module problems: This kernel has got zero bagage, and barely has enough to run on my testsystem. comparing problems with this (core only) kernel with a fully feautured one (or vice versa) can reveal alot of info surrounding a problem. (like when the problem lies in a non-core module)

Im glad that you are so interested, but long story short, this kernel is probably more usefull to me than it is to you :-)

jogai commented on 2021-02-17 07:51

This one: The znver2 variant has a clear description why it exists, but its not so clear what the slimmed version actually provides, or left out.

eggz commented on 2021-02-15 20:42

You will have to specify "amd kernels".

jogai commented on 2021-02-15 20:19

Whats the difference with your linux-amd kernels?

eggz commented on 2020-12-20 13:32

Well I for one am very proud that I am not compatible with proprietary nvidia software :-) Jokes asside though, I will ommit the provides sections enterely if this solves any conflicts.

Scimmia commented on 2020-12-20 13:12

dkms has nothing to do with this, as they don't have binary modules and therefor don't have a hard dep on the kernel they are built against. It's not a bad example, but take a look at any of the binary modules in the repos. They have a dep on 'linux' because they require that package to work. Saying that this provides 'linux' means that this package can satisfy that dep, which it can't.

eggz commented on 2020-12-20 13:07

That package is made up by proprietary, non standard dependencies (like nvidia-dkms instead of dkms) and other blobs which have nothing to do with using open standards.

I am however compatible with standard dkms installations of modules. I could not care less about non-open implementations that are not compatible with my kernel, that is not the linux way.

Bad example perhaps?

Scimmia commented on 2020-12-20 12:54

Let's try this another way. This package: requires 'linux'. Can you install this package instead of the 'linux' package and use that module? If not, it doesn't provide 'linux'.

eggz commented on 2020-12-20 12:51

My kernels are build to satisfy most packages, and are binary compatible with them, as I do not make drastic changes into the kernel. If this kernel was incompatible with them in the way that you claimed then it would be an almost unusable kernel. I'm not trying to invent a new kernel here like Vmware or Darwin. this is just another finetuned linux kernel.

Scimmia commented on 2020-12-20 12:44

That's the problem. The packages claim to, but they don't. 'linux' is a specific package, not a virtual dep meaning any kernel. The binary modules in the repos require 'linux' because they are built against that kernel, these packages are not binary compatible with that kernel and cannot use those modules, so it can't satisfy that dep.