git.archlinux.org is dead, therefore, sphinx-workaround.patch can't be downloaded.
Search Criteria
Package Details: linux-xanmod-headers 6.11.10-1
Package Actions
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) |
Dependencies (10)
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- xz (xz-gitAUR) (make)
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 52 Next › Last »
aviallon commented on 2021-07-02 14:43 (UTC)
figue commented on 2021-06-21 10:38 (UTC)
@Logical_Master try to add to MODULES and install the package again (only install with pacman -U, not build). Perhaps you have to add to vfat to /etc/modules-load.d/vfat.conf
Logical_Master commented on 2021-06-21 01:05 (UTC)
@figue They are both present in the modprobed.db file. Should I add "vfat" to the MODULES array in /etc/mkinitcpio.conf?
figue commented on 2021-06-20 22:39 (UTC)
@Logical_Master ensure that ext4 and vfat are in ~/.config/modprobed.db
Logical_Master commented on 2021-06-20 18:27 (UTC) (edited on 2021-06-20 18:28 (UTC) by Logical_Master)
@figue it says command not found
Edit: Booting into the mainline kernel, it says ext4 for root and vfat for efi
figue commented on 2021-06-20 18:11 (UTC)
@Logical_Master what's your "lsblk -f" output? You need to add the correct FS type.
Logical_Master commented on 2021-06-20 12:17 (UTC) (edited on 2021-06-20 14:54 (UTC) by Logical_Master)
@figue What exactly do I need to add to those files?
Edit: (i.e) The exact text / name of the module
Edit 2: I added "ext4" in modprobed.db and in the modules array, rebuilt the kernel and initramfs. Still getting the same error
figue commented on 2021-06-20 10:35 (UTC)
@Logical_Master probably your root fs type is not built because _localmodcfg
Check if your FS is in $HOME/.config/modprobed.db and in MODULES array (/etc/mkinitcpio.conf).
Logical_Master commented on 2021-06-20 09:04 (UTC)
I built the xanmod 5.12.11 and 5.12.12. There are no errors during build and after booting into the kernel, I get this error. " Starting version 240.x ERROR: device 'UUID=xxx-...' not found. Skipping fsck. mount: /new_root: can't find UUID=xxx... You are now being dropped into an emergency shell. sh: can't access tty; job control turned off [rootfs ]# "
I built with custom microarchitecture and modprobed-db
My /etc/mkinitcpio.conf -->
SPDX-License-Identifier: GPL-3.0-or-later
vim:set ft=sh
MODULES
The following modules are loaded before any boot hooks are
run. Advanced users may wish to specify all system modules
in this array. For instance:
MODULES=(piix ide_disk reiserfs)
MODULES=(i915)
BINARIES
This setting includes any additional binaries a given user may
wish into the CPIO image. This is run last, so it may be used to
override the actual binaries included by a given hook
BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
FILES
This setting is similar to BINARIES above, however, files are added
as-is and are not parsed in any way. This is useful for config files.
FILES=""
HOOKS
This is the most important setting in this file. The HOOKS control the
modules and scripts added to the image, and what happens at boot time.
Order is important, and it is recommended that you do not change the
order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
help on a given hook.
'base' is required unless you know precisely what you are doing.
'udev' is required in order to automatically load modules
'filesystems' is required unless you specify your fs modules in MODULES
Examples:
This setup specifies all modules in the MODULES setting above.
No raid, lvm2, or encrypted root is needed.
HOOKS=(base)
This setup will autodetect all modules for your system and should
work as a sane default
HOOKS=(base udev autodetect block filesystems)
This setup will generate a 'full' image which supports most systems.
No autodetection is done.
HOOKS=(base udev block filesystems)
This setup assembles a pata mdadm array with an encrypted root FS.
Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
HOOKS=(base udev block mdadm encrypt filesystems)
This setup loads an lvm2 volume group on a usb device.
HOOKS=(base udev block lvm2 filesystems)
NOTE: If you have /usr on a separate partition, you MUST include the
usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap filesystems"
COMPRESSION
Use this to compress the initramfs image. By default, gzip compression
is used. Use 'cat' to create an uncompressed image.
COMPRESSION="gzip"
COMPRESSION="bzip2"
COMPRESSION="lzma"
COMPRESSION="xz"
COMPRESSION="lzop"
COMPRESSION="lz4"
COMPRESSION_OPTIONS
Additional options for the compressor
COMPRESSION_OPTIONS=(-9)
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: