NVIDIA/nvidia-drivers/ja

はnVidia製グラフィックスカード用のプロプライエタリなドライバーです. オープンソースの代替としてnouveauがあります.

Portage TreeにあるはnVidiaによって公開されていて、Linuxカーネルと共に動くようビルドされています. これらにはグラフィックスカードとのやりとりの大部分を行うバイナリ・ブロブが含まれています. ドライバーはカーネルモジュールとX11ドライバーの二つの部分で攻勢されています. この両方が一つのソフトウェアパッケージに含まれています. nVidiaが行ったパッケージのしかたにより、インストール前にいくつか決めなければならない事柄があります.

はnVidiaの最新のドライバーが含まれていて、「すべて」のカードがサポートされています. カードの製造時期によっては対応するドライバーのいくつかのバージョンが含まれています. このパッケージはeclassを使用し、システムに含まれるカードの種類を特定した上で正しいバージョンのドライバーをインストールします.

ハードウェアの互換性
は幅広いnVidiaのグラフィックスカードをサポートします. システムに含まれるカードに合わせられるよう、このパッケージには複数のバージョンがあります. どのバージョンのを使うべきかを確認するには、What's a legacy driver?を参照してください. 確認の際に便利なものとしてan interactive formがあります. システムに含まれるグラフィックスカードを入力すると、もっとも適したバージョンを教えてくれます. (なお、'Product Type'の入力欄にあるLegacyオプションにはご注意ください)

もしグラフィックスカードがレガシーカードと分かったならば、以下のような最近のをマスクしてください.

Gentooが71.86.xxバージョンを提供していないことを念頭に置いておいてください. もしこのドライバーを必要とするグラフィックスカードがシステム内にあるならば、nouveauドライバーを使うことが推奨されます.

Kernel
上記の通り、nVidiaのカーネルドライバーは現在のカーネルに合わせてインストールされ、実行されます. カーネルモジュールとしてビルドされるので、カーネルはモジュールのロードに対応していなければなりません. (下記参照)

The kernel module consists of a proprietary part (commonly known as the "binary blob") which drives the graphics chip(s), and an open source part (the "glue") which at runtime acts as intermediary between the proprietary part and the kernel. These all need to work nicely together as otherwise the user might be faced with data loss (through kernel panics, X servers crashing with unsaved data in X applications) and even hardware failure (overheating and other power management related issues should spring to mind).

Kernel compatibility
時々、新しいカーネルのリリースによってドライバー用の内部ABIが変わることがあります. これは、それらのABIを利用するすべてのドライバーをこの変更に合わせなければならないことを意味します. オープンソースのドライバー、特にカーネルとともに頒布されるものに関しては、ドライバーやカーネルの他の部分をつなぐ一連の機能呼び出しを見直すことが容易で、この様な変更はほとんど手間な加えることができます. しかし、プロプライエタリなドライバーに関しては同じようにはいきません. 内部ABIが変わるとき、プロプライエタリな部分によってどのように「のり」の部分が使われているか分からないため、ただ単に「のり」の部分を修正することは不可能です. うまく修正を重ねて順調に動いているようであっても、nvidia.koを新しい、サポートされていないカーネルで使うことにはデータの損失やハードウェアの不具合が起きるといったリスクが付随します.

新しい、互換性のないバージョンのカーネルがリリースされたとき、しばらくはサポートされる最新のカーネルを使用しつづけることが最善でしょう. Nvidiaが一般に公開してもいいと判断するプロプライエタリなドライバーを公開するのには通常数週間かかります. 気長に待つべきです. もし新しいカーネルが絶対に必要ならば、nvidia-driversのebuildでepatch_userコマンドを使うこともできます. これによってnvidia-driversに何らかの修正を加えて、最新のサポートされていないカーネルでも動くようにすることができます. nvidia-driversのメンテナも、Nvidia自体もこのような用法はサポートしないことを念頭に置いてください. ハードウェアの保証もおそらく無効になるでしょう. また、NvidiaのみがまともにデバッグできるのでGentooのメンテナも修正を加えることはできません. (Gentoo、Upstreamの双方の)カーネルのメンテナはプロプライエタリなドライバー、ひいてはプロプライエタリなソフトウェアに「汚染」されたシステムの不調に対してサポートを提供しません.

If was used to configure the kernel, then everything is all set. If not, double check the kernel configuration so that this support is enabled:

カーネル内のMemory Type Range Registerも有効にしてください.

If the system has an AGP graphics card, then optionally enable agpgart support to the kernel, either compiled in or as a module. If the in-kernel agpgart module is not used, then the drivers will use its own agpgart implementation, called NvAGP. On certain systems, this performs better than the in-kernel agpgart, and on others, it performs worse. Evaluate either choice on the system to get the best performance. When uncertain what to do, use the in-kernel agpgart:

A framebuffer alternative is uvesafb, which can be installed parallel to.

For (U)EFI systems, uvesafb will not work. Be warned that enabling efifb support in kernel causes intermittent problems with the initialization of the nvidia drivers. There is no known alternative framebuffer for (U)EFI systems.

The nvidia-drivers ebuild automatically discovers the kernel version based on the symlink. Please ensure that this symlink is pointing to the correct sources and that the kernel is correctly configured. Please refer to the "Configuring the Kernel" section of the Gentoo Handbook for details on configuring the kernel.

First, choose the right kernel source using. When using version 3.7.10 for instance, the kernel listing might look something like this:

In the above output, notice that the linux-3.7.10-gentoo kernel is marked with an asterisk to show that it is the symlinked kernel.

If the symlink is not pointing to the correct sources, update the link by selecting the number of the desired kernel sources, as in the example above.

Drivers
Now it's time to install the drivers. First follow the X Server Configuration Guide and set  in. During the installation of the X server, it will then install the right version of.

Once the installation has finished, run to load the kernel module into memory. If this is an upgrade, remove the previous module first.

To prevent from having to manually load the module on every bootup, have this done automatically each time the system is booted, so edit and add   to it.

Kernel module signing (optional)
If you are using secure boot kernel signing then you will need to sign the Nvidia kernel modules before they can be loaded.

You do this by using the kernel provided script as follows.

As of driver version 358.09 a new module has been made to handle monitor mode setting and for this driver version this module must also be signed.

Once you have signed these modules then the driver will load as expected on boot up. This module signing method can be used to sign other modules not only your nvidia-drivers. You would have to modify the path and corresponding module accordingly.

The X server
Once the appropriate drivers are installed, configure the X server to use the  driver instead of the default   driver.

Run so that the X server uses the nVidia GLX libraries:

Enabling global nvidia support
Some tools, such as and, use a local USE flag called   which enables XvMCNVIDIA support, useful when watching high resolution movies. Add in  in the USE variable in  or add it as USE flag to  and/or  in.

GeForce 8 series and later GPUs do come with VDPAU support which superseded XvMCNVIDIA support. See the VDPAU article for enabling VDPAU support.

There are also some applications that use the  USE flag, so it might be a good idea to add it to.

Then, run to rebuild the applications that benefit from the USE flag change.

Using the nVidia settings tool
nVidia also provides a settings tool. This tool allows the user to monitor and change graphical settings without restarting the X server and is available through Portage as. As mentioned earlier, it will be pulled in automatically when installing the drivers with the  USE flag set in  or in.

Enable OpenGL/OpenCL
To enable OpenGL and OpenCL though the device, run:

Make sure that the Xorg server is not running during these changes.

Testing the card
To test the nVidia card, fire up X and run, which is part of the package. It should say that direct rendering is activated:

To monitor the FPS, run.

Driver fails to initialize when MSI interrupts are enabled
The Linux NVIDIA driver uses Message Signaled Interrupts (MSI) by default. This provides compatibility and scalability benefits, mainly due to the avoidance of IRQ sharing. Some systems have been seen to have problems supporting MSI, while working fine with virtual wire interrupts. These problems manifest as an inability to start X with the NVIDIA driver, or CUDA initialization failures.

MSI interrupts can be disabled via the NVIDIA kernel module parameter. This can be set on the command line when loading the module, or more appropriately via the distribution's kernel module configuration files (such as those under ).

例えば:

Getting 2D acceleration to work on machines with 4GB memory or more
When nVidia 2D acceleration is giving problems, then it is likely that the system is unable to set up a write-combining range with MTRR. To verify, check the contents of :

Every line should contain  or. When a line shows up with  in it then it is necessary to change a BIOS setting to fix this.

Reboot and enter the BIOS, then find the MTRR settings (probably under "CPU Settings"). Change the setting from  to   and boot back into Linux. There is now no  entry anymore and 2D acceleration now works without any glitches.

"no such device" appears when trying to load the kernel module
This is usually caused by one of the following issues:


 * 1) The system does not have a nVidia card at all.  Check  output to confirm that the system has a nVidia graphics card installed and detected.
 * 2) The currently installed version of  does not support the installed graphics card model.  Check the README file in /usr/share/nvidia-drivers-*/ for a list of supported devices, or use the driver search at http://www.geforce.com/drivers.
 * 3) Another kernel driver has control of the hardware. Check  to see if another driver like "nouveau" is bound to the graphics card. If so, disable or blacklist this driver.

Xorg says it can't find any screens
When after booting the system, it ends up with a black screen or a console prompt instead of the GUI; then press ++ to bring up a virtual console. Next, run:

to see the output of Xorg. If one of the first errors is that Xorg can't find any screens, then follow the following steps to resolve the issue.

It should be enough to run the following command before rebooting:

But if that doesn't work, run and notice that the video card starts off like this:

Take the first bit,  and put it in the  file with the   option:

Direct rendering is not enabled
If direct rendering does not work, it may be because the kernel has Direct Rendering Manager enabled, which conflicts with the driver. See the direct rendering status by following instructions in the section Testing the card.

First, disable Direct Rendering Manager in the kernel :

Next, rebuild since the driver may have built against the kernel DRM symbols. It should fix the problem.

Video playback stuttering or slow
Lately there seems to be some breaking with playback of some types of video with the NVidia binary drivers, causing slow video playback or significant stuttering. This problem seems to be occurring within the Intel CPU Idle replacement instead of the common ACPI CPU idling method for certain CPU's.

Disable the Intel CPU idling method using  on the kernel command line boot method, which should cause the kernel to automatically fall back to the normal or older ACPI CPU idling method. Also, disabling the NVidia Powermizer feature, or setting Powermizer to maximum performance within has been said to help. Although the Intel CPU idling method recently was introduced as the default CPU idling method for i5 and i7 CPUs (versus using ACPI CPU idling) is the root cause here. This idling method significantly solves the problem, however some minimal stuttering or slow video is encountered if deinterlacing was enabled; this is when the video is likely already deinterlaced (ie. alias  with something similar to   as a work around.)

No vertical synchronization (no VSync, tearing) in OpenGL applications
Adding the following option to the screen section prevents tearing on GTX 660, 660 Ti, and probably some other GPUs (reference):

Documentation
The package also comes with comprehensive documentation. This is installed into and can be viewed with the following command:

カーネルモジュールのパラメーター
The  kernel module accepts a number of parameters (options) which can be used to tweak the behaviour of the driver. Most of these are mentioned in the documentation. To add or change the values of these parameters, edit the file. Remember to run after modifying this file, and bear in mind to reload the   module before the new settings take effect.

を編集:

Update module information:

Unload the  module...

...and load it once again:

X の高度な設定
The GLX layer also has a plethora of options which can be configured. These control the configuration of TV out, dual displays, monitor frequency detection, etc. Again, all of the available options are detailed in the documentation.

To use any of these options, list them in the relevant Device section of the X config file (usually ). For example, to disable the splash logo:

参考

 * nouveau & nvidia-drivers switching - Hybrid graphics mode using open-source drivers.
 * NVIDIA Optimus - Configure a system to use closed-source drivers for hybrid graphics (modesetting).