Package Details: linux-amd-znver3-headers 6.12.v.5-1

Git Clone URL: https://aur.archlinux.org/linux-amd-znver3.git (read-only, click to copy)
Package Base: linux-amd-znver3
Description: Header files and scripts for building modules for the linux-amd-znver3 kernel
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: None
Maintainer: bebna
Last Packager: bebna
Votes: 10
Popularity: 0.124813
First Submitted: 2023-05-04 15:47 (UTC)
Last Updated: 2024-12-15 16:04 (UTC)

Latest Comments

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

bebna commented on 2024-08-15 22:27 (UTC)

@deemon @scruffidog I changed the config, tried to merge as much as possible from the mainline kernel w/o dropping the AMD changes. Probably have overseen some stuff or took to much from the mainline kernel.

I compiled and run the kernel on my system and it didn't show any problems in the first look. Drop me a comment if you find anything. Probably with the stuff I shall change in the config.

deemon commented on 2024-08-07 00:45 (UTC)

Alright. Don't change the LSM, but could you please enable the rest, so I can apply the LSM parameter to boot config?

bebna commented on 2024-08-03 14:12 (UTC)

These settings are from the previous maker creator / maintainer. I prefer to keep it as is, until it breaks.

Adding Apparmor as std in the CONFIG_LSM, would break other peoples setups. Please do it in your own aur package.

deemon commented on 2024-08-03 00:16 (UTC) (edited on 2024-08-03 00:53 (UTC) by deemon)

There is a problem with this kernel - it disables apparmor ... and now on second look, almost all kernel security options. Why? So could you kindly please re-apply apparmor? https://wiki.archlinux.org/title/AppArmor#Custom_kernel

CONFIG_SECURITY_APPARMOR=y
CONFIG_AUDIT=y

and also add apparmor to CONFIG_LSM (in arch wiki CONFIG_LSM="landlock,lockdown,yama,integrity,apparmor,bpf")

and while at it, is there a reason why you have also disabled landlock, lockdown and loadpin?

$ zgrep CONFIG_SECURITY /proc/config.gz
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
# CONFIG_SECURITY_NETWORK is not set
# CONFIG_SECURITY_INFINIBAND is not set
# CONFIG_SECURITY_PATH is not set
# CONFIG_SECURITY_SMACK is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_SECURITY_LOADPIN is not set
CONFIG_SECURITY_YAMA=y
# CONFIG_SECURITY_SAFESETID is not set
# CONFIG_SECURITY_LOCKDOWN_LSM is not set
# CONFIG_SECURITY_LANDLOCK is not set
$ zgrep CONFIG_LSM /proc/config.gz
CONFIG_LSM="yama,loadpin,safesetid,integrity"
$ cat /sys/kernel/security/lsm
capability,yama%                                                                                                                                                       

please add those also back. In fact can you please copy almost everything back from default arch kernel Security section for less confusion?? maybe skip selinux :-D and add to _LSM also apparmor.

https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main/config?ref_type=heads

scruffidog commented on 2024-08-02 19:32 (UTC)

I just noticed that NTFSv3 is compiled into the kernel instead of as a module. Out of curiosity, is there a reason for that other than just personal preference ?

deemon commented on 2024-07-24 19:23 (UTC) (edited on 2024-07-24 20:11 (UTC) by deemon)

New weird issue with the 6.10.0-AMD-znver3. Getting this continuous dmesg spam forever after boot:

[K juuli 24 21:33:13 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:14 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:14 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:14 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:14 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:15 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:15 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:15 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:15 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:16 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:16 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:16 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:17 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:17 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:17 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:17 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:18 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:18 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:18 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:18 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:19 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:19 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:19 2024] thermal thermal_zone0: failed to read out thermal zone (-61)
[K juuli 24 21:33:19 2024] thermal thermal_zone0: failed to read out thermal zone (-61)

...until I enable wifi interface, then it stops. Can even disable wifi afterwards and the spam doesn't return luckily.

Apparently it's a blast-from-the-past type of bug already reported and now resurfacing: https://bugzilla.kernel.org/show_bug.cgi?id=201761 check new entries since comment 72+

deemon commented on 2024-06-28 13:59 (UTC)

[ 0.034892] Booting paravirtualized kernel on bare hardware just curious, but since this kernel is supposed to be like specific hardware tailored kernel to run better on Zen3 architecture on bare hardware compared to generic kernel, how will it being able to run in a VM make any sense? Is there any downsides for it being able to run in VM?

Anarconda commented on 2024-05-19 13:47 (UTC)

@bebna I can't understand how I'm using latest kernel (6.9.1) since a few days (May 17th) without any problem. No patch file touched here. Puzzled!!

bebna commented on 2024-05-19 13:39 (UTC)

Dropped patch file in favor of flags in build time, because the patch wasn't matching the source code anymore.

Drop me a comment if that broke something, worked fine on my machine.