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.155502
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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 56 Next › Last »

MegaDeKay commented on 2021-05-08 15:03 (UTC)

Back in March on 5.11, people were having luck with GTK based greeters but Qt based ones weren't working (e.g. SDDM). So Googling around the error that @jayache80 reported, I found some references to people having weird problems with Qt that were fixed with setting QT_X11_NO_MITSHM=1 in someplace like /etc/environment. Maybe this explains why some people have luck and some don't? I'll admit that this is far-fetched, but it might be worth a shot given that it is low effort to try. The rabbit hole I went down are in the links below. Disabling the nvidia splash screen with Option "NoLogo" "1" in xorg.conf might not help, but it wouldn't hurt either.

https://forum.mxlinux.org/viewtopic.php?t=53653

https://forum.mxlinux.org/viewtopic.php?f=108&t=53603&start=10

https://ubuntuforums.org/showthread.php?t=2423870

auriculaire commented on 2021-05-08 13:46 (UTC)

I think that linux arch users who use this module have been running on linux-lts since the arrival of the latest 5.11.x and 5.12.x kernels with which for me this module has never been operational ..... I read the comments every day while waiting for the miracle solution. Have a good day and good luck everyone.

tioguda commented on 2021-05-08 11:55 (UTC)

This is the change I make to compile for Manjaro, I believe that there is no significant change that I have not reported here before.

graysky commented on 2021-05-08 10:56 (UTC)

I'm not sure what I can do with your reply. You're modifying the PKGBUILD I provide to build without dkms on a foreign distro and you're reporting that it works. You're not sharing the code you're using to do this so it's impossible to make a comparison back to help users of Arch build via dkms.

What if you uninstall your non-dkms tweaked package and try building with this unmodified. Does that build? If so do it give a functional module?

tioguda commented on 2021-05-08 10:53 (UTC) (edited on 2021-05-08 10:54 (UTC) by tioguda)

Yes, they abandoned it, but I am using this package as a base to build one for Manjaro.

This driver is starting/working with the Manjaro (Gnome) 5.12 kernel and the Zen kernel (compiled locally).

As I mentioned before, I use this package as a base, since small changes are needed to compile the non-dkms module in Manjaro.

Greetings.

graysky commented on 2021-05-08 10:28 (UTC)

I am unfamiliar with manjaro but I thought they dropped this driver a while ago. Are you using the 5.12 kernel there where you report a functional driver? Is it this package you're using to build the kernel module?

tioguda commented on 2021-05-08 01:17 (UTC)

@graysky could you tell me a test to make sure everything is fine with the 5.12 kernel?

In Manjaro Gnome the system starts and I don't have the problems reported by @jayache80. In Plasma I can only start via startx on tty2, I haven't tested it with Xfce.

Greetings.

graysky commented on 2021-05-07 12:39 (UTC)

OK, if this doesn't give a functional module for the 5.12 series of kernels, we need to either 1) identify someone else's work to fix it (ie a patch from another distro or person), or 2) we need someone with expertise to fix it for us. I am not that someone nor do I have any hardware for testing.

nahno commented on 2021-05-07 03:59 (UTC)

I can confirm 2). Tested yesterday. My machine (xfce4) stills runs on Linux 5.11.7 without any issues though.

graysky commented on 2021-05-06 18:33 (UTC)

So there are two independent issues:

1) The patch shared by @qileilu is for the 460 series of drivers and not applicable to this version. 2) The package is-as does not work under 5.12.

Can someone else confirm point #2 is valid? If so, we will need to identify the reason why and see if a known fix is out there.