Package Details: linux-amd 6.10.5-1

Git Clone URL: https://aur.archlinux.org/linux-amd.git (read-only, click to copy)
Package Base: linux-amd
Description: The Linux kernel and modules - With some improvement patches
Upstream URL: https://www.kernel.org/
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: None
Maintainer: archdevlab
Last Packager: archdevlab
Votes: 34
Popularity: 1.17
First Submitted: 2019-11-10 15:20 (UTC)
Last Updated: 2024-08-21 00:22 (UTC)

Required by (7)

Sources (21)

Pinned Comments

archdevlab commented on 2024-08-15 03:38 (UTC)

Hi

I have adopted this package and have updated it!

Thanks!

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

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

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

If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

<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 :

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

Latest Comments

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 37 Next › Last »

hina commented on 2022-02-18 11:49 (UTC)

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

Gatenkaas commented on 2022-01-31 15:52 (UTC) (edited on 2022-01-31 16:14 (UTC) by Gatenkaas)

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

lucastanure commented on 2022-01-31 09:28 (UTC)

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

<deleted-account> commented on 2022-01-27 12:54 (UTC)

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.

<deleted-account> commented on 2022-01-22 09:25 (UTC)

Thank you for bringing this to my attention blackhole!

blackhole commented on 2022-01-22 08:09 (UTC)

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 (UTC)

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 (UTC) (edited on 2022-01-17 16:24 (UTC) by Gero)

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!

<deleted-account> commented on 2022-01-17 15:00 (UTC)

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

<deleted-account> commented on 2022-01-17 14:57 (UTC)

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

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 37 Next › Last »