AUR (en) - linux-amd

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)
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-installer^AUR, texlive-full^AUR, texlive-dummy^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 .. 6 7 8 9 10 11 12 13 14 15 16 .. 37 Next › Last »

<deleted-account> commented on 2022-12-10 23:24 (UTC)

OK. I was just "firing for effect" in the beginning, Indeed, I wasn't sure which flags took effect or which not. Thank you for your information. If I have the time I will clean it up.

nsmks1508 commented on 2022-12-10 20:25 (UTC) (edited on 2022-12-10 20:35 (UTC) by nsmks1508)

CFLAGS and CXXFLAGS are just useless for building linux kernel. Kernel project has own flags management system, only CONFIG_MZEN3=y is matter here. (add -march=znver3) If you wanna add extra '-mtune=znver3 -O2 -pipe -fstack-protector-strong', you need to use ccflags-{module_name} = or ccflags-y = (globally)

make ... ccflags-y='-mtune=znver3 -O2 -pipe -fstack-protector-strong'

OR safer way is change Makefile or the patch:

cflags-$(CONFIG_MZEN3)  += -march=znver3

cflags-$(CONFIG_MZEN3)  += -march=znver3 -mtune=znver3 -pipe -fstack-protector-strong

-O2 has already appied by default

Use make V=1 ... to check out if it's work

FGD commented on 2022-10-09 18:31 (UTC) (edited on 2022-10-09 18:31 (UTC) by FGD)

Hey @eggz, just confirming both config options worked, sensors are now displayed. :) Awesome thanks for the great work!!

<deleted-account> commented on 2022-10-04 06:57 (UTC)

ok, done

FGD commented on 2022-10-03 14:15 (UTC)

Tnx @eggz, yes that seems to be the one.

As for Gigabyte WMI, I believe it's CONFIG_GIGABYTE_WMI. https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2538128.html

I can test this by compiling another kernel, with and without that option, if that can help?

<deleted-account> commented on 2022-10-03 11:32 (UTC)

looks to be CONFIG_NVME_HWMON, ill have it ready this release.

FGD commented on 2022-10-02 20:11 (UTC) (edited on 2022-10-02 20:12 (UTC) by FGD)

Hello, the kernel does not recognize 2 of my 7 sensors: "nvme-pci" and "gigabyte_wmi-virtual".

Any other kernel does so far, including Zen, Mainline, my custom TKG-BMQ, etc..

Not sure what to give as info but this is what I should show with the NVME part of hwmon and sensors:

╰─λ sensors
nvme-pci-0100
Adapter: PCI adapter
Composite:    +37.9°C  (low  = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +49.9°C  (low  = -273.1°C, high = +65261.8°C)

gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1:        +27.0°C
temp2:        +32.0°C
temp3:        +32.0°C
temp4:        +31.0°C
temp5:        +32.0°C
temp6:        +42.0°C

╰─λ ls /sys/class/hwmon/
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon1 -> ../../devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/hwmon/hwmon1
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon2 -> ../../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/hwmon2
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon3 -> ../../devices/platform/it87.2624/hwmon/hwmon3
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon4 -> ../../devices/pci0000:00/0000:00:18.3/hwmon/hwmon4
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon5 -> ../../devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/DEADBEEF-2001-0000-00A0-C90629100000/hwmon/hwmon5
lrwxrwxrwx 0 root  2 Oct 15:37  hwmon6 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:406E.0005/power_supply/hidpp_battery_0/hwmon6
lrwxrwxrwx 0 root  2 Oct 15:38  hwmon7 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:4069.0004/power_supply/hidpp_battery_1/hwmon7

This is what it shows with linux-amd:

╰─λ ls /sys/class/hwmon/
lrwxrwxrwx 0 root  2 Oct 15:23  hwmon0 -> ../../devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/hwmon/hwmon0
lrwxrwxrwx 0 root  2 Oct 15:23  hwmon1 -> ../../devices/platform/it87.2624/hwmon/hwmon1
lrwxrwxrwx 0 root  2 Oct 15:23  hwmon2 -> ../../devices/pci0000:00/0000:00:18.3/hwmon/hwmon2
lrwxrwxrwx 0 root  2 Oct 15:23  hwmon3 -> ../../devices/virtual/thermal/thermal_zone0/hwmon3
lrwxrwxrwx 0 root  2 Oct 15:23  hwmon4 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:406E.0005/power_supply/hidpp_battery_0/hwmon4
lrwxrwxrwx 0 root  2 Oct 15:24  hwmon5 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:4069.0004/power_supply/hidpp_battery_1/hwmon5

Missing /devices/virtual/thermal/thermal_zone0 and /devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/hwmon2.

Absolutely not idea how to troubleshoot this, but since all my other kernels (tried 4-5) are showing the device, I'm guessing something could be missing within linux-amd.