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.73
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 .. 41 42 43 44 45 46 47 48 49 50 51 .. 58 Next › Last »

fvsc commented on 2020-08-22 19:10 (UTC)

@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 (UTC)

@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 (UTC)

@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 (UTC) (edited on 2020-08-22 10:46 (UTC) by graysky)

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 (UTC) (edited on 2020-08-22 07:54 (UTC) by fvsc)

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 (UTC)

@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 (UTC)

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.

wurbelgrumpff commented on 2020-08-21 21:26 (UTC) (edited on 2020-08-21 21:30 (UTC) by wurbelgrumpff)

Hello, I'm sorry, but with updating on Kernel 5.8.2 I encounter some real problems: Together with the kernel also gcc and gcc-libs were updated from 10.1.0-2 to 10.2.0-1, I don't know if this is important....

Messages from pacman.log:

==> dkms install --no-depmod -m nvidia -v 340.108 -k 5.8.2-arch1-1 Error! Bad return status for module build on kernel: 5.8.2-arch1-1 (x86_64) Consult /var/lib/dkms/nvidia/340.108/build/make.log for more information. ==> Warning, `dkms install --no-depmod -m nvidia -v 340.108 -k 5.8.2-arch1-1´ returned 10 ==> depmod 5.8.2-arch1-1

[....]

I tried to reinstall nvidia but:

==> Unable to remove module nvidia/340.108 for kernel 5.8.2-arch1-1: Not found in dkms status output.

In make.log gcc-version-check failed. (I mentioned gcc was upgraded):

DKMS make.log for nvidia-340.108 for kernel 5.8.2-arch1-1 (x86_64)

Fr 21. Aug 21:54:01 CEST 2020

gcc-version-check failed:

The compiler used to compile the kernel (gcc 10.1) does not exactly match the current compiler (gcc 10.2). The Linux 2.6 kernel module loader rejects kernel modules built with a version of gcc that does not exactly match that of the compiler used to build the running kernel.

If you know what you are doing and want to override the gcc version check, you can do so by setting the IGNORE_CC_MISMATCH environment variable to "1".

In any other case, set the CC environment variable to the name of the compiler that was used to compile the kernel.

Failed CC version check. Bailing out!

make: *** [nvidia-modules-common.mk:201: build-sanity-checks] Fehler 1 [Error 1]

make: Verzeichnis „/var/lib/dkms/nvidia/340.108/build/uvm“ wird betreten [directory ... is entered]

cd ./..; make module SYSSRC=/lib/modules/5.8.2-arch1-1/build SYSOUT=/lib/modules/5.8.2-arch1-1/build KBUILD_EXTMOD=./..

make[1]: Verzeichnis „/var/lib/dkms/nvidia/340.108/build“ wird betreten [directory ... is entered]

NVIDIA: calling KBUILD...

make[2]: Verzeichnis „/usr/lib/modules/5.8.2-arch1-1/build“ wird betreten [directory ... is entered]

test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \

echo >&2; \

echo >&2 " ERROR: Kernel configuration is invalid."; \

echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\

echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \

echo >&2 ; \

/bin/false)

make -f ./scripts/Makefile.build obj=.. \

single-build= \

need-builtin=1 need-modorder=1

scripts/Makefile.build:44: ../Makefile: Datei oder Verzeichnis nicht gefunden [:file or directory not found]

make[3]: *** Keine Regel, um „../Makefile“ zu erstellen. Schluss. [no rule to build ../Makefile. Exit.]

make[2]: *** [Makefile:1756: ..] Fehler 2 [error 2]

make[2]: Verzeichnis „/usr/lib/modules/5.8.2-arch1-1/build“ wird verlassen [directory ... is exited]

NVIDIA: left KBUILD.

nvidia.ko failed to build!

make[1]: *** [Makefile:202: nvidia.ko] Fehler 1 [error 1]

make[1]: Verzeichnis „/var/lib/dkms/nvidia/340.108/build“ wird verlassen [directory ... is exited]

make: *** [Makefile:222: ../Module.symvers] Fehler 2 [error 2]

make: Verzeichnis „/var/lib/dkms/nvidia/340.108/build/uvm“ wird verlassen [directory ... is exited]

(Translation is appended within []); pls, ignore my english......

Well, I'm badly surprised, because all formerly updates worked without any problems. Patch 5.7 worked really well and also upgrading to 5.8.1 was without any errors. I use an over ten years old machine (core2duo) with Nvidia gt210 and running xfce4 on it.

Please, can anyone help with this? Best regards!

johnvranos commented on 2020-08-18 03:15 (UTC) (edited on 2020-08-18 03:15 (UTC) by johnvranos)

You can try installing flatpak or snapd.

They have the latest version of Spotify:

https://paste.pics/9UL4W

graysky commented on 2020-08-15 10:36 (UTC)

@fvsc - Thanks for testing. Now that 5.8.1 has moved to [core] I pushed this formally a few min ago.