Package Base Details: linux-amd-znver2

Git Clone URL: https://aur.archlinux.org/linux-amd-znver2.git (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 9
Popularity: 1.73
First Submitted: 2020-10-26 18:04
Last Updated: 2021-07-31 08:14

Pinned Comments

eggz commented on 2020-10-26 18:15

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 Next › Last »

eggz commented on 2021-05-01 09:50

@techxero

I See. How strange, I have a 3900x right here so it shouldn't be that diffrent from your CPU, and rebooting works just fine, so I really don't know what to tell you. :-(

Your older kernel will work for many years to come, but I suspect by then you will have found what the real problem is...

I have looked upstream for you and there is no mention of a reboot issue with the latest kernel..

Can you give your journalctl output right before your computer freezes?

TechXero commented on 2021-05-01 08:43

@eggz

Before restoring my system was rebooting fine. Now after formatting it and installing Arch fresh.

Rebooting not booting, meaning, when I type sudo reboot or reboot, or even select reboot from panel it goes through motions then freezes on black screen that has the 2 Kernel lines top left..

Keyboard is unresponsive I have to hard reset.. 5.11.16-amd-znver2 works great.. If I update same issue.. What could I be missing if older version works not new one ? If I was missing anything then even older version shouldn't work right ?

eggz commented on 2021-04-30 23:28

@techxero, so you did an arch fresh install, but it was working fine before upgrading the kernel? This sounds a bit confusing to me, when did you upgrade? before or after the fresh install?

I have this kernel running on a bunch of systems, all of them are working fine. I also haven't got any complaint yet for this kernel. I'll never say never, but for now all evidence points towards your install missing having another problem instead of the kernel having a problem.

At what point exactly do you have a black screen? After grub? After the rootswitch? What do you see on your screen after grub? If I had to take a wild guess guess with almost no info (low hitrate though), it seems like your created ramdisk image is completely failing you.

TechXero commented on 2021-04-30 17:57

@eggz Thanks for this but recently had to do fresh install of Arch now when using this Kernel and I try rebooting it just hangs on black screen. I am on Ryzen 5 3600X so a ZEN2 CPU.. Was working fine before upgrading to 5.12..

Seems 5.12 isn't yet ready for release. 5.11.16 is last one that works. So am sticking to that setting update to ignore for now :(

Tried Repo and compiling same result :(

ThirstyShark commented on 2021-04-26 22:55

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

eggz commented on 2021-04-26 21:48

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

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

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

Thanks for the thorough answer.

eggz commented on 2021-03-12 18:16

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.