Package Details: linux-amd-znver2-headers 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: Headers and scripts for building modules for the linux-amd-znver2 package
Upstream URL: https://www.kernel.org/
Licenses: GPL-2.0-only
Submitter: None
Maintainer: archdevlab
Last Packager: archdevlab
Votes: 17
Popularity: 0.42
First Submitted: 2020-10-26 18:04 (UTC)
Last Updated: 2024-10-11 02:39 (UTC)

Latest Comments

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

ThirstyShark commented on 2021-04-26 22:55 (UTC)

Yep, touchpad is working again with the latest changes. Thanks for your quick response! Interesting how the config is split.

<deleted-account> commented on 2021-04-26 21:48 (UTC)

Thank you for picking this up, it seems that they renamed that option to these lines:

+CONFIG_I2C_HID_ACPI=m
+CONFIG_I2C_HID_CORE=m

which would explain why I lost that config, since I always reuse the old config.

Can you please confirm these new options work? thanks!

ThirstyShark commented on 2021-04-26 20:28 (UTC) (edited on 2021-04-26 20:29 (UTC) by ThirstyShark)

Hi,

in the latest version i2c-hid is gone. Can you re-add it? it's needed for most laptop touchpads.

CONFIG_I2C_HID=m

dedguy21 commented on 2021-03-12 20:43 (UTC) (edited on 2021-03-12 21:03 (UTC) by dedguy21)

Actually never mind, something messed up and so I'll just stick to the PKGBUILD. Thanks

How do we force "make localmodconfig" on your PKGBUILD?

I have it set to "menuconfig" so I can force zstd compress, but now the kernel, it build every module and the kitchen sink, was searching and didn't see an option where you would expect to see one?

dedguy21 commented on 2021-03-12 20:31 (UTC)

Thanks for the thorough answer.

<deleted-account> commented on 2021-03-12 18:16 (UTC)

It sure does. This was enabled by default starting from version 5.0. It should be enabled anywhere. You can check if its working with these steps. (everybody loves some feedback)

1) add 'drm.debug=0x04' to your kernel parameters preferably in "/etc/default/grub", in the GRUB_CMDLINE_LINUX, like this: GRUB_CMDLINE_LINUX="drm.debug=0x04" and then run grub-mkconfig -o /boot/grub/grub.cfg

or directly in "/boot/grub/grub.cfg" at the 'linux /boot/vmlinuz-linux' line, something like this: linux /boot/vmlinuz-linux root=UUID=<uuid> rw drm.debug=0x04

2) monitor dmesg output for 'VRR'(variable refresh rate?) strings (when the DE starts or when doing something opengl);

log search: dmesg | grep -e drm -e VRR realtime monitor: dmesg -w | grep -e drm -e VRR

You should see something like:

[  316.044970] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=0 state=2
[  316.058560] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=0 state=2
[  319.678906] [drm:drm_mode_addfb2 [drm]] [FB:132]
[  319.679766] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=1 state=3
[  319.683630] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=1 state=3
[  319.740178] [drm:drm_mode_addfb2 [drm]] [FB:140]
[  319.763956] [drm:drm_mode_addfb2 [drm]] [FB:141]
[  322.578440] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=0 state=2
[  322.589016] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=0 state=2
[  342.316459] [drm:drm_mode_addfb2 [drm]] [FB:131]
[  342.317336] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=1 state=3
[  342.331751] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=1 state=3
[  342.387385] [drm:drm_mode_addfb2 [drm]] [FB:132]
[  342.413740] [drm:drm_mode_addfb2 [drm]] [FB:133]
[  352.512071] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=0 state=2
[  352.522602] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=0 state=2
[  354.964177] [drm:drm_mode_addfb2 [drm]] [FB:137]
[  354.965248] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=77 enabled=1 state=3
[  354.968819] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet update: crtc=80 enabled=1 state=3
[  355.024555] [drm:drm_mode_addfb2 [drm]] [FB:132]
[  355.051308] [drm:drm_mode_addfb2 [drm]] [FB:141]

the VRR packet updates will show you that freesync is doing its thing.

ADDITION: you can even check out the monitor(s?) freesync range(s?) with this command: cat /sys/kernel/debug/dri/0/DP-*/vrr_range

Initial support was for a single monitor only, but my tests show now it should always be working, atleast when you are using OGL fullscreen on some monitor.

dedguy21 commented on 2021-03-12 15:14 (UTC)

Quick question, does this kernel come with freesync baked in and enabled?

<deleted-account> commented on 2021-02-26 10:15 (UTC)

5.11.2 still does not contain the upstream amdgpu fixes, but atleast they are spotted in the master tree of stable:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9c712c9c382ca69a955e3a384fc245ad8c42b005

Which leads me to believe they will finally be merged in 5.11.3

Until then, enjoy this prepatched kernel I guess..

macgeneral commented on 2021-02-23 15:29 (UTC) (edited on 2021-02-23 15:30 (UTC) by macgeneral)

Don't worry, there are no hard feelings - I hope I didn't sound rude :) As for the build pipeline: that's a valid point I didn't consider. It's just that your current PKGBUILD takes way longer than it could for everyone else (especially people with slow internet access).

I don't like binary builds (from the AUR) too much for critical things like the kernel, but I might give it a try.

Thank you for the fast response and for maintaining this project.

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

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