Difference between revisions of "Talk:NVIDIA"

From ArchWiki
Jump to: navigation, search
m (Switching between nvidia and nouveau drivers: OK, I'll include my scripts in the article.)
m (kk)
Line 83: Line 83:
::I'll move it in a couple hours and I'll fix things like calling 'pacman' instead of '/usr/bin/pacman' :-)
::I'll move it in a couple hours and I'll fix things like calling 'pacman' instead of '/usr/bin/pacman' :-)
::[[User:Karol|Karol]] 10:49, 4 April 2011 (EDT)
::[[User:Karol|Karol]] 10:49, 4 April 2011 (EDT)
:::Good job! -- [[User:Kynikos|Kynikos]] 19:22, 4 April 2011 (EDT)

Revision as of 23:22, 4 April 2011


Nice documentation. Thanks to contributors. --Gen2ly 07:53, 17 October 2009 (EDT)


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/

Since most of the wiki is aimed at new users anyway: why differentiate between the Xorg client and server? manolo 19:23, 9 November 2009 (EST)

Just got to say thanks for you edits Manolo, you're doing a great job on the wiki. As for Xorg naming, their is no client only a server (Wikepedia). However, the nomenclature of it is a bit awkward. Xorg server got its' name from when the popular design philosophy was that computer hubs would essential be dum-terminals (i.e. not have an graphic card) and one machine would handle the graphic load. It's sort of an outdated (and awkward) term now but is still used and the proper and common wording.
--Gen2ly 01:34, 10 November 2009 (EST)
Thanks for the clarification/compliments. So if I understand correctly, "Xorg" is referring to "Xorg server"? manolo 02:05, 10 November 2009 (EST)

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)

Reboot after installing the driver

It's mentioned here: Rebooting is generally recommended after updating kernel and graphic drivers.

I created a Tip at the end of the Install section saying just that, because many people install the drivers, 'startx' and <sadface>.

/var/abs/extra/nvidia/ no such file or directory

When trying to follow this page's instructions regarding a custom kernel, after successfully installing abs I am unable to cp -r /var/abs/extra/nvidia/ because I get a no such file or directory error. In fact, there is nothing in /var/abs/ except "README" and a "local" directory, which also has no "extra" or "nvidia" dir. Are these instructions outdated? Brianwc 12:43, 7 January 2011 (EST)

Switching between nvidia and nouveau drivers


I use

# nvidia -> nouveau

sudo sed -i 's/#options nouveau modeset=1/options nouveau modeset=1/' /etc/modprobe.d/modprobe.conf
sudo sed -i 's/#MODULES="nouveau"/MODULES="nouveau"/' /etc/mkinitcpio.conf

sudo pacman -Rdds --noconfirm nvidia-173xx{,-utils}
sudo pacman -S --noconfirm nouveau-dri xf86-video-nouveau

sudo cp {10-monitor,20-nouveau}.conf /etc/X11/xorg.conf.d/

sudo mkinitcpio -p kernel26


# nouveau -> nvidia

sudo sed -i 's/options nouveau modeset=1/#options nouveau modeset=1/' /etc/modprobe.d/modprobe.conf
sudo sed -i 's/MODULES="nouveau"/#MODULES="nouveau"/' /etc/mkinitcpio.conf

sudo pacman -Rdds --noconfirm nouveau-dri xf86-video-nouveau libgl
sudo pacman -S --noconfirm nvidia-173xx{,-utils}

sudo rm /etc/X11/xorg.conf.d/{10-monitor,20-nouveau}.conf

sudo mkinitcpio -p kernel26

and reboot. I keep 10-monitor.conf and 20-nouveau.conf in the same directory as this script. Adjust accordingly if you use other version of nvidia drivers (I use nvidia-173xx).

Karol 12:33, 3 April 2011 (EDT)

If these script work well (and they should) why don't you move them into the Tips and Tricks section? Discussion pages are less likely to be read I guess... -- Kynikos 19:39, 3 April 2011 (EDT)
I've used it for a long long time and it never failed. I updated it to work with pacman 3.5 and tested it again - still does its job.
I'll move it in a couple hours and I'll fix things like calling 'pacman' instead of '/usr/bin/pacman' :-)
Karol 10:49, 4 April 2011 (EDT)
Good job! -- Kynikos 19:22, 4 April 2011 (EDT)