Package Details: linux-xanmod-lts 4.19.102-1

Git Clone URL: https://aur.archlinux.org/linux-xanmod-lts.git (read-only, click to copy)
Package Base: linux-xanmod-lts
Description: The Linux kernel and modules with Xanmod patches
Upstream URL: http://www.xanmod.org/
Licenses: GPL2
Submitter: figue
Maintainer: figue (figuepluto, jfigueras)
Last Packager: figuepluto
Votes: 6
Popularity: 1.61
First Submitted: 2017-11-22 02:00
Last Updated: 2020-02-16 00:30

Pinned Comments

figue commented on 2018-12-15 22:40

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=25 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 25
## Default is: 0 => generic
## Good option if your package is for one machine: 22 => native
_microarchitecture=0
##
## 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
##
## Enable PDS CPU scheduler by default https://gitlab.com/alfredchen/linux-pds
## Set variable "use_pds" to: n to disable (stock Xanmod)
##

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

env _tracers=0 _numa=0 _pds=1 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 to use this feature
  if [ -f "${startdir}/myconfig" ]; then
    msg2 "Using user CUSTOM config..."
    cp -f "${startdir}"/myconfig .config
  fi

Latest Comments

1 2 Next › Last »

figue commented on 2020-02-14 23:23

@Markospox you can set all CFLAGS you want, but probably the easiest you can do is to use tuning options already present in package. I personally use:

_microarchitecture=19 use_numa=n use_tracers=n use_ns=y _localmodcfg=y makepkg

Set your microarchitecture to native (22) or exactly for your CPU (execute this to know what you have: gcc -c -Q -march=native --help=target | grep march | head -1 | awk '{print $2}'). All is documented in PKGBUILD and choose-gcc-optimization.sh

In flags posted in Phoronix, compilation is for generic CPUs (mtune=generic), so you will gain a bit speed tunning microarchitecture. Also if you want a specific package, install modprobed-db (see archlinux wiki how to use) and that way you only build needed modules for your system. If not, don't use _localmodcfg

Markospox commented on 2020-02-14 20:05

How can I use this:

--build=x86_64-linux-gnu --disable-vtable-verify --disable-werror --enable-bootstrap --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-gnu-unique-object --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-multiarch --enable-multilib --enable-nls --enable-offload-targets=nvptx-none,hsa --enable-plugin --enable-shared --enable-threads=posix --host=x86_64-linux-gnu --program-prefix=x86_64-linux-gnu- --target=x86_64-linux-gnu --with-abi=m64 --with-arch-32=i686 --with-default-libstdcxx-abi=new --with-gcc-major-version-only --with-multilib-list=m32,m64,mx32 --with-target-system-zlib=auto --with-tune=generic --without-cuda-driver -v

to have possibly more tweaked kernel? Do I set CFLAGS to this? (https://www.phoronix.com/scan.php?page=article&item=xanmod-2020-kernel&num=1)

figue commented on 2019-02-06 22:10

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.

figue commented on 2019-02-06 16:57

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

Markospox commented on 2019-02-06 13:22

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..

figue commented on 2019-01-11 23:49

Switched to LTS branch 4.19.

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

figue commented on 2018-12-15 22:40

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=25 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 25
## Default is: 0 => generic
## Good option if your package is for one machine: 22 => native
_microarchitecture=0
##
## 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
##
## Enable PDS CPU scheduler by default https://gitlab.com/alfredchen/linux-pds
## Set variable "use_pds" to: n to disable (stock Xanmod)
##

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

env _tracers=0 _numa=0 _pds=1 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 to use this feature
  if [ -f "${startdir}/myconfig" ]; then
    msg2 "Using user CUSTOM config..."
    cp -f "${startdir}"/myconfig .config
  fi

figue commented on 2018-10-13 21:12

@Yosh latest release is 4.14.74-xanmod46:

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

Markospox commented on 2018-08-02 18:43

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 ;).. :))

figue commented on 2018-07-12 19:11

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!