Arch Linux User Repository

Hi

I have adopted this package and have updated it!

Thanks!

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

@webmeister In addition to what @eggz said, this kernel specifically omits certain features deemed unnecessary. For example, filesystem encryption is specifically disabled despite the encryption being compatible with AMD hardware.

@webmeister The config is based on my pickings, findings, and testing. Its not copy pasted from anywhere, so it will be impossible for me to give you any source except but myself. I took a look at almost every CONFIG line and researched it was still relevant for modern AMD hardware. My Friend NhaMeh (comaintainer) also assisted in this picking. This didn't sit well indeed with some people in the past searching for a vanillaarch 'drop in' replacement, but this is, for all intends and purposes, a custom kernel.

Now, for the reason why I stay away from 1:1 vanilla arch based configs, I will need to go back in the past. I started maintaining amd kernels because the vanilla config of arch linux was completely incompatible with amd and amdgpu hardware in the past (~2018) for months on end. Now I want to be very clear in this: Arch linux does not build or test anything on AMD hardware, atleast they didn't for a very large period. My kernels their intention is to keep an upstream kernel version compatible with specific amd hardware. Apperantly this was a very unique thing to do around 2018. Long story short: I will never release a kernel that doesn't run/work on AMD hardware. I'm sorry, but making a 1:1 "drop in" kernelconfig simply puts that fact into serious jeopardy.

And thank you so much for pointing out the mtune! its still an old reference. I'll fix it asap! Can't believe I missed that. Thanks again!!

Thanks for maintaining this. What is your config.x86_64 based on? I assumed, it would follow https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config more closely, but the diff is huge (which makes it difficult to use as a drop-in replacement).

Also, is there any reason it still says mtune=znver2 in the PKGBUILD?

Linux Kernel 5.13 git development log:

      amdgpu:
       - Revert GFX9/10 doorbell fixes, we just end up trading one bug for
         another

Yeah, totaly didn't see that one coming ..

5.13 Coming up.

I reverted the faulty "doorbell" (thats how they call it in the git...) commits to remove the idle bug as referenced in the linux-slim and linux-amd-znver2 aur comments

FYI, With the current kernelrelease I have a problem with my SIENNA (6800 series) GPU. The idle usage is through the roof, for some reason the GPU is not clocking back. There seems to be something using it but I have no idea what. This is at the kernel level.

I have succesfully removed the problem on my linux-slim kernel by reverting the "doorbell" commits which seems to cause this high usage bug (in some way I do not understand)

I have searched around alot EVERYWHERE the last few days, and it seems to me I am the ONLY one with this problem (or a sienna gpu?), if there is a need for the fix on this kernel, let me know and I will make it so.

5.11.2 still does not contain the upstream amdgpu fixes, but atleast they are spotted in the master tree of stable:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c712c9c382ca69a955e3a384fc245ad8c42b005

Which leads me to believe they will finally be merged in 5.11.3

Until then, enjoy this prepatched kernel I guess..

Looks like the amdgpu patches are still not mainlined, so... enjoy this patched kernel I guess? Can't really follow why it is so hard to merge these commits to stable.

Hey fellow AMD users, this is just a PSA; Be sure to check this thread out: https://www.reddit.com/r/Amd/comments/lnmet0/an_update_on_usb_connectivity_with_500_series/

As it turns out, I myself was/is also affected by those problems. But mostly the 'replug' happens so fast I don't even notice it. But my kernel logs sure does! :

Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver usbfs
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver hub
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new device driver usb
Feb 23 09:45:21 eggzpc kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb: port power management may be unreliable
Feb 23 09:45:21 eggzpc kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb 1-3: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 5-1: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 3-4: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 7-2: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 3-4: config 1 has an invalid interface number: 2 but max is 1
Feb 23 09:45:21 eggzpc kernel: usb 3-4: config 1 has no interface number 1
Feb 23 09:45:21 eggzpc kernel: usb 5-1: not running at top speed; connect to a high speed hub
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver usbhid

Lets hope AMD adresses them soon!

I identified the AMDgpu troubles in the linux-next tree and "backported" the patch

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=85f4f00c1e88b2a5aced59cca7354631e8889dfb

Description:

This reverts commit 8866a67ab86cc0812e65c04f1ef02bcc41e24d68.

This breaks hotplug of HDMI on some systems, resulting in
a blank screen also causes failures for displays to light up
on other systems.

There are a bunch of other fixes in upstream (linux-next), but this one seems standalone and is compatible with the stable tree. I'm not going to put everything upstream inhere, this seems to be enough for me to supress all the AMDGPU errors.

I tested this on 2 machines already and it seems to have good results.