Package Details: linux-amd-znver3 6.9.v.1-1

Git Clone URL: https://aur.archlinux.org/linux-amd-znver3.git (read-only, click to copy)
Package Base: linux-amd-znver3
Description: Linux kernel aimed at the znver3 AMD Ryzen CPU based hardware
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: None
Maintainer: bebna
Last Packager: bebna
Votes: 11
Popularity: 1.34
First Submitted: 2023-05-04 15:47 (UTC)
Last Updated: 2024-05-19 13:37 (UTC)

Pinned Comments

<deleted-account> commented on 2023-05-07 09:41 (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 2 3 4 5 6 7 8 .. 10 Next › Last »

hardfalcon commented on 2024-04-10 20:07 (UTC) (edited on 2024-04-10 20:31 (UTC) by hardfalcon)

eggz: I have a suspicion that you're affected by the same bug that I stumbled across, though it is caused by another commit.

The same commit is also present in kernel 6.6.26 btw.

Here's a fix that worked for me (at least with the reduced kernel config that I used for bisecting).

For details, see this thread.

Anarconda commented on 2024-04-10 20:02 (UTC)

I have this in my /proc/config.gz right now (kernel 6.8.5)

CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_HANDOVER_PROTOCOL=y ...

CONFIG_X86_MEM_ENCRYPT=y CONFIG_AMD_MEM_ENCRYPT=y CONFIG_NUMA=y

Sorry, but still not convinced.

<deleted-account> commented on 2024-04-10 19:54 (UTC)

It seems this is the commit that broke my kernels:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.8.y&id=7596a378a1aeead848b13bf442a4a678ce64cfce

if you enable CONFIG_EFI you will get into trouble. Probably because of the CONFIG_AMD_MEM_ENCRYPT dependency. This isnt the first time CONFIG_EFI got broken by upstream so I will probably leave it off on all the kernels even if they fix it afterwards (which they did last time, but only after a while). builds are coming up.

<deleted-account> commented on 2024-04-10 17:54 (UTC)

The problem is definetly upstairs. you are simply not using the module that is broken right now on your working kernel. The problem is I dont know which one it is.

<deleted-account> commented on 2024-04-10 17:51 (UTC)

ty for feedback. Yeah the linux-slim 6.8.5 also works for my system, but it has like 100 less modules

Anarconda commented on 2024-04-10 17:32 (UTC)

@eggz Yes, the kernel 6.8.5 compiled with your PKGBUILD returns to my UEFI menu but a different 6.8.5 PKGBUILD tweaked for an AMD znver3 CPU is working (using it right now). Meaning: I don't think the problem is upstairs.

I hope this is useful to you. Cheers.

<deleted-account> commented on 2024-04-10 16:59 (UTC)

On this moment, linux 6.8.5 does not boot on my AMD CPU hardware. It's reproduced on serveral AMD CPU systems and my amd kernels. The only kernel that works is my slimmed down linux-slim, pointing to an upstream bug somewhere in more complex kernel configs. Because of the number of commits in the 6.8.5 and no debuginfo (the kernel crashes right after the initramfs pivot), I am currently at a loss what the problem specifically is.

Anarconda commented on 2024-02-01 14:20 (UTC)

Just a heads-up for nvidia users: the package nvidia-open-dkms-545.29.06-15 in extra-testing is compiling and probably working (not sure because my GPU is not supported) but the PC is working in text mode.

<deleted-account> commented on 2024-02-01 10:22 (UTC)

I'm sure they'll fix the dkms sooner or later, this kernel has just released.