NVoption Online Version - great tool to make tv-out easy and fast
- A user found this useful to get TV-Out working with an old Geforce 2 MX: Alad (talk) 13:56, 3 March 2016 (UTC) AUR --
'/dev/nvidia0' Input/Output error... suggested fixes
Can anyone verify that the BIOS related suggestions work and are not coincidentally set (either automatically when changing the IRQ or turning off ACPI) while troubleshooting? I have found little information that confirms any of the suggestions would work. The file permissions thing seems to be completely unfounded and never works (as noted in the article) that I could find. It would probably be a good idea if we cleaned out items that have not been verified to work. For my setup I was having this error and none of the items in the wiki nor the many file permission search results worked. -- click, them so hard 19:16, 4 March 2012 (EST)
- I've added an Accuracy template, please next time add it yourself so that discussions like this are more visible. -- Kynikos 05:40, 6 March 2012 (EST)
Run a test
There is confusing paragraph saying You can run a test to see if the Xorg server will function correctly without a configuration file.. IMHO, it should be clarified what kind of test the author has in mind, an exact command would be helpful. Currently, this suggestion is simply confusing, especially to less experienced users. --Mloskot (talk) 19:52, 26 November 2012 (UTC)
- It's strange. I agree. The link goes to the section for running X. After a beat, I realized you simply try to launch X. And in my case the screen was black. So the "test" failed. A better instruction might say to try launching launching X, and then provide the link which describes all the ways this is done--depending on your configuration. Xtian (talk) 22:05, 21 October 2017 (UTC)
Several of the commands which are suggested to be run with nvidia-xconfig (such as nvidia-xconfig --twinview) don't work with the current nvidia packages in the repository. I just went through setting mine up so I intend to clean up the ones that I can from my experience. Some don't seem to have a 1:1 replacement (there is a --dynamic-twinview argument now; is that the same as --twinview was?). Teh (talk) 13:10, 20 June 2013 (UTC)
While it shouldn't be necessary to use xconfig to get nvidia working on X, creating a 20-nvidia.conf file is an integral step to fix screen tearing for people that suffer from that issue. Perhaps this section should have this explained and include a link to the nvidia troubleshooting article which contains the section about fixing screen tearing? --TheChickenMan (talk) 21:54, 22 December 2016 (UTC)
- Troubleshooting sections link to the main documentation, not vice versa. Otherwise there would be no point in having separate troubleshooting sections. -- Lahwaacz (talk) 22:03, 22 December 2016 (UTC)
Accuracy of driver selection
A thread on the forums revealed that nvidia is more conservative in their suggestion than needed and checking their website tells you to use an older driver (nvidia-340xx) while the latest 'nvidia' one will do just fine. Gusar suggested the removal of the second point in the 'Installing' section. Do we want to get rid of this potentially useful, although somewhat confusing info? -- Karol (talk) 02:52, 15 November 2014 (UTC)
- Well, I've rewritten the second point to make it clearer, I hope I got it correctly. However steps 2 and 3 there should probably merged into one, because they deal with the same problem, i.e. finding the correct driver to install. Maybe we could use a table? (just brainstorming). -- Kynikos (talk) 03:47, 16 November 2014 (UTC)
I think it could be helpful for anyone that's still using X server to be guided on setting up compositing.
One way to update the Xorg.conf file to enable composition is to use the nvidia command line tool:
# nvidia-xconfig --composite
The other is to edit the file manually, as per the example below adding the Composite Option to the Extensions section of /etc/X11/xorg.conf:
Section "Extensions" Option "Composite" "Enable" EndSection
For those running KDE, to check if compositing is enabled they can run the following command, compositing information is at the end of the output:
$ qdbus org.kde.KWin /KWin supportInformation
Rebranded cards and driver versions
"GeForce 600 series cards and newer [NVEx and newer]" is generally the right description for cards supported by the current driver (410).
But as noted, it is not completely correct: some very low end OEM cards are rebrands of older (pre-600 series) cards, notably: GeForce GT 610M, GT 620M, GT 630M, GT 635M, GT 640M LE, GT 615, GT 620, GT 630, GT 705(A), GT 730, GeForce 800(A) and some others.
However, most mid and high and cards from the 600, 700, 800, 900, 1000 and 2000 series are supported just fine by the current 410 driver. This makes the explanation given after misleading in my opinion.
I think we should keep the description as it was but maybe add some more notices about that some low end rebrands are not included, or alternatively, completely remove the mention of GeForce series cards and just point people to the Nvidia site and let them figure out this mess themselves (we also don't list supported Quadro or Tesla cards).
Regarding , as you can see from this link  in the supported products tab, the 410 driver supports only the GeForce RTX 20 series, while all the previous cards work with the 390 driver, as this other link says . For example, my GeForce 970 card worked neither with the 340 nor with the 410, only with the 390, as stated in the Nvidia website. I think we should update according to what the Nvidia website says.
Goldgoat 12 ott 2018, 20.45 UTC
I think the 410 driver has only been officially released for the 2000 series, but it is definitely coming for the other supported series too. The 390 driver was branched a few months ago and put all pre-600 series cards in legacy support mode. None of the >600 series cards are listed as legacy.
For example take a look at this 410.57 beta release of that supports all current (>600 series) cards.
It looks like that is the same one that is currently distributed as thepackage. I actually also have a GTX 970 card which works fine with that driver.
You are right, I didn't know about the beta versions. But I don't understand why my card didn't work with the 410 driver, maybe I downloaded an older version.
Goldgoat 13 ott 2018, 13.01 (UTC)
So today they released the first real stable version, which lists the 600/700/800/900 series and more as supported. (by the way, Goldgoat: if you're having issues with it you should open a bug report!)
But back to what I meant originally: this edit seems to be about the fact that the list "The 390.xx driver supports the following set of GPUs:" contains some low end 600 series card that seem to require that legacy driver and are no longer supported by the latest one. I'm not sure what to do about that. Any opinions about the options mentioned in my first post (keep note about low-end cards or remove GeForce series entirely)?