Ubuntu&Fedora装机&Mac装机（UOS装机将会持续更新）

[243750496]

Ubuntu manuals

12.04 LTS
14.04 LTS
15.10
16.04 LTS
16.10
17.04

Name
Synopsis
Description
Options
Advanced Options
Examples
Author
See Also
Copyright
zesty (1) alt-nvidia-304-xconfig.1.gz
Provided by: nvidia-304_304.134-0ubuntu1_amd64 bug

NAME
nvidia-xconfig - manipulate X configuration files for the NVIDIA driver

SYNOPSIS
nvidia-xconfig [ options ]

DESCRIPTION
nvidia-xconfig is a tool intended to provide basic control over
configuration options available in the NVIDIA X driver.

nvidia-xconfig performs its operations in several steps:

1) The system X configuration file is found and read into memory.
If no configuration file can be found, nvidia-xconfig generates
one from scratch using default settings; in this case, nvidia-
xconfig will automatically determine the name of the X
configuration file to create: /etc/X11/xorg.conf if the X server
in use is X.org or /etc/X11/XF86Config if the X server in use is
XFree86.

2) The configuration in memory is modified to support the NVIDIA
driver. This consists of changing the display driver to
"nvidia", removing the commands to load the "GLcore" and "dri"
modules, and adding the command to load the "glx" module.

3) The configuration in memory is modified according to the options
specified on the command line. Please see the NVIDIA README for
a description of the NVIDIA X configuration file options. Note
that nvidia-xconfig does not perform any validation of the X
configuration file options requested on the command line; X
configuration file option validation is left for the NVIDIA X
driver.

4) The configuration is written back to the file from which it was
read. A backup of the original configuration is created with
".backup" appended. For example, if your X configuration is
/etc/X11/xorg.conf then nvidia-xconfig will copy it to
/etc/X11/xorg.conf.backup before writing the new configuration.
The --post-tree (-T) option can be used to print the new
configuration to standard out in tree form instead. This option
is useful to see what nvidia-xconfig will do while leaving the
original configuration intact.

The source code to nvidia-xconfig is released under the GPL and
available here:

⟨ftp://download.nvidia.com/XFree86/nvidia-xconfig/⟩

Patches are welcome.

OPTIONS
-c XCONFIG, --xconfig=XCONFIG
Use XCONFIG as the input X config file; if this option is not
specified, then the same search path used by the X server will
be used to find the X configuration file.

-o OUTPUT-XCONFIG, --output-xconfig=OUTPUT-XCONFIG
Use OUTPUT-XCONFIG as the output X configuration file; if this
option is not specified, then the input X configuration filename
will also be used as the output X configuration filename.

-s, --silent
Run silently; no messages will be printed to stdout, except for
warning and error messages to stderr.

-t, --tree
Read the X configuration file, print to stdout the X
configuration data in a tree format, and exit.

-v, --version
Print the nvidia-xconfig version and exit.

-h, --help
Print usage information for the common commandline options and
exit.

-A, --advanced-help
Print usage information for the common commandline options as
well as the advanced options, and then exit.

ADVANCED OPTIONS
--acpid-socket-path=ACPID-SOCKET-PATH, --no-acpid-socket-path
Set this option to specify an alternate path to the Linux ACPI
daemon (acpid)'s socket, which the NVIDIA X driver will use to
connect to acpid.

--add-argb-glx-visuals, --no-add-argb-glx-visuals
Enables or disables support for OpenGL rendering into 32-bit
ARGB windows and pixmaps.

--allow-glx-with-composite, --no-allow-glx-with-composite
Enable or disable the "AllowGLXWithComposite" X configuration
option.

--bandwidth-test, --no-bandwidth-test
Disable or enable the "NoBandWidthTest" X configuration option.

--busid=BUSID, --no-busid
This option writes the specified BusID to the device section of
the X configuration file. If there are multiple device
sections, then it adds the BusID field to each of them. To add
the BusID to only a specific device or screen section, use the
'--device' or '--screen' options.

--preserve-busid, --no-preserve-busid
By default, nvidia-xconfig preserves the existing BusID in the X
configuration file only if there are multiple X screens
configured for the X server. Use '--preserve-busid' or
'--no-preserve-busid' to force the BusID to be preserved or not
preserved, overriding the default behavior.

--cool-bits=COOL-BITS, --no-cool-bits
Enable or disable the "Coolbits" X configuration option.
Setting this option will enable support in the NV-CONTROL X
extension for manipulating GPU clock and GPU fan control
settings. Default value is 0. For fan control set it to 4.
WARNING: this may cause system damage and void warranties.

--composite, --no-composite
Enable or disable the "Composite" X extension.

--connected-monitor=CONNECTED-MONITOR, --no-connected-monitor
Enable or disable the "ConnectedMonitor" X configuration
option; setting this option forces the X driver to behave as if
the specified display devices are connected to the GPU.

--connect-to-acpid, --no-connect-to-acpid
Enable or disable the "ConnectToAcpid" X configuration option.
If this option is set, the NVIDIA X driver will attempt to
connect to the Linux ACPI daemon (acpid). Set this option to
off to prevent the X driver from attempting to connect to acpid.

--constant-dpi, --no-constant-dpi
Enable or disable the "ConstantDPI" X configuration option,
which controls whether the NVIDIA X driver maintains a constant
dots per inch (DPI) value by recomputing the reported size in
millimeters of the X screen when XRandR changes the size in
pixels of the X screen.

--custom-edid=CUSTOM-EDID, --no-custom-edid
Enable or disable the "CustomEDID" X configuration option;
setting this option forces the X driver to use the EDID
specified.This option is a semicolon-separated list of pairs of
display device names and filename pairs; e.g "CRT-0:mp\did.bin".
Note that a display device name must always be specified even if
only one EDID is specified.

--dac-8bit, --no-dac-8bit
Most Quadro parts by default use a 10 bit color look up table
(LUT) by default; setting this option to TRUE forces these
graphics chips to use an 8 bit (LUT).

-d DEPTH, --depth=DEPTH
Set the default depth to DEPTH ; valid values for DEPTH are 8,
15, 16, 24, and 30.

--device=DEVICE
The nvidia-xconfig utility operates on one or more devices in
the X configuration file. If this option is specified, the
device named DEVICE in the X configuration file will be used.
If this option is not specified, all the devices within the X
configuration file will be used.

--disable-glx-root-clipping, --no-disable-glx-root-clipping
Disable or enable clipping OpenGL rendering to the root window
via the "DisableGLXRootClipping" X configuration option.

--damage-events, --no-damage-events
Use OS-level events to notify the X server when a
direct-rendering client has performed rendering that needs to be
composited to the screen. Improves performance when using GLX
with the composite extension.

--dynamic-twinview, --no-dynamic-twinview
Enable or disable support for dynamically configuring TwinView.

--preserve-driver-name
By default nvidia-xconfig changes the display driver to
"nvidia" for all configured X screens; this option preserves the
existing driver name of each X screen.

--enable-acpi-hotkeys, --no-enable-acpi-hotkeys
The "EnableACPIHotkeys" option can be specified to override the
NVIDIA X driver's default decision to enable or disable ACPI
display change hotkey events.

-a, --enable-all-gpus
Configure an X screen on every GPU in the system.

--exact-mode-timings-dvi, --no-exact-mode-timings-dvi
Forces the initialization of the X server with the exact timings
specified in the ModeLine.

-E FILE, --extract-edids-from-file=FILE
Extract any raw EDID byte blocks contained in the specified X
log file LOG ; raw EDID bytes are printed by the NVIDIA X driver
to the X log as hexidecimal when verbose logging is enabled with
the "-logverbose 6" X server commandline option. Any extracted
EDIDs are then written as binary data to individual files.
These files can later be used by the NVIDIA X driver through the
"CustomEDID" X configuration option.

--extract-edids-output-file=FILENAME
When the '--extract-edids-from-file' option is used,
nvidia-xconfig writes any extracted EDID to a file, typically
"edid.bin" in the current directory. Use this option to specify
an alternate filename. Note that nvidia-xconfig, if necessary,
will append a unique number to the EDID filename, to avoid
overwriting existing files (e.g., "edid.bin.1" if "edid.bin"
already exists).

--flatpanel-properties=FLATPANEL-PROPERTIES, --no-flatpanel-properties
Set the flat panel properties. The supported properties are
'dithering' and 'ditheringmode'. Please see the NVIDIA README
'Appendix B. X Config Options' for more details on the possible
values and syntax.

--flip, --no-flip
Enable or disable OpenGL flipping

--force-generate
Force generation of a new X config file, ignoring any existing
system X config file. This is not typically recommended, as
things like the mouse protocol, keyboard layout, font paths,
etc, are setup by your Unix distribution. While nvidia-xconfig
can attempt to infer these values, it is best to use your Unix
distribution's X config file for the basis of anything that
nvidia-xconfig creates.

--force-stereo-flipping, --no-force-stereo-flipping
Normally, stereo flipping is only performed when a stereo
drawable is visible. This option forces stereo flipping even
when no stereo drawables are visible.

--handle-special-keys=WHEN, --no-handle-special-keys
Specify when the X server should use the builtin keyboard
handler to process special key combinations (such as
Ctrl+Alt+Backspace); see the X configuration man page for
details. The value of WHEN can be 'Always', 'Never', or
'WhenNeeded'.

--include-implicit-metamodes, --no-include-implicit-metamodes
Enable or disable the "IncludeImplicitMetaModes" X configuration
option.

--keyboard=KEYBOARD
When generating a new X configuration file (which happens when
no system X configuration file can be found, or the
'--force-generate' option is specified), use KEYBOARD as the
keyboard type, rather than attempting to probe the system for
the keyboard type. For a list of possible keyboard types, see
the '--keyboard-list' option.

--keyboard-driver=DRIVER
In most cases nvidia-xconfig can automatically determine the
correct keyboard driver to use (either 'kbd' or 'keyboard'). Use
this option to override what nvidia-xconfig detects. Typically,
if you are using an X.Org X server, use 'kdb'; if you are using
an XFree86 X server, use 'keyboard'.

--keyboard-list
Print to stdout the available keyboard types recognized by the
'--keyboard' option, and then exit.

--layout=LAYOUT
The nvidia-xconfig utility operates on a Server Layout within
the X configuration file. If this option is specified, the
layout named LAYOUT in the X configuration file will be used.
If this option is not specified, the first Server Layout in the
X configuration file is used.

--logo, --no-logo
Disable or enable the "NoLogo" X configuration option.

--logo-path=PATH, --no-logo-path
Set the path to the PNG file to be used as the logo splash
screen at X server startup.

--mode=MODE
Add the specified mode to the mode list.

--mode-debug, --no-mode-debug
Enable or disable the "ModeDebug" X configuration option; when
enabled, this option causes the X driver to print verbose
details about mode validation to the X log file.

--mode-list=MODELIST
Remove all existing modes from the X configuration's modelist
and add the one(s) specified in the MODELIST string.

--remove-mode=MODE
Remove the specified mode from the mode list.

--metamodes=METAMODES
Add the MetaMode X configuration option with the value METAMODES
which will replace any existing MetaMode option already in the X
configuration file.

--mouse=MOUSE
When generating a new X configuration file (which happens when
no system X configuration file can be found, or the
'--force-generate' option is specified), use MOUSE as the mouse
type, rather than attempting to probe the system for the mouse
type. For a list of possible mouse types, see the
'--mouse-list' option.

--mouse-list
Print to stdout the available mouse types recognized by the
'--mouse' option, and then exit.

--multigpu=MULTIGPU, --no-multigpu
Enable or disable MultiGPU. Valid values for MULTIGPU are
'Off', 'On', 'Auto', 'AFR', 'SFR', 'AA'.

--multisample-compatibility, --no-multisample-compatibility
Enable or disable the use of separate front and back multisample
buffers.

--nvagp=NVAGP, --no-nvagp
Set the NvAGP X config option value. Possible values are 0 (no
AGP), 1 (NVIDIA's AGP), 2 (AGPGART), 3 (try AGPGART, then try
NVIDIA's AGP); these values can also be specified as 'none',
'nvagp', 'agpgart', or 'any'.

--nvidia-cfg-path=PATH
The nvidia-cfg library is used to communicate with the NVIDIA
kernel module to query basic properties of every GPU in the
system. This library is typically only used by nvidia-xconfig
when configuring multiple X screens. This option tells
nvidia-xconfig where to look for this library (in case it cannot
find it on its own). This option should normally not be needed.

--only-one-x-screen
Disable all but one X screen.

--overlay, --no-overlay
Enable or disable the "Overlay" X configuration option.

--cioverlay, --no-cioverlay
Enable or disable the color index overlay.

--overlay-default-visual, --no-overlay-default-visual
Enable or disable the "OverlayDefaultVisual" X configuration
option.

--transparent-index=INDEX, --no-transparent-index
Pixel to use as transparent when using color index overlays.
Valid values for TRANSPARENT-INDEX are 0-255.

-T, --post-tree
Like the '--tree' option, but goes through the full process of
applying any user requested updates to the X configuration,
before printing the final configuration to stdout in a tree
format. Effectively, this option just causes the configuration
to be printed to stdout as a tree instead of writing the results
to file.

--power-connector-check, --no-power-connector-check
Disable or enable the "NoPowerConnectorCheck" X configuration
option.

--probe-all-gpus, --no-probe-all-gpus
Disable or enable the "ProbeAllGpus" X configuration option.

--query-gpu-info
Print information about all recognized NVIDIA GPUs in the
system.

--randr-rotation, --no-randr-rotation
Enable or disable the "RandRRotation" X configuration option.

--registry-dwords=REGISTRY-DWORDS, --no-registry-dwords
Enable or disable the "RegistryDwords" X configuration option.

--render-accel, --no-render-accel
Enable or disable the "RenderAccel" X configuration option.

--render-extension, --no-render-extension
Disable or enable the "NoRenderExtension" X configuration
option.

--rotate=ROTATE, --no-rotate
Enable or disable the "Rotate" X configuration option. Valid
values for ROTATE are 'normal', 'left', 'CCW', 'inverted',
'right', and 'CW'. Rotation can be disabled

--screen=SCREEN
The nvidia-xconfig utility operates on one or more screens
within a Server Layout in the X configuration file. If this
option is specified, the screen named SCREEN in the X
configuration file will be used. If this option is not
specified, all screens within the selected Server Layout in the
X configuration file will be used used.

--separate-x-screens, --no-separate-x-screens
A GPU that supports multiple simultaneous display devices can
either drive these display devices in TwinView, or as separate X
screens. When the '--separate-x-screens' option is specified,
each GPU on which an X screen is currently configured will be
updated to have two X screens configured. The
'--no-separate-x-screens' option will remove the second
configured X screen on each GPU. Please see the NVIDIA README
description of "Separate X Screens on One GPU" for further
details.

--sli=SLI, --no-sli
Enable or disable SLI. Valid values for SLI are 'Off', 'On',
'Auto', 'AFR', 'SFR', 'AA', 'AFRofAA', 'Mosaic'.

--stereo=STEREO, --no-stereo
Enable or disable the stereo mode. Valid values for STEREO are:
0 (Disabled), 1 (DDC glasses), 2 (Blueline glasses), 3 (Onboard
stereo), 4 (multi-display clone mode stereo), 5 (SeeReal digital
flat panel), 6 (Sharp3D digital flat panel), 7
(Arisawa/Hyundai/Zalman/Pavione/Miracube), 8 (3D DLP), 9 (3D DLP
INV), 10 (NVIDIA 3D VISION), 11 (NVIDIA 3D VISION PRO).

--thermal-configuration-check, --no-thermal-configuration-check
Disable or enable the "ThermalConfigurationCheck" X
configuration option.

--tv-standard=TV-STANDARD, --no-tv-standard
Enable or disable the "TVStandard" X configuration option. Valid
values for "TVStandard" are: "PAL-B", "PAL-D", "PAL-G", "PAL-H",
"PAL-I", "PAL-K1", "PAL-M", "PAL-N", "PAL-NC", "NTSC-J",
"NTSC-M", "HD480i", "HD480p", "HD720p", "HD1080i", "HD1080p",
"HD576i", "HD576p".

--tv-out-format=TV-OUT-FORMAT, --no-tv-out-format
Enable or disable the "TVOutFormat" X configuration option.
Valid values for "TVOutFormat" are: "SVIDEO" and "COMPOSITE".

--tv-over-scan=TV-OVER-SCAN, --no-tv-over-scan
Enable or disable the "TVOverScan" X configuration option. Valid
values are decimal values in the range 1.0 and 0.0.

--metamode-orientation=ORIENTATION, --no-metamode-orientation
Specify the MetaModeOrientation. Valid values for ORIENTATION
are: "RightOf" (the default), "LeftOf", "Above", "Below", or
"Clone".

--nvidia-xinerama-info, --no-nvidia-xinerama-info
Enable or disable providing Xinerama information from the NVIDIA
X driver.

--nvidia-xinerama-info-order=NVIDIA-XINERAMA-INFO-ORDER, --no-nvidia-
xinerama-info-order
Enable or disable the "nvidiaXineramaInfoOrder" X configuration
option. NVIDIA-XINERAMA-INFO-ORDER is a comma-separated list of
display device names that describe the order in which
nvidiaXineramaInfo should be reported. E.g., "CRT, DFP, TV".

--ubb, --no-ubb
Enable or disable the "UBB" X configuration option.

--use-edid, --no-use-edid
Enable or disable use of the EDID (Extended Display
Identification Data) from your display device(s). The EDID will
be used for driver operations such as building lists of
available modes, determining valid frequency ranges, and
computing the DPI (Dots Per Inch). This option defaults to TRUE
(the NVIDIA X driver will use the EDID, when available). It is
NOT recommended that you use this option to globally disable use
of the EDID; instead, use '--no-use-edid-freqs' or
'--no-use-edid-dpi' to disable specific uses of the EDID.

--use-edid-dpi, --no-use-edid-dpi
Enable or disable use of the physical size information in the
display device's EDID, if any, to compute the DPI (Dots Per
Inch) of the X screen. This option defaults to TRUE (the NVIDIA
X driver uses the EDID's physical size, when available, to
compute the DPI).

--use-edid-freqs, --no-use-edid-freqs
Enable or disable use of the HorizSync and VertRefresh ranges
given in a display device's EDID, if any. EDID provided range
information will override the HorizSync and VertRefresh ranges
specified in the Monitor section. This option defaults to TRUE
(the NVIDIA X driver will use frequency information from the
EDID, when available).

--use-int10-module, --no-use-int10-module
Enable use of the X Int10 module to soft-boot all secondary
cards, rather than POSTing the cards through the NVIDIA kernel
module.

--use-display-device=DISPLAY-DEVICE, --no-use-display-device
Force the X driver to use the display device specified.

--use-events, --no-use-events
Enable or disable "UseEvents" X configuration option. Setting
this option will enable the X driver to use the system events in
some cases when it is waiting for the hardware. With this option
X driver sets an event handler and waits for the hardware
through the poll() system call. This option defaults to FALSE.

--virtual=WIDTHxHEIGHT, --no-virtual
Specify the virtual screen resolution.

--x-prefix=X-PREFIX
The X installation prefix; the default is /usr/X11R6/. Only
under rare circumstances should this option be needed.

--xinerama, --no-xinerama
Enable or disable Xinerama.

--xvmc-uses-textures, --no-xvmc-uses-textures
Forces XvMC to use the 3D engine for XvMCPutSurface requests
rather than the video overlay.

--color-space=COLORSPACE, --no-color-space
Enable or disable the "ColorSpace" X configuration option. Valid
values for "COLORSPACE" are: "RGB" and "YCbCr444".

--color-range=COLORRANGE, --no-color-range
Sets the "ColorRange" X configuration option. Valid values for
"COLORRANGE" are: "Full" and "Limited".

--3dvision-usb-path=3DVISION-USB-PATH
Set this option to specify the sysfs path of the connected USB
dongle.

--3dvisionpro-config-file=3DVISIONPRO-CONFIG-FILE
Set this option to specify the NVIDIA 3DVisionPro configuration
file. Ensure X server has a read and write access permissions to
this file. NVIDIA X driver stores the hub and the pairing
configuration in this file to re-use across X restarts. If this
option is not provided, 3D VisionPro configuration will not be
stored.

--3dvision-display-type=3DVISION-DISPLAY-TYPE, --no-3dvision-display-
type
When NVIDIA 3D Vision is enabled with a non 3D Vision ready
display, use this option to specify the display type. Valid
values are: 0 (Assume it is a CRT), 1 (Assume it is a DLP) and 2
(Assume it is a DLP TV and enable the checkerboard output).

--base-mosaic, --no-base-mosaic
Enable or disable the "BaseMosaic" X configuration option.

--restore-original-backup
Restore a backup of the X configuration that was made before any
changes were made by nvidia-xconfig, if such a backup is
available. This type of backup is made by nvidia-xconfig before
it modifies an X configuration file that it has not previously
touched; this is assumed to be an X configuration file that
predates the involvement of the NVIDIA X driver. As an example,
nvidia-xconfig will copy an X configuration file at
/etc/X11/xorg.conf to /etc/X11/xorg.conf.nvidia-xconfig-original
the first time it makes changes to that file.

EXAMPLES
nvidia-xconfig
Reads an existing X config file and adapts it to use the NVIDIA
driver. If no X config file can be found, a new one is created
at /etc/X11/XF86Config with default settings.

nvidia-xconfig --post-tree --metamode-orientation=clone
Reads the existing X configuration file, adds the
MetaModeOrientation option, and then prints the resulting config
file to standard out in tree form. The configuration file is
not modified.

nvidia-xconfig --enable-all-gpus
Examines the system and configures an X screen for each display
device it finds.

nvidia-xconfig --mode=1600x1200
Adds a 1600x1200 mode to an existing X configuration.

nvidia-xconfig --mode-list=1600x1200 1280x1024
Removes any existing modes from the X configuration file,
replacing them with "1600x1200" and "1280x1024".

nvidia-xconfig --metamodes=1024x768 +0+0, 1024x768 +1024+0
Adds the MetaMode "1024x768 +0+0, 1024x768 +1024+0" to the
existing X configuration file, replacing any existing MetaModes
X configuration option.

nvidia-xconfig --only-one-x-screen --sli=Auto
Configures the X server to have just one X screen that will use
SLI when available.

AUTHOR
Aaron Plattner
NVIDIA Corporation

SEE ALSO
nvidia-settings(1), /usr/share/doc/NVIDIA_GLX-1.0/README.txt

COPYRIGHT
Copyright © 2005-2010 NVIDIA Corporation.

[243750496]

https://devtalk.nvidia.com/default/topi ... /?offset=1

[243750496]

Exactly the same thing happens to me. I changed SLI "On" to SLI "SFR" and it works much better. You get some flickering when you first login strangely, and it goes away after about 3 minutes.

[243750496]

NVIDIA的SLI技术与早先3dfx的SLI虽然缩写相同，其实已经是全新的技术，不但工作原理不同，甚至名称都不相同，3dfx的SLI（Scan Line Interleave，双扫描线交错技术）是将画面分为一条条扫描帧线（Scanline），两块显卡对奇数帧线和偶数帧线分别渲染，然后将同时渲染完毕的帧线进行合并后写入到帧缓冲中，接下来显示器就可以显示出一幅完整的画面。而nVIDIA的SLI则有两种渲染模式：分割帧渲染模式（Scissor Frame Rendering，SFR）和交替帧渲染模式（Alternate Frame Rendering，AFR），分割帧渲染模式是将每帧画面划分为上下两个部分，主显卡完成上部分画面渲染，副显卡则完成下半部分的画面渲染，然后副显卡将渲染完毕的画面传输给主显卡，主显卡再将它与自己渲染的上半部分画面合成为一幅完整的画面；而交替帧渲染模式则是一块显卡负责渲染奇数帧画面，而另外一块显卡则负责渲染偶数帧画面，二者交替渲染，在这种模式下，两块显卡实际上都是渲染的完整的画面，此时并不需要连接显示器的主显卡做画面合成工作。
在SLI状态下，特别是在分割帧渲染模式下，两块显卡并不是对等的，在运行工作中，一块显卡做为主卡（Master），另一块做为副卡（Slave），其中主卡负责任务指派、渲染、后期合成、输出等运算和控制工作，而副卡只是接收来自主卡的任务进行相关处理，然后将结果传回主卡进行合成然后输出到显示器。由于主显卡除了要完成自己的渲染任务之外，还要额外担负副显卡所传回信号的合成工作，所以其工作量要比副显卡大得多。另外，在SLI模式下，就只能连接一台显示器，并不能支持多头显示。

[243750496]

# Linux install instructions

**NOTE**: _If you experience a problem with dependencies while installing, you may
want to try installing `git` using the package manager for your distro._

## Debian (jessie) and Ubuntu (Trusty and Xenial) AMD64:
To install brave using apt and lsb\_release :

```
curl https://s3-us-west-2.amazonaws.com/brave-apt/keys.asc | sudo apt-key add -
echo "deb [arch=amd64] https://s3-us-west-2.amazonaws.com/brave-apt `lsb_release -sc` main" | sudo tee -a /etc/apt/sources.list.d/brave-`lsb_release -sc`.list
```

You will want to make sure the /etc/apt/sources.list.d/brave-\*.list file lists a new repository and does not contain the word lsb\_release. If you see the word lsb\_release you might not have lsb\_release installed. Otherwise run:

```
sudo apt update
sudo apt install brave
```

[243750496]

How to install Brave browser via repo for Ubuntu 14.04 - 16.04
The new Brave browser ( https://brave.com ), based on Chromium, is garnering a lot of interest lately. It is only available for amd64 currently. You can download the 64-bit deb file and install it, but this will not keep your Brave installation updated. Brave has a repo that can be added to your sources, but their instructions on adding it are borked and do not work. So, I decided to provide corrected instructions on adding the repo to the sources list so that you can install Brave and keep it updated. The instructions are as follows:

*IMPORTANT* Brave is only offered for the amd64 arch.

*NOTE* When I originally made this post, I inadvertently made an error. The code read 'sudo install brave' when it should have read 'sudo apt install brave'. The error has been corrected.

First, we need to download the repo keys and add them to the keyring:
Code:
wget -qO - https://s3-us-west-2.amazonaws.com/brave-apt/keys.asc | sudo apt-key add -
Second, we need to add the repo. **NOTE** If you're running 14.04 <= Ubuntu < 16.04 then change 'xenial' in the following line to 'trusty'
Code:
sudo add-apt-repository "deb [arch=amd64] https://s3-us-west-2.amazonaws.com/brave-apt xenial main"
sudo add-apt-repository "deb [arch=amd64] https://s3-us-west-2.amazonaws.com/brave-apt zesty main"

The '[arch=amd64]' in the line above is to prevent apt from whining that it cannot find repo files for the i386 arch if your system is multiarch (i.e. you have added the i386 architecture).

Next, we need to update our sources.
Code:
sudo apt-get update
And finally, intall Brave
Code:
sudo apt-get install brave
That's it. Enjoy!
Last edited by SeanKD; December 15th, 2016 at 06:20 PM. Reason: Minor edit to text in thread
Advanced reply Adv Reply Reply With Quote Reply With Quote
December 15th, 2016 #2 happydog500 happydog500 is offline
5 Cups of Ubuntu

Join Date
Jan 2009
Location
Washington St.
Beans
42
Distro
Kubuntu 8.10 Intrepid Ibex
Re: How to install Brave browser via repo for Ubuntu 14.04 - 16.04
Nice Job, doesn't work. Says this;

@Linux:~$ sudo install brave
install: missing destination file operand after ‘brave’
Try 'install --help' for more information.
roger@Linux:~$ sudo install brave
install: missing destination file operand after ‘brave’
Hope adding a repo key and repo without anything else doesn't have any other negative effects. I downloaded from the site last time and it worked fine.

Chris.
Advanced reply Adv Reply Reply With Quote Reply With Quote
December 15th, 2016 #3 QIII's Avatar QIII QIII is online now
Dark-Roasted but Half-Baked

Join Date
Jul 2008
Location
The Left Coast of the USA
Beans
Hidden!
Distro
Kubuntu
Re: How to install Brave browser via repo for Ubuntu 14.04 - 16.04
That should be

Code:
sudo apt install brave
My Blog
Ubuntu Help Pages I'm constructing: AMDGPU and AMDGPU-PRO
Don't let the truth get in the way of a good story!
This universe is crazy. I'm going back to my own.
Advanced reply Adv Reply Reply With Quote Reply With Quote
December 15th, 2016 #4 SeanKD SeanKD is offline
First Cup of Ubuntu

Join Date
Oct 2012
Beans
4
Re: How to install Brave browser via repo for Ubuntu 14.04 - 16.04
Thanks for the proofreading! Correcting it now.
Advanced reply Adv Reply Reply With Quote Reply With Quote
December 15th, 2016 #5 SeanKD SeanKD is offline
First Cup of Ubuntu

Join Date
Oct 2012
Beans
4
Re: How to install Brave browser via repo for Ubuntu 14.04 - 16.04
It was a typo on my part. It should be 'sudo apt install brave'. I have corrected it. Thanks for catching the error!
Advanced reply Adv Reply Reply With Quote Reply With Quote
December 15th, 2016 #6 SeanKD SeanKD is offline
First Cup of Ubuntu

Join Date
Oct 2012
Beans
4
Re: How to install Brave browser via repo for Ubuntu 14.04 - 16.04
Quote Originally Posted by happydog500 View Post
Nice Job, doesn't work. Says this;



Hope adding a repo key and repo without anything else doesn't have any other negative effects. I downloaded from the site last time and it worked fine.

Chris.
The error was caused by a typo on my part. It should read 'sudo apt install brave', not 'sudo install brave'. There aren't any negative effects from adding a repo and keys and both can easily be removed by opening Software&Updates if you feel so inclined.

[243750496]

wget -O brave.deb https://laptop-updates.brave.com/latest/dev/ubuntu64
sudo dpkg -i ./brave.deb

[243750496]

Hello. Welcome to the painful world of configuring Linux.

This Guide is now a two part, mostly SLI in Linux, but also to help configure graphic options.

Part 1. SLI


So, I've been trying to enable SLI on SuSe 10.3 for, seriously months and months. Heres the guide I was always looking for.

1.) First we need our distro.


There are many out there, I use SuSe GNOME. Its powerful, easy and well my first choice. Theres also popular ones such as Gentoo, RedHat, Ubuntu, Solaris, Fedora core and many more. This will normally refer to RPM packages and miscellaneous package managers, some distro's are different such as Debian. nVidia supports about all of them, including 64 bit, so no worries. IMPORTANT! Make sure you have your SLI disabled in your BIOS, or just remove the bridge, so you can configure and enable it in the GUI . If it is enabled while you install, you will not get a desktop.

2.) Drivers.

Time to download. Heres nVidia's download page and list: http://www.nvidia.com/object/unix.html
find the driver you need. I used YaST, which is SuSe's package manager, so I'll go over that first. Here is a direct instruction list from the site if you are using Yast,

Update your Kernel via YOU (YaST Online Update). Use

YaST -> Software -> Software Repositories -> Add

Protocol: HTTP
Server Name: : download.nvidia.com
Directory on Server: /opensuse/10.3

to add the nVidia http server as additional installation source.
Now use

YaST -> Software -> Software Management

to install the NVIDIA driver. Select the following packages:

x11-video-nvidiaG01
After that is done, (which you just updated the Kernel) you need to install the driver UI and so on, which luckily, is just a click installation, http://opensuse-community.org/nvidia.ymp
for SuSe users, the rest is simple from there on for the initial driver installation.

(Non SuSe users)
This is right on the site, but just for further clarifacation.


Download the file marked on the download page, heres a copy and paste right from the site.


STEP 2: Download the Driver File
Download - NVIDIA-Linux-x86_64-169.07-pkg2.run
SuSE users: please read the SuSE NVIDIA Installer HOWTO before downloading the driver.
STEP 3: Install
Type "sh NVIDIA-Linux-x86_64-169.07-pkg2.run" to install the driver. NVIDIA now provides a utility to assist you with configuration of your X config file. Please see Chapter 3 of the README or run 'man nvidia-xconfig' for details on usage. Instructions for those wishing to edit their X config file by hand can also be found in the README.
If you have any questions or problems, please check the linux discussion forum. If you don't find an answer to your question there, you can send email (in English) to linux-bugs@nvidia.com.
When emailing linux-bugs@nvidia.com, please attach an nvidia-bug-report.log, which is generated by running "nvidia-bug-report.sh".









So theres the driver installation, any question post and I'll try to clarify.

Driver installation for non-SuSe, Fedora, Redhat, Solaris ect.

Now SuSe is great because it installs the drivers for you. Now lets install the drivers from the command line!

First we need the file: http://us.download.nvidia.com/XFree86/L ... 9-pkg2.run

Now this driver cannot be installed when your are in you GUI, basically we need to switch to a black screen with a blinky cursor. To do this, open your terminal and login as root,

Code:
# su

(enter your root password.)
Now, we need to switch to run level 3, type:

Code:
# init 3

now navigate to where you downloaded it, most likely your desktop, so type:

Code:
# cd /home/(your user name)/Desktop
Now we need to run the installer which we type:
Code:
# sh NVIDIA-Linux-x86_64-169.09-pkg2.run
So, the installer should run. Now heres the problem I had and how to fix it.

The nVidia driver has to recompile your kernel if it does not match the version it wants. This is easy. Sometimes the installer will connect to a repo. and do it it self, but theres a way to do it before hand. Open up your package manager, which is just your Add/remove programs, the software manager. We need to download the source for the kernel your currently running. These files will be labeled kernel-devel. Download all of your kernel source files which any source file will have the suffix -devel. Once these are downloaded you will be good to go.






3.) Configuring your nVidia XServer program

Now you should have a configuration UI called nVidia XServer settings, its under applications, looks like so...(screenie from my system, if not there its cause I haven't posted the pic yet.)

[​IMG]


This is your general configuration, and if you notice, the second card should be running at 2x, if disabled, as most boards run one card at 16x and the other at 2, or some board will run full SLI 16x by 16x. So there should be one card running at 16x.

If you have this UI, the drivers are installed and time to enabled the SLI

4.) Enabling.

Open up your terminal, the command line interface for all Linux distro's. SLI on Linux has different configurations, we will use the "AUTO" settings, as you can tweak with the different settings later. What we will be doing here is telling the xorg file (your graphic configuration) to set multi GPU'S on the same xscreen, or xserver, which is basically your monitors output. To see whats happening before we enable, lets go through the different options. First in terminal, set your permissions to root by typing:

Code:
$ su
hit enter, then it will prompt you for your root password(admin password), type it then hit enter. Notice your now using the terminal as the root user. Now type:

Code:
$ nvidia-xconfig --advanced-help
hit enter. This will give you all the different options for the nvidia-xconfig command. Notice theres one called SLI(if you scroll down) also notice the different options for the SLI command. Like I said, we will be using the "AUTO" setting, as it is the easiest to work with. Now type:

Code:
$ nvidia-xconfig --sli=Auto
hit enter. It should tell you about a new configuration file /ect/xll/xorg.conf. Now restart and enabled SLI in your BIOS. If you load up with a GUI, check the nVidia xserver program and it should look like mine with it telling you both your cards are SLI, as in, if you go to GPU 0 or GPU 1, click it and you should see where it says X Screens: Screen 0(SLI) you have successfully enabled SLI in Linux. Have fun tweaking!

Heres a Screenie of my SLI in the nVidia XServer program

[​IMG]

Any comments, edits, ideas are welcome. (First revision of this guide.)

Part 2. Graphic configuring


*Further editing for advanced users*


Beyond our new nVidia XServer, we can edit deeper. All of the graphic configuring is saved, and can be edited in the /etc/X11/xorg.conf file. There are many different root editing programs for different distros. The one I currently am using is gedit, though ive used nano too. They all do the same thing, just gotta know which one you have so you know the corret syntax for the shell command. Editing this is very risky, know your coding when doing this. Ill post all about it tomorrow I need to sleep. But if you just want to poke around(DONT SAVE)type:

Code:
$ sudo

gedit /etc/X11/xorg.conf
Have fun =P

Some example code in the xorg edit, this is a problem I've had with many systems dealing with again your distro not recognizing the settings for your video card and or your monitor, having to deal with your resolution. What we will do is add a new "mode" to your monitor in xorg, giving you the option to change it to resolutions that before hand were not offered. Heres some example code to help you out:

Code:
Section "Screen"
Identifier "Default Screen"
Device "NVIDIA Corporation NV34 [GeForce FX 5200]"
Monitor "CM752ET"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768_75.00"
EndSubSection
EndSection
Now remember, this is not to do with the terminal, and it not to be entered in such. This is after we open the xorg config file in gedit or nano(refer to earlier instructions about editing) I'll throw some screen shots up later of me editing my own xorg.


BETA Code.)Enabling 3D Hardware Acceleration


Note: The code below refers to enabling the 3D acceleration when using the nVidia XServer program. For the most part, you will not need to enable the acceleration if you do not have a card new enough so the XGL will not regonize it. If someone has a problem enabling acceleration for other cards (ATI, onboard ect,) post and I will firgure it out and add it to the guide.

Now, different distros, most all popular ones I'm sure, use the XGL config for 3D acceleration. This allows you to use different desktop effects for GNOME and KDE. To be honest, I do not know any other reasoning for using the acceleration, I will research and post later.

Most newer cards are not recognized but the XGL server, thus it will not enable the acceleration by default, and may give you warnings about your card not supporting it. Now we all know most 7.XX and about all 8.XX nVidia cards will support this, Linux just does not think so. So we can force it on and it works fine. Now to the code.

Here is, what I call BETA code, because I will explain the problems I had later despite the fact it worked. Open up the terminal and shoot this out:

Code:
$ su -
$ nvidia-xconfig --composite
$ nvidia-xconfig --render-accel
$ nvidia-xconfig --add-argb-glx-visuals -d 24
Bam! Works. =P. As you can see we are using the nvidia-xconfig like we used to enable SLI, same core but it will react with the XGL server to enable it. Now the problems I had are some user error, and some I don't know. My screen would go all white, though still have a cursor sometimes when I start playing with the desktop effect settings. If your screen goes to an unusable state, just press CTRL+ALT+Backspace, it ends your session and you can re-login and start over. Ill get more into the acceleration configuration when I learn more about it.


EXTRA. The first posting about the creation of my OS.

Yes, I am working on creating my own linux based operating system. So far there is not much info I can relese about it because its like super beta right now. But heres a list of some stuff I can tell right now:

Name
VixIn
I got this name from a friend actually. a Vixen is a female fox, so obviously my handle is fox this seems appropriate, and yes its misspelled, but purposely because, well its a linux distro.

Kernel
FoxxIx
The kernel is not from scratch just to get that out there. I took the source from my current fedora 8 install. I have made many changes to it, mostly to deal with the configuration of my own compuiter, but it will benefit others, mostly to try and optomize for newer hardware and such. I also have been trying to work it out with different SATA configs and SCSI. It previously had SCSI support, cept I was having problems mounting the live CD to my server at school, so thats somewhat in development. The Kernel is very very far away so nothing really to post about that right now.

GUI
KDE 3.5/4.0
For the most part I have always used KDE for all my distros ive downloaded. Overall it looks better. Also I like the organization of KDE over any GNOME revision. KDE is still in development so I really wont use it yet, but I will be done with this project most likey well after 4.0 is finished. Bell again gotta go to nest class, post later.

[243750496]

maybe it is too late ,but hope can help for others. the follow tips worked for ubuntu 16.04 and elementary os 0.4.

remove all nvidia packages ,skip this if your system is fresh installed

sudo apt-get remove nvidia* && sudo apt autoremove
install some packages for build kernel:

sudo apt-get install dkms build-essential linux-headers-generic
now block and disable nouveau kernel driver:

sudo vim /etc/modprobe.d/blacklist.conf
Insert follow lines to the blacklist.conf:

blacklist nouveau
blacklist lbm-nouveau
options nouveau modeset=0
alias nouveau off
alias lbm-nouveau off
save and exit.

Disable the Kernel nouveau by typing the following commands(nouveau-kms.conf may not exist,it is ok):

echo options nouveau modeset=0 | sudo tee -a /etc/modprobe.d/nouveau-kms.conf
build the new kernel by:

sudo update-initramfs -u
reboot



As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.

Make sure you are logged out.

Hit CTRL+ALT+F1 and login using your credentials.
kill your current X server session by typing sudo service lightdm stop or sudo lightdm stop
Enter runlevel 3 by typing sudo init 3 and install your *.run file.
You might be required to reboot when the installation finishes. If not, run sudo service lightdm start or sudo start lightdm to start your X server again.

[243750496]

9.3. Run levels

A run level is a state of init and the whole system that defines what system services are operating. Run levels are identified by numbers. Some system administrators use run levels to define which subsystems are working, e.g., whether X is running, whether the network is operational, and so on. Others have all subsystems always running or start and stop them individually, without changing run levels, since run levels are too coarse for controlling their systems. You need to decide for yourself, but it might be easiest to follow the way your Linux distribution does things.

The following table defines how most Linux Distributions define the different run levels. However, run-levels 2 through 5 can be modified to suit your own tastes.

Table 9-1. Run level numbers

0 Halt the system.
1 Single-user mode (for special administration).
2 Local Multiuser with Networking but without network service (like NFS)
3 Full Multiuser with Networking
4 Not Used
5 Full Multiuser with Networking and X Windows(GUI)
6 Reboot.

[243750496]

4)检查nouveau driver确保没有被加载！
$ lsmod | grep nouveau

lz是缺失了驱动的依赖kernel－devel。首先要安装kernel－devel才能继续安装驱动。不过kernel－devel是rpm的东西。
在ubuntu下，安装的不一样，打开终端，输入sudo　apt－get　install　linux－headers－generic，安装好之后再安装驱动。

sudo apt-get install linux-source

报错the distribution-provided pre-install script failed!不必理会，继续安装；


For example:
The distribution-provided pre-install script failed!
Failed to install the kernel module through DKMS.
ERROR: Unable to find the kernel source tree for
the currently running kernel. Please make sure
you have installed the kernel source files for
your kernel and that they are properly configured;
on Red Hat Linux systems, for example, be sure you
have the 'kernel-source' or 'kernel-devel' RPM
installed. If you know the correct kernel source
files are installed, you may specify the kernel
source path with the '--kernel-source-path' command
line option.




sh NVIDIAxxx --kernel-source-path=/usr/src/kernels/x.xx.x-xxxx

其中 NVIDIAxxx 为 nvidia 驱动脚本文件， x.xx.x-xxxx 为 kernel 版本号。



sudo ./cuda_6.5.14_linux_64.run --kernel-source-path=/usr/src/linux-headers-`uname -r`/

ls /usr/src/linux-headers/$(uname -r)


ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 304.22 -k
3.5.0-21-generic`: Error! Your kernel headers for kernel
3.5.0-21-generic cannot be found.
Please install the linux-headers-3.5.0-21-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located

ERROR: Failed to install the kernel module through DKMS. No kernel module
was installed; please try installing again without DKMS, or check the
DKMS logs for more information.

ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find
suggestions on fixing installation problems in the README available
on the Linux driver download page at www.nvidia.com.

sudo apt-get install dkms build-essential linux-headers-$(uname -r)

[243750496]

Hi everybody

I met difficulty to use NVIDIA drivers on recent distributions like Ubuntu because of "nouveau" drivers and MESA libraries :
- Regular crash of the office environment
- Update of the MESA library canceling the use of the NVIDIA driver
- Some versions of Ubuntu "nvidia" .deb packages refusing to be installed
And it would still exist other problems after using the .deb packages according to other users of Ubuntu or derivatives such as Linux Mint, Lubuntu, Xubuntu, etc ...

But now I find the solution to get the proprietary driver of NVIDIA on our computer without using NVIDIA .deb packages of Ubuntu

Here is the method : hope it will help you. And sorry for my English frog :p
I tested it on Linux Mint 17 - 64 bit version. It works successfully .

French version available here : http://jg.imbert.free.fr/nvidia.html

Setup NVIDIA driver:

1°) Install the dependencies :
sudo apt-get install build-essential linux-headers-`uname -r` xserver-xorg-dev dkms

2°) Blacklist "nouveau" module that can go to conflict with the NVIDIA proprietary driver :
sudo echo "blacklist nouveau" >> /etc/modprobe.d/blacklist-nouveau.conf
sudo echo "options nouveau modeset=0" >> /etc/modprobe.d/blacklist-nouveau.conf

3°) Execute this command to activate the desactivation of the "nouveau" module on the next reboot:
sudo update-initramfs -u

4°) Restart computer

5°) Verify that "NVIDIA" packages are uninstalled :
sudo apt-get remove --purge nvidia*

6°) Download the correct .run file of your graphics from the NVIDIA site : http://www.nvidia.fr/Download/index.aspx or http://www.geforce.com/drivers

7°) Execute one of the following commands :
- If you have Ubuntu : sudo /etc/init.d/lightdm stop
- If you have Kubuntu : sudo /etc/init.d/kdm stop
- If you have Lubuntu : sudo /etc/init.d/lxdm stop
- If you have Linux Mint : sudo /etc/init.d/mdm stop

8°) Execute the NVIDIA .run file :
cd "Directory where you downloaded the .run file"
chmod +x *.run
sudo ./NVIDIA*.run

9°) The setup has started. Accept the licence and follow these steps :
- Answer Yes if you see : The distribution-provided pre-install script failed ! Continue anyway ?
- Answer Yes if you see : Would you like to run the nvidia-xconfig utility [...] ?
- Answer Yes if you see : Install NVIDIA's 32-bit compatibility OpenGL libraries ?
- Answer Yes if you see the question for DKMS support (it will update NVIDIA driver for the update of the kernel of your distribution)
- Select Ok when the setup is finished.

10°) Re-correct symlinks of libGL.so (conflit with MESA) :
- For 64-bit version of your Linux distribution :
1: Add '#' at the beginning of the lines of these files : /etc/ld.so.conf.d/i386-linux-gnu_GL.conf et /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf

/etc/ld.so.conf.d/i386-linux-gnu_GL.conf :
#/usr/lib/i386-linux-gnu/mesa

/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf :
#/usr/lib/x86_64-linux-gnu/mesa

2: Execute this command : sudo ldconfig

- For 32-bit version of your Linux distribution :
Verify if the NVIDIA is correctly installed when you restart your computer at the end of the tutorial. I will add modifications if you have issues on 32-bit version of your Linux distribution.

11°) Execute this command to update the startup menu :
sudo update-initramfs -u

12°) Reboot your computer

Thanks you again for your work NVIDIA team ! I can now play games on my Linux Mint 17 thanks to your .run file to setup the Linux driver .

If you have issues or comments, don't hesitate to post here

In a friendly manner,
Jackobo

[243750496]

chmod是权限管理命令change the permissions mode of a file的缩写。。
u代表所有者，x代表执行权限。 + 表示增加权限。
chmod u+x file.sh 就表示对当前目录下的file.sh文件的所有者增加可执行权限。。。

[243750496]

正常情况屏蔽了nouveau 是仍然可以进入系统的 如果进不了请先将NVIDIA 驱动卸载 然后执行sudo service lightdm stop
然后在执行sudo lightdm start
输入密码登录即可

[243750496]

给NVIDIA驱动打补丁（可以使用ryzen的4.10内核与Nvidia 378.13兼容性不好导致了一个bug出现）

代码： 全选

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Mon Mar 13 10:23:31 2017
installer version: 378.13

PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

nvidia-installer command line:
    ./nvidia-installer

Unable to load: nvidia-installer ncurses v6 user interface

Using: nvidia-installer ncurses user interface
-> Detected 16 CPUs online; setting concurrency level to 16.
-> License accepted.
-> Installing NVIDIA driver version 378.13.
-> Running distribution scripts
   executing: '/usr/lib/nvidia/pre-install'...
-> done.
-> The distribution-provided pre-install script failed!  Are you sure you want to continue? (Answer: Continue installation)
-> Would you like to register the kernel module sources with DKMS? This will allow DKMS to automatically build a new module, if you install a different kernel later. (Answer: Yes)
-> Installing both new and classic TLS OpenGL libraries.
-> Installing both new and classic TLS 32bit OpenGL libraries.
-> Install NVIDIA's 32-bit compatibility libraries? (Answer: Yes)
-> Will install GLVND GLX client libraries.
-> Will install GLVND EGL client libraries.
-> Skipping GLX non-GLVND file: "libGL.so.378.13"
-> Skipping GLX non-GLVND file: "libGL.so.1"
-> Skipping GLX non-GLVND file: "libGL.so"
-> Skipping EGL non-GLVND file: "libEGL.so.378.13"
-> Skipping EGL non-GLVND file: "libEGL.so"
-> Skipping EGL non-GLVND file: "libEGL.so.1"
-> Skipping GLX non-GLVND file: "./32/libGL.so.378.13"
-> Skipping GLX non-GLVND file: "libGL.so.1"
-> Skipping GLX non-GLVND file: "libGL.so"
-> Skipping EGL non-GLVND file: "./32/libEGL.so.378.13"
-> Skipping EGL non-GLVND file: "libEGL.so"
-> Skipping EGL non-GLVND file: "libEGL.so.1"
Looking for install checker script at ./libglvnd_install_checker/check-libglvnd-install.sh
   executing: '/bin/sh ./libglvnd_install_checker/check-libglvnd-install.sh'...
   Checking for libglvnd installation.
   Checking libGLdispatch...
   Can't load library libGLdispatch.so.0: libGLdispatch.so.0: cannot open shared object file: No such file or directory
Will install libglvnd libraries.
Will install libEGL vendor library config file to /usr/share/glvnd/egl_vendor.d
-> Searching for conflicting files:
-> done.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' (378.13):
   executing: '/sbin/ldconfig'...
-> done.
-> Driver file installation is complete.
-> Installing DKMS kernel module:
ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 378.13 -k 4.10.0-11-generic`: 
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.10.0-11-generic modules....(bad exit status: 2)
ERROR (dkms apport): binary package for nvidia: 378.13 not found
Error! Bad return status for module build on kernel: 4.10.0-11-generic (x86_64)
Consult /var/lib/dkms/nvidia/378.13/build/make.log for more information.
-> error.
ERROR: Failed to install the kernel module through DKMS. No kernel module was installed; please try installing again without DKMS, or check the DKMS logs for more information.
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.

cd ~/Downloads
sudo sh NVIDIA-*.run -x
cd ~/Downloads/NV*13
sudo patch -p1 <<< $(curl https://gist.githubusercontent.com/tpru ... tfile1.txt)




参考文:1：https://devtalk.nvidia.com/default/topi ... rnel-4-10/



Downloads
Training
Ecosystem
Forums

Join
Login

Home > CUDA ZONE > Forums > GPU Unix Graphics > Linux > View Topic
Failed Installed Nvidia With kernel 4.10
Reply
Follow
Drthrax74
Hello everyone,
First of all I have a problem related to installing nvidia driver under ubuntu 16.04 with kernel 4.10.



sudo apt-get update && sudo apt-get upgrade && reboot

#Download Kernel 4.10 (linux-header...all linux-header...amd64 | linux-image...generic)
Wget Http://kernel.ubuntu.com/~kernel-ppa/ma ... 31_all.deb Http://kernel.ubuntu.com/~kernel-ppa/ma ... _amd64.deb Http://kernel.ubuntu.com/~kernel-ppa/ma ... _amd64.deb

#Install kernel
Sudo dpkg -i linux - *. Deb



Reboot

In a TTY console:

Sudo service lightdm stop
Sudo ./Nvidia-....run
reboot





/var/lib/dkms/nvidia/378.13/build/make.log

DKMS make.log for nvidia-378.13 for kernel 4.10.0-041000rc8-generic (x86_64)
mardi 21 février 2017, 18:08:13 (UTC+0100)
make "CC=cc" KBUILD_VERBOSE= -C /lib/modules/4.10.0-041000rc8-generic/build M=/var/lib/dkms/nvidia/378.13/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/4.10.0-041000rc8-generic/build NV_KERNEL_OUTPUT=/lib/modules/4.10.0-041000rc8-generic/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video modules
make[1]*: on entre dans le répertoire «*/usr/src/linux-headers-4.10.0-041000rc8-generic*»
SYMLINK /var/lib/dkms/nvidia/378.13/build/nvidia/nv-kernel.o
SYMLINK /var/lib/dkms/nvidia/378.13/build/nvidia-modeset/nv-modeset-kernel.o
CONFTEST: INIT_WORK
CONFTEST: remap_pfn_range
CONFTEST: follow_pfn
CONFTEST: vmap
CONFTEST: set_pages_uc
CONFTEST: set_memory_uc
CONFTEST: change_page_attr
CONFTEST: set_memory_array_uc
CONFTEST: pci_get_class
CONFTEST: pci_choose_state
CONFTEST: vm_insert_page
CONFTEST: acpi_device_id
CONFTEST: acquire_console_sem
CONFTEST: console_lock
CONFTEST: kmem_cache_create
CONFTEST: on_each_cpu
CONFTEST: smp_call_function
CONFTEST: acpi_evaluate_integer
CONFTEST: ioremap_cache
CONFTEST: ioremap_wc
CONFTEST: acpi_walk_namespace
CONFTEST: pci_dma_mapping_error
CONFTEST: pci_domain_nr
CONFTEST: sg_alloc_table
CONFTEST: sg_init_table
CONFTEST: pci_get_domain_bus_and_slot
CONFTEST: get_num_physpages
CONFTEST: efi_enabled
CONFTEST: proc_create_data
CONFTEST: pde_data
CONFTEST: proc_remove
CONFTEST: pm_vt_switch_required
CONFTEST: drm_driver_has_set_busid
CONFTEST: drm_driver_has_gem_prime_res_obj
CONFTEST: xen_ioemu_inject_msi
CONFTEST: phys_to_dma
CONFTEST: get_dma_ops
CONFTEST: write_cr4
CONFTEST: of_parse_phandle
CONFTEST: for_each_online_node
CONFTEST: node_end_pfn
CONFTEST: pci_bus_address
CONFTEST: pci_stop_and_remove_bus_device
CONFTEST: pci_remove_bus_device
CONFTEST: request_threaded_irq
CONFTEST: remap_page_range
CONFTEST: address_space_init_once
CONFTEST: kbasename
CONFTEST: fatal_signal_pending
CONFTEST: list_cut_position
CONFTEST: vzalloc
CONFTEST: wait_on_bit_lock_argument_count
CONFTEST: bitmap_clear
CONFTEST: usleep_range
CONFTEST: radix_tree_empty
CONFTEST: drm_dev_unref
CONFTEST: drm_reinit_primary_mode_group
CONFTEST: drm_atomic_set_mode_for_crtc
CONFTEST: drm_atomic_clean_old_fb
CONFTEST: get_user_pages_remote
CONFTEST: drm_gem_object_lookup
CONFTEST: drm_atomic_state_free
CONFTEST: i2c_adapter
CONFTEST: irq_handler_t
CONFTEST: pm_message_t
CONFTEST: acpi_device_ops
CONFTEST: acpi_op_remove
CONFTEST: outer_flush_all
CONFTEST: proc_dir_entry
CONFTEST: scatterlist
CONFTEST: sg_table
CONFTEST: file_operations
CONFTEST: vm_operations_struct
CONFTEST: atomic_long_type
CONFTEST: pci_save_state
CONFTEST: file_inode
CONFTEST: task_struct
CONFTEST: kuid_t
CONFTEST: dma_ops
CONFTEST: dma_map_ops
CONFTEST: noncoherent_swiotlb_dma_ops
CONFTEST: vm_fault_present
CONFTEST: fault_flags
CONFTEST: atomic64_type
CONFTEST: address_space
CONFTEST: backing_dev_info
CONFTEST: kernel_write
CONFTEST: strnstr
CONFTEST: iterate_dir
CONFTEST: kstrtoull
CONFTEST: mm_context_t
CONFTEST: vm_fault_has_address
CONFTEST: vm_ops_fault_removed_vma_arg
CONFTEST: drm_bus_present
CONFTEST: drm_bus_has_bus_type
CONFTEST: drm_bus_has_get_irq
CONFTEST: drm_bus_has_get_name
CONFTEST: drm_driver_has_legacy_dev_list
CONFTEST: drm_crtc_state_has_connectors_changed
CONFTEST: drm_init_functions_have_name_arg
CONFTEST: drm_mode_connector_list_update_has_merge_type_bits_arg
CONFTEST: drm_helper_mode_fill_fb_struct_has_const_mode_cmd_arg
CONFTEST: drm_master_drop_has_from_release_arg
CONFTEST: drm_mode_config_funcs_has_atomic_state_alloc
CONFTEST: dom0_kernel_present
CONFTEST: nvidia_vgpu_kvm_build
CONFTEST: drm_available
CONFTEST: nvidia_grid_build
CONFTEST: drm_atomic_available
CONFTEST: drm_atomic_modeset_nonblocking_commit_available
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-frontend.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-instance.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-acpi.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-chrdev.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-gvi.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-dma.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-cray.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-i2c.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-mempool.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-mmap.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-p2p.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-procfs.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-usermap.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-vm.o
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-vtophys.o


/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nvidia_cpu_callback’:
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:213:14: error: ‘CPU_DOWN_FAILED’ undeclared (first use in this function)
case CPU_DOWN_FAILED:
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:213:14: note: each undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:220:14: error: ‘CPU_DOWN_PREPARE’ undeclared (first use in this function)
case CPU_DOWN_PREPARE:
^
In file included from /var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:15:0:
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nv_init_pat_support’:
/var/lib/dkms/nvidia/378.13/build/common/inc/nv-linux.h:391:34: error: implicit declaration of function ‘register_cpu_notifier’ [-Werror=implicit-function-declaration]
#define register_hotcpu_notifier register_cpu_notifier
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:258:17: note: in expansion of macro ‘register_hotcpu_notifier’
if (register_hotcpu_notifier(&nv_hotcpu_nfb) != 0)
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nv_teardown_pat_support’:
/var/lib/dkms/nvidia/378.13/build/common/inc/nv-linux.h:388:36: error: implicit declaration of function ‘unregister_cpu_notifier’ [-Werror=implicit-function-declaration]
#define unregister_hotcpu_notifier unregister_cpu_notifier
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:283:9: note: in expansion of macro ‘unregister_hotcpu_notifier’
unregister_hotcpu_notifier(&nv_hotcpu_nfb);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:294*: la recette pour la cible «*/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.o*» a échouée
make[2]: *** [/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.o] Erreur 1
make[2]: *** Attente des tâches non terminées....
Makefile:1496*: la recette pour la cible «*_module_/var/lib/dkms/nvidia/378.13/build*» a échouée
make[1]: *** [_module_/var/lib/dkms/nvidia/378.13/build] Erreur 2
make[1]*: on quitte le répertoire «*/usr/src/linux-headers-4.10.0-041000rc8-generic*»
Makefile:81*: la recette pour la cible «*modules*» a échouée
make: *** [modules] Erreur 2

#1
Posted 02/21/2017 08:14 PM
towo
If you would use the search function, you would see, that it's well known and a crude patch is available.

#2
Posted 02/21/2017 09:32 PM
Drthrax74
hello,

i successfull patching !

Infos Patch:

Patch for driver: nvidia-378.09
GIT: https://gist.github.com/tpruzina



Folder: (Very important)

~/Downloads/NVIDIA-Linux-x86_64-378.09/ <= Folder when your Extract (by command)
~/Downloads/NVIDIA-Linux-x86_64-378.09.run
~/Downloads/nvidia-378.09-kernel-4.10-rc4.patch



Downloads + Permission: (French)

cd ~/Downloads
wget https://gist.githubusercontent.com/tpru ... -rc4.patch
wget http://fr.download.nvidia.com/XFree86/L ... 378.09.run
sudo chmod +x NVIDIA-Linux-x86_64-378.09.run



Extracted Run: (*.run -x)

./NVIDIA-*.run -x



Apply patch

patch -p0 < ./nvidia-*.patch



My Logs:

patching file NVIDIA-Linux-x86_64-378.09/kernel/common/inc/nv-linux.h
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia/nv-p2p.c
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-drm/nvidia-drm-fence.c
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-drm/nvidia-drm-gem.c
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-drm/nvidia-drm-gem.h
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-drm/nvidia-drm-modeset.c
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-drm/nvidia-drm-priv.h
patching file NVIDIA-Linux-x86_64-378.09/kernel/nvidia-uvm/uvm8_test.c




Installed: Press CTRl+ALT+F3 (or F4)

Boot on kernel 4.10 (good version to patch Ex: nvidia-378.09-kernel-4.10-rc4.patch is kernel 4.10 RC4)
sudo service lightdm/gdm stop
sudo ./nvidia-installer
sudo servcice lightdm/gdm start
reboot

#3
Posted 02/22/2017 01:20 AM
leigh123linux

said:If you would use the search function, you would see, that it's well known and a crude patch is available.



ubuntu have a proper patch


https://pkgs.rpmfusion.org/cgit/nonfree ... 4.10.patch

#4
Posted 02/22/2017 08:07 AM
Drthrax74
Hello,
I would like to point out that only the Mate interface works with this driver.
Cinnamon, unity and xfce plant

#5
Posted 02/22/2017 10:44 AM
Drthrax74
Hello,
for apply patch.

Download pilote (permission + extraction)

wget http://fr.download.nvidia.com/XFree86/L ... 375.39.run
sudo chmod +x ./NVIDIA-Linux-x86_64-375.39.run
./NVIDIA-Linux-x86_64-375.39.run -x



Download Patch

cd ./NVIDIA-Linux-x86_64-375.39
wget https://pkgs.rpmfusion.org/cgit/nonfree ... 4.10.patch



Apply patch:

patch -p1 < kernel_4.10.patch



Installation

TTY (CTRL+ALT+F4)
sudo service lightdm/gdm stop
./NVIDIA-Linux-x86_64-375.39/nvidia-install
sudo service lightdm/gdm start
reboot



LOG:

m
arc:~/Bureau/NVIDIA-Linux-x86_64-375.39$ patch -p1 < kernel_4.10.patch
patching file kernel/common/inc/nv-mm.h
patching file kernel/nvidia-drm/nvidia-drm-fence.c
patching file kernel/nvidia-drm/nvidia-drm-gem.h
patching file kernel/nvidia-drm/nvidia-drm-priv.h
patching file kernel/nvidia/nv-pat.c

#6
Posted 02/22/2017 11:54 AM
Scroll To Top

Add Reply

Please Login | Register to add a comment.
Receive email notifications when someone replies to this topic
Reply
Preview

COMPUTEWORKS
GAMEWORKS
JETPACK
DESIGNWORKS

GET STARTED

About CUDA
Parallel Computing
CUDA Toolkit
CUDACasts

LEARN MORE

Training and Courseware
Tools and Ecosystem
Academic Collaboration
Documentation

GET INVOLVED

Forums
Parallel Forall Blog
Developer Program
Contact Us

Copyright © 2017 NVIDIA Corporation | Legal Information | Privacy Policy | Support




参考文章2：https://devtalk.nvidia.com/default/topi ... s-master-/


CPU_HOTPLUG workaround still in, care if you need hotplug/hibernate support.

https://gist.github.com/tpruzina/3e36f7 ... 53b8d99b02

patch -p1 <<< $(curl https://gist.githubusercontent.com/tpru ... tfile1.txt)

#1
Posted 02/15/2017 01:33 AM