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 ?
Git Clone URL: | https://aur.archlinux.org/linux-amd.git (read-only, click to copy) |
---|---|
Package Base: | linux-amd |
Description: | The Linux kernel and modules - With some improvement patches |
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: | archdevlab |
Last Packager: | archdevlab |
Votes: | 33 |
Popularity: | 0.186671 |
First Submitted: | 2019-11-10 15:20 (UTC) |
Last Updated: | 2024-08-21 00:22 (UTC) |
« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 37 Next › Last »
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 ?
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.
SMB3_11 works here on 5.18.8 so I am still really lost in how I can help you.
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.
Try to remove forceuid forcegid
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.
Pinned Comments
archdevlab commented on 2024-08-15 03:38 (UTC)
Hi
I have adopted this package and have updated it!
Thanks!
<deleted-account> 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.
<deleted-account> commented on 2020-10-26 18:15 (UTC)
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.
<deleted-account> commented on 2019-11-10 15:23 (UTC)
Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :