Arch linux kernel version

Arch linux kernel version DEFAULT

Arch Linux ARM is a distribution of Linux for ARM computers. We provide targeted kernel and software support for soft-float ARMv5te, hard-float ARMv6 and ARMv7, and ARMv8 AArch64 instruction sets on a variety of consumer devices and development platforms. Our collaboration with Arch Linux brings users the best platform, newest packages, and installation support.

Arch Linux ARM carries forward the Arch Linux philosophy of simplicity and user-centrism, targeting and accommodating competent Linux users by giving them complete control and responsibility over the system. Instructions are provided to assist in navigating the nuances of installation on the various ARM platforms; however, the system itself will offer little assistance to the user.

The entire distribution is on a rolling-release cycle that can be updated daily through small packages instead of huge updates on a defined release schedule. Most packages are unmodified from what the upstream developer originally released.


Arch Linux

Rolling release distribution of Linux

Arch Linux ()[5] is a Linux distribution meant for computers with x processors.[6] Arch Linux adheres to the KISS principle ("Keep It Simple, Stupid").[7] The project attempts to have minimal distribution-specific changes, and therefore minimal breakage with updates, and be pragmatic over ideological design choices and focus on customizability rather than user-friendliness.[8]

Pacman, a package manager written specifically for Arch Linux, is used to install, remove and update software packages.[9] Arch Linux uses a rolling release model, meaning there are no "major releases" of completely new versions of the system; a regular system update is all that is needed to obtain the latest Arch software; the installation images released every month by the Arch team are simply up-to-date snapshots of the main system components.[10]

Arch Linux has comprehensive documentation, which consists of a community wiki known as the ArchWiki.[11][12][13]


Inspired by CRUX, another minimalist distribution, Judd Vinet started the Arch Linux project in March The name was chosen because Vinet liked the word's meaning of "the principal," as in "arch-enemy".[5][14]

Originally only for bit x86 CPUs, the first x86_64 installation ISO was released in April [15]

Vinet led Arch Linux until 1 October , when he stepped down due to lack of time, transferring control of the project to Aaron Griffin.[16]

The migration to systemd as its init system started in August ,[17] and it became the default on new installations in October [18] It replaced the SysV-style init system, used since the distribution inception.[19]

On 24 February , Aaron Griffin announced that due to his limited involvement with the project, he would, after a voting period, transfer control of the project to Levente Polyak.[20] This change also led to a new 2-year term period being added to the Project Leader position.[21]

The end of i support was announced in January , with the February ISO being the last one including i[22] and making the architecture unsupported in November [23] Since then, the community derivative Arch Linux 32 can be used for i hardware.

Repository security[edit]

Until Pacman version ,[24] Arch Linux's package manager lacked support for signed packages.[25] Packages and metadata were not verified for authenticity by Pacman during the download-install process. Without package authentication checking, tampered-with or malicious repository mirrors could compromise the integrity of a system.[26]Pacman 4 allowed verification of the package database and packages, but it was disabled by default. In November , package signing became mandatory for new package builds, and as of the 21st of March , every official package is signed.[27]

In June , package signing verification became official and is now enabled by default in the installation process.[28][29]

Design and principles[edit]

Arch is largely based on binary packages. Packages target xmicroprocessors to assist performance on modern hardware. A ports/ebuild-like system is also provided for automated source compilation, known as the Arch Build System.[30]

Arch Linux focuses on simplicity of design, meaning that the main focus involves creating an environment that is straightforward and relatively easy for the user to understand directly, rather than providing polished point-and-click style management tools&#;— the package manager, for example, does not have an official graphical front-end. This is largely achieved by encouraging the use of succinctly commented, clean configuration files that are arranged for quick access and editing.[31] This has earned it a reputation as a distribution for "advanced users" who are willing to use the command line.[32]

Relying on complex tools to manage and build your system is going to hurt the end-users. [] "If you try to hide the complexity of the system, you'll end up with a more complex system". Layers of abstraction that serve to hide internals are never a good thing. Instead, the internals should be designed in a way such that they NEED no hiding.

—&#;Aaron Griffin[33]


Screenshot of pacstrap during installation.

The Arch Linux website supplies ISO images that can be run from CD or USB. After a user partitions and formats their drive, a simple command line script (pacstrap) is used to install the base system.[29] The installation of additional packages which are not part of the base system (for example, desktop environments), can be done with either pacstrap, or Pacman after booting (or chrooting) into the new installation.[34][35][9]

Neofetchoutput of an Arch Linux Installation.

An alternative to using CD or USB images for installation is to use the static version of the package manager Pacman, from within another Linux-based operating system.[36] The user can mount their newly formatted drive partition, and use pacstrap (or Pacman with the appropriate command-line switch) to install base and additional packages with the mountpoint of the destination device as the root for its operations. This method is useful when installing Arch Linux onto USB flash drives, or onto a temporarily mounted device which belongs to another system.[citation needed]

Regardless of the selected installation type, further actions need to be taken before the new system is ready for use, most notably by installing a bootloader and configuring the new system with a system name, network connection, language settings, and graphical user interface.[37]

The installation images come packaged with an experimental command line installer, archinstall, which can assist with installing Arch Linux.[38]

Arch Linux does not schedule releases for specific dates but uses a "rolling release" system where new packages are provided throughout the day. Its package management allows users to easily keep systems updated.[39]

Occasionally, manual interventions are required for certain updates, with instructions posted on the news section of the Arch Linux website.[40]

Package management[edit]

Arch Linux's only supported binary platform is x86_ The Arch package repositories and User Repository (AUR) contain 58, binary and source packages, which comes close to Debian's 68, packages; however, the two distributions' approaches to packaging differ, making direct comparisons difficult. For example, six out of Arch's 58, packages comprise the software AbiWord, of which three in the user repository replace the canonical Abiword package with an alternative build type or version (such as sourcing from the latest commit to Abiword's source control repository), whereas Debian installs a single version of Abiword across seven packages.[41] The Arch User Repository also contains a writerperfect package which installs several document format converters, while Debian provides each of the more than 20 converters in its own subpackage.[42]


To facilitate regular package changes, Pacman (a contraction of "package manager") was developed by Judd Vinet to provide Arch with its own package manager to track dependencies.[43] It is written in C.[44]

All packages are managed using the Pacman package manager. Pacman handles package installation, upgrades, downgrades, removal and features automatic dependency resolution. The packages for Arch Linux are obtained from the Arch Linux package tree and are compiled for the x architecture. It uses binary packages in the [45][46][47] (for zstd compression), with placed before this to indicate that it is a Pacman package (giving ).[44]

As well as Arch Linux, Pacman is also used for installing packages under MSYS2 (a fork of Cygwin) on Windows.[48]


The following official binary repositories exist:[49]

  • core, which contains all the packages needed to set up a base system
  • extra, which holds packages not required for the base system, including desktop environments and programs
  • community, which contains packages built and voted on by the community; includes packages that have sufficient votes and have been adopted by a "trusted user".
  • multilib, a centralized repository for x users to more readily support bit applications in a bit environment.

Additionally, there are testing repositories which include binary package candidates for other repositories. Currently, the following testing repositories exist:

  • testing, with packages for core and extra.
  • community-testing, with packages for community.
  • multilib-testing, with packages for multilib.

The staging and community-staging repositories are used for some rebuilds to avoid broken packages in testing.

There are also two other repositories that include the newest version of certain desktop environments.

  • gnome-unstable, which contains packages of a new version of the software from GNOME before being released into testing.
  • kde-unstable, which contains packages of a new version of KDE software before being released into testing.

The unstable repository was dropped in July and most of the packages moved to other repositories.[50] In addition to the official repositories, there are a number of unofficial user repositories.

The most well-known unofficial repository is the Arch User Repository, or AUR, hosted on the Arch Linux site. However, the AUR does not host binary packages, hosting instead a collection of build scripts known as PKGBUILDs.

The Arch Linux repositories contain both libre and nonfree software, and the default Arch Linux kernel contains nonfree proprietary blobs, hence the distribution is not endorsed by the GNU project.[51]

Arch Build System (ABS)[edit]

The Arch Build System (ABS) is a ports-like source packaging system that compiles source tarballs into binary packages, which are installed via Pacman.[52] The Arch Build System provides a directory tree of shell scripts, called PKGBUILDs, that enable any and all official Arch packages to be customized and compiled. Rebuilding the entire system using modified compiler flags is also supported by the Arch Build System. The Arch Build System tool can be used to create custom packages from third-party sources. The resulting packages are also installable and trackable via Pacman.[53][54]

Arch User Repository (AUR)[edit]

In addition to the repositories, the Arch User Repository (AUR) provides user-made PKGBUILD scripts for packages not included in the repositories. These PKGBUILD scripts simplify building from source by explicitly listing and checking for dependencies and configuring the install to match the Arch architecture.[55] Arch User Repository helper programs can further streamline the downloading of PKGBUILD scripts and associated building process. However, this comes at the cost of executing PKGBUILDs not validated by a trusted person; as a result, Arch developers have stated that the utilities for automatic finding, downloading and executing of PKGBUILDs will never be included in the official repositories.[56]

Users can create packages compatible with Pacman using the Arch Build System and custom PKGBUILD scripts.[57] This functionality has helped support the Arch User Repository, which consists of user contributed packages to supplement the official repositories.[58]

The Arch User Repository provides the community with packages that are not included in the repositories. Reasons include:

  • Licensing issues: software that cannot be redistributed, but is free to use, can be included in the Arch User Repository since all that is hosted by the Arch Linux website is a shell script that downloads the actual software from elsewhere. Examples include proprietary freeware such as Google Earth and RealPlayer.
  • Modified official packages: the Arch User Repository also contains many variations on the official packaging as well as beta versions of software that is contained within the repositories as stable releases.
  • Rarity of the software: rarely used programs have not been added to the official repositories (yet).
  • Betas or "nightly" versions of the software which are very new and thus unstable. Examples include the "firefox-nightly" package, which gives new daily builds of the Firefox web browser.

PKGBUILDs for any software can be contributed by ordinary users and any PKGBUILD that is not confined to the Arch User Repository for policy reasons can be voted into the community repositories.


See also: List of Linux distributions §&#;Pacman-based

There are several projects working on porting the Arch Linux ideas and tools to other kernels, including PacBSD (formerly ArchBSD) and Arch Hurd,[59] which are based on the FreeBSD and GNU Hurd kernels, respectively. There is also the Arch Linux ARM project, which aims to port Arch Linux to ARM-based devices, including the Raspberry Pi, as well as the Arch Linux 32 project, which continued support for systems with bit only CPUs after the mainline Arch Linux project dropped support for the architecture in November [60][61]

SteamOS , the upcoming version of SteamOS used in Steam Deck is based on Arch Linux.[62][63][64][65]


The current Arch Linux logo was designed by Thayer Williams[66][67] in as part of a contest to replace the previous logo.[68]


OSNews reviewed Arch Linux in [69] OSNews also has 5 later reviews about Arch Linux.[70][71][72][73][74] wrote a review about Arch Linux in [75] also has 2 later reviews about Arch Linux.[76][77]

Tux Machines reviewed Arch Linux in [78]

Chris Smart from DistroWatch Weekly wrote a review about Arch Linux in January [79] DistroWatch Weekly reviewed Arch Linux again in September and in December [80][81]

Linux maintainer Greg Kroah-Hartman[82] has stated that he uses Arch and that it "works really really well," he also praised the Arch Wiki, and that the distribution stays close to upstream development, as well as the feedback loop with the community.[83]

See also[edit]



  1. ^"Arch Linux - Releases". Archived from the original on 4 December Retrieved 12 October
  2. ^"Pacman Home Page". Retrieved 9 May
  3. ^"Arch Linux 32". Arch Linux 32. Retrieved 19 June
  4. ^
  5. ^ abAaron Griffin (24 August ). "Pronnounciation [sic] of our beloved distribution's name". Archived from the original on 12 February Retrieved 19 October
  6. ^"About". Arch Linux. Archived from the original on 2 January Retrieved 27 September
  7. ^"Arch terminology - ArchWiki". Retrieved 22 December
  8. ^"Arch Linux Principles". ArchWiki. 16 September Archived from the original on 11 November Retrieved 13 November
  9. ^ ab"Pacman Home Page". Archived from the original on 26 February Retrieved 30 October
  10. ^Ivan Jelic (10 March ). "Rolling with Arch Linux". Archived from the original on 20 October Retrieved 30 September
  11. ^Smith, Jesse (21 December ). "Arch Linux - Feature Story". Archived from the original on 12 September Retrieved 17 January
  12. ^Linton, Susan (17 July ). "Debian Project Lead: Snappy and Mir Bad Ideas". OStatic. Archived from the original on 4 February Retrieved 4 February
  13. ^"The Arch Way | Linux Journal". Archived from the original on 30 October Retrieved 30 October
  14. ^"Interview with Judd Vinet". Archived from the original on 8 September Retrieved 30 October
  15. ^"Arch Linux - News: Official Arch64 install cd available". Archived from the original on 12 June Retrieved 12 May
  16. ^apeiro (Judd Vinet) (1 October ). "Arch Leadership". Arch Linux Forums. Archived from the original on 9 August Retrieved 19 October
  17. ^Gaudreault, Stéphane (14 August ). "Migration to systemd". arch-dev-public (Mailing list). Retrieved 24 September
  18. ^Bächler, Thomas (13 October ). "systemd is now the default on new installations". Retrieved 24 September
  19. ^"Archlinux installer ".
  20. ^"Arch Linux - News: The Future of the Arch Linux Project Leader". Retrieved 24 June
  21. ^"DeveloperWiki:Project Leader - ArchWiki". Retrieved 24 June
  22. ^Bartłomiej Piotrowski (25 January ). "Phasing out i support". Arch Linux. Archived from the original on 27 January Retrieved 26 January
  23. ^Bartłomiej Piotrowski (8 November ). "The end of i support". Arch Linux. Archived from the original on 8 November Retrieved 8 November
  24. ^"NEWS - pacman.git - The official pacman repository". Retrieved 12 May
  25. ^"FS#&#;: Signed packages". Archived from the original on 28 July Retrieved 12 May
  26. ^"Attacks on Package Managers". 10 July Archived from the original on 5 September Retrieved 14 September
  27. ^McRae, Allan (17 December ). "Pacman Package Signing – 4: Arch Linux". Archived from the original on 20 February Retrieved 29 February
  28. ^Gaetan Bisson (4 June ). "Having pacman verify packages". Arch Linux. Archived from the original on 6 June Retrieved 4 June
  29. ^ abPierre Schmitz (22 July ). "Install media released". Arch Linux. Archived from the original on 12 December Retrieved 13 August
  30. ^Campbell, Alex; Hacker, Tech; PT, PCWorld | (2 November ). "5 reasons to opt for a Linux rolling distro vs. a standard release". PCWorld. Retrieved 12 May
  31. ^"The Arch Way". ArchWiki. 9 October Archived from the original on 18 April Retrieved 18 March
  32. ^Williams, rew; April , Brian Turner "Best Linux distros of for beginners and advanced users". TechRadar. Archived from the original on 21 April Retrieved 17 April
  33. ^"FS# - [pacman] provide workaround for removing --asroot from makepkg". arch linux. Retrieved 4 July
  34. ^"pacman - ArchWiki". Archived from the original on 18 August Retrieved 13 September
  35. ^"General recommendations - ArchWiki". Archived from the original on 21 September Retrieved 13 September
  36. ^"Install From Existing Linux". ArchWiki. 21 November Archived from the original on 26 January Retrieved 5 December
  37. ^"Installation guide - ArchWiki". Retrieved 13 September
  38. ^"archinstall - ArchWiki". Retrieved 12 April
  39. ^"Arch Linux Review". Archived from the original on 14 September Retrieved 13 September
  40. ^"News". Archived from the original on 15 August Retrieved 15 August
  41. ^"Debian -- Package Search Results -- abiword". Archived from the original on 7 July Retrieved 12 May
  42. ^"Debian -- Package Search Results -- writerperfect". Archived from the original on 8 July Retrieved 12 May
  43. ^Eugenia Loli (21 March ). "Arch Linux: Why It Rocks". OSNews. Archived from the original on 30 September Retrieved 30 September
  44. ^ ab"pacman". ArchWiki. 6 August Archived from the original on 18 August Retrieved 20 August
  45. ^"Arch Linux Nears Roll-Out Of Zstd Compressed Packages For Faster Pacman Installs - Phoronix". Retrieved 31 October
  46. ^Broda, Robin (24 March ). "[arch-dev-public] RFC: (devtools) Changing default compression method to zstd". Archived from the original on 21 October Retrieved 31 October
  47. ^"Arch Linux - News: Required update to recent libarchive". Archived from the original on 21 October Retrieved 31 October
  48. ^"Package Management - MSYS2". Retrieved 11 November
  49. ^"Official Repositories". ArchWiki. Archived from the original on 18 November Retrieved 23 November
  50. ^"Arch Linux Newsletter ". Arch Linux. 4 August Archived from the original on 3 June Retrieved 19 October
  51. ^"Explaining Why We Don't Endorse Other Systems". GNU Project. Archived from the original on 24 April Retrieved 28 September
  52. ^"Arch Build System". ArchWiki. Archived from the original on 17 January Retrieved 19 October
  53. ^"Makepkg". ArchWiki. Archived from the original on 26 January Retrieved 15 February
  54. ^"Arch Linux - News: Now using Zstandard instead of xz for package compression". Retrieved 13 July
  55. ^"AUR (en) - Home". AUR. Archived from the original on 3 November Retrieved 5 February
  56. ^Robin Heggelund Hansen (25 March ). "Arch Linux: Popular KISS distro – Interview – Part II". Archived from the original on 2 April Retrieved 19 October
  57. ^"Using the Arch Build System". 8 September Archived from the original on 27 September Retrieved 30 September
  58. ^Bo Milanovich (8 March ). "Arch Linux". Archived from the original on 21 February Retrieved 30 September
  59. ^"Arch Hurd". Arch Hurd. Archived from the original on 26 March Retrieved 25 March
  60. ^"Arch Linux ARM". Arch Linux ARM. Archived from the original on 28 March Retrieved 25 March
  61. ^"Arch Linux 32". Arch Linux Retrieved 22 October
  62. ^Duckett, Chris. "Steam Deck is an AMD-powered handheld PC from Valve that runs KDE on Arch Linux". ZDNet. Retrieved 18 July
  63. ^"Valve's handheld console 'The Steam Deck' is heard with an Arch Linux based OS". TechnoSports. 16 July Retrieved 18 July
  64. ^Prasad (15 July ). "Valve Steam Deck is a handheld gaming PC that runs SteamOS". GSMArena. Retrieved 19 July
  65. ^"Valve has formally announced the Steam Deck, a portable handheld console with SteamOS". GamingOnLinux. Retrieved 16 July
  66. ^Willard, Travis (22 December ). "Arch Linux - News: Logo Contest Results (and Winner!)". Retrieved 4 October
  67. ^Williams, Thayer (). "Arch Linux logo submission". Retrieved 4 October
  68. ^Willard, Travis (24 October ). "Arch Linux - News: Arch Linux Logo Competition". Retrieved 4 October
  69. ^"Introduction to Arch Linux – OSnews". Archived from the original on 12 May Retrieved 12 May
  70. ^"Arch Linux: A Better Distribution – OSnews". Archived from the original on 12 May Retrieved 12 May
  71. ^"Arch Linux: An End To My Distro Shuffle? – OSnews". Archived from the original on 12 May Retrieved 12 May
  72. ^"A Week in the Life of an Arch Linux Newbie – OSnews". Archived from the original on 12 May Retrieved 12 May
  73. ^"Arch Linux: Why It Rocks – OSnews". Archived from the original on 12 May Retrieved 12 May
  74. ^"Watching the Evolution of Arch Linux – OSnews". Archived from the original on 12 May Retrieved 12 May
  75. ^"Arch Linux for Power Users []". Archived from the original on 12 May Retrieved 12 May
  76. ^"Rolling with Arch Linux []". Archived from the original on 7 February Retrieved 12 May
  77. ^"The grumpy editor's Arch Linux experience []". Archived from the original on 15 November Retrieved 12 May
  78. ^Fallen Under the Spell of Arch Voodoo | Tux MachinesArchived 20 June at the Wayback Machine 20 April
  79. ^"Arch Linux in review". Archived from the original on 20 June Retrieved 12 May
  80. ^"A distro odyssey, part 2 - the Arch way". Archived from the original on 20 June Retrieved 12 May
  81. ^"Arch Linux". Archived from the original on 12 September Retrieved 12 May
  82. ^" - linux/kernel/git/torvalds/linuxgit/blob - MAINT…". 13 January Archived from the original on 13 January Retrieved 30 October
  83. ^"Let's Talk To Linux Kernel Developer Greg Kroah-Hartman - Open Source Summit, ". 10 September Retrieved 17 September

External links[edit]

Wikimedia Commons has media related to Arch Linux.
  1. Pokemon generations collection box
  2. Philips warm white led
  3. Minecraft bedrock edition smp servers
  4. Ksp addons
  5. Furry anatomy

Arch Linux

Latest News

RSS Feed

Sorting out old password hashes

Starting with , weak password hashes (such as MD5 and SHA1) are no longer accepted for new passwords. Users that still have their passwords stored with a weak hash will be asked to update their password on their next login.

If the login just fails (for example from display manager) switch to a virtual terminal (Ctrl-Alt-F2) and log in there once.

Move of official IRC channels to

As some of you may have read over the past days, there has been an ownership dispute over the network. The IRC network has been used by Arch Linux and many other projects over the past decades as a platform for discussion and support. The dispute led to the exodus of most former freenode staff from the network and the founding of a new network:

Starting today, Arch Linux and its sister projects Arch Linux ARM and Arch Linux 32 will begin migrating the official IRC channels from to Please bear with us as this can …

Installation medium with installer

The installation medium now provides a guided installer.

This addition to the default method of installation (based on the installation guide) is similar to the other methods.

If you use this installer, do not forget to mention it when asking for support and also to provide the archinstall log, when asked.

Moving to Zstandard images by default on mkinitcpio

As linux-lts moved to the version, all official kernels of Arch Linux now support zstd compressed initramfs images, so mkinitcpio is switching to zstd compressed images by default with version 30, which is currently on [testing].

If, for any reason, you are using a kernel version prior to , make sure to change mkinitcpio.conf COMPRESSION to use one of the compressors supported, like gzip, otherwise you will not be able to boot images generated by mkinitcpio.

Chromium losing Sync support in early March

Google has announced that they are going to block everything but Chrome from accessing certain Google features (like Chrome sync) starting on March This decision by Google is going to affect Arch's package a bit earlier, on March 2, when Chromium 89 gets released.

We know for sure that data syncing will stop working (passwords, bookmarks, etc.). Other features such as geolocation or enhanced spell check might continue to function for a bit longer. Extensions integrating with Google Drive might misbehave and LibreOffice will lose access to documents stored there.

Other distros such as openSUSE and Fedora have …

Older News

PHP and PHP 7 legacy packages are available
Manual pages indexing service
Arch Linux mailing list id changes
Accessible installation medium
libtraceevent>= update requires manual intervention
nvidia is incompatible with linux >=
ghostpcl>= and ghostxps>= updates require manual intervention
Arch Conf schedule
Kill Arch Bugs: Help us on the 13th of September!
AUR Migration: New SSH HostKeys
Arch Linux: The LTS Kernel


Related articles

According to Wikipedia:

The Linux kernel is an open-source monolithic Unix-like computer operating system kernel.

Arch Linux is based on the Linux kernel. There are various alternative Linux kernels available for Arch Linux in addition to the latest stable kernel. This article lists some of the options available in the repositories with a brief description of each. There is also a description of patches that can be applied to the system's kernel. The article ends with an overview of custom kernel compilation with links to various methods.

Kernel packages are installed onto the file system under . To be able to boot into kernels, the boot loader has to be configured appropriately.

Officially supported kernels

Community support on forum and bug reporting is available for officially supported kernels.

  • Stable &#; Vanilla Linux kernel and modules, with a few patches applied. || linux
  • Hardened &#; A security-focused Linux kernel applying a set of hardening patches to mitigate kernel and userspace exploits. It also enables more upstream kernel hardening features than linux. || linux-hardened
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-lts
  • Zen Kernel &#; Result of a collaborative effort of kernel hackers to provide the best Linux kernel possible for everyday systems. Some more details can be found on (which provides kernel binaries based on Zen for Debian). || linux-zen


Following methods can be used to compile your own kernel:

/Arch Build System
Takes advantage of the high quality of existing linuxPKGBUILD and the benefits of package management.
/Traditional compilation
Involves manually downloading a source tarball, and compiling in your home directory as a normal user.
  • Using custom kernels may cause all kinds of stability and reliability issues, including data loss. Having backups is strongly advised.
  • Arch Linux only has official support for #Officially supported kernels. When using a different kernel, please mention so in support requests.
  • Best way to increase the speed of your system is to first tailor your kernel config to your architecture and processor type.
  • You can reduce the size of your kernel (and therefore build time) by not including support for things you do not have or use. For example support for things like bluetooth, video4linux, Mbit ethernet, etc.
The config files for the Arch kernel packages are in the Arch package source files (for example, [1]linked from linux). The config file of your currently running kernel may also be available in your file system at if the kernel option is enabled.

Some of the listed packages may also be available as binary packages via Unofficial user repositories. kernels

  • Git &#; Linux kernel and modules built using sources from Linus Torvalds' Git repository || linux-gitAUR
  • Mainline &#; Kernels where all new features are introduced, released every months. || linux-mainlineAUR
  • Next &#; Bleeding edge kernels with features pending to be merged into next mainline release. || linux-next-gitAUR
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-lts44AUR
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-lts49AUR
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-ltsAUR
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-ltsAUR
  • Longterm &#; Long-term support (LTS) Linux kernel and modules. || linux-lts54AUR

Unofficial kernels

  • Aufs &#; The aufs-compatible linux kernel and modules, useful when using docker. || linux-aufsAUR
  • Ck &#; Contains patches by Con Kolivas (including the MuQSS scheduler) designed to improve system responsiveness with specific emphasis on the desktop, but they are suitable to any workload. || linux-ckAUR
  • Clear &#; Patches from Intel's Clear Linux project. Provides performance and security optimizations. || linux-clearAUR
  • GalliumOS &#; The Linux kernel and modules with GalliumOS patches for Chromebooks. || linux-galliumosAUR || linux-libreAUR
  • Liquorix &#; Kernel replacement built using Debian-targeted configuration and the Zen kernel sources. Designed for desktop, multimedia, and gaming workloads, it is often used as a Debian Linux performance replacement kernel. Damentz, the maintainer of the Liquorix patchset, is a developer for the Zen patchset as well. || linux-lqxAUR
  • MultiPath TCP &#; The Linux Kernel and modules with Multipath TCP support. || linux-mptcpAUR
  • pf-kernel &#; Provides a handful of awesome features which are not merged into a kernel mainline. Maintained by a kernel engineer. If the port for the included patch for new kernels was not released officially, the patchset provides and supports patch ports to new kernels. The current most prominent patches of linux-pf are PDS CPU scheduler and UKSM. || Packages:
  • Realtime kernel &#; Maintained by a small group of core developers led by Ingo Molnar. This patch allows nearly all of the kernel to be preempted, with the exception of a few very small regions of code ("raw_spinlock critical regions"). This is done by replacing most kernel spinlocks with mutexes that support priority inheritance, as well as moving all interrupt and software interrupts to kernel threads. || linux-rtAUR, linux-rt-ltsAUR
  • tkg &#; A highly customizable kernel build system that provides a selection of patches and tweaks aiming for better desktop and gaming performance. It is maintained by Etienne Juvigny. Amongst other patches, it offers various CPU schedulers: CFS, Project C PDS, Project C BMQ, MuQSS and CacULE. || not packaged? search in AUR
  • VFIO &#; The Linux kernel and a few patches written by Alex Williamson (acs override and i) to enable the ability to do PCI Passthrough with KVM on some machines. || linux-vfioAUR, linux-vfio-ltsAUR
  • XanMod &#; Aiming to take full advantage in high-performance workstations, gaming desktops, media centers and others and built to provide a more rock-solid, responsive and smooth desktop experience. This kernel uses the MuQSS or CacULE scheduler, BFQ I/O scheduler, UKSM realtime memory data deduplication, TCP BBR congestion control, x86_64 advanced instruction set support, and other default changes. || linux-xanmodAUR, linux-xanmod-caculeAUR

Debugging regressions

See General troubleshooting#Debugging regressions.

Try linux-mainlineAUR to check if the issue is already fixed upstream. The stickied comment also mentions a repository which contains already built kernels, so it may not be necessary to build it manually, which can take some time.

It may also be worth considering trying the LTS kernel (linux-lts) to debug issues which did not appear recently. Older versions of the LTS kernel can be found in the Arch Linux Archive.

If the issue still persists, bisectlinux-gitAUR and report the bug on the kernel bugzilla. It is important to try the "vanilla" version without any patches to make sure it is not related to them. If a patch causes the issue, report it to the author of the patch.

Note: Bisecting the kernel can take a lot of time since it may need to be rebuilt many times.

See also


Kernel version linux arch


Building a Custom Kernel on Arch Linux


Similar news:


576 577 578 579 580