tuxinvader / focal-mainline-builder Goto Github PK

The build script has no error checking. A side effect of this is that when the kernel package building fails for any reason (it's normal for the mainline builds to fail sometimes), the metapackage is built and uploaded regardless.

The result is that those who use the PPA, will have a broken apt status, because the metapackage depends on a package that doesn't exist.

I switched the vesion of dwarves used in the docker container to download one from my PPA. This is exactly the same version as the one used in Groovy (built from groovy source deb). The change was made because I needed dwarves to be available in focal, so that launchpad can build binaries from the linux source deb. However there's no reason to use my PPA version in the container itself.

The dwarves package is the only non-transparent part of this project, so revert to using the official package.

I'm trying to compile 5.10.46 and keep running into issues at the end when generating man pages.
After 1h+ I first got an issue with missing rst2man for tools/bpf/bpftool/Documentation/Makefile.
I "fixed" this by adding apt-get install python-docutils to your image.
But after another 1h+ attempt I get a similar issue now with asciidoc for tools/perf.

I'm not sure why I get these issues now, the last time with 5.10.39 it worked just fine. I don't see changes to the Makefiles of these tools.

It is very frustrating that all the time to compile the kernel is lost and the process needs to be started from the beginning again each attempt / after installing a dependency, and I don't know what else I will need.

Do you have any idea / am I doing something wrong?

install -m755 debian/tools/generic /home/source/debian/linux-tools-common/usr/sbin/bpftool
make -C /home/source/debian/build/tools/tools/bpf/bpftool doc
make[1]: Entering directory '/home/source/debian/build/tools/tools/bpf/bpftool'
  DESCEND  Documentation
make[2]: Entering directory '/home/source/debian/build/tools/tools/bpf/bpftool/Documentation'
Makefile:45: *** "rst2man not found, but required to generate man pages".  Stop.
make[2]: Leaving directory '/home/source/debian/build/tools/tools/bpf/bpftool/Documentation'
make[1]: *** [Makefile:205: doc] Error 2
make[1]: Leaving directory '/home/source/debian/build/tools/tools/bpf/bpftool'
make: *** [debian/rules.d/3-binary-indep.mk:114: install-tools] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
********

Moving packages to debs folder

********
mv: cannot stat '/home/source/../*.*': No such file or directory

Makefile:215: Please install asciidoc to have the man pages installed
  ASCIIDOC perf-diff.xml
/bin/sh: 2: asciidoc: not found
make[4]: *** [Makefile:296: perf-diff.xml] Error 127
make[3]: *** [Makefile.perf:864: man] Error 2
make[2]: *** [Makefile.perf:229: sub-make] Error 2
make[1]: *** [Makefile:110: man] Error 2
make[1]: Leaving directory '/home/source/debian/build/tools/tools/perf'
make: *** [debian/rules.d/3-binary-indep.mk:119: install-tools] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Hi,

thanks for the work you put into this, it works great (for 5.12.6) and is very transparent too.

However I cannot manage to build 5.10.39 (LTS) or 5.11.22 .

Output from "your" script with -e kver=v5.10.39:

********

Renaming source package and updating control files

********
********

Applying default configs

********
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
debian/rules.d/0-common-vars.mk:15: *** first argument to 'word' function must be greater than 0.  Stop.
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
sed: can't read debian.master-21.10/changelog: No such file or directory
debian/rules.d/0-common-vars.mk:15: *** first argument to 'word' function must be greater than 0.  Stop.
********

Building packages
Command: dpkg-buildpackage --build=binary -aamd64 -d -uc -ui -us

********
dpkg-buildpackage: error: cannot open file debian/changelog: No such file or directory
********

Moving packages to debs folder

********
mv: cannot stat '/home/source/../*.*': No such file or directory
********

Cleaning git source tree

Actually the error is even similar to the log output of the official mainline builder that kept failing recently:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928535/comments/3

So maybe this is not even an issue here but rather upstream in the ubuntu build scripts?
I'm not too familiar with the whole kernel build process so I hope it's OK I opened this issue here to ask.

Is it possible to check out just the specific version being built instead of the entire cod tree? I see that build.sh has an option to skip the update step, but after building it still does git checkout master.

Consider using git switch $kver instead of git checkout. At the end you can do git switch (without arguments) to switch back to the previous state of the local git repo (if that is important).

It's also possible to use git worktrees (git worktree add /new/path <commit-ish>) to checkout the desired revision somewhere in tmp and leave the main local repo alone. At the end you can simply drop the temporary worktree, and not worry about cleanup at all.

I don't know why but I can't install 6.0 or 6.1 kernels on Jammy since some weeks. I saw on launchpad that you were getting errors with amd64, but now I see you have been able to build succesfully though I still get these errors:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-generic-6.00 : Depends: linux-headers-6.0.18-060018-generic but it is not instalable
                      Depends: linux-image-unsigned-6.0.18-060018-generic but it is not instalable
                      Depends: linux-modules-6.0.18-060018-generic but it is not instalable
E: Unable to correct problems, you have held broken packages.

Same happens with linux-generic.6.01 package.

# perf
WARNING: perf not found for kernel 5.12.10-051210

  You may need to install the following packages for this specific kernel:
    linux-tools-5.12.10-051210-generic
    linux-cloud-tools-5.12.10-051210-generic

  You may also want to install one of the following packages to keep up to date:
    linux-tools-generic
    linux-cloud-tools-generic
# apt-get install linux-tools-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  linux-tools-5.4.0-74 linux-tools-5.4.0-74-generic
The following NEW packages will be installed:
  linux-tools-5.4.0-74 linux-tools-5.4.0-74-generic linux-tools-generic
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 5623 kB of archives.
After this operation, 25.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

5.4.0 it is not current kernel version

# apt-get install linux-tools-5.12.10-051210-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package linux-tools-5.12.10-051210-generic
E: Couldn't find any package by glob 'linux-tools-5.12.10-051210-generic'
E: Couldn't find any package by regex 'linux-tools-5.12.10-051210-generic'
# 

I found some similar names and tried to install linux-tools-common-5.12.10 linux-tools-host-5.12.10, but they does not contain binary files:

# dpkg -L linux-tools-common-5.12.10 linux-tools-host-5.12.10
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-common-5.12.10
/usr/share/doc/linux-tools-common-5.12.10/changelog.Debian.gz
/usr/share/doc/linux-tools-common-5.12.10/copyright

/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-host-5.12.10
/usr/share/doc/linux-tools-host-5.12.10/changelog.Debian.gz
/usr/share/doc/linux-tools-host-5.12.10/copyright

I am searching the following but for the new kernel:

# dpkg -L linux-tools-5.4.0-74-generic              
/.
/usr
/usr/lib
/usr/lib/linux-tools
/usr/lib/linux-tools/5.4.0-74-generic
/usr/share
/usr/share/doc
/usr/share/doc/linux-tools-5.4.0-74-generic
/usr/share/doc/linux-tools-5.4.0-74-generic/copyright
/usr/lib/linux-tools/5.4.0-74-generic/acpidbg
/usr/lib/linux-tools/5.4.0-74-generic/bpftool
/usr/lib/linux-tools/5.4.0-74-generic/cpupower
/usr/lib/linux-tools/5.4.0-74-generic/libperf-jvmti.so
/usr/lib/linux-tools/5.4.0-74-generic/perf
/usr/lib/linux-tools/5.4.0-74-generic/turbostat
/usr/lib/linux-tools/5.4.0-74-generic/usbip
/usr/lib/linux-tools/5.4.0-74-generic/usbipd
/usr/lib/linux-tools/5.4.0-74-generic/x86_energy_perf_policy
/usr/share/doc/linux-tools-5.4.0-74-generic/changelog.Debian.gz

No sound with latest from https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline (6.0.3-060003.202210220529). Downgrading to 6.0.2-060002.202210150929 brings sound back.
Output of inxi is the same with 6.0.3 apart from kernel version string.

> inxi -A
Audio:     Device-1: Intel Comet Lake PCH cAVS driver: sof-audio-pci-intel-cnl
           Sound Server: ALSA v: k6.0.2-060002-generic

> cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

The issue is exactly as described here: https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ (no hardware device, only dummy output/input) and the only option which almost helped was to add options snd-hda-intel snd-intel-dspcfg.dsp_driver=1 to /etc/modprobe.d/alsa-base.conf and force-reload alsa — this felt back from sof-audio-pci-intel-cnl driver to snd-hda-intel and brought back sound output, but no mic. Had to downgrade to 6.0.2 where there's no such issue.

Please let me know whether I should provide any additional info to help you figure the root cause.
Thanks.

Is it reasonable to expect your PPA to eventually support the latest kernels for 22.04, or would we need to fork this and make that change ourselves? I love the ease with which you've made the latest Linux kernels accessible to Ubuntu users, and I hope that eventually we'll get to enjoy these amazing kernels on 22.04!

I am getting the following error on build

dpkg-buildpackage: info: source package linux-5.15.18
dpkg-buildpackage: info: source version 5.15.18-051518.202201291503
dpkg-buildpackage: info: source distribution focal
dpkg-buildpackage: info: source changed by Mainline Build <kernel@sita>
 dpkg-source --before-build .
dpkg-source: info: using options from source/debian/source/options: --diff-ignore --tar-ignore
dpkg-source: warning: can't parse dependency dwarves (>=1.17-1) (>= 1.21) [amd64 arm64 armhf ppc64el s390x riscv64] <!stage1>
dpkg-source: error: error occurred while parsing Build-Depends
dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 255

Works as expected if you comment out this line

It's quite a big package and I understand that is quite troublesome to have such large blob ready to download, but I don't see any option to build one from local docker.
What way do you suggest then? (IMO: still the best would be to provide option to docker)

Hello there.

I just wanted to let you know that there seems to be a boot error on 20.04 with kernels 5.14.12 and up. I don't know what the ubuntu people changed, but it seems to be the same issue as before when you recompiled their kernel. It looks like it's loading up drivers, network, but the video never loads. Like the video driver is wrong or it's hung up on that kernel switch that the ubuntu developers are using. I forget the name usbmon_blah_blah something. Whatever it was they did to jack up the kernel for LTS, it looks like it's back. Could you test on some non-virtual hardware if possible. This device with this issue is a old intel laptop. So, the drivers are fairly mature. Specs are listed below:

System: Host: user Kernel: 5.14.11-051411-generic x86_64 bits: 64 Desktop: Cinnamon 5.0.6 Distro: Linux Mint 20.2 Uma
Machine: Type: Laptop System: Dell product: Latitude E6420 v: 01 serial: CptCrunch
Mobo: Dell model: 0K0DNP v: A01 serial: gerbil BIOS: Dell v: A26 date: 09/14/2018
Battery: ID-1: BAT0 charge: 93.7 Wh condition: 93.7/96.6 Wh (97%)
CPU: Topology: Quad Core model: Intel Core i7-2760QM bits: 64 type: MT MCP L2 cache: 6144 KiB
Speed: 807 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 885 2: 949 3: 820 4: 833 5: 819 6: 846 7: 898
8: 898
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
Display: server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 21.2.4 - kisak-mesa PPA
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.14.11-051411-generic
Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi
IF: wlp2s0 state: up mac: an:dc:he:es:ee
Drives: Local Storage: total: 465.76 GiB used: 271.44 GiB (58.3%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
Partition: ID-1: / size: 338.74 GiB used: 271.44 GiB (80.1%) fs: ext4 dev: /dev/sda3
Sensors: System Temperatures: cpu: 52.0 C mobo: 27.0 C sodimm: 36.0 C
Fan Speeds (RPM): cpu: 0
Info: Processes: 300 Uptime: 19m Memory: 7.65 GiB used: 2.08 GiB (27.2%) Shell: bash inxi: 3.0.38

There are no fatal hardware errors in dmesg. Software packaging is clean.

Thank you for your time. Your kernel has made Ubuntu LTS suck a lot less.

Hi Tuxinvader, I see there's not been any activity on the code for this repo for a while, or engagement with questions. I understand that, we all get caught up with life, coding takes a back seat, priorities change. It's a popular repo, so it'd be a shame for it to lapse into abandonment.

What can we do to help? Is there a particular bug you're stuck with, perhaps another maintainer would help? Or maybe passing it on to someone else? Let us know, I'm sure there's plenty of folks here who'll be keen to help.

Thanks

At the moment, the long-term ppa only contains the 5.10 branch, but 5.15 is now also a lts version. Please add build of 5.15 branch to the long-term ppa, it is very convenient to use

The build script just sets it to jammy.

Therefore it is required to provide the --series option.

TuxInvader: first off, THANK YOU. I was able to upgrade again.

This request is for a little hand holding on understanding, so I am ok if you say no, close it and ban me. lol.
Even though it takes forever to compile, i have run tests for buildmeta yes and no, rename yes and no, and every possible combination. ...and I am not getting something obviously.

So I was expecting that one of these combinations to yield 3 header files, 2 modules and 2 image debs....but I am getting that and many others. I have already passed the flag --exclude=cloud-tools,udebs,tools but still get the following additional ones.:

• linux-cloud-tools-common-*
• linux-cloud-tools-common-*
• linux-source-*
• linux-tools-common-*
• linux-tools-host-*
• linux-buildinfo-*

So, here are my questions:

• Can you confirm that buildmeta basically adds:
  • linux-generic-kernelmajorversion_kernelactualversion.gz and deb
  • same but for latency.
• can you confirm that rename, adds the version with no dots after the kernelactualversion? i wasn't really sure.
• is there anything i can add to --exclude, so that i just get the 7 debs that you find in the kernel mainline site, but also to speed the compile by not having to do any work on the items that are supposed to be excluded?

Thank you in advance, thanks for your patience, and thanks again for this work!!!!

Hello.
I see not any kernel 6.3 for focal 20.04 in your ppa.
Not demanding .. only trying see if not more updates for focal.
Happening any issues when compiling ?

Have an nice week.

Hi,

Could you please release a 5.19.X kernel again via your lts-mainline ppa?

I have compatibility issue with my AMD CPU with NVIDIA GPU on the 6.X kernels.

(Any 5.X version from 5.16 and higher does work for me, but of course the most recent is preferred.)

The mainline kernel removed LZ4 as an AMD64 build dependency on 5.12.11, and added zstd.

$ git diff cod/mainline/v5.12.10 debian.master/control.stub.in
diff --git a/debian.master/control.stub.in b/debian.master/control.stub.in
index c8bc555da0f6..01cd82721efd 100644
--- a/debian.master/control.stub.in
+++ b/debian.master/control.stub.in
@@ -37,7 +37,8 @@ Build-Depends:
  libnuma-dev [amd64 arm64 ppc64el s390x] <!stage1>,
  dkms <!stage1>,
  curl <!stage1>,
- lz4 [amd64 s390x] <!stage1>,
+ lz4 [s390x] <!stage1>,
+ zstd [amd64] <!stage1>,
  dwarves [amd64 arm64 armhf ppc64el s390x] <!stage1>,
 Build-Depends-Indep:
  xmlto <!stage1>,

However the kernel config file is still set to use LZ4 compression.

$ grep -i lz4 debian.master/config/amd64/config.common.amd64 
CONFIG_KERNEL_LZ4=y
CONFIG_LZ4HC_COMPRESS=y
CONFIG_LZ4_COMPRESS=y

It looks like mainline may be intending to switch to zstd compression on amd64, so I've not opened a bug on launchpad.
The build.sh script now checks for LZ4 in the kernel config and re-adds the dependency.

Fix: 3435a1d

When/if mainline switch to zstd we should automatically stop adding the dependency.

my organization blocking this ppa to add on our systems , any possible way u can help ?? thanks

TuxInvader ... thanks very much for compiling kernel 6.5 for Focal.
Have an nice next week !

Hi @TuxInvader, thank you for the great work. I wanted to modify the code but realized that the license was not specified. May I know what the license of this repository is? Could you kindly add a license file to this repository as well? Thanks!

The 6.8 kernel series adds the following kconfig logic for pahole versioning:

root@x220:/build/linux-6.8# grep -A1 'config PAHOLE_HAS_LANG_EXCLUDE' lib/Kconfig.debug
config PAHOLE_HAS_LANG_EXCLUDE
	def_bool PAHOLE_VERSION >= 124

20.04 (focal) is at pahole version 1.21 from the dwarves(https://packages.ubuntu.com/focal-updates/dwarves) (thank you for that too, or we'd be stuck with 5.15 🤦 ), and this triggers the impossible config situation disabling rust as mentioned by you at https://bugs.launchpad.net/ubuntu/+source/rustc-1.62/+bug/1993183/comments/16 :

root@x220:/build/linux-6.8# grep "config RUST$" init/Kconfig -A7
config RUST
	bool "Rust support"
	depends on HAVE_RUST
	depends on RUST_IS_AVAILABLE
	depends on !GCC_PLUGINS
	depends on !RANDSTRUCT
	depends on !DEBUG_INFO_BTF || PAHOLE_HAS_LANG_EXCLUDE
	select CONSTRUCTORS

This triggers invalidating the debian control changes implemented at

I have not had the chance to see when this change was introduced into the kernel, unfortunately.

Would you have the bandwidth to see if back-porting dwarves or pahole from mantic Jammy (version 1.25) to focal is possible?

EDIT:
The list of versions of packages for Linux-6.8 keeps getting larger:

• pahole >=1.24 (jammy packaged source builds successfully on focal with only debian/changelog mod).
• ld (i.e. binutils(binutils-x86-64-linux-gnu)) >= 2.40 (for zstd compressed debug sections).

Looks like the headers (the one without the -generic) do not include any of the actual source header fiels in them. Thus all of the symlinks from the -generic header are breaking. As a temporary work around I could download the original kernel-ppa and install the _all .deb file and then do the following symlink

sudo ln -s /usr/src/linux-headers-5.12.7-051207 /usr/src/linux-5.12.7-headers-5.12.7-051207

To make it work but the one included in your package is missing the header files completely (only looked at the .6 and .7 releases so I figure it has been a problem for a longer) and also the naming pattern that the symlinks are looking for is inaccurate as well so in addition to using the original .deb packages just to get the source code, you also have to create a symlink to have your version of the -generic symlink to the correct headers as well.

Just to add why this is important, you cannot build the nvidia binaries or anything else that requires kernel source code (thus anything from the dkms) without making this correction by hand after installing from your lts ppa (which I also assume is temporary until the actual kernel-ppa fixes their junk and goes back to the 5.31 instead of 5.33 glib)

Hi TuxInvader

I'm working on some functionality and I'd like to build a kernel with a local patch.
As I can see '--patch' option requires patch to be present on https://cdn.kernel.org, which is not this case.

would you suggest any idea?

regards

Hello.
Only trying understand if will have kernel updates for Focal.

When accessing
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.1/amd64/
not any kernel compiled deb files.
Canonical is having build issues too ?

However Jammy has build issues with 6.1.
Perhaps not more kernel updates to Focal 20.04 ?

Thanks for reply.
Have an nice week.

I just checked Jammy LTS Mainline Kernels and it has failure on recent builds. After checking the build log it seems rust is missing.

Not sure if rustup could help.

Hi! How to add binder_linux module in this kernel?

# modprobe binder_linux
modprobe: FATAL: Module binder_linux not found in directory /lib/modules/6.2.7-060207-generic

Last from a month ago (5.10.128) and latest came out today (5.10.135)?

Are these 5.10.x kernel build discontinued or they will be back?

If no, how I will change to 5.18, 5.19 builds on my 20.04?

Hello.
Thanks for making kernel updates.

Please see the link
pkoutoupis/rapiddisk#133

Not is possible compile
warning: the compiler differs from the one used to build the kernel

What is exactly the compiler name used in yout kernel ?

Thanks for reply.

Hi, very cool project, thanks very much! Could you give more info how the kernel sources you use get into

git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack

and what modifications are done. Are you the owner of that repository?

Cheers,
Martin

Thanks for providing this great tool. I've been using it to build my own lowlatency kernels for some weeks now. All worked fine until v5.16.11 (I didn't try v5.16.12). But with v5.16.13 it didn't work.
I invoked it with:

sudo docker run --cpus=7 -ti -e kver=v5.16.13 -v /usr/local/src/cod/mainline:/home/source -v /usr/local/src/cod/debs:/home/debs --rm tuxinvader/focal-mainline-builder:latest --flavour=lowlatency --exclude=cloud-tools,udebs

It ended like this and I got no packages in the debs folder:

make[2]: Leaving directory '/home/source/debian/build/build-lowlatency'
make[1]: Leaving directory '/home/source'
Debug: /home/source/debian/stamps/stamp-prepare-indep
dh_prep -i
Debug: /home/source/debian/stamps/stamp-install-headers
dh_testdir
install -d /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613
find . -path './debian' -prune -o -path './debian.master' -prune \
  -o -path './include/*' -prune \
  -o -path './scripts/*' -prune -o -type f \
  \( -name 'Makefile*' -o -name 'Kconfig*' -o -name 'Kbuild*' -o \
     -name '*.sh' -o -name '*.pl' -o -name '*.lds' \) \
  -print | cpio -pd --preserve-modification-time /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613
23327 blocks
cp -a scripts include /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613
(find arch -name include -type d -print | \
        xargs -n1 -i: find : -type f) | \
        cpio -pd --preserve-modification-time /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arm64/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arm64/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/um/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/um/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/sh/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/sh/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/alpha/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/alpha/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/hexagon/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/hexagon/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/microblaze/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/microblaze/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/mips/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/mips/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/s390/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/s390/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/x86/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/x86/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arm/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arm/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/xtensa/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/xtensa/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/powerpc/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/powerpc/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/openrisc/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/openrisc/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/nios2/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/nios2/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arc/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/arc/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/parisc/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/parisc/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/h8300/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/h8300/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/riscv/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/riscv/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/m68k/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/m68k/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/nds32/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/nds32/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/sparc/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/sparc/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/ia64/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/ia64/include/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/csky/include/uapi/asm/Kbuild not created: newer or same age version exists
cpio: /home/source/debian/linux-headers-5.16.13-051613/usr/src/linux-headers-5.16.13-051613/arch/csky/include/asm/Kbuild not created: newer or same age version exists
28722 blocks
+ grep -q CONFIG_MODULE_SIG=y /home/source/debian/build/build-lowlatency/.config
+ echo /home/source/debian/build/build-lowlatency/scripts/sign-file sha512 /home/source/debian/build/build-lowlatency/certs/signing_key.pem /home/source/debian/build/build-lowlatency/certs/signing_key.x509
Debug: /home/source/debian/stamps/stamp-install-lowlatency kernel_file arch/x86/boot/bzImage kernfile arch/x86/boot/bzImage install_file vmlinuz instfile vmlinuz
dh_testdir
dh_prep -plinux-image-unsigned-5.16.13-051613-lowlatency
dh_prep: error: Requested unknown package linux-image-unsigned-5.16.13-051613-lowlatency via -p/--package, expected one of: linux-source-5.16.13 linux-headers-5.16.13-051613 linux-tools-common linux-tools-5.16.13-051613 linux-cloud-tools-common linux-cloud-tools-5.16.13-051613 linux-tools-host linux-image-unsigned-5.16.13-051613-generic linux-modules-5.16.13-051613-generic linux-modules-extra-5.16.13-051613-generic linux-headers-5.16.13-051613-generic linux-image-unsigned-5.16.13-051613-generic-dbgsym linux-tools-5.16.13-051613-generic linux-cloud-tools-5.16.13-051613-generic linux-buildinfo-5.16.13-051613-generic linux-image-unsigned-5.16.13-051613-generic-64k linux-modules-5.16.13-051613-generic-64k linux-modules-extra-5.16.13-051613-generic-64k linux-headers-5.16.13-051613-generic-64k linux-image-unsigned-5.16.13-051613-generic-64k-dbgsym linux-tools-5.16.13-051613-generic-64k linux-cloud-tools-5.16.13-051613-generic-64k linux-buildinfo-5.16.13-051613-generic-64k linux-image-unsigned-5.16.13-051613-generic-lpae linux-modules-5.16.13-051613-generic-lpae linux-modules-extra-5.16.13-051613-generic-lpae linux-headers-5.16.13-051613-generic-lpae linux-image-unsigned-5.16.13-051613-generic-lpae-dbgsym linux-tools-5.16.13-051613-generic-lpae linux-cloud-tools-5.16.13-051613-generic-lpae linux-buildinfo-5.16.13-051613-generic-lpae
dh_prep: error: unknown option or error during option parsing; aborting
make: *** [debian/rules.d/2-binary-arch.mk:126: /home/source/debian/stamps/stamp-install-lowlatency] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
********

Building meta package

********
********

Moving packages to debs folder

********
mv: cannot stat '/home/source/../*.*': No such file or directory
********

Hello.
I have installed Ubuntu 20.04.3 kernel 5.11.
After installed PPA https://launchpad.net/~tuxinvader/+archive/ubuntu/lts-mainline
sudo apt-get install linux-generic-5.17

Using uname -r show
5.17.3-051703-generic

Using dpkg --list | grep linux-image
ii linux-image-5.11.0-27-generic 5.11.0-27.2920.04.1 amd64 Signed kernel image generic
ii linux-image-generic-hwe-20.04 5.11.0.27.2920.04.11 amd64 Generic Linux kernel image
ii linux-image-unsigned-5.17.3-051703-generic 5.17.3-051703.202204140912 amd64 Linux kernel image for version 5.17.3 on 64 bit x86 SMP

I have installed Rapiddisk (disk read write cache utility).
Rapiddisk have option to install modules in initrd with an command line

sudo bash install_initrd.sh --install --size=128 --cache-mode=wb --kernel=5.11.0-27-generic

changing 5.11.0-27-generic to 5.17.3-051703-generic show the message
**** Error: the kernel version you specified is not installed. Exiting...

I have installed the files below from PPA
linux-headers-5.17.3-051703_5.17.3-051703.202204140912_all
linux-headers-5.17.3-051703-generic_5.17.3-051703.202204140912_amd64.deb
linux-generic-5.17_5.17.3_amd64
linux-image-unsigned-5.17.3-051703-generic_5.17.3-051703.202204140912_amd64
linux-modules-5.17.3-051703-generic_5.17.3-051703.202204140912_amd64

I not understand if need any another file to register information in OS allowing the command line work with the updated kernel.
Please is need to install more others files ? Is correct install kernel 5.17 directly over 5.11 not installing kernel 5.13 before ?

Thanks for read.
Have an nice week.

Hello.
Only for understand ... not demand ...
kernel 6.3 is the last version for focal ?
Thanks for read my topic.
Have an nice week.

Just wondering if anyone else is getting the same errors I am getting:
check-config: loading annotations from /home/source/debian.master/config/annotations

Traceback (most recent call last):
  File "/home/source/debian/scripts/misc/kconfig/annotations.py", line 79, in _parse_body
    entry['policy'] |= literal_eval(m.group(1))
TypeError: unsupported operand type(s) for |=: 'dict' and 'dict'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "debian/scripts/misc/annotations", line 248, in <module>
    main()
  File "debian/scripts/misc/annotations", line 239, in main
    do_check(args)
  File "debian/scripts/misc/annotations", line 178, in do_check
    a = Annotation(args.file)
  File "/home/source/debian/scripts/misc/kconfig/annotations.py", line 20, in __init__
    self._parse(raw_data)
  File "/home/source/debian/scripts/misc/kconfig/annotations.py", line 120, in _parse
    self._parse_body(data)
  File "/home/source/debian/scripts/misc/kconfig/annotations.py", line 88, in _parse_body
    raise Exception(str(e) + f', line = {line}')
Exception: unsupported operand type(s) for |=: 'dict' and 'dict', line = CONFIG_104_QUAD_8 policy<{'amd64': 'm'}>
make: *** [debian/rules.d/4-checks.mk:32: config-prepare-check-generic] Error 1
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

@TuxInvader , i noticed that in your PPA, you had uploaded 6.0.10 and 11...i think. So you are being able to compile without issue?

During the kernel build, the command fakeroot debian/rules clean defaultconfigs actually fails.

The failure is non-significant, and it's ignored because the build.sh doesn't have the errexit shell option enabled, however, it's very confusing when one tries to reproduce the code in order to understand it.

This (based on my understanding) is due to the mainline kernel configured, by default, to build several architectures, which fails, due to cross-compiling toolings missing.

I'm not sure if there is a scripted way to change this option (or an env variable), but regardless, it can be easily changed:

# removes all entries except `amd64` from `archs="amd64 armhf arm64 ppc64el riscv64 s390x`
#
perl -i -pe 's/archs="amd64\K.+/"/' debian.master/etc/kernelconfig

Thank you for your work can you please upload kernel headers for 5.13

Apparently 5.13 has same dependency problem of libc6 2.33

I was trying to build kernel 5.18.15 and ran into the errors below. This was for the following command line:

sudo docker run -ti -e kver=v5.18.15 -v /usr/local/src/cod/mainline:/home/source -v /usr/local/src/cod/debs:/home/debs --rm tuxinvader/focal-mainline-builder:latest

Excerpt from output:
[ "false" != 'true' ] && true ||
rsync -a --exclude debian --exclude debian.master --exclude debian.master * /home/source/debian/build/build-generic
cat /home/source/debian.master/config/config.common.ubuntu /home/source/debian.master/config/amd64/config.common.amd64 /home/source/debian.master/config/amd64/config.flavour.generic | sed -e 's/.CONFIG_VERSION_SIGNATURE./CONFIG_VERSION_SIGNATURE="Ubuntu 5.18.15-051815.202207300418-generic 5.18.15"/' > /home/source/debian/build/build-generic/.config
[ "true" = 'true' ] && true ||
sed -ie 's/.CONFIG_UBUNTU_ODM_DRIVERS./# CONFIG_UBUNTU_ODM_DRIVERS is not set/'
/home/source/debian/build/build-generic/.config
find /home/source/debian/build/build-generic -name "*.ko" | xargs rm -f
make ARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- HOSTCC=x86_64-linux-gnu-gcc-11 CC=x86_64-linux-gnu-gcc-11 KERNELVERSION=5.18.15-051815-generic CONFIG_DEBUG_SECTION_MISMATCH=y KBUILD_BUILD_VERSION="202207300418" LOCALVERSION= localver-extra= CFLAGS_MODULE="-DPKG_ABI=051815" PYTHON=python3 O=/home/source/debian/build/build-generic -j1 syncconfig prepare scripts
make[1]: Entering directory '/home/source'
make[2]: Entering directory '/home/source/debian/build/build-generic'
GEN Makefile
HOSTCC scripts/basic/fixdep
/bin/sh: 1: x86_64-linux-gnu-gcc-11: not found
make[4]: *** [/home/source/scripts/Makefile.host:95: scripts/basic/fixdep] Error 127
make[3]: *** [/home/source/Makefile:564: scripts_basic] Error 2
make[2]: *** [/home/source/Makefile:350: __build_one_by_one] Error 2
make[2]: Leaving directory '/home/source/debian/build/build-generic'
make[1]: *** [Makefile:219: __sub-make] Error 2
make[1]: Leaving directory '/home/source'
make: *** [debian/rules.d/2-binary-arch.mk:31: /home/source/debian/stamps/stamp-prepare-tree-generic] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Building meta package

Moving packages to debs folder

mv: cannot stat '/home/source/../.': No such file or directory

Hi,

Thanks for building the mainline kernel!

I added the ppa and my update manager showed a "kernel update 6.5.4". I tried to install, but got only an error message ("could not install the security updates"). Please see also attached screenshot

(Linux Mint 21.2).

Thanks very much for doing kernel updates for Ubuntu 20.04.
Have an nice week.