Package Base Details: linux-amd

Git Clone URL: https://aur.archlinux.org/linux-amd.git (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 17
Popularity: 2.29
First Submitted: 2019-11-10 15:20
Last Updated: 2022-01-27 12:05

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 :

[linuxkernels]
Server = http://nhameh.ovh/$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

1 2 3 4 5 6 ... Next › Last »

eggz commented on 2022-01-27 12:54

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.

eggz commented on 2022-01-22 09:25

Thank you for bringing this to my attention blackhole!

blackhole commented on 2022-01-22 08:09

I think that the problems is this:

CONFIG_FW_LOADER_COMPRESS is not set

It should set to

CONFIG_FW_LOADER_COMPRESS=y

blackhole commented on 2022-01-22 08:05

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

Gero commented on 2022-01-17 16:14

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!

eggz commented on 2022-01-17 15:00

@gero,

I now see you mean CONFIG_RTW89 instead of CONFIG_RTW88. :-)

Thank you for bringing this to my attention, I will include it asap.

eggz commented on 2022-01-17 14:57

Gero, im unsure what you mean here.

This is our config right now:

CONFIG_RTW88=m
CONFIG_RTW88_CORE=m
CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822B=m
CONFIG_RTW88_8822C=m
CONFIG_RTW88_8822BE=m
CONFIG_RTW88_8822CE=m

CONFIG_RTW88 is included in our .config file (which forces it inside the kernel) . Also what do you mean with

 CONFIG_RTW89=n

Because that doesnt seem like a valid Kconfig line to me. option "n" doesn't exist. Are you refering to the commented "is not set" option?

Because it is included right now. You can check this with doing zcat /proc/config.gz | grep CONFIG_RTW88

Please clarify...

Gero commented on 2022-01-17 11:35

rtw89 for RTL8852AE wireless nics has landed in 5.16, which means I can do with one less dkms module. However, make olddefconfig with no default means CONFIG_RTW89=n.

@eggz is it possible to semi-regularly pull in upstream changes from the official Arch Linux kernel .config into linux-amd?

See https://github.com/archlinux/svntogit-packages/commit/94f84e1ad8a530e54aa34cadbaa76e8dcc439d10#diff-6503b30d816e211d1909eed3e1eff5f9105fdc48f5735921a59f4906f99415beR3840

I'd understand if keeping up with official Arch Linux would be too much work ;)

Anarconda commented on 2022-01-10 11:27

Just to end this "conversation":

  1. XOrg is working with nvidia proprietary drivers using the patch linked by @blackhole.
  2. Messages about "pstore: crypto_comp-decompress failed ..." and "Bluetooth: hci0: Failed to read codec ..." are still there. Obviously, they are not related to X system.

Thanks to both of you I'm using latest and greatest.

eggz commented on 2022-01-10 10:32

Good, because I know nothing about nvidia and certainly nothing about closed sourced drivers, and I really intend to keep it that way.

I had an AMDGPU crash But I think its just a one-off.