Arch Linux User Repository

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: linux-amd-headers 6.10.5-1

Package Actions

Git Clone URL:	https://aur.archlinux.org/linux-amd.git (read-only, click to copy)
Package Base:	linux-amd
Description:	Headers and scripts for building modules for the linux-amd package
Upstream URL:	https://www.kernel.org/
Licenses:	GPL-2.0-only
Submitter:	None
Maintainer:	None
Last Packager:	archdevlab
Votes:	34
Popularity:	0.169975
First Submitted:	2019-11-10 15:20 (UTC)
Last Updated:	2024-08-21 00:22 (UTC)

Dependencies (28)

linux-amd^AUR
pahole (pahole-git^AUR)
bc (bc-gh^AUR) (make)
binutils (make)
bison (byacc-bison^AUR, bison-git^AUR) (make)
cpio (cpio-git^AUR) (make)
flex (flex-git^AUR) (make)
gcc (gcc-git^AUR, gccrs-git^AUR, gcc11^AUR, gcc-snapshot^AUR) (make)
gcc-libs (gcc-libs-git^AUR, gccrs-libs-git^AUR, gcc11-libs^AUR, gcc-libs-snapshot^AUR) (make)
gettext (gettext-git^AUR) (make)
git (git-git^AUR, git-gl^AUR) (make)
glibc (glibc-git^AUR, glibc-linux4^AUR, glibc-eac^AUR) (make)
graphviz (make)
imagemagick (imagemagick-git^AUR, imagemagick-full-git^AUR, imagemagick-full^AUR) (make)
kmod (busybox-coreutils^AUR, kmod-git^AUR) (make)
libelf (elfutils-git^AUR) (make)
make (make-git^AUR) (make)
pahole (pahole-git^AUR) (make)
patch (patch-git^AUR) (make)
perl (perl-git^AUR) (make)
python (python37^AUR, python311^AUR, python310^AUR) (make)
python-sphinx (python-sphinx-git^AUR) (make)
python-yaml (python-yaml-git^AUR) (make)
tar (tar-git^AUR, busybox-coreutils^AUR) (make)
texlive-latexextra (texlive-dummy^AUR, texlive-installer^AUR, texlive-full^AUR) (make)
xmlto (xmlto-git^AUR) (make)
xz (xz-git^AUR) (make)
zstd (zstd-git^AUR, zstd-static^AUR) (make)

Required by (0)

Sources (21)

Pinned Comments

archdevlab commented on 2024-08-15 03:38 (UTC)

I have adopted this package and have updated it!

Thanks!

<deleted-account> commented on 2023-05-04 16:38 (UTC)

GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver3 based hardware, please use linux-amd-znver3
If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

<deleted-account> commented on 2020-10-26 18:15 (UTC)

GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

<deleted-account> commented on 2019-11-10 15:23 (UTC)

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

[linuxkernels]
Server = http://nhameh.ovh/$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 37 Next › Last »

jansuX2 commented on 2023-03-25 01:13 (UTC) (edited on 2023-03-25 01:53 (UTC) by jansuX2)

From what I understand, and I could be wrong as I haven't ever build a package myself, so either ignore/forgive me or correct me, as long as you have included linux-amd.preset in backup= in the PKGBUILD, the current (= my edited linux-amd.preset without the fallback option) is being renamed and preserved as a .pacsave, (making it unuseable in this case) https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#.pacsave and in order to prevent the upgrade from overwriting my file I'm going to add its path to NoUpgrade=etc/mkinitcpio.d/linux-amd.preset in /etc/pacman.conf : "All files listed with a NoUpgrade directive will never be touched during a package install/upgrade, and the new files will be installed with a .pacnew extension."https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#Package_backup_files and I'll see from that point on. (iirc building and installing with the traditional way, makepkg -si, works fine, instead of pacman locally or using a helper, or I could try & error editing out that line from the PKGBUILD -as an educational process-)

According to your link, there should be by default imo a .pacnew situation, yet (I assume because of the inclusion in backup=) there is a .pacsave situation: "original = X, current = Y, new = X The original package and the new package both contain exactly the same version of the file, but the version currently in the filesystem has been modified. Leave the current version in place and discard the new version without notifying the user." Thanks for all the work nonetheless.

eclairevoyant commented on 2023-03-20 01:59 (UTC)

@jansux2 see https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave#Types_explained

<deleted-account> commented on 2023-03-17 10:43 (UTC)

Well first of all your current configuration will never get overwritten. I disabled the rescue as well in my file and it gets left alone.

I do not know why you are discussing pacman behaviour with me -- pacman is not maintained by me, please take up your issue with the archlinux core team.

jansuX2 commented on 2023-03-17 10:25 (UTC) (edited on 2023-03-17 10:31 (UTC) by jansuX2)

Hi, replacing (an edited) linux-amd.preset with the default each time and keeping a .pacsave for the old version isn't suitable for the cases one doesn't want a fallback initramfs image (small ESP), could you provide a .pacnew instead?

<deleted-account> commented on 2023-03-11 10:13 (UTC)

Looks like they did the exact thing upstream, but a whole day later..... https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-6.2.y

Building new version of the kernel... Which is exactly the same as this one....

<deleted-account> commented on 2023-03-10 12:28 (UTC)

Reverted the faulty git commits. How this kernel panic did not get spotted upstream is completely beyond me.

<deleted-account> commented on 2023-03-10 10:18 (UTC)

I am personally experiencing problems when shutting down/ rebooting this latest 6.2.3 kernel. Im investigating.

<deleted-account> commented on 2023-02-22 08:18 (UTC)

When znver4 finally lands I will make a linux-amd-znver3 and this will become the mainline znver4 version. But judging by the very late work of znver4, please, don't hold your breath for it :-)

FGD commented on 2023-02-22 01:52 (UTC) (edited on 2023-02-22 01:53 (UTC) by FGD)

Thank you for the info @flakusha! :)

flakusha commented on 2023-02-22 01:48 (UTC)

@FGD Kernel works on Zen4 (I have 7950X), optimization for znver4 will be available after release of gcc 13 in the following months, at the moment using "native" just falls back to znver3

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 37 Next › Last »