Difference between revisions of "Talk:NVIDIA"

From ArchWiki
Jump to: navigation, search
((U)EFI support)
(Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz: unsigned + close old discussion)
 
(88 intermediate revisions by 22 users not shown)
Line 1: Line 1:
== (U)EFI support ==
+
== <s>XRandR support</s> ==
  
I was told in [https://bbs.archlinux.org/viewtopic.php?id=136807 this thread] that the proprietary nvidia drivers do not work with EFI (by what appeared to be a senior community member), and repeated attempts to install the drivers on a UEFI system have met with little success. As a result, I am placing the warning back. Apologies if this isn't in keeping with wiki etiquette!
+
As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups? {{Unsigned|15:00, 9 November 2012|TripleSpeeder}}
  
--[[User:Rsmb|Rsmb]] ([[User talk:Rsmb|talk]]) 02:59, 13 December 2012 (UTC)
+
== TV-Out ==
 
+
:I had success using the nvidia driver on a efi system by adding 'nomodeset' to the kernel parameters. This prevents kms from loading, which causes a blank screen and is probably the source of the problems most users are seeing. X afterwards works just fine. I was able to play Doom 3 with a high fps rate :)
+
[[User:Davvil|Davvil]] ([[User talk:Davvil|talk]]) 10:59, 17 December 2012 (UTC)
+
 
+
:I have also had no problems with the current proprietary drivers after I blacklisted the i915 module on an ASRock Z68 PRO3 GEN3 mobo and a Zotac 9600 GT 512MB video card.
+
[[User:Polychoron|Polychoron]] ([[User talk:Polychoron|talk]]) 03:44, 27 December 2012 (UTC)
+
 
+
== XRandR support ==
+
As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups?
+
 
+
== NVoption Online ==
+
  
 
NVoption Online Version - great tool to make tv-out easy and fast  
 
NVoption Online Version - great tool to make tv-out easy and fast  
  
 
[I'm using gmplayer with gl and twinview]
 
[I'm using gmplayer with gl and twinview]
[http://www.sorgonet.com/linux/nv-online/]http://www.sorgonet.com/linux/nv-online/
+
[http://www.sorgonet.com/linux/nv-online/]http://www.sorgonet.com/linux/nv-online/ {{Unsigned|01:23, 23 March 2006‎|Suw}}
 +
 
 +
:A user found this useful to get TV-Out working with an old Geforce 2 MX: {{AUR|nvtv}} -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:56, 3 March 2016 (UTC)
  
== Reword ==
+
== <s>Reword</s> ==
 
Maybe someone can put this in better words:
 
Maybe someone can put this in better words:
 
Logging out, or switching to a different terminal using ctrl+alt+F<2-9>  consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that  a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X.
 
Logging out, or switching to a different terminal using ctrl+alt+F<2-9>  consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that  a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X.
Line 32: Line 23:
 
Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. [[User:Thestinger|thestinger]] 20:13, 13 December 2010 (EST)
 
Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. [[User:Thestinger|thestinger]] 20:13, 13 December 2010 (EST)
  
== Nvidia 173xx ==
+
== '/dev/nvidia0' Input/Output error... suggested fixes ==
The nvidia-173xx package no longer exists (29 Oct 2011). 
+
  
Has it been replaced by nvidia-173xx-all?  If so, this package hasn't been updated since Feb 2011.
+
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. -- [[User:Clickthem|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. -- [[User:Kynikos|Kynikos]] 05:40, 6 March 2012 (EST)
  
Will it need to be updated to be able to use the latest xorg 1.11? 
+
== <s>Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz</s> ==
  
In the meantime, please include instructions for which xorg related packages pacman should ignore.
+
Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. {{Unsigned|12:16, 8 November 2012‎|Biltong}}
:[http://mailman.archlinux.org/pipermail/arch-dev-public/2011-October/021764.html] -- [[User:Karol|Karol]] 21:14, 28 October 2011 (EDT)
+
::I commented out the info about older drivers, since they're not compatible with Xorg 1.11. Maybe if someone create the appropriate packages for Xorg 1.10 in AUR, then we could add back some info, but until it's misleading I think. --[[User:City-busz|City-busz]] 23:32, 3 November 2011 (EDT)
+
:::nvidia-96xx and nvidia-71xx are in the AUR, you can't use pacman to install them. -- [[User:Karol|Karol]] 00:03, 4 November 2011 (EDT)
+
::::You can't install these packages from AUR, because they requires Xorg 1.10/1.7, which is not available in official repos, nor in AUR. Once NVidia make them compatible with Xorg 1.11, then someone should add them back to the official repos. Another option is to someone create xorg-server-1.10, xf86-input-evdev-1.10 etc. packages to support these drivers. --[[User:City-busz|City-busz]] 01:31, 4 November 2011 (EDT)
+
:::::You can use [[Downgrading_Packages#ARM|ARM]] or some other mirror that holds old packages and still use nvidia-173xx and older drivers. My question is, why did you put {{ic|# pacman -S nvidia-96xx nvidia-96xx-utils}} instead of "install {{AUR|nvidia-96xx-all}} and {{AUR|nvidia-96xx-utils}} from the [[AUR]]."??
+
:::::The latter still works with out of date packages while the former does not, because I'm not aware of any repo that has nvidia-96xx. -- [[User:Karol|Karol]] 09:06, 4 November 2011 (EDT)
+
::::::It's possible, but it requires further explanation (maybe in a new section). Simply install nvidia-* packages from AUR is not work currently. --[[User:City-busz|City-busz]] 10:20, 4 November 2011 (EDT)
+
:::::::And installing them with pacman does work? I still don't get this change. -- [[User:Karol|Karol]] 11:16, 4 November 2011 (EDT)
+
  
The following section was commented in the article. I am moving it here instead:
+
== Run a test ==
  
These drivers are not compatible with the latest Xorg release in the official repo.
+
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. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 19:52, 26 November 2012 (UTC)
  
:Whereas users with older cards should install (GeForce 5 FX series cards [NV30-NV38]):
+
== nvidia-xconfig ==
:{{bc|# pacman -S nvidia-173xx nvidia-173xx-utils}}
+
  
:or (GeForce2 MX, GeForce3 and GeForce4 series cards [NV11 and NV17-NV28]):
+
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?). [[User:Techprophet|Teh]] ([[User talk:Techprophet|talk]]) 13:10, 20 June 2013 (UTC)
:{{bc|# pacman -S nvidia-96xx nvidia-96xx-utils}}
+
  
:or (Riva TNT, TNT2, GeForce and GeForce2 series cards [NV03-NV10 and NV15-NV16]):
+
== Automatic re-compilation of the NVIDIA module with every update of any kernel ==
:{{bc|# pacman -S nvidia-71xx nvidia-71xx-utils}}
+
  
-- [[User:Pointone|pointone]] 10:31, 4 April 2012 (EDT)
+
Is this section also (for comfort) needed when installing nvidia driver if one is using the stock kernel? Or is it only needed when installing the driver for a custom kernel? The chapter layout of the Installation chapter is maybe misleading me. --[[User:Strubbl|Strubbl]] ([[User talk:Strubbl|talk]]) 21:14, 5 May 2014 (UTC)
  
== custom kernel ==
+
== Accuracy of driver selection ==
  
The package changed for kernel 3.0 and the instructions no longer work. Please fix this. [[User:Z.T.|Z.T.]] 09:14, 23 November 2011 (EST)
+
[https://bbs.archlinux.org/viewtopic.php?id=189859 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. [https://bbs.archlinux.org/viewtopic.php?pid=1475567#p1475567 Gusar suggested] the removal of the second point in [https://wiki.archlinux.org/index.php/NVIDIA#Installation the 'Installing' section]. Do we want to get rid of this potentially useful, although somewhat confusing info? -- [[User:Karol|Karol]] ([[User talk:Karol|talk]]) 02:52, 15 November 2014 (UTC)
  
== '/dev/nvidia0' Input/Output error... suggested fixes ==
+
:Well, I've [https://wiki.archlinux.org/index.php?title=NVIDIA&diff=344863&oldid=344745 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). -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:47, 16 November 2014 (UTC)
  
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. -- [[User:Clickthem|click, them so hard]] 19:16, 4 March 2012 (EST)
+
== <s>Driver Persistence</s> ==
:I've added an Accuracy template, please next time add it yourself so that discussions like this are more visible. -- [[User:Kynikos|Kynikos]] 05:40, 6 March 2012 (EST)
+
  
== Rewrite ==
+
Nvidia started using a new method for driver persistence since version 3.19. Basically it's now a daemon that one can start with systemd. Assuming no objections, I'll add a blurb about it at the end of the config section. One can read all the gory details at http://docs.nvidia.com/deploy/driver-persistence/index.html
I think the "Installing" section is a little ambiguous and could use a bit of rewording. Because the steps are numbered, and little indication is given otherwise, it is implied that you need both the packages named like nvidia-173xx, ''and'' the regular nvidia packages. I don't actually have my nvidia drivers working properly, so maybe I'm misinterpreting this, but if I'm right in assuming that you need ''either'' the specifically named drivers like nvidia-173xx ''or'' the plain ol' nvidia drivers, step 2 needs to be reworded. I would suggest displaying two separate [code] blocks, one with # pacman -S nvidia-173xx nvidia-173xx-utils, and the one that's there now. Then make it explicitly clear that you need to do one or the other, not both. --[[User:Sotanaht|Sotanaht]] 18:45, 17 May 2012 (EDT)
+
  
Oh, I forgot that the nvidia-173xx drivers were not in the official repos.  Scratch the part about including the command for installing that.  I still think it's important to make clear that people using the nvidia-173xx drivers ''do not need'' the regular nvidia drivers.  Also make it clear that people using the regular nvidia drivers do not need any nvidia-XXXxx drivers.  --[[User:Sotanaht|Sotanaht]] 18:49, 17 May 2012 (EDT)
+
{{unsigned|05:30, 22 May 2015‎|Zeroedout}}
  
:Well, I've never had to use the old Nvidia drivers, but the note says that the old modules don't support Xorg 1.11 (Arch provides 1.12 now). Unless the situation has changed, those drivers are useless unless you also write instructions on how to safely downgrade Xorg. Please correct me if I'm wrong. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:27, 19 May 2012 (UTC)
+
[[User:Zeroedout|Zeroedout]] ([[User talk:Zeroedout|talk]]) 15:56, 2 June 2015 (UTC)
  
== Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz ==
+
:This was added to the article, closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:52, 3 March 2016 (UTC)
Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. [[User:Biltong|Biltong]] ([[User talk:Biltong|talk]])
+
  
== Run a test ==
+
== <s>Order of install/deinstall for changing drivers</s> ==
  
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. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 19:52, 26 November 2012 (UTC)
+
I think the intent of the author is to provide a way to switch from various proprietary nvidia builds, e.g. nvidia to nvidia-352 drivers, without breaking dependencies / uninstalling a lot of stuff. although this may be somtimes useful (to test different "branches" of the nvidia drivers, at the moment 361.xx and 352.xx), the process as described does not work or is out of date. It works by using pacman -Rdd <all installed nvidia packages> and then installing <new nvidia packages> with pacman -S. Or do we remove this paragraph entirely? [[User:Zeb|zeb]] ([[User talk:Zeb|talk]]) 13:29, 16 February 2016 (UTC)
 +
 
 +
:That section does seem useless. I would argue the same for [[NVIDIA#Switching between NVIDIA and nouveau drivers]]. If switching drivers is as simple as "uninstall all existing drivers, install new drivers", then it doesn't deserve its own section and we can add that sentence somewhere else on the page. [[User:Silverhammermba|Silverhammermba]] ([[User talk:Silverhammermba|talk]]) 15:50, 16 February 2016 (UTC)
 +
 
 +
::Removed with [https://wiki.archlinux.org/index.php?title=NVIDIA/Tips_and_tricks&diff=423827&oldid=423817], closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:50, 3 March 2016 (UTC)

Latest revision as of 14:01, 3 March 2016

XRandR support

As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups? —This unsigned comment is by TripleSpeeder (talk) 15:00, 9 November 2012. Please sign your posts with ~~~~!

TV-Out

NVoption Online Version - great tool to make tv-out easy and fast

[I'm using gmplayer with gl and twinview] [1]http://www.sorgonet.com/linux/nv-online/ —This unsigned comment is by Suw (talk) 01:23, 23 March 2006‎. Please sign your posts with ~~~~!

A user found this useful to get TV-Out working with an old Geforce 2 MX: nvtvAUR -- Alad (talk) 13:56, 3 March 2016 (UTC)

Reword

Maybe someone can put this in better words: Logging out, or switching to a different terminal using ctrl+alt+F<2-9> consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X. rwd

Was it with this driver or nouveau? The proprietary drivers don't have KMS. thestinger 17:42, 13 December 2010 (EST)

This was with the proprietary driver. I originally had put vga=.. because it made gave the bootup screen a higher resolution, and because the beginners guide mentions it (https://wiki.archlinux.org/index.php/Beginners%27_Guide#GRUB). Apart from leaving out the vga option, I discovered that setting it to the native resolution as explained on https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution fixes the black screens as well. Maybe a warning for using vga= option with with proprietary drivers would be useful.rwd

Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. thestinger 20:13, 13 December 2010 (EST)

'/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)

Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz

Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. —This unsigned comment is by Biltong (talk) 12:16, 8 November 2012‎. Please sign your posts with ~~~~!

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)

nvidia-xconfig

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)

Automatic re-compilation of the NVIDIA module with every update of any kernel

Is this section also (for comfort) needed when installing nvidia driver if one is using the stock kernel? Or is it only needed when installing the driver for a custom kernel? The chapter layout of the Installation chapter is maybe misleading me. --Strubbl (talk) 21:14, 5 May 2014 (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)

Driver Persistence

Nvidia started using a new method for driver persistence since version 3.19. Basically it's now a daemon that one can start with systemd. Assuming no objections, I'll add a blurb about it at the end of the config section. One can read all the gory details at http://docs.nvidia.com/deploy/driver-persistence/index.html

—This unsigned comment is by Zeroedout (talk) 05:30, 22 May 2015‎. Please sign your posts with ~~~~!

Zeroedout (talk) 15:56, 2 June 2015 (UTC)

This was added to the article, closing. -- Alad (talk) 12:52, 3 March 2016 (UTC)

Order of install/deinstall for changing drivers

I think the intent of the author is to provide a way to switch from various proprietary nvidia builds, e.g. nvidia to nvidia-352 drivers, without breaking dependencies / uninstalling a lot of stuff. although this may be somtimes useful (to test different "branches" of the nvidia drivers, at the moment 361.xx and 352.xx), the process as described does not work or is out of date. It works by using pacman -Rdd <all installed nvidia packages> and then installing <new nvidia packages> with pacman -S. Or do we remove this paragraph entirely? zeb (talk) 13:29, 16 February 2016 (UTC)

That section does seem useless. I would argue the same for NVIDIA#Switching between NVIDIA and nouveau drivers. If switching drivers is as simple as "uninstall all existing drivers, install new drivers", then it doesn't deserve its own section and we can add that sentence somewhere else on the page. Silverhammermba (talk) 15:50, 16 February 2016 (UTC)
Removed with [2], closing. -- Alad (talk) 12:50, 3 March 2016 (UTC)