How can we fix 'xanmod' being duplicated in uname -r
?
Currently it shows 5.8.5-xanmod1-xanmod-1
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.20 |
First Submitted: | 2017-02-14 09:40 (UTC) |
Last Updated: | 2024-11-22 21:25 (UTC) |
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 52 Next › Last »
How can we fix 'xanmod' being duplicated in uname -r
?
Currently it shows 5.8.5-xanmod1-xanmod-1
@ANDRoid7890 I'm not planning to add cosmetic patches to this package. A simple solution can be to use Manjaro's kernel or patch it with Xanmod. Or you can always fork my package and include all packages you want :)
Could you add bootsplash patches from manjaro kernel? https://gitlab.manjaro.org/packages/core/linux58
Running into an issue with "(builtin)"
loading packages... warning: linux-xanmod-5.8.0-2 is up to date -- reinstalling warning: linux-xanmod-headers-5.8.0-2 is up to date -- reinstalling resolving dependencies... looking for conflicting packages...
Packages (2) linux-xanmod-5.8.0-2 linux-xanmod-headers-5.8.0-2
Total Installed Size: 458.28 MiB Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y (2/2) checking keys in keyring [###############################################] 100% (2/2) checking package integrity [###############################################] 100% (2/2) loading package files [###############################################] 100% (2/2) checking for file conflicts [###############################################] 100% (2/2) checking available disk space [###############################################] 100% :: Running pre-transaction hooks... (1/1) Save Linux kernel modules :: Processing package changes... (1/2) reinstalling linux-xanmod [###############################################] 100% (2/2) reinstalling linux-xanmod-headers [###############################################] 100% :: Running post-transaction hooks... (1/5) Arming ConditionNeedsUpdate... (2/5) Updating module dependencies... (3/5) Updating linux initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod.preset: 'default' -> -k /boot/vmlinuz-linux-xanmod -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod.img ==> Starting build: 5.8.0-xanmod2-2-xanmod -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: xhci_pci -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [encrypt] -> Running build hook: [lvm2] -> Running build hook: [openswap] -> Running build hook: [resume] -> Running build hook: [filesystems] cp: cannot stat '(builtin)': No such file or directory ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-xanmod.img ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod.preset: 'fallback' -> -k /boot/vmlinuz-linux-xanmod -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-fallback.img -S autodetect ==> Starting build: 5.8.0-xanmod2-2-xanmod -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] ==> WARNING: Possibly missing firmware for module: xhci_pci -> Running build hook: [keyboard] -> Running build hook: [keymap] -> Running build hook: [encrypt] -> Running build hook: [lvm2] -> Running build hook: [openswap] -> Running build hook: [resume] -> Running build hook: [filesystems] cp: cannot stat '(builtin)': No such file or directory ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-xanmod-fallback.img ==> WARNING: errors were encountered during the build. The image may not be complete. error: command failed to execute correctly (4/5) Updating Grub-Bootmenu Generating grub configuration file ... Found theme: /usr/share/grub/themes/manjaro/theme.txt Found linux image: /boot/vmlinuz-linux-xanmod Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-xanmod.img Found initrd fallback image: /boot/initramfs-linux-xanmod-fallback.img Found linux image: /boot/vmlinuz-5.6-x86_64 Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.6-x86_64.img Found initrd fallback image: /boot/initramfs-5.6-x86_64-fallback.img Adding boot menu entry for UEFI Firmware Settings ... Found memtest86+ image: /boot/memtest86+/memtest.bin done (5/5) Restore Linux kernel modules
==> Warning: -> This computer hasn't been restarted for a while. -> You are running an old kernel. In order to use a -> new version of the kernel, please restart your -> computer as soon as possible.
The git clone procedure worked. It pulls a new 0001-ZEN...patch file.
The problem that I have been reporting here is that the PKGBUILD file is downloading an older 0001-ZEN...patch file. So if one starts just with a PKGBUILD file makepkg will fail because of that old 0001-ZEN...patch file.
Usually, you need to clone the repo and build:
$ git clone https://aur.archlinux.org/linux-xanmod.git
$ cd linux-xanmod
$ makepkg -sic
that way you build standard package. If you want custom options:
_microarchitecture=42 use_numa=n use_tracers=n use_ns=y makepkg -sic
When a new release came up, just:
$ cd linux-xanmod
$ git pull
$ makepkg -sic
@figue:
I do not know what to do. I take the latest PKGBUILD here from this webpage: https://aur.archlinux.org/packages/linux-xanmod/
It downloads a patch file which is not working:
'0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-CLONE_NEWUSER.patch::https://aur.archlinux.org/cgit/aur.git/plain/0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-C.patch?h=linux-ck&id=616ec1bb1f2c0fc42b6fb5c20995996897b4f43b')
@mabod please update your local repo, I have fixed the patch a few days ago... Compare sums:
figue@pluto ~/packages-figue/linux-xanmod
% LC_ALL=C makepkg -g
==> Retrieving sources...
-> Found linux-5.8.tar.xz
-> Found linux-5.8.tar.sign
-> Found patch-5.8.0-xanmod2.xz
-> Found choose-gcc-optimization.sh
-> Found 0001-ZEN-Add-sysctl-and-CONFIG-to-disallow-unprivileged-CLONE_NEWUSER.patch
==> Generating checksums for source files...
sha256sums=('e7f75186aa0642114af8f19d99559937300ca27acaf7451b36d4f9b0f85cf1f5'
'SKIP'
'c4f5fea00eed0dd0809f5ce7cefff1af0a6ab70a27c9f9cceade88f3c2ba531d'
'2c7369218e81dee86f8ac15bda741b9bb34fa9cefcb087760242277a8207d511'
'6c66dba73251440352f93ff32b72f5dd49536d0f17ef9347867660fd3a626991')
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: