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

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

@eggz I have the following logs (building px4_drv dkms):

make[1]: Entering directory '/usr/lib/modules/5.16.10-AMD/build'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: gcc (GCC) 11.1.0
  You are using:           gcc (GCC) 11.2.0
  CC [M]  /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver/driver_module.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/stackleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[2]: *** [scripts/Makefile.build:287: /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver/driver_module.o] Error 1
make[1]: *** [Makefile:1846: /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.16.10-AMD/build'
make: *** [Makefile:19: px4_drv.ko] Error 2

@hina yes, these are the changes:

-CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.1.0"
+CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.2.0"
-CONFIG_GCC_VERSION=110100
+CONFIG_GCC_VERSION=110200
-CONFIG_AS_VERSION=23601
+CONFIG_AS_VERSION=23800
-CONFIG_LD_VERSION=23601
+CONFIG_LD_VERSION=23800

But can you elaborate on what the problem is exactly? All I can see it's enabled:

CONFIG_HAVE_ARCH_STACKLEAK=y
CONFIG_GCC_PLUGIN_STACKLEAK=y
CONFIG_STACKLEAK_TRACK_MIN_SIZE=100

The problem with stackleak_plugin is happening again. It seems that gcc11.2 has been mainlined recently, is this the reason?

CONFIG_FW_LOADER_COMPRESS is not set. The new linux-firmware package 20220119.0c6a7b3-2 implements kernel firmware compression. Without it my wifi cannot find the firmware. [OK, on latest firmware 5.16-4AMD it is enabled, thank you!]]

I did a benchmark on this kernel with my Ryzen Threadripper 3970X.

Running the standard kernel takes 6mins and 20 seconds to fully build the Linux kernel with 64 threads. It takes 6mins and 21 seconds to build the same Linux kernel.

So this kernel doesn't improve much if you, like me, only care about compiling source code.

Thanks Lucas Tanure

I seem to be having problems with the latest kernel when I reboot a system. Poweroff is fine. I have never seen a kernelupdate with this many commits, going through them seems like hell. As of now I have no idea where this issue comes from.

Thank you for bringing this to my attention blackhole!

I think that the problems is this:

CONFIG_FW_LOADER_COMPRESS is not set

It should set to

CONFIG_FW_LOADER_COMPRESS=y

After last system update with new firmware package I have a lot of errors:

platform regulatory.0: Direct firmware load for regulatory.db failed with error -2

iwlwifi 0000:05:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-67.ucode failed with error -2

etc.

This is not happening with standard archlinux kernel

Apologies, "CONFIG_RTW89 is not set" was indeed what I meant.

Ie: (made sure to only copy from Arch kernel github)

CONFIG_RTW89=m
CONFIG_RTW89_CORE=m
CONFIG_RTW89_PCI=m
CONFIG_RTW89_8852AE=m
CONFIG_RTW89_DEBUG=y
CONFIG_RTW89_DEBUGMSG=y
CONFIG_RTW89_DEBUGFS=y

Thanks for your efforts!