Arch Linux User Repository

The prebuilt kernel is built using Clang/LLVM 16.

The linux-nitrous binary package can be installed by adding following lines to your /etc/pacman.conf:

[linux-nitrous]
Server = https://github.com/xdevs23/linux-nitrous/releases/latest/download/

Then you can install the package using your AUR helper or pacman (e. g. sudo pacman -Syu linux-nitrous linux-nitrous-headers)

You probably need to add the keys before being able to install my packages:

sudo pacman-key --recv-keys E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0
sudo pacman-key --lsign-key E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0

scripts/Kconfig.include:40: linker 'ld.lld' not found

extra/lld dependency missing?

Found out two issues on my setup.

1. You don't need to depmod/mkinitcpio anymore with post-install/post-upgrade hooks, since it's now done by pacman itself, check other AUR packages (like, "linux-pds", etc.) or official kernel packages for reference. This way all DKMS modules wouldn't fail to be added to initramfs (as they only are built and become available after the install, thus the new behaviour).
2. Any chance to add ZFS support ("zfs-dkms" and "zfs-utils" packages in AUR) to your kernel? Right now it's failing to build with following message:

[2020-10-17T18:15:03+0300] [ALPM-SCRIPTLET] ==> dkms install --no-depmod -m zfs -v 0.8.5 -k 5.9.0-nitrous+
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET] configure: error: 
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** None of the expected "make_request_fn" interfaces were detected.
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** This may be because your kernel version is newer than what is
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** supported, or you are using a patched custom kernel with
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** incompatible modifications.
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     ***
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** ZFS Version: zfs-0.8.5-1
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     *** Compatible Kernels: 2.6.32 - 5.6
[2020-10-17T18:16:08+0300] [ALPM-SCRIPTLET]     
[2020-10-17T18:16:09+0300] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.9.0-nitrous+ (x86_64)
[2020-10-17T18:16:09+0300] [ALPM-SCRIPTLET] Consult /var/lib/dkms/zfs/0.8.5/build/make.log for more information.
[2020-10-17T18:16:09+0300] [ALPM-SCRIPTLET] ==> Warning, `dkms install --no-depmod -m zfs -v 0.8.5 -k 5.9.0-nitrous+' returned 10

There seems to be an issue with 5.8.1-1

I'm recompiling the kernel using stock clang which will be 5.8.1-2

Hopefully this fixes the issue.

Tried the linux-nitrous-git version to take advantage of LSMOD, it did not work as intended and seem to load all generic Linux modules were still loaded, way beyond the 61 listed in my modepribed.db file.

I forgot to mention but the nvidia-dkms package now works just fine on 5.7.

NVIDIA also has already released a driver that looks to be compatible with the upcoming 5.8 version so hopefully we will be able to transition to 5.8 smoothly without any hiccups.

Warning: nvidia-dkms does not seem to work with it – it will not compile and even if you apply patches to it there is a good chance that you won't reach the login screen. Please refrain from using 5.7, try patches or use nouveau until nvidia has published a working driver...

Other dkms modules will probably work. Problems with, for example, vboxhost have been fixed in 5.7.0-2.

@soloturn I have implemented support for it in the linux-nitrous-git package by checking if $HOME/.config/modprobed.db exists. I'm not sure whether the implementation will work that way, I will probably need to change a few more things. Let me know if this is a good way of checking for modprobed-db or whether it would be better to just check for LSMOD.

@superboringdev to enable a switch for it would be cool. maybe if the environment variable LSMOD is set?

@dedguy21 this repository (and its PKGBUILD) are used to build the binaries found in my custom repository

I do not intend to enable the used modules config by default as that is not what would resemble the binaries provided in my custom repository. I could try making it do that by checking for an environment variable in the PKGBUILD but I won't be doing it by default. The other thing is that I want the kernel to be able to build and run on pretty much any system that has a compatible CPU, regardless of the remaining hardware.

I think he means like they do in other Linux builds in AuR (this is from linux-ck for example only:

**" Compile ONLY used modules to VASTLYreduce the number of modules built

and the build time.

To keep track of which modules are needed for your specific system/hardware,

give module_db script a try: https://aur.archlinux.org/packages/modprobed-db

This PKGBUILD read the database kept if it exists

More at this wiki page ---> https://wiki.archlinux.org/index.php/Modprobed-db

_localmodcfg=

IMPORTANT: Do no edit below this line unless you know what you're doing

* Somewhere down the pkgbuil***

### Optionally load needed modules for the make localmodconfig # See https://aur.archlinux.org/packages/modprobed-db if [ -n "$_localmodcfg" ]; then if [ -f $HOME/.config/modprobed.db ]; then echo "Running Steven Rostedt's make localmodconfig now" make LSMOD=$HOME/.config/modprobed.db localmodconfig else echo "No modprobed.db data found" exit fi fi