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:	archdevlab
Last Packager:	archdevlab
Votes:	33
Popularity:	0.21
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, glibc-eac-bin^AUR, glibc-eac-roco^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)
Show 8 more dependencies...

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 .. 3 4 5 6 7 8 9 10 11 12 13 .. 37 Next › Last »

<deleted-account> commented on 2023-04-28 08:12 (UTC)

OK, I will test it on znver3 hardware soon, as I dont have acces to it right now. Stay tuned.

flakusha commented on 2023-04-28 07:48 (UTC)

Hello! Can you check out the new AMD P-State EPP for this kernel? https://www.phoronix.com/review/linux-63-amd-epyc-epp

<deleted-account> commented on 2023-03-31 09:20 (UTC)

I had no idea AMD did thunderbolt :D, Coming right up ...

FGD commented on 2023-03-31 00:34 (UTC)

Your answer is right here: https://aur.archlinux.org/cgit/aur.git/tree/config.x86_64?h=linux-amd#n8760

Keridos commented on 2023-03-31 00:29 (UTC)

Is CONFIG_USB4 enabled in this kernel?

I am currently trying to debug s2idle issues on my amd thinkpad and AMDs debug scripts says no driver for thunderbolt (aka usb4) is installed causing s2idle to not properly work.

<deleted-account> commented on 2023-03-27 21:56 (UTC)

oh, ok well, just be advised I cannot give any support on dracut image generation on arch linux. (I use it on rhel but not here...)

FGD commented on 2023-03-27 20:44 (UTC)

My distro uses dracut by default. I just ignore the mkinitcpio msg.

<deleted-account> commented on 2023-03-27 14:07 (UTC)

I would advise to stop using dracut and start using the distrubution's way of making ramdisks, called mkinitcpio.

killajoe commented on 2023-03-27 10:53 (UTC)

using dracut i got theis "error" it does not harm i bet ;)

>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio.  Please wait...
/tmp/alpm_4art4J/.INSTALL: line 24: mkinitcpio: command not found

only wanted to mention this may tehre is a way to omit this too.

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.

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