Package Details: nvidia-340xx-dkms 340.108-37

Git Clone URL: https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy)
Package Base: nvidia-340xx
Description: NVIDIA driver sources for linux, 340xx legacy branch
Upstream URL: https://www.nvidia.com/
Licenses: custom
Conflicts: nvidia, nvidia-340xx
Provides: nvidia-340xx
Submitter: simonsmh
Maintainer: JerryXiao
Last Packager: JerryXiao
Votes: 72
Popularity: 0.036735
First Submitted: 2019-06-07 10:29 (UTC)
Last Updated: 2024-05-10 16:52 (UTC)

Pinned Comments

JerryXiao commented on 2022-10-13 03:51 (UTC) (edited on 2022-10-14 02:44 (UTC) by JerryXiao)

For testing users, contributors: check out https://github.com/archlinux-jerry/nvidia-340xx
Warning: force push may happen to match the aur tree

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 59 Next › Last »

nahno commented on 2022-09-18 09:31 (UTC)

Hi @freeartist, is all okay still valid for you and 5.19.9-arch1-1? Thanks (for me it does not work)

mauzil commented on 2022-09-18 07:56 (UTC)

Hi all. Does the DRI3 extensions are supported with nvidia 340?

Thanks all

MZ

freeartist commented on 2022-09-07 22:19 (UTC) (edited on 2022-09-07 22:20 (UTC) by freeartist)

All ok, 340.108 driver patch 5.18 works on 5.19 kernel

[deepforest@home ~]$ grep "X Driver" /var/log/Xorg.0.log

[ 30.444] (II) NVIDIA dlloader X Driver 340.108 Wed Dec 11 14:06:00 PST 2019

[deepforest@home ~]$ uname -r

5.19.7-arch1-1

freeartist commented on 2022-09-06 21:42 (UTC)

Hello! Can i ask here? Will there be a patch for 5.19 kernel for this 340.108 driver?

sebalis commented on 2022-08-24 17:49 (UTC)

Apologies, I didn’t check thoroughly enough when I said that v4l2loopback-dkms does not seem to be affected – it is. The module is not loaded with a message saying “Invalid argument” and the journal says “kernel: failed to validate module [v4l2loopback] BTF: -22”, So in all likelihood that module has the same issue.

sebalis commented on 2022-08-24 12:56 (UTC) (edited on 2022-08-24 12:57 (UTC) by sebalis)

Reading the details in the linked-to reddit thread I think you’re spot on. I have seen the “Operation not permitted” message when trying to load the module manually and the update did include GCC. I have one other dkms module, v4l2loopback-dkms, which does not seem affected – maybe it does not use BTF/BPF in its source. (I don’t actually know what BTF/BPF is.)

What is to be done then – apply something like that reddit script to strip those BTF sections from the object files?

seth commented on 2022-08-24 12:32 (UTC)

That's not the nvidia module, DKMS "broke" for reasons. https://bbs.archlinux.org/viewtopic.php?pid=2053486#p2053486

sebalis commented on 2022-08-24 01:38 (UTC) (edited on 2022-08-24 10:54 (UTC) by sebalis)

This is a Dell Latitude E6510 by the way, in case that is relevant in any way. [There was a sentence about not being able to suspend/hibernate with nouveau here earlier, but I solved that by adding the kernel parameter init_on_alloc=0 to grub and it was off-topic anyway.)

sebalis commented on 2022-08-24 01:08 (UTC) (edited on 2022-08-24 01:29 (UTC) by sebalis)

After the latest full update, which includes the 5.19.3 kernel, the nvidia-340xx-dkms won’t work anymore on my system. journalctl contains the following lines:

Aug 24 02:36:07 Io kernel: BPF: [112185] Invalid kind:19

Aug 24 02:36:07 Io kernel: failed to validate module [nvidia] BTF: -22

and no nvidia module is shown via lsmod.

I removed the nvidia driver completely and am using nouveau for the time being, but previously I have had issues with it and would like to return to nvidia-340xx-dkms driver if possible.

bigjuck commented on 2022-08-23 08:15 (UTC)

Runs fine on kernel 5.15.62-1-lts after dkms remove and dkms install

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 59 Next › Last »