Package Details: linux-amd-znver2 6.11.0-1

Git Clone URL: https://aur.archlinux.org/linux-amd-znver2.git (read-only, click to copy)
Package Base: linux-amd-znver2
Description: The Linux kernel and modules - Compile with AMD Family 17h Zen 2 processors support
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: None
Last Packager: archdevlab
Votes: 18
Popularity: 0.180560
First Submitted: 2020-10-26 18:04 (UTC)
Last Updated: 2024-10-11 02:39 (UTC)

Required by (7)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 Next › Last »

<deleted-account> commented on 2021-02-23 15:21 (UTC)

I'm Sorry, but that would break my entire build pipeline. I hope you don't take this personally..

You sound like a capable guy (since you don't want to use the binary repo), maybe you can, for example, "sed" my PKGBUILD to your likings before you fire the build? Shouldn't be that hard to automate that. I also love automation.

macgeneral commented on 2021-02-23 15:01 (UTC) (edited on 2021-02-23 15:16 (UTC) by macgeneral)

Could you please either change the retrieval of the source code to the tar archive like for examlpe the linux-clear package does or alternatively use something like git clone --depth 1 --branch $gitver https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git?

It's completely unnecessary to retrieve the complete git history of the kernel (it wastes a lot of space when being kept in the cache directory and takes forever to download on a clean build).

Compare your current PKGBUILD:

[..]
Receiving objects: 100% (9277799/9277799), 3.43 GiB | 8.04 MiB/s, done.
[..]
dev@vm:~$ du -hs ~/.cache/yay/linux-amd-znver2/linux
3,7G    ~/.cache/yay/linux-amd-znver2/linux

Using only the current/required state (--depth 1):

dev@vm:~$ git clone --depth 1 --branch v5.11.1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[..]
Receiving objects: 100% (75668/75668), 202.59 MiB | 6.19 MiB/s, done.
[..]
dev@vm:~$ du -hs linux
1,4G    linux

Using the tar-Archive instead:

dev@vm:~$ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.11.1.tar.xz
[..]
linux-5.11.1.tar.xz 100%[===================>] 112,17M  9,14MB/s    in 13s     
[..]

So a https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-$gitver.tar.xz would be optimal ;)

<deleted-account> commented on 2021-02-23 13:52 (UTC)

Looks like the amdgpu patches are still not mainlined, so... enjoy this patched kernel I guess? Can't really follow why it is so hard to merge these commits to stable.

<deleted-account> commented on 2021-02-23 09:25 (UTC)

Hey fellow AMD users, this is just a PSA; Be sure to check this thread out: https://www.reddit.com/r/Amd/comments/lnmet0/an_update_on_usb_connectivity_with_500_series/

As it turns out, I myself was/is also affected by those problems. But mostly the 'replug' happens so fast I don't even notice it. But my kernel log sure does! :

Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver usbfs
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver hub
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new device driver usb
Feb 23 09:45:21 eggzpc kernel: usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb: port power management may be unreliable
Feb 23 09:45:21 eggzpc kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
Feb 23 09:45:21 eggzpc kernel: usb 1-3: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 5-1: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 3-4: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 7-2: new full-speed USB device number 2 using xhci_hcd
Feb 23 09:45:21 eggzpc kernel: usb 3-4: config 1 has an invalid interface number: 2 but max is 1
Feb 23 09:45:21 eggzpc kernel: usb 3-4: config 1 has no interface number 1
Feb 23 09:45:21 eggzpc kernel: usb 5-1: not running at top speed; connect to a high speed hub
Feb 23 09:45:21 eggzpc kernel: usbcore: registered new interface driver usbhid

Lets hope AMD adresses them soon!

<deleted-account> commented on 2021-02-21 00:43 (UTC)

I'm sorry but i chose lzo compression since its much faster in compressing. You can always override it to the compression of your choice, but I'm not changing the default.

toxygen commented on 2021-02-21 00:40 (UTC)

since arch is moving to ztsd compression on mkinitcpio, should linux-amd-znver2.preset line 6 be changed to:

export COMPRESSION="ztsd"

?

i had no problems with changing it manually

<deleted-account> commented on 2021-02-19 16:34 (UTC)

Hey, smart maintainers actually just wait for upstream and do nothing. I'm not a smart maintainer. I am an impatient one. I think I'm going to leave it like that, take the big problem out, let upstream take care of the rest. (Unless it's still not fixed in 5.11.1, then I'll have another look)

Thank you so much for your feedback. Now I know it's worth implementing on all my kernels. It's hard to debug/fix for hardware you do not even have.

scruffidog commented on 2021-02-19 16:24 (UTC)

I think you targeted the right fiddly bits. I've performed the poweroff under a few different scenarios and they all seem to work correctly in that when I take it down, it stays down.

The weird trace and the "Renoir unsupported power profile" issues are still there. One step at a time.

<deleted-account> commented on 2021-02-19 07:56 (UTC)

@scruffidog I implemented a proposed shutdown patch for renoir hardware. It seems to work in most cases (but not all of them).

If you are able, please provide feedback to me, to see if it is worth implementing on all kernels (or its just better to wait for upstream if it doesnt work in most cases).

<deleted-account> commented on 2021-02-19 07:33 (UTC)

This is probably the new renoir modules that aren't working 100%. The vanilla arch kernel works because they never bother activating AMD modules and that might be the probable cause.

as mentioned before this is probably because of these modules (which vanilla doesnt activate)

CONFIG_AMD_SFH_HID=m
CONFIG_AMD_PMC=m

If the complaints still keep rolling in after 5.11.1, I am disabeling these modules ...

EDIT:

Looks like you are not the only one: https://bugzilla.kernel.org/show_bug.cgi?id=211799