Package Base Details: linux-amd

Git Clone URL: (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 13
Popularity: 1.21
First Submitted: 2019-11-10 15:20
Last Updated: 2021-12-01 09:30

Pinned Comments

eggz commented on 2020-10-26 18:15

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

eggz commented on 2019-11-10 15:23

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

Server =$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

eggz commented on 2021-07-22 06:36

Hello Graysky,

I use the patches on, Are you maintaining those aswel, or? Are those the same?

graysky commented on 2021-07-21 21:56

You might want to link my compiler patch directly:

JP-Ellis commented on 2021-07-18 00:22

@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.

eggz commented on 2021-07-17 18:01

@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!!

webmeister commented on 2021-07-17 17:14

Thanks for maintaining this. What is your config.x86_64 based on? I assumed, it would follow 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?

eggz commented on 2021-06-28 08:27

Linux Kernel 5.13 git development log:

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

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

5.13 Coming up.

eggz commented on 2021-06-26 13:19

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

eggz commented on 2021-06-24 11:37

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.

eggz commented on 2021-02-26 10:15

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

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

Until then, enjoy this prepatched kernel I guess..

eggz commented on 2021-02-23 13:53

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.