Arch Linux User Repository

Please, check new release. You have now several variables to enable/disable features.

References:

##
## The following variables can be customized at build time. Use env or export to change at your wish
##
##   Example: env _microarchitecture=99 use_numa=n use_tracers=n use_pds=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: 99 => 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

## For performance you can disable FUNCTION_TRACER/GRAPH_TRACER. Limits debugging and analyzing of the kernel.
## Stock Archlinux and Xanmod have this enabled. 
## Set variable "use_tracers" to: n to disable (possibly increase performance)
##                                y to enable  (stock default)
if [ -z ${use_tracers+x} ]; then
  use_tracers=y
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
_makenconfig=

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

env use_numa=n use_tracers=n makepkg -s

Also, you can now put a file in your local repo to build this package with a custom config. You have to call this file myconfig.

Reference:

  # Put the file "myconfig" at the package folder (this will take preference) or "${XDG_CONFIG_HOME}/linux-xanmod/myconfig"
  # If we detect partial file with scripts/config commands, we execute as a script
  # If not, it's a full config, will be replaced

For me, it looks like Arch kernel...

figue@pluto ~ % uname -a
Linux pluto 4.19.19-xanmod10-1-xanmod-lts #1 SMP PREEMPT Wed Feb 6 21:46:53 CET 2019 x86_64 GNU/Linux

but if you want to change I think you need to recompile. Keep your source files (don't use pacman wrappers or -c flag in makepkg) to rebuild if you need to test with CONFIG_LOCALVERSION.

@Markospox I'll take a look later at home, maybe I need to merge something from the linux-lts PKGBUILD... Cheers

How to change version? I get somehow 4.19.19-xanmod10-1-MANJARO-xanmod-lts-4.19.19 and I'd like 4.19.19-xanmod10-1-MANJARO

src/version: 4.19.19-xanmod10-1-MANJARO-xanmod-lts-4.19.19 src/linux-4.19.19-xanmod10/localversion: -xanmod10 src/linux-4.19.19-xanmod10/localversion.10-pkgrel: -1 src/linux-4.19.19-xanmod10/localversion.20-pkgname: -MANJARO CONFIG_LOCALVERSION="" in src/linux-4.19.19-xanmod10/.config

it'd be great if it was without recompiling the whole thing..

Switched to LTS branch 4.19.

Old 4.12 will remain in other package: linux-xanmod-lts414

Please, check new release. You have now several variables to enable/disable features.

References:

##
## The following variables can be customized at build time. Use env or export to change at your wish
##
##   Example: env _microarchitecture=99 use_numa=n use_tracers=n use_pds=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: 99 => 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

## For performance you can disable FUNCTION_TRACER/GRAPH_TRACER. Limits debugging and analyzing of the kernel.
## Stock Archlinux and Xanmod have this enabled. 
## Set variable "use_tracers" to: n to disable (possibly increase performance)
##                                y to enable  (stock default)
if [ -z ${use_tracers+x} ]; then
  use_tracers=y
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
_makenconfig=

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

env use_numa=n use_tracers=n makepkg -s

Also, you can now put a file in your local repo to build this package with a custom config. You have to call this file myconfig.

Reference:

  # Put the file "myconfig" at the package folder (this will take preference) or "${XDG_CONFIG_HOME}/linux-xanmod/myconfig"
  # If we detect partial file with scripts/config commands, we execute as a script
  # If not, it's a full config, will be replaced

@Yosh latest release is 4.14.74-xanmod46:

https://github.com/xanmod/linux/releases

Hi, it seems to be fine now, I twiddled with modules and there's also an xf86-input-something update coming although the same thing happened just after recompiling and surprisingly I had to run fallback version to have mouse cursor moving fine, and run back normally to have it movin' as freely. I'm not sure what you're askin' about, is this snap development branch thing? I wanted to use latest stable version with my configuration changes - IBM IOMMU disabled, some other unused crap disabled, CPU-specific binarch ;).. :))

Hola Markos,

I honestly don't know why your compiled version 4.14.50 has this issue with touchpad. I don't know if there was some regression in some driver, it's very odd, but could happen. Also, maybe, could be related to xorg-input drivers, that are not related to kernel package. Is for some kind of know bug that you build a snapshot of this package?

Today I pushed latest xanmod-lts (4.14.55), all should be fine in kernel level, nothing has changed in packaging... So I don't know how I can help you. If you have some dmesg or something related to touchpad driver that should be reported upstream, we can see. But from my point of view (packaging level), I don't know if it's something that could be fixed.

Anyway, all suggestions are very welcome.

¡Saludos!