Package Base Details: nvidia-340xx

Git Clone URL: https://aur.archlinux.org/nvidia-340xx.git (read-only, click to copy)
Submitter: simonsmh
Maintainer: JerryXiao (graysky)
Last Packager: graysky
Votes: 44
Popularity: 2.85
First Submitted: 2019-06-07 10:29
Last Updated: 2020-12-31 11:00

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

leopseft commented on 2020-09-06 17:31

@holyArch Yes, just tried it, the module build successfully with no errors but the driver doesn't work.

holyArch commented on 2020-09-05 23:32

Have you tried

env IGNORE_CC_MISMATCH=1 dkms install -m nvidia -v 340.108 -k 5.8.6-arch1-1

leopseft commented on 2020-09-04 17:46

Today I updated with the latest toolchain first, then reboot (just in case), then installed the latest kernel (5.8.5 and tested with 5.8.6 too) and the headers and still nothing. Gave a try to the 5.8.3 too and still nothing. The only combination that works for me as well is linux 5.8.1.arch1-1 with linux-headers 5.8.1.arch1-1 and gcc 10.1.0-2 with gcc-libs 10.1.0-2 and lib32-gcc-libs 10.1.0-2 as mentioned before.

fvsc commented on 2020-08-22 19:10

@graysky also cat /proc/version gives the info for the installed kernel. Linux version 5.8.2-arch1-1 (linux@archlinux) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Thu, 20 Aug 2020 20:45:00 +0000

But I want to know the toolchain of a new kernel before I install it. Downgrading, insert [testing] in pacman.conf, upgrading and so on is a little too time consuming for me. I will see if I find some info and let you know.

graysky commented on 2020-08-22 15:23

@fvsc - It's rare that the kernel build with an outdated toolchain is offered.

I guess you can look in [testing] if you know they updated gcc and see what's there. You can grep dmesg for it on your current kernel and then just see what is in [testing]:

% dmesg| grep gcc
[  +0.000000] Linux version 5.4.60-1-lts (linux-lts@archlinux) (gcc version 10.2.0 (GCC)) #1 SMP Fri, 21 Aug 2020 16:53:54 +0000

Maybe there's an easier way.

fvsc commented on 2020-08-22 14:40

@graysky I followed your solution and it is OK now. Many thanks.

Do you know how I can check which toolchain was used to build the kernel before upgrading my system. Thanks in advance.

graysky commented on 2020-08-22 09:05

Again, the problem is that 5.8.2 was build with gcc 10.1.0. At that time, gcc 10.2.0 was in [staging] not [testing]. 5.8.2 went into [core] before gcc 10.2.0 went into [testing]. 5.8.3 was build with gcc 10.2.0 and they moved gcc 10.2.0 to [core] before 5.8.3 came out of [testing].

Solution: update your system so you get the new toolchain then pull 5.8.3 and (headers) from [testing] so dkms builds for you.

fvsc commented on 2020-08-22 07:52

I had the same problem. Version 5.8.3 of the kernel was not working for me. Downgraden the kernel and gcc solved the problem.

Combination that works: linux 5.8.1.arch1-1 linux-headers 5.8.1.arch1-1

gcc 10.1.0-2 gcc-libs 10.1.0-2 lib32-gcc-libs 10.1.0-2

wurbelgrumpff commented on 2020-08-21 23:34

@graysky: Thanks a lot for your fast response, it works with 5.8.3 from [testing]. Normally I ignore [testing], so I will see, what happens when I comment out testing-repo again and wait for coming of 5.8.3 in [core]. Wouldn't it not also be okay to downgrade gcc to former version while installing 5.8.2? Maybe it would be a better solution for people who don't like [testing]? We'll see.... At least a dkms-issue remains: ==> Unable to remove module nvidia/340.108 for kernel 5.8.2-arch1-1: Not found in dkms status output. Do you know something about it? Despite this, system is working.... oups(!): That was former kernel, maybe a dkms-issue....

@graysky and all others working on this nvidia-patches: I really want to say 'Thank you!' to you for spending so much time and energy on this project. It makes it possible to users like me to run old hardware a little longer time - thanks a lot!! best regards!

graysky commented on 2020-08-21 22:42

It's because your kernel was build with the earlier version of gcc and 5.8.3 is not yet in [core]. Grab it and the headers from [testing] and it should work.