Arch Linux User Repository

GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver3 based hardware, please use linux-amd-znver3
If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.

This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.

If you use znver2 based hardware, please use linux-amd-znver2
If you use raven based hardware, please use linux-amd-raven

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

Samba mounts work fine here on my rig using 5.18.8-AMD. It looks to me that the cause of your SMB problems lie elsewhere and have nothing to do with the kernelupgrade.

Since 5.18.8-AMD I'm unable to mount any cifs share, it returns error code -22. With 5.18.7-AMD it works fine.

This is from my fstab:

//mynas/myshare /mnt/nas     cifs            x-systemd.automount,_netdev,nofail,vers=3.1.1,credentials=/path/to/my/.smbcredentials,uid=1000,gid=1000,forceuid,forcegid,nofail  0       0

@pooh You already said "after upgrading to 5.17". There is no need to repeat things. Since its "only" (?) a major release in diffrence, the number of commits to sift through is just way to much to find the problem, especially when I cannot reproduce the problem on my current hardware. I'm really sorry, but theres not much i can (humanly) do from my end. If you have more useful information I remain ready to investigate, but for now: I have no idea.

@eggz 5.16.16 works correctly.

@pooh

Sorry no idea man, dont have BT issues here and the hiberate could mean a million things.

Hi. I had a bt mouse cursor lag after upgrading to 5.17.

And sometimes the laptop hangs when coming out of hibernation.

Any idea what may be causing this?

Regards.

@cgu No... that was an announcemet from more than a year ago....

Please check the config to see with which gcc this kernel was built...

CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.2.0"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=110200

@eggz Thanks for your fast response. Nevertheless it feels strange. I am using manjaro and installed your kernel manually via aur. I have every package up to date. Also my gcc version is:

gcc --version
gcc (GCC) 11.2.0

I am wondering at the moment, since you mentioned the mainlined gcc 11.1 where i am getting the 11.2 from official repos.

@cgu

Works fine over here:

(2/2) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.14-AMD-znver2
Deprecated feature: REMAKE_INITRD
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.13-arch1-1
Deprecated feature: REMAKE_INITRD
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.14-AMD
Deprecated feature: REMAKE_INITRD
==> depmod 5.16.13-arch1-1
==> depmod 5.16.14-AMD-znver2
==> depmod 5.16.14-AMD

@cgu

Works fine over here:

(2/2) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.14-AMD-znver2
Deprecated feature: REMAKE_INITRD
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.13-arch1-1
Deprecated feature: REMAKE_INITRD
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.14-AMD
Deprecated feature: REMAKE_INITRD
==> depmod 5.16.13-arch1-1
==> depmod 5.16.14-AMD-znver2
==> depmod 5.16.14-AMD