Arch Linux User Repository

Adding

scripts/config --disable CONFIG_IMA_ARCH_POLICY

to myconfig does solve the "Failed to insert module 'nvidia': Key was rejected by service" problem.

Anyone who configured secure boot using sbctl and want to load dkms modules can try this solution.

This package have several variables to enable/disable features.

##
## The following variables can be customized at build time. Use env or export to change at your wish
##
##   Example: env _microarchitecture=98 use_numa=n use_tracers=n makepkg -sc
##
## Look inside 'choose-gcc-optimization.sh' to choose your microarchitecture
## Valid numbers between: 0 to 99
## Default is: 0 => generic
## Good option if your package is for one machine: 98 (Intel native) or 99 (AMD native)
if [ -z ${_microarchitecture+x} ]; then
  _microarchitecture=0
fi

## Disable NUMA since most users do not have multiple processors. Breaks CUDA/NvEnc.
## Archlinux and Xanmod enable it by default.
## Set variable "use_numa" to: n to disable (possibly increase performance)
##                             y to enable  (stock default)
if [ -z ${use_numa+x} ]; then
  use_numa=y
fi

## Since upstream disabled CONFIG_STACK_TRACER (limits debugging and analyzing of the kernel)
## you can enable them setting this option. Caution, because they have an impact in performance.
## Stock Archlinux has this enabled. 
## Set variable "use_tracers" to: n to disable (possibly increase performance, XanMod default)
##                                y to enable  (Archlinux default)
if [ -z ${use_tracers+x} ]; then
  use_tracers=n
fi

# Unique compiler supported upstream is GCC
## Choose between GCC and CLANG config (default is GCC)
## Use the environment variable "_compiler=clang"
if [ "${_compiler}" = "clang" ]; then
  _compiler_flags="CC=clang HOSTCC=clang LLVM=1 LLVM_IAS=1"
fi

# Choose between the 4 main configs for stable branch. Default x86-64-v1 which use CONFIG_GENERIC_CPU2:
# Possible values: config_x86-64-v1 (default) / config_x86-64-v2 / config_x86-64-v3 / config_x86-64-v4
# This will be overwritten by selecting any option in microarchitecture script
# Source files: https://github.com/xanmod/linux/tree/5.17/CONFIGS/xanmod/gcc
if [ -z ${_config+x} ]; then
  _config=config_x86-64-v1
fi

# Compress modules with ZSTD (to save disk space)
if [ -z ${_compress_modules+x} ]; then
  _compress_modules=n
fi

# Compile ONLY used modules to VASTLY reduce 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
if [ -z ${_localmodcfg} ]; then
  _localmodcfg=n
fi

# Tweak kernel options prior to a build via nconfig
if [ -z ${_makenconfig} ]; then
  _makenconfig=n
fi

Personally I'm running now xanmod kernel compiled with this:

env _microarchitecture=98 use_tracers=n use_numa=n _localmodcfg=y _compress_modules=y makepkg -sic

Also, you can now create the file myconfig in your local repo to build this package with a custom config or use ${XDG_CONFIG_HOME}/linux-xanmod/myconfig. This file can be a full kernel config or be a script with several entries to add/remove options (you have several examples in PKGBUILD by using scripts/config):

Code involved:

  for _myconfig in "${SRCDEST}/myconfig" "${HOME}/.config/linux-xanmod/myconfig" "${XDG_CONFIG_HOME}/linux-xanmod/myconfig" ; do
    if [ -f "${_myconfig}" ] && [ "$(wc -l <"${_myconfig}")" -gt "0" ]; then
      if grep -q 'scripts/config' "${_myconfig}"; then
        # myconfig is a partial file. Executing as a script
        msg2 "Applying myconfig..."
        bash -x "${_myconfig}"
      else
        # myconfig is a full config file. Replacing default .config
        msg2 "Using user CUSTOM config..."
        cp -f "${_myconfig}" .config
      fi
      echo
      break
    fi
  done

export _microarchitecture=99 use_numa=n use_tracers=n _compiler=clang && makepkg -sric

curl: (22) The requested URL returned error: 404 ==> ОШИБКА: Ошибка при загрузке 'https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-6.0.tar.xz' Прерывание...

fixed in PKGBUILD

_branch=6.x

after error =)

-> Setting version... cp: не удалось выполнить stat для 'CONFIGS/xanmod/gcc/config_x86-64': Нет такого файла или каталога ==> ОШИБКА: Произошел сбой в prepare(). Прерывание...    /tmp/linux

Bad Url to get the kernel. It says https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-6.0.tar.xz. It should say https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.0.tar.xz

Edit: thanks for the fixes, now it's working

@sk21 depends on what you change. If it's already done by a PKGBUILD variable, you can launch your paru with your custom variables (add to your .bashrc or directly from terminal).

how can i edit the PKGBUILD and make it permanent across updates? currently i download it using paru and edit it, but updating my system seems to revert to the defaults

@That1Calculator unflagged:

Current Stable (STABLE) 5.17.13-xanmod1 2022-06-06

https://xanmod.org/#install_via_apturl

@figue I flagged it out of date because 5.18.2 is out, not for 5.17.3

@vegancookies as far as I know, Xanmod uses graysky's patches:

https://github.com/graysky2/kernel_compiler_patch

Check his repo.

Does this not work well with Kaby Lake? It lists all intel CPU's in the i3 i5 and i7 line ups up until 8th generation with the exception of the 7th generation? Is this a mistake?

@BitGaming - Things are a little confusing right now since the most recent LTS kernel is the same as the previous kernel.org stable release.

Xanmod kernel branches breaks down like this:

• xanmod-edge always tracks the newest kernel.org stable branch
• xanmod tracks the previous stable branch (oldstable in debian terminology)
• xanmod-lts tracks the newest lts branch prior to oldstable

Following those rules you get:

• xanmod-edge -> 5.16 (kernel.org stable)
• xanmod -> 5.15 (oldstable)
• xanmod-lts -> 5.10 (newest LTS prior to oldstable)

I suspect -lts will promote to 5.15 as soon as 'xanmod' moves to 5.16, which should happen when 5.17 is released in a couple of months.

Anyway, there you go.

@BlitGaming I forwarded your question here: https://forum.xanmod.org/thread-4256-post-7962.html#pid7962