Package Base Details: linux-amd

Git Clone URL: https://aur.archlinux.org/linux-amd.git (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 29
Popularity: 0.029121
First Submitted: 2019-11-10 15:20 (UTC)
Last Updated: 2024-04-17 10:53 (UTC)

Pinned Comments

eggz commented on 2023-05-04 16:38 (UTC)

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

eggz commented on 2019-11-10 15:23 (UTC) (edited on 2020-02-18 12:08 (UTC) by eggz)

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 .. 7 8 9 10 11 12 13 14 15 16 17 .. 36 Next › Last »

killajoe commented on 2022-08-30 19:55 (UTC)

Would it be possible to add support for dracut? Just try that and see dependency for mkinitcpio and runnings in the PKGBUILD.

eggz commented on 2022-08-04 12:11 (UTC)

@blackhole thanks for the heads up!

blackhole commented on 2022-08-04 05:52 (UTC)

Using the repo package some kernel modules cannot be build, since gcc version differs:

The kernel was built by: gcc (GCC) 12.1.0 You are using: cc (GCC) 12.1.1 20220730

Could you update using gcc 12.1.1 ?

dekart811 commented on 2022-07-02 16:04 (UTC) (edited on 2022-07-02 16:06 (UTC) by dekart811)

I also have no idea why it only works with vers=2.1 for me, but at this point I don't really care. As long as I can mount my share, I'm OK with that.

Maybe it has something to do with that the server is still running Ubuntu 20.04 LTS? I didn't have the time to do an upgrade yet.

eggz commented on 2022-06-30 11:22 (UTC)

SMB3_11 works here on 5.18.8 so I am still really lost in how I can help you.

dekart811 commented on 2022-06-30 10:34 (UTC)

I got it working by changing vers=3.1.1 to vers=2.1. Now my cifs share is mounting fine.

They must have changed something in the kernel, because it only happens with 5.18.8-AMD. When I downgrade to 5.18.7-AMD or boot the lts kernel (5.15.50-1) it's working without even specifying a smb version.

blackhole commented on 2022-06-29 12:36 (UTC)

Try to remove forceuid forcegid

eggz commented on 2022-06-29 11:50 (UTC)

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.

dekart811 commented on 2022-06-29 10:47 (UTC)

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

eggz commented on 2022-04-07 12:39 (UTC)

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

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