Package Details: nvidia-340xx 340.108-37

Git Clone URL: https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy)
Package Base: nvidia-340xx
Description: NVIDIA drivers for linux, 340xx legacy branch
Upstream URL: https://www.nvidia.com/
Licenses: custom
Conflicts: nvidia
Submitter: simonsmh
Maintainer: JerryXiao
Last Packager: JerryXiao
Votes: 72
Popularity: 0.114966
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 .. 46 47 48 49 50 51 52 53 54 55 56 .. 59 Next › Last »

osvcos commented on 2020-04-07 00:14 (UTC)

Hello everyone, here is a patch: https://pastebin.com/3zaKNyDV

Manjaro was the first one as far as I know (https://gitlab.manjaro.org/packages/extra/linux56-extramodules/nvidia-340xx/-/blob/master/340.108-build-fix.patch) to release a patch, but:

  • It fixes things we fixed before
  • It modifies more files than this patch
  • This patch uses tests (conftest) instead of relying on kernel version

hackins commented on 2020-04-06 21:53 (UTC) (edited on 2020-04-06 21:59 (UTC) by hackins)

Can’t make to work this package on linux 5.6.2-arch1-2

anyone know what to fix?

Makepkg finishes with

“****

error: implicit declaration of function •drm_pci_exit•;

did you mean •drm_dev_exit•? [-Werror=implicit-function-declaration]

Some warnings being treated as errors

****”

wurbelgrumpff commented on 2020-03-22 22:41 (UTC)

with upgrading to kernel 5.5.10-arch1-1 dkms also failed due to the gcc version mismatch. With the altered command from @osvcos sudo env IGNORE_CC_MISMATCH=1 dkms install -m nvidia -v 340.108 -k 5.5.10-arch1-1 the upgrade of kernel and nvidia worked fine again.

graysky commented on 2020-03-19 13:20 (UTC)

OK, added in 340.108-6

https://aur.archlinux.org/cgit/aur.git/commit/?h=nvidia-340xx&id=9ae3a28fa19b416e5e8cc972c1da824bcc00893a

vova7890 commented on 2020-03-19 10:34 (UTC) (edited on 2020-03-19 10:36 (UTC) by vova7890)

That simply adds SLAB_USERCOPY flag to kmem_cache_create, that come from some kernel version. You can see that in 390xx kernel module

` nv_memdbg_init();

/* Allocated memory that is used for copying to/from userspace should be
 * tagged as such, on kernels that support this feature.
 */
nvidia_stack_t_cache = NV_KMEM_CACHE_CREATE_USERCOPY(nvidia_stack_cache_name,
                                                     nvidia_stack_t);
if (nvidia_stack_t_cache == NULL)
{
    nv_printf(NV_DBG_ERRORS, "NVRM: stack cache allocation failed!\n");
    rc = -ENOMEM;
    goto failed6;
}

rc = nv_kmem_cache_alloc_stack(&sp);

`

And i had tested this on nvidia 210 gpu, work fine.

graysky commented on 2020-03-19 08:50 (UTC) (edited on 2020-03-19 08:56 (UTC) by graysky)

I have no hardware myself for testing. Does the error in dmesg also cause breakage or is it just a harmless line in dmesg? Can you post a link or two from your searching? Can you verify there are no ill-effects of that patch?

vova7890 commented on 2020-03-19 01:01 (UTC)

I'm facing this message in dmesg: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t'

A little search and I had portback this patch to 340xx. Can you please add this? https://zvova7890.com.ua/s/ed9JJG8KyQKQQBx

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 54 55 56 .. 59 Next › Last »