The sha256sum for the patch file has changed. The new checksum is 2f99d9e37f372925e054115bfead4723a328ffbdb7bf958753aab2ac48dc5673
Search Criteria
Package Base Details: linux-amd
Package Actions
| Git Clone URL: | https://aur.archlinux.org/linux-amd.git (read-only, click to copy) |
|---|---|
| Submitter: | None |
| Maintainer: | archdevlab |
| Last Packager: | None |
| Votes: | 29 |
| Popularity: | 0.014873 |
| First Submitted: | 2019-11-10 15:20 (UTC) |
| Last Updated: | 2024-04-29 09:32 (UTC) |
Packages (2)
Darkpelz commented on 2021-09-16 14:55 (UTC)
ciupenhauer commented on 2021-09-10 19:40 (UTC)
Anyone interested in creating a linux-amd-pstate package for the new patches? I would if I knew how to compile custom patches myself
<deleted-account> commented on 2021-09-02 15:38 (UTC)
4800H = renoir = znver2, correct.
traysh commented on 2021-09-02 10:27 (UTC)
I've got a AMD Ryzen 7 4800H with Radeon Graphics. I suppose I should use linux-amd-znver2, is that correct?
<deleted-account> commented on 2021-08-25 15:25 (UTC)
Yeah, they are probably good enough on zen 3.
itoffshore commented on 2021-08-25 12:09 (UTC)
The performance impact is zero for signed modules once booted & enforcing them is a kernel boot option choice by the user. They are implemented with no issues on the following performance kernels:
- linux-hardened-cacule
- linux-cacule-rt
- linux-xanmod-cacule
The cacule kernels allow AMD optimizations which is probably good enough on Zen 3.
<deleted-account> commented on 2021-08-25 07:11 (UTC)
For the same reason I disabled audit on these kernels, Hardening security is not a prio on this kernel, performance is. Signing all drivers by default and then not forcing a lockdown policy seems a pointless exercise to me (heck, signing modules in general is a bit too paranoid for my taste anyway) -- It would take away from the performance profile we have been building up.
If you want a hardened kernel, this is not the one.
itoffshore commented on 2021-08-25 02:57 (UTC) (edited on 2021-08-25 03:56 (UTC) by itoffshore)
Can you enable configuration please so that for example /usr/lib/modules/5.13.12-AMD/build/scripts/sign-file is created ? (so kernel modules can be cryptographically signed):
At the moment it is not enabled with /usr/lib/modules/5.13.12-AMD/build/scripts/sign-file.c showing in the package.
Officially supported kernels are configured with:
CONFIG_MODULE_SIG_FORMAT=y
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_SIG_ALL=y
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
CONFIG_MODULE_SIG_SHA512=y
CONFIG_MODULE_SIG_HASH="sha512"
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
<deleted-account> commented on 2021-08-22 07:27 (UTC)
in regards to powersaving features this kernel does not offer any special features.
ciupenhauer commented on 2021-08-21 23:11 (UTC)
Are there any notes about power saving regarding this kernel? Is it optimized to be more power hungry than default or does it not have any impact?
Pinned Comments
<deleted-account> commented on 2023-05-04 16:38 (UTC)
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.
<deleted-account> commented on 2020-10-26 18:15 (UTC)
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.
<deleted-account> commented on 2019-11-10 15:23 (UTC)
Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :