Difference between revisions of "Talk:NVIDIA"

From ArchWiki
Jump to: navigation, search
(Accuracy of driver selection: fix link)
(NVoption Online: re)
Line 8: Line 8:
[I'm using gmplayer with gl and twinview]
[I'm using gmplayer with gl and twinview]
:A user found this useful to get TV-Out working with an old Geforce 2 MX: {{AUR|nvtv}}
== Reword ==
== Reword ==

Revision as of 13:34, 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?

NVoption Online

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/

A user found this useful to get TV-Out working with an old Geforce 2 MX: nvtvAUR


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. Biltong (talk)

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)


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)