Hi @Anarconda
please don't flag out-of-date if official release is not ready yet:
Git Clone URL: | https://aur.archlinux.org/linux-xanmod.git (read-only, click to copy) |
---|---|
Package Base: | linux-xanmod |
Description: | Headers and scripts for building modules for the Linux Xanmod - Stable Mainline [MAIN] kernel |
Upstream URL: | http://www.xanmod.org/ |
Licenses: | GPL2 |
Submitter: | Yoshi2889 |
Maintainer: | figue (figuepluto, jfigueras) |
Last Packager: | figue |
Votes: | 132 |
Popularity: | 2.07 |
First Submitted: | 2017-02-14 09:40 (UTC) |
Last Updated: | 2024-11-22 21:25 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 52 Next › Last »
Hi @Anarconda
please don't flag out-of-date if official release is not ready yet:
@duht I'll wait a bit more. Perhaps the final fix will be realeased in next minor release.
@figue firstly thank you for your support, you're doing a great job!
I installed 6.4.2-3
and VMA_LOCK is disabled here. Working for now without issues.
As you can read here Suren Baghdasaryan posted "the fix along with another less critical one" at link.
With that fix there is no need to disable vma locking anymore. Maybe you want to add this fix intsead of v4 workaround before they add this to the main kernel.
@duht I applied the patch posted, as I tested disabling in a normal way with "scripts/config --disable CONFIG_PER_VMA_LOCK", but when compilation starts it's enabled automatically again. That's why I suposed patch was the right way.
I'll wait a bit until the discussion goes a little further and look for a better patch.
Edit: Finally I added the same patch but v4 (I didn't see it last time) https://lore.kernel.org/lkml/20230706011400.2949242-2-surenb@google.com/T/#md6ecb2cb14e14276e2dc03157d1b2bb255cb77e7
Check if this workaround works for you.
@figue I'm not sure you done it right way...
If you have an existing .config this patch does nothing link.
linux-xanmod
already has existing configs (config_x86-64-v*), so you should disable it in config_x86-64-v2 (as this is default in your package now), similar way as Arch did here.
Edit: I installed linux-xanmod 6.4.1-2
from chaoticaur repo and CONFIG_PER_VMA_LOCK is still enabled, conky still freezes:(
@duht thanks. I'm testing the patch
Edit: done 811e14eafebc
Also default config will be config_x86-64-v2
@figue could you disable PER_VMA_LOCK? Vma lock is buggy in 6.4 and causing crashing in some applications link, especially in conky link. Kernel devs decided to disable it by default until fix link, and newest Arch kernel has it also disabled link I'm instaling this package from ChaoticAur repository, so I can't "disable it myself" in PKGBUILD.
@aunjbr thanks. Updated script choose-gcc-optimization.sh
Check new microarchitectures supported!
Please add AMD Zen 4 architecture
I want to apologize because I pushed the package to the EDGE version by mistake. For now, I'll keep at EDGE but the idea is to keep this package following the Stable Mainline [MAIN] branch. Probably for the next release I'll make a new package for the edge. Same for all -bin packages.
Thank you to understand.
Cheers
Pinned Comments
anlorsp commented on 2024-07-13 17:07 (UTC) (edited on 2024-07-15 04:53 (UTC) by anlorsp)
Adding
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.
figue commented on 2018-12-14 00:50 (UTC) (edited on 2023-02-27 20:00 (UTC) by figue)
This package have several variables to enable/disable features.
Personally I'm running now xanmod kernel compiled with this:
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: