Driver fails using nvidia for OpenGL interface but works using Mesa OpenGL interface
GentooThis forum is for the discussion of Gentoo Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Driver fails using nvidia for OpenGL interface but works using Mesa OpenGL interface
Hello forum,
I am running gentoo with the 2.6.30-r8 kernel and I get a perfect screen with the proper resolutions and everything works great as long as I use xorg-x11 (mesa) for the OpenGL interface which seems to be the default setting. But if I use nvidia for the OpenGL interface using the "eselect opengl set nvidia" command, I boot up to a black screen and I get the message "could not open the device file /dev/nvidia0 (input/output error)". I have to switch it back to using the xorg-x11 interface to get it back to working again.
Below is my xorg.conf and I am using nvidia-driver-185.18.36-r1 and have tried using an earlier driver also.
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "dri2" (module does not exist, 0)
(EE) Failed to load module "dri" (module does not exist, 0)
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
(EE) NVIDIA(0): Please check your system's kernel log for additional error
(EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
(EE) NVIDIA(0): README for additional information.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
Below is an excerpt from the Xorg.0.log file:
Code:
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "RenderAccel" "true"
(**) NVIDIA(0): Option "TwinView" "0"
(**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +0+0"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "true"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
(EE) NVIDIA(0): Please check your system's kernel log for additional error
(EE) NVIDIA(0): messages and refer to Chapter 8: Common Problems in the
(EE) NVIDIA(0): README for additional information.
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(**) NVIDIA(1): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Option "ConnectedMonitor" "TV"
(**) NVIDIA(1): Option "TVStandard" "HD1080i"
(**) NVIDIA(1): Option "TVOutFormat" "COMPONENT"
(**) NVIDIA(1): Option "TwinView" "0"
(**) NVIDIA(1): Option "MetaModes" "TV: 1920x1080 +0+0"
(**) NVIDIA(1): Enabling RENDER acceleration
(**) NVIDIA(1): Forcing COMPONENT output
(**) NVIDIA(1): TV Standard string: "HD1080i"
(II) NVIDIA(1): NVIDIA GPU GeForce 7600 GT (G73) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(1): Memory: 262144 kBytes
(--) NVIDIA(1): VideoBIOS: 05.73.22.25.88
(II) NVIDIA(1): Detected AGP rate: 8X
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce 7600 GT at PCI:1:0:0:
(--) NVIDIA(1): LG L246WP (CRT-1)
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0)
(--) NVIDIA(1): LG L246WP (CRT-1): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(1): TV encoder: NVIDIA
(II) NVIDIA(1): Display Device found referenced in MetaMode: TV-0
(II) NVIDIA(1): Assigned Display Device: TV-0
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1): "TV:1920x1080+0+0"
(II) NVIDIA(1): Virtual screen size determined to be 1920 x 1080
(==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) NVIDIA(0): Initialized AGP GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "TV:1920x1080+0+0"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
The reason I would like to use nvidia for the OpenGL interface is in hopes of getting my KDE 4.3.3 desktop effects to working using OpenGL instead of X-render.
How did you install the nvidia driver? Their install script does ask whether to install/replace opengl libraries. I think I would check your nvidia installation, and check whether the nvidia kernel module is being loaded.
Code:
ls /dev/nv
nvidia0 nvidiactl nvram
Does your /dev/ directory contain the nvidia0 and nvidiactl devices?
Yes, the kernel modules are being loaded. I put "nvidia" in the "modules.autoload.d" directory under my kernel version and during the POST I can see where the nvidia module loads up.
Later on I did add this (below) to my xorg.conf and it did enable direct rendering but my opengl screensavers were jerky and too slow and I still could not use the nvidia implimemtation of opengl. I can only use the mesa (xorg-x11) implimentation of opengl.
but the above entries did not enable me to use the nvidia libraries. I still have to use the Mesa libaries.
As for the next question:
Code:
ls /dev/nv
nvidia0 nvidiactl nvram
I do not have a nv directory in the /dev directory but I do have nvidia0 and nvidiactl in the dev directory whenever I am using the Mesa libraries. I have no way of knowing if I have these items if I am using the nvidia libraries because I boot up to a black screen.
The problem is whenever I use the nvidia libraries, I boot up to a black screen and I am unable to read the output of dmesg. I can use a rescue disk and read all of the other log files but dmesg shows up empty from a rescue disk. As long as I am using the rescue disk, nvidia0 would not show up anyway so I have no way of knowing if I have a nvidia0 or a nvidiactl in the /dev directory whenever I attempt to use the nvidia libraries.
I am using the nvidia-drivers from portage (185.18.36-r1).
Thank you for your input. If you have any more suggestions, please post.
I uninstalled the Portage supplied nvidia driver and installed the nvidia driver from Nvidia's web site and now I have 3D acceleration. The Portage supplied driver failed to give me 3D acceleration. The Portage supplied driver was 185.18.36-r1 and the driver from Nvidia's web site was 185.18.36.
All of the error messages have gone away from my log files concerning glx with this new driver.
After I installed the Nvidia driver from Nvidia's web site, there is no way to use Nvidia's OpenGL's implementation. Running the command "eselect opengl list" only shows xorg-x11 as OpenGL's implemtation. Only the Portage supplied Nvidia driver offered me a choice between xorg-x11 and nvidia to use as OpenGL's implementation.
Just for curiosities sake, I would still like to try using the nvidia's implemptation of OpenGL instead of using xorg-x11 but now that it is not offered as a choice with this new driver, I don't know how.
I uninstalled the Portage supplied nvidia driver and installed the nvidia driver from Nvidia's web site and now I have 3D acceleration. The Portage supplied driver failed to give me 3D acceleration. The Portage supplied driver was 185.18.36-r1 and the driver from Nvidia's web site was 185.18.36.
All of the error messages have gone away from my log files concerning glx with this new driver.
After I installed the Nvidia driver from Nvidia's web site, there is no way to use Nvidia's OpenGL's implementation. Running the command "eselect opengl list" only shows xorg-x11 as OpenGL's implemtation. Only the Portage supplied Nvidia driver offered me a choice between xorg-x11 and nvidia to use as OpenGL's implementation.
So I guess my original question in this post is now void with the new driver. I do not have a way to use the nvidia libraries using the eselect command anymore because it is not offered as a choice using the driver from Nvidia's web site.
Regards,
Roy
if i remember correctly, nvidia installer asks user to override the system opengl libraries. did you do such a thing ?
I installed the Portage driver using "emerge =x11-drivers/nvidia-drivers-185.18.36-r1" and I installed the driver from Nvidia's web site by running "sh NVIDIA-Linux-x86-185.18.36-pkg1.run".
Perhaps I should have used the expert mode?
Below are the options for installing the Nvidia driver from their web site:
Code:
This program will install the NVIDIA Accelerated Graphics Driver for
Linux-x86 185.18.36 by unpacking the embedded tarball and executing
the ./nvidia-installer installation utility.
--info
Print embedded info (title, default target directory) and exit.
--lsm
Print embedded lsm entry (or no LSM) and exit.
--pkg-history
Print the package history of this file and exit.
--list
Print the list of files in the archive and exit.
--check
Check integrity of the archive and exit.
-x, --extract-only
Extract the contents of /media/disk/NVIDIA-Linux-x86-185.18.36-pkg1.run, but do not
run 'nvidia-installer'.
--add-this-kernel
Build a precompiled kernel interface for the currently running
kernel and repackage the .run file to include this newly built
precompiled kernel interface. The new .run file will be placed
in the current directory and the string "-custom" appended
to its name, unless already present, to distinguish it from the
original .run file.
--apply-patch [Patch]
Apply the patch 'Patch' to the kernel interface files included
in the .run file, remove any precompiled kernel interfaces
and then repackage the .run file. The new .run file will be
placed in the current directory and the string "-custom"
appended to its name, unless already present, to distinguish it
from the original .run file.
--keep
Do not delete target directory when done.
--target [NewDirectory]
Extract contents in 'NewDirectory'
The following arguments will be passed on to the ./nvidia-installer
utility:
COMMON OPTIONS:
-a, --accept-license
Bypass the display and prompting for acceptance of the
NVIDIA Software License Agreement. By passing this option
to nvidia-installer, you indicate that you have read and
accept the License Agreement contained in the file
'LICENSE' (in the top level directory of the driver
package).
--update
Connect to the NVIDIA FTP server '
ftp://download.nvidia.com ' and determine the latest
available driver version. If there is a more recent driver
available, automatically download and install it. Any
other options given on the commandline will be passed on to
the downloaded driver package when installing it.
-v, --version
Print the nvidia-installer version and exit.
-h, --help
Print usage information for the common commandline options
and exit.
-A, --advanced-options
Print usage information for the common commandline options
as well as the advanced options, and then exit.
ADVANCED OPTIONS:
-a, --accept-license
Bypass the display and prompting for acceptance of the
NVIDIA Software License Agreement. By passing this option
to nvidia-installer, you indicate that you have read and
accept the License Agreement contained in the file
'LICENSE' (in the top level directory of the driver
package).
--update
Connect to the NVIDIA FTP server '
ftp://download.nvidia.com ' and determine the latest
available driver version. If there is a more recent driver
available, automatically download and install it. Any
other options given on the commandline will be passed on to
the downloaded driver package when installing it.
-v, --version
Print the nvidia-installer version and exit.
-h, --help
Print usage information for the common commandline options
and exit.
-A, --advanced-options
Print usage information for the common commandline options
as well as the advanced options, and then exit.
-i, --driver-info
Print information about the currently installed NVIDIA
driver version.
--uninstall
Uninstall the currently installed NVIDIA driver.
--sanity
Perform basic sanity tests on an existing NVIDIA driver
installation.
-e, --expert
Enable 'expert' installation mode; more detailed questions
will be asked, and more verbose output will be printed;
intended for expert users. The questions may be suppressed
with the '--no-questions' commandline option.
-q, --no-questions
Do not ask any questions; the default (normally 'yes') is
assumed for all yes/no questions, and the default string is
assumed in any situation where the user is prompted for
string input. The one question that is not bypassed by
this option is license acceptance; the license may be
accepted with the commandline option '--accept-license'.
-s, --silent
Run silently; no questions are asked and no output is
printed, except for error messages to stderr. This option
implies '--ui=none --no-questions --accept-license'.
--x-prefix=X-PREFIX
The prefix under which the X components of the NVIDIA
driver will be installed; the default is '/usr/X11R6'
unless nvidia-installer detects that X.Org >= 7.0 is
installed, in which case the default is '/usr'. Only under
rare circumstances should this option be used.
--xfree86-prefix=XFREE86-PREFIX
This is a deprecated synonym for --x-prefix.
--x-module-path=X-MODULE-PATH
The path under which the NVIDIA X server modules will be
installed. If this option is not specified,
nvidia-installer uses the following search order and
selects the first valid directory it finds: 1) `X
-showDefaultModulePath`, 2) `pkg-config
--variable=moduledir xorg-server`, or 3) the X library path
(see the '--x-library-path' option) plus either 'modules'
(for X servers older than X.Org 7.0) or 'xorg/modules' (for
X.Org 7.0 or later).
--x-library-path=X-LIBRARY-PATH
The path under which the NVIDIA X libraries will be
installed. If this option is not specified,
nvidia-installer uses the following search order and
selects the first valid directory it finds: 1) `X
-showDefaultLibPath`, 2) `pkg-config --variable=libdir
xorg-server`, or 3) the X prefix (see the '--x-prefix'
option) plus 'lib' on 32bit systems, and either 'lib64' or
'lib' on 64bit systems, depending on the installed Linux
distribution.
--opengl-prefix=OPENGL-PREFIX
The prefix under which the OpenGL components of the NVIDIA
driver will be installed; the default is: '/usr'. Only
under rare circumstances should this option be used. The
Linux OpenGL ABI
(http://oss.sgi.com/projects/ogl-sample/ABI/) mandates this
default value.
--opengl-libdir=OPENGL-LIBDIR
The path relative to the OpenGL library installation prefix
under which the NVIDIA OpenGL components will be installed.
The default is 'lib' on 32bit systems, and 'lib64' or 'lib'
on 64bit systems, depending on the installed Linux
distribution. Only under very rare circumstances should
this option be used.
--installer-prefix=INSTALLER-PREFIX
The prefix under which the installer binary will be
installed; the default is: '/usr'. Note: please use the
'--utility-prefix' option instead.
--utility-prefix=UTILITY-PREFIX
The prefix under which the NVIDIA utilities
(nvidia-installer, nvidia-settings, nvidia-xconfig,
nvidia-bug-report.sh) and the NVIDIA utility libraries will
be installed; the default is: '/usr'.
--utility-libdir=UTILITY-LIBDIR
The path relative to the utility installation prefix under
which the NVIDIA utility libraries will be installed. The
default is 'lib' on 32bit systems, and 'lib64' or 'lib' on
64bit systems, depending on the installed Linux
distribution.
--documentation-prefix=DOCUMENTATION-PREFIX
The prefix under which the documentation files for the
NVIDIA driver will be installed. The default is: '/usr'.
--kernel-include-path=KERNEL-INCLUDE-PATH
The directory containing the kernel include files that
should be used when compiling the NVIDIA kernel module.
This option is deprecated; please use
'--kernel-source-path' instead.
--kernel-source-path=KERNEL-SOURCE-PATH
The directory containing the kernel source files that
should be used when compiling the NVIDIA kernel module.
When not specified, the installer will use
'/lib/modules/`uname -r`/build', if that directory exists.
Otherwise, it will use '/usr/src/linux'.
--kernel-output-path=KERNEL-OUTPUT-PATH
The directory containing any KBUILD output files if either
one of the 'KBUILD_OUTPUT' or 'O' parameters were passed to
KBUILD when building the kernel image/modules. When not
specified, the installer will assume that no separate
output directory was used.
--kernel-install-path=KERNEL-INSTALL-PATH
The directory in which the NVIDIA kernel module should be
installed. The default value is either
'/lib/modules/`uname -r`/kernel/drivers/video' (if
'/lib/modules/`uname -r`/kernel' exists) or
'/lib/modules/`uname -r`/video'.
--proc-mount-point=PROC-MOUNT-POINT
The mount point for the proc file system; if not specified,
then this value defaults to '/proc' (which is normally
correct). The mount point of the proc filesystem is needed
because the contents of '<proc filesystem>/version' is used
when identifying if a precompiled kernel interface is
available for the currently running kernel. This option
should only be needed in very rare circumstances.
--log-file-name=LOG-FILE-NAME
File name of the installation log file (the default is:
'/var/log/nvidia-installer.log').
--tmpdir=TMPDIR
Use the specified directory as a temporary directory when
downloading files from the NVIDIA ftp site; if not given,
then the following list will be searched, and the first one
that exists will be used: /tmp, /tmp, ., /home/roy.
-m, --ftp-mirror=FTP-MIRROR
Use the specified FTP mirror rather than the default '
ftp://download.nvidia.com ' when downloading driver
updates.
-l, --latest
Connect to the NVIDIA FTP server '
ftp://download.nvidia.com ' (or use the ftp mirror
specified with the '--ftp-mirror' option) and query the
most recent Linux-x86 driver version number.
-f, --force-update
Forces an update to proceed, even if the installer thinks
the latest driver is already installed; this option implies
'--update'.
--ui=UI
Specify what user interface to use, if available. Valid
values for UI are 'ncurses' (the default) or 'none'. If the
ncurses interface fails to initialize, or 'none' is
specified, then a simple printf/scanf interface will be
used.
-c, --no-ncurses-color
Disable use of color in the ncurses user interface.
--no-opengl-headers
Normally, installation will install NVIDIA's OpenGL header
files. This option disables installation of the NVIDIA
OpenGL header files.
--force-tls=FORCE-TLS
NVIDIA's OpenGL libraries are compiled with one of two
different thread local storage (TLS) mechanisms: 'classic
tls' which is used on systems with glibc 2.2 or older, and
'new tls' which is used on systems with tls-enabled glibc
2.3 or newer. nvidia-installer will select the OpenGL
libraries appropriate for your system; however, you may use
this option to force the installer to install one library
type or another. Valid values for FORCE-TLS are 'new' and
'classic'.
-k, --kernel-name=KERNEL-NAME
Build and install the NVIDIA kernel module for the
non-running kernel specified by KERNEL-NAME (KERNEL-NAME
should be the output of `uname -r` when the target kernel
is actually running). This option implies
'--no-precompiled-interface'. If the options
'--kernel-install-path' and '--kernel-source-path' are not
given, then they will be inferred from KERNEL-NAME; eg:
'/lib/modules/KERNEL-NAME/kernel/drivers/video/' and
'/lib/modules/KERNEL-NAME/build/', respectively.
-n, --no-precompiled-interface
Disable use of precompiled kernel interfaces.
--no-runlevel-check
Normally, the installer checks the current runlevel and
warns users if they are in runlevel 1: in runlevel 1, some
services that are normally active are disabled (such as
devfs), making it difficult for the installer to properly
setup the kernel module configuration files. This option
disables the runlevel check.
--no-abi-note
The NVIDIA OpenGL libraries contain an OS ABI note tag,
which identifies the minimum kernel version needed to use
the library. This option causes the installer to remove
this note from the OpenGL libraries during installation.
--no-rpms
Normally, the installer will check for several rpms that
conflict with the driver (specifically: NVIDIA_GLX and
NVIDIA_kernel), and remove them if present. This option
disables this check.
-b, --no-backup
During driver installation, conflicting files are backed
up, so that they can be restored when the driver is
uninstalled. This option causes the installer to simply
delete conflicting files, rather than back them up.
-N, --no-network
This option instructs the installer to not attempt to
connect to the NVIDIA ftp site (for updated precompiled
kernel interfaces, for example).
--no-recursion
Normally, nvidia-installer will recursively search for
potentially conflicting libraries under the default OpenGL
and X server installation locations. With this option set,
the installer will only search in the top-level
directories.
-K, --kernel-module-only
Install a kernel module only, and do not uninstall the
existing driver. This is intended to be used to install
kernel modules for additional kernels (in cases where you
might boot between several different kernels). To use this
option, you must already have a driver installed, and the
version of the installed driver must match the version of
this kernel module.
--no-kernel-module
Install everything but the kernel module, and do not remove
any existing, possibly conflicting kernel modules. This
can be useful in some DEBUG environments. If you use this
option, you must be careful to ensure that a NVIDIA kernel
module matching this driver version is installed
seperately.
--no-x-check
Do not abort the installation if nvidia-installer detects
that an X server is running. Only under very rare
circumstances should this option be used.
--precompiled-kernel-interfaces-path=PRECOMPILED-KERNEL-INTERFA
CES-PATH
Before searching for a precompiled kernel interface in the
.run file, search in the specified directory.
-X, --run-nvidia-xconfig
nvidia-installer can optionally invoke the nvidia-xconfig
utility. This will update the system X configuration file
so that the NVIDIA X driver is used. The pre-existing X
configuration file will be backed up. At the end of
installation, nvidia-installer will ask the user if they
wish to run nvidia-xconfig; the default response is 'no'.
Use this option to make the default response 'yes'. This
is useful with the '--no-questions' or '--silent' options,
which assume the default values for all questions.
--force-selinux=FORCE-SELINUX
Linux installations using SELinux (Security-Enhanced Linux)
require that the security type of all shared libraries be
set to 'shlib_t' or 'textrel_shlib_t', depending on the
distribution. nvidia-installer will detect when to set the
security type, and set it using chcon(1) on the shared
libraries it installs. If the execstack(8) system utility
is present, nvidia-installer will use it to also clear the
executable stack flag of the libraries. Use this option to
override nvidia-installer's detection of when to set the
security type. Valid values for FORCE-SELINUX are 'yes'
(force setting of the security type), 'no' (prevent setting
of the security type), and 'default' (let nvidia-installer
decide when to set the security type).
--selinux-chcon-type=SELINUX-CHCON-TYPE
When SELinux support is enabled, nvidia-installer will try
to determine which chcon argument to use by first trying
'textrel_shlib_t', then 'texrel_shlib_t', then 'shlib_t'.
Use this option to override this detection logic.
--no-sigwinch-workaround
Normally, nvidia-installer ignores the SIGWINCH signal
before it forks to execute commands, e.g. to build the
kernel module, and restores the SIGWINCH signal handler
after the child process has terminated. This option
disables this behavior.
--no-cc-version-check
The NVIDIA kernel module should be compiled with the same
compiler that was used to compile the currently running
kernel. The layout of some Linux kernel data structures may
be dependent on the version of gcc used to compile it. The
Linux 2.6 kernel modules are tagged with information about
the compiler and the Linux kernel's module loader performs
a strict version match check. nvidia-installer checks for
mismatches prior to building the NVIDIA kernel module and
aborts the installation in case of failures. Use this
option to override this check.
--no-distro-scripts
Normally, nvidia-installer will run scripts from
/usr/lib/nvidia before and after installing or uninstalling
the driver. Use this option to disable execution of these
scripts.
roy@roylocalhost ~ $
I installed the Portage driver using "emerge =x11-drivers/nvidia-drivers-185.18.36-r1" and I installed the driver from Nvidia's web site by running "sh NVIDIA-Linux-x86-185.18.36-pkg1.run".
Below are the options for installing the Nvidia driver from their web site:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
