Arch Linux User Repository

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

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

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

Some AsRock motherboards use Mediatek WiFi modules (it's not marked in specification of motherboards). To enable WiFi modify config to include more Mediatek devices.

oh I see what you mean now, ok I fixed it

@eggz: Of course not, I only mean the package description is no longer correct. Thanks for maintaining this, it works great. :)

"... aimed at the latest AMD Ryzen CPU based hardware (ZNVER3/MZEN3)" -> Latest generation is Zen 4, not Zen 3.

1) I have got many complaints from dracut users forcing that dependency, so no thanks 2) gcc doesnt support znver4 yet? Are you saying people should use an unstable alpha gcc? I am not going to be part of this, no thanks.

Is the missing "initramfs" dependency intended? I doubt it's safe to uninstall "mkinitcpio".

You may also update the package description. Zen 4 is now the latest generation. :)

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.

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

to

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

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

ok, done

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?