Arch Linux User Repository

Hi. Since the package became an orphan, I adopted it to continue what I actively maintain on https://aur.archlinux.org/pkgbase/linux-mainline-git, now on this AUR package.

The build script and config file will be up-to-date with Arch's official Linux package unless an update is required to be functional.

But I intentionally removed the documentation package because it consumes too much building time.

This package supports certain customization if compiled by the user. Check for the README file inside the package repo, or the .INSTALL message after package installation to learn how.

I personally use this a lot to build arbitrary kernels but it needs a cleanup;

Tons of Steam Deck users are gonna be playing around so wanna add 'any', and GKH is maintaining 5.10.y and a whole bunch of other kernels due to popular demand.

@osimarr should I delete this or convert it into just a generic x.x.y PKGBUILD?

5.15    Greg Kroah-Hartman & Sasha Levin    2021-10-31  Oct, 2023
5.10    Greg Kroah-Hartman & Sasha Levin    2020-12-13  Dec, 2026
5.4     Greg Kroah-Hartman & Sasha Levin    2019-11-24  Dec, 2025
4.19    Greg Kroah-Hartman & Sasha Levin    2018-10-22  Dec, 2024
4.14    Greg Kroah-Hartman & Sasha Levin    2017-11-12  Jan, 2024
4.9     Greg Kroah-Hartman & Sasha Levin    2016-12-11  Jan, 2023

via kernel.org

Ok created a public working copy here with history: https://github.com/sickcodes/linux-git

Just submitting a PR, with the way I use it; would love to see how everyone else uses this

@osimarr, see https://github.com/sickcodes/linux-git/invitations

Perhaps merge and you take charge?

I changed it to 'any' and used zcat config.gz

@osimarr sure gimme sec, I will create a repo for PRs if that helps, Ill show you what I use and you can show me what you use and we can come up with something cool

If possible, I'd like to co-maintain too. I created linux-mainline-git as I'm using it regularly. I'm basing the config on official Arch's config + extra configs I may notice important.

Just adopted unless anyone else wants to co-maintain, I'll make it update to latest release kernel, based off what /proc/config.gz you're using.

I got this error when compiling second time to bisect a bug.

make[4]: *** No rule to make target 'libbpf_legacy.h', needed by '/mnt/d/code/linux-git/src/linux/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf.o'.  Stop.
make[3]: *** [Makefile:158: /mnt/d/code/linux-git/src/linux/tools/bpf/resolve_btfids/libbpf/staticobjs/libbpf-in.o] Error 2
make[2]: *** [Makefile:44: /mnt/d/code/linux-git/src/linux/tools/bpf/resolve_btfids//libbpf/libbpf.a] Error 2

I fixed it by changing make all to make clean all.

After upgrading to 5.16-rc1, it requires resolve_btfids 1 to build modules correctly, so it misses the following steps:

    mkdir -p /lib/modules/$(uname -r)/build/tools/bpf/resolve_btfids/
    cp /tmp/packerbuild-1000/linux-git/linux-git/src/linux/tools/bpf/resolve_btfids/resolve_btfids /lib/modules/$(uname -r)/build/tools/bpf/resolve_btfids/

Otherwise you will get an error during building modules:

/bin/sh: line 1: ./tools/bpf/resolve_btfids/resolve_btfids: No such file or directory
make[2]: *** [scripts/Makefile.modfinal:61: /var/lib/dkms/vboxhost/6.1.28_OSE/build/vboxnetadp>
make[2]: *** Deleting file '/var/lib/dkms/vboxhost/6.1.28_OSE/build/vboxnetadp/vboxnetadp.ko'
make[2]: *** Waiting for unfinished jobs....
/bin/sh: line 1: ./tools/bpf/resolve_btfids/resolve_btfids: No such file or directory
make[2]: *** [scripts/Makefile.modfinal:61: /var/lib/dkms/vboxhost/6.1.28_OSE/build/vboxnetflt>
make[2]: *** Deleting file '/var/lib/dkms/vboxhost/6.1.28_OSE/build/vboxnetflt/vboxnetflt.ko'
make[1]: *** [scripts/Makefile.modpost:140: __modpost] Error 2
make: *** [Makefile:1761: modules] Error 2
make: Leaving directory '/usr/lib/modules/5.16.0-rc1-1-git-00003-g8ab774587903/build'

Extremely important if you use a swap file (e.g. fallocate, dd)

https://lwn.net/Articles/848265/

Do not touch 5.12-rc1, Linus says there is a bug that can overwrite data if you use a swap file.

@mxfm: I can confirm that the linux-mainline package works for me. You seem to be right. Thanks for the hint!

@Harey then there is a bug in kernel code (if generated package is unbootable for several rc versions) or there is some rare issue with the package (if you cannot boot neither 5.09 or 5.10). Perhaps the -git package does not include some necessary driver for your machine, which is included in core archlinux package (you can try to copy 'config' file from archlinux trunk).

For the reasons already mentioned, I switched to the mainline AUR package which provides rc versions each Monday. These rc versions are likely to be more stable that random git versions, but bugs are still possible. I can say that the mainline pakage is bootable at least for me for the last 5-7 rc versions, including current rc5.