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.

Just for reference for anyone using this package - it looks like a configuration change between 5.9 and 5.10 is resulting in a significant increase in the size of the modules being created: The vmlinuz is still fine for me at about 9MB but the overall package is close to 1GB.

I thought I fixed it with a revert in the last commit, but there is still an issue so I'll continue looking into this over the next few days.

Admittadly, I normally run mine though a Jenkins job every week on a Monday morning, after the next -rc release it out, so it just runs make oldconfig and selects the defaults for the next release.

However, in previous versions that has not always worked. IIRC both 5.6 and 5.7 releases failed to build due to an issue at the configuration stage which required updated defaults from the previous version, and hence a custom config file for the build.

Are you asked for to select the options for all the new entries during build time? If so, it might be worth swapping to run make oldconfig and perform the migration automatically.

Why does the PKGBUILD supply its own kernel configuration file instead of running “zcat /proc/config.gz > config” on the system that it’s being installed to? The kernel configuration tries to re-run from scratch whenever I try to install this package due to so many mismatches. Would be a much better solution to simply use the configuration from an already running kernel to build this, given that Arch itself supports that.

@mxfm No problem. Glad it's fixed :)

@jonathanio Thanks, the issue is resolved :)

For reference, these are the recent commits I've built successfully.

#225 24-Aug-2020 04:46 linux-git ​5.9rc2.r0.gd012a7190fc1-1
#2​24 17-Aug-2020 04:46 linux-git ​5.9rc1.r0.g9123e3a74ec7-1
#2​23 10-Aug-2020 04:46 linux-git ​5.8.r11991.gfc80c51fd4b2-1
#2​22 03-Aug-2020 04:46 linux-git ​5.8.r0.gbcf876870b95-1
#2​21 27-Jul-2020 04:46 linux-git ​5.8rc7.r0.g92ed30191993-1

I have a Jenkins job on my build server that builds the kernel every Monday morning in the early hours. This includes a full wipe of the build workspace beforehand so it's a fresh build. There are no current issues with the build for me right now.

I don't use dracut, so like @gardotd426 suggests, it seems that darcut is probably the issue as it's the only difference (that we're aware of) between the three of us.

Have you tried building it without dracut and from a clean workspace?

@gardotd426 I knew the kernel is not broken for the reasons outlined by you. My suspect was that something is changed in kernel build process which required changes in PKGBUILD, so this would affect only Arch.

Regarding dracut. I can assure, that dracut is fully fine in my setup, which is quite complicated (full disk encryption). I even have created custom scripts to facilitate my minor needs. I would recommend to any advanced Arch user to use dracut because it is at least as flexible as mkinitcpio.

Regarding the problem. It turns out, that depmod and modinfo (which were called by dracut) were complaining on garbage '/usr/lib/modules' previous kernel version installation which no longer existed (trashed by power failure). After clearing this not tracked by pacman gargabe I was able to compile package. Thanks for quick response!

@mxfm um, the "git repo" is literally the actual main Linux kernel repo. There's nothing wrong with it, if there were, the whole world would know. It would also mean that no other 5.9-rc1 kernels could be built using that source, which isn't true (I'm running one right now).

It's very likely a Dracut issue. Dracut on Arch is nowhere near ready for prime time on Arch Linux. An Arch dev reported not being able to use their keyboard and mouse when testing Dracut, etc.

But it's definitely not the git repo. If it's not the PKGBUILD, then it's your setup or dracut.