Package Base Details: nvidia-340xx

Git Clone URL: https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy)
Submitter: simonsmh
Maintainer: JerryXiao
Last Packager: JerryXiao
Votes: 70
Popularity: 0.23
First Submitted: 2019-06-07 10:29 (UTC)
Last Updated: 2024-03-17 06:41 (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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 55 Next › Last »

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

osvcos commented on 2020-03-16 20:51 (UTC)

@holyArch As graysky wrote, this is probaly due to the gcc version mismatch. Try with: sudo env IGNORE_CC_MISMATCH=1 dkms install -m nvidia -v 340.108 -k 5.5.9-arch1-2

holyArch commented on 2020-03-16 20:40 (UTC) (edited on 2020-03-17 17:00 (UTC) by holyArch)

@graysky The mirrors I use are all listed under Successfully Syncing Mirrors, so that's not the issue.

Edit: Thank you, osvcos, the command words (after upgrading kernel).

« First ‹ Previous 1 .. 43 44 45 46 47 48 49 50 51 52 53 .. 55 Next › Last »