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

243750496 · #331

asus x99-a manual PCIE Lane Distribution
或搜索asus x99-a specification PCIE Lane Distribution
即可搜到关于expansion slot 交火分配模式的说明

243750496 · #332

linux zip 解压乱码
请用以下命令：
unzip -O cp936 *.zip

243750496 · #333

blender教程
https://pan.baidu.com/s/1eS7kcJw

243750496 · #334

sudo apt-get install epiphany-browser
wget -O brave.deb https://laptop-updates.brave.com/latest/dev/ubuntu64
sudo dpkg -i brave.deb
开源浏览器
sudo mkdir /usr/lib/pepperflashplugin-nonfree/
sudo cp /usr/lib/adobe-flashplugin/manifest.json /usr/lib/pepperflashplugin-nonfree/
sudo cp /usr/lib/adobe-flashplugin/libpepflashplayer.so /usr/lib/pepperflashplugin-nonfree/
然后就可以再brave中启用flash插件了

243750496 · #335

51CTO
好用的学习编程的软件（ios客户端）
ios应用摩拜单车

243750496 · #336

243750496 · #337

linux查看cpu温度
2013-04-05 21:23阅读：7,292
一、安装
sudo apt-get install lm-sensors
二、查看
linux@cdyemail:~$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +33.6°C (high = +70.0°C)
(crit = +72.0°C, hyst = +70.0°C)
radeon-pci-0100
Adapter: PCI adapter
temp1: +54.0°C

243750496 · #338

AG06调音台参数
1搞怪版：

2播音版（带鼻音）：

3播音清亮版（弱化鼻音）

243750496 · #339

荔枝订阅号
FM1839515
微信公众号
ATC243750496
优酷自频道
http://i.youku.com/i/UMjU2MjEzMzU2?spm= ... rap.DD~8~A

https://pan.baidu.com/s/1bpxgUdx
https://pan.baidu.com/s/1hr8RM88
https://pan.baidu.com/s/1kVc7Rq3
https://pan.baidu.com/s/1hsgI5Oo
https://pan.baidu.com/s/1dFvbdvj
https://pan.baidu.com/s/1c1ZzmUW
https://pan.baidu.com/s/1gfoSiD9

服务器刀片.xls: (8.5 KiB) 已下载 83 次

https://pan.baidu.com/s/1hrPNF4C
https://pan.baidu.com/s/1b0X8f0

243750496 · #340

sudo add-apt-repository ppa:openshot.developers/ppa
sudo apt-get update
sudo apt-get install openshot-qt pitivi

243750496 · #341

sudo add-apt-repository ppa:budgie-remix/ppa
sudo apt-get update
sudo apt-get install budgie-desktop budgie-welcome

243750496 · #342

Ryzen 1800X +微星（MSI）X370 XPOWER GAMING TITANIUM主板(AM4)+双新泰坦(如果是京东的能换新就换新尽管可能购买这个服务需要多花点钱399（第一年换新）+72（第二年换新）)
Ryzen 1800X
http://item.jd.com/3885175.html
微星（MSI）X370 XPOWER GAMING TITANIUM主板(AM4)
http://item.jd.com/4482420.html
装机：
酷冷至尊官方旗舰店的一体式水冷（AM4）：
https://detail.tmall.com/item.htm?id=54 ... dmg8j26111
注：用手机买G240，电脑上只能看到G120 3月6日才开售
如急买请打开京东：
https://item.jd.com/3837765.html
酷冷至尊官方旗舰店的显卡千斤顶支架
https://detail.tmall.com/item.htm?id=54 ... 3453954099
酷冷至尊官方旗舰店MasterCase Maker 5机箱配件组件MasterCase 5模组配件
https://detail.tmall.com/item.htm?id=53 ... 63:6536025
如果买不到红光风扇（需一次买3个）请打开京东：
https://item.jd.com/2997561.html
三星960PRO M2固态
https://item.taobao.com/item.htm?spm=a1 ... dmg8j26111
海盗船官方企业店的1500W电源
https://item.taobao.com/item.htm?spm=a1 ... dmg8j26111
海盗船官方企业店的3000MHZ内存条16Gx2=32G
https://item.taobao.com/item.htm?spm=a1 ... dmg8j26111
LG 29UC88-B 29寸IPS曲面窄边框液晶显示器21:9 2K 包完美
https://item.taobao.com/item.htm?spm=a1 ... dmg8j26111
内存散热马甲片：
https://detail.tmall.com/item.htm?id=52 ... dmg8j26111
英特尔台式机内置wifi蓝牙模块
https://item.taobao.com/item.htm?spm=a1 ... d0ltsk3049
新泰坦
https://item.taobao.com/item.htm?spm=a1 ... d0ltskf8dd

电脑电源线（买0.75平方直头5m的2根）：
https://detail.tmall.com/item.htm?id=42 ... d0ltsk12e1
原装sli桥（金手指）
https://item.taobao.com/item.htm?spm=a1 ... d0ltskafea
HDMI线（5m圆线）：
https://detail.tmall.com/item.htm?id=12 ... d0ltsk91d1

243750496 · #343

This will be a step-by-step tutorial on how to Install nVidia drivers, enabling SLI (if applicable) & control the GPU-fan speed at startup!

1. Installation of Drivers
2. Enabling SLI
3. Fan control at boot
==========================

1. INSTALLATION OF DRIVERS:
For installation of STABLE drivers, add the following PPA to your system
CODE: SELECT ALL
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu trusty main
deb-src http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu trusty main

- Open up your terminal & fun the following commands,
CODE: SELECT ALL
sudo apt-get update

and then once that's completed,
CODE: SELECT ALL
sudo apt-get upgrade && sudo apt-get dist-upgrade

Once everything is done, close it out and open up your "Driver Manager" and select the version you want.
STABLE = nVidia-352.63
--You can select nVidia-352-updates, if you want to... but it's less stable.

Once you've chosen, let it install and complete (this may take a few minutes) then reboot when completed.
A. In terminal run:
CODE: SELECT ALL
sudo nvidia-xconfig

B. In terminal run:
CODE: SELECT ALL
sudo nvidia-xconfig --cool-bits=12

C. In terminal run:
CODE: SELECT ALL
sudo reboot

D. Once booted, run:
CODE: SELECT ALL
sudo nvidia-settings

E. Click on x-server and set up your display(s), then apply.
F. Click "save to x-configuration file.
G. Click THERMAL SETTINGS under your video card
H. Click AGREE, scroll to bottom, then close.
I. adjust fan to desired speed.
J. Close settings window & terminal.

====================================================
====================================================

2. Setting up SLI
- begin by getting everything closed out, so your DE is running.
- open your terminal, and enter
CODE: SELECT ALL
sudo nvidia-xconfig --sli=On

A. a new xorg.conf will be created... this is normal. Accept the new build and continue.
B. Once that's done, enter
CODE: SELECT ALL
sudo reboot

C. After reboot, open your file-browser (nemo) and head to /etc/X11
D. As root, open xorg.conf and in (Section "Screen") change SLI from off to On. (big O, little n)
E. Save and close the file.

-- continue to next section for FAN CONTROL.

====================================================
====================================================

3. FAN CONTROL AT START-UP:
--- If you have done all of the above in this tutorial, then you do not need to do the first step in this section.

A. In terminal run: "sudo nvidia-xconfig --cool-bits=12"
B. Navigate to ~/.config/autostart/ now create a document named "nvidia-fan-speed.desktop"
C. open the file with a text editor.
D. so there are no fowl-ups, copy and paste the text below into the file.
E. replace XX with the fan speed you would like. 10-100, numerical value only, no percent sign needed.

CODE: SELECT ALL
[Desktop Entry]
Type=Application
Exec=nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUCurrentFanSpeed=XX"
X-GNOME-Autostart-enabled=true
Name=nvidia-fan-speed

F. To add in the second GPU-fan, add the code below into the file.

CODE: SELECT ALL
[Desktop Entry]
Type=Application
Exec=nvidia-settings -a "[gpu:1]/GPUFanControlState=1" -a "[fan:1]/GPUCurrentFanSpeed=XX"
X-GNOME-Autostart-enabled=true
Name=nvidia-fan-speed

G. save and exit the file.
H. log out of your system, then back in...
I. PROFIT!

243750496 · #344

Whew, I know that’s a long title for a post, but I wanted to make sure that I mentioned every term so that people having the same problem could readily find the post that explains what solved it for me. For some time now (ever since the 346.x series [340.76, which was the last driver that worked for me, was released on 27 January 2015]), I have had a problem with the NVIDIA Linux Display Drivers (known as nvidia-drivers in Gentoo Linux). The problem that I’ve experienced is that the newer drivers would, upon starting an X session, immediately clock up to Performance Level 2 or 3 within PowerMizer.
Before using these newer drivers, the Performance Level would only increase when it was really required (3D rendering, HD video playback, et cetera). I probably wouldn’t have even noticed that the Performance Level was changing, except that it would cause the GPU fan to spin faster, which was noticeably louder in my office.
After scouring the interwebs, I found that I was not the only person to have this problem. For reference, see this article, and this one about locking to certain Performance Levels. However, I wasn’t able to find a solution for the exact problem that I was having. If you look at the screenshot below, you’ll see that the Performance Level is set at 2 which was causing the card to run quite hot (79°C) even when it wasn’t being pushed.
NVIDIA Linux drivers stuck on high Performance Level in Xorg
Click to enlarge
It turns out that I needed to add some options to my X Server Configuration. Unfortunately, I was originally making changes in /etc/X11/xorg.conf, but they weren’t being honoured. I added the following lines to /etc/X11/xorg.conf.d/20-nvidia.conf, and the changes took effect:

Section "Device"
Identifier "Device 0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 470"
Option "RegistryDwords" "PowerMizerEnable=0x1; PowerMizerDefaultAC=0x3;"
EndSection
The portion in bold (the RegistryDwords option) was what ultimately fixed the problem for me. More information about the NVIDIA drivers can be found in their README and Installation Guide, and in particular, these settings are described on the X configuration options page. The PowerMizerDefaultAC setting may seem like it is for laptops that are plugged in to AC power, but as this system was a desktop, I found that it was always seen as being “plugged in to AC power.”
As you can see from the screenshots below, these settings did indeed fix the PowerMizer Performance Levels and subsequent temperatures for me:
NVIDIA Linux drivers Performance Level after Xorg settings
Click to enlarge
Whilst I was adding X configuration options, I also noticed that Coolbits (search for “Coolbits” on that page) were supported with the Linux driver. Here’s the excerpt about Coolbits for version 364.19 of the NVIDIA Linux driver:
Option “Coolbits” “integer”
Enables various unsupported features, such as support for GPU clock manipulation in the NV-CONTROL X extension. This option accepts a bit mask of features to enable.
WARNING: this may cause system damage and void warranties. This utility can run your computer system out of the manufacturer’s design specifications, including, but not limited to: higher system voltages, above normal temperatures, excessive frequencies, and changes to BIOS that may corrupt the BIOS. Your computer’s operating system may hang and result in data loss or corrupted images. Depending on the manufacturer of your computer system, the computer system, hardware and software warranties may be voided, and you may not receive any further manufacturer support. NVIDIA does not provide customer service support for the Coolbits option. It is for these reasons that absolutely no warranty or guarantee is either express or implied. Before enabling and using, you should determine the suitability of the utility for your intended use, and you shall assume all responsibility in connection therewith.
When “2” (Bit 1) is set in the “Coolbits” option value, the NVIDIA driver will attempt to initialize SLI when using GPUs with different amounts of video memory.
When “4” (Bit 2) is set in the “Coolbits” option value, the nvidia-settings Thermal Monitor page will allow configuration of GPU fan speed, on graphics boards with programmable fan capability.
When “8” (Bit 3) is set in the “Coolbits” option value, the PowerMizer page in the nvidia-settings control panel will display a table that allows setting per-clock domain and per-performance level offsets to apply to clock values. This is allowed on certain GeForce GPUs. Not all clock domains or performance levels may be modified.
When “16” (Bit 4) is set in the “Coolbits” option value, the nvidia-settings command line interface allows setting GPU overvoltage. This is allowed on certain GeForce GPUs.
When this option is set for an X screen, it will be applied to all X screens running on the same GPU.
The default for this option is 0 (unsupported features are disabled).
I found that I would personally like to have the options enabled by “4” and “8”, and that one can combine Coolbits by simply adding them together. For instance, the ones I wanted (“4” and “8”) added up to “12”, so that’s what I put in my configuration:

Section "Device"
Identifier "Device 0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 470"
Option "Coolbits" "12"
Option "RegistryDwords" "PowerMizerEnable=0x1; PowerMizerDefaultAC=0x3;"
EndSection
and that resulted in the following options being available within the nvidia-settings utility:
NVIDIA Linux drivers Performance Level after Xorg settings
Click to enlarge
Though the Coolbits portions aren’t required to fix the problems that I was having, I find them to be helpful for maintenance tasks and configurations. I hope, if you’re having problems with the NVIDIA drivers, that these instructions help give you a better understanding of how to workaround any issues you may face. Feel free to comment if you have any questions, and we’ll see if we can work through them.
Cheers,
Zach

243750496 · #345

Contents

Introduction
NVIDIA drivers provided by the Ubuntu repositories
Installation
Removing Nouveau (advanced/expert users)
Installation without X / from the console
Ubuntu 14.04 and up
Ubuntu 12.04
Troubleshooting
Installation Fails
Driver Not Active
Boot Splash Screen Issues
Can't Save Settings
Some text (for example in menu) is rendered incorrect
Suspend/Hibernation
Onboard Graphics Chipset
Low/Missing Screen Resolutions
Low Resolution Icons and OS Features
Screen Blanks/Monitor Turns Off
Problems with Video Playback
Creating Application Profiles
SLI / Multi-GPU on Ubuntu(and Linux in general)
SLI Application Profiles for ID Tech 4 Engine Games on Ubuntu (and Linux in general)
Filing bug reports
NVIDIA driver from the Ubuntu repositories
Reporting an upstream bug
See Also
Introduction
By default Ubuntu will use the open source video driver Nouveau for your NVIDIA graphics card. This driver lacks support for 3D acceleration and may not work with the very latest video cards or technologies from NVIDIA.
An alternative to Nouveau are the closed source NVIDIA drivers, which are developed by NVIDIA. This driver provides excellent 3D acceleration and video card support.
NVIDIA drivers provided by the Ubuntu repositories
What package one would use depends on the version of Ubuntu one is using, and what graphics card one has installed.
nvidia-graphics-drivers-375

nvidia-graphics-drivers-367

nvidia-graphics-drivers-361

nvidia-graphics-drivers-352-updates

nvidia-graphics-drivers-352

nvidia-graphics-drivers-346-updates

nvidia-graphics-drivers-346

nvidia-graphics-drivers-340-updates

nvidia-graphics-drivers-340

nvidia-graphics-drivers-331-updates

nvidia-graphics-drivers-331

nvidia-graphics-drivers-319-updates

nvidia-graphics-drivers-319

nvidia-graphics-drivers-310-updates

nvidia-graphics-drivers-304-updates

nvidia-graphics-drivers-304

nvidia-graphics-drivers-173

Precise only

nvidia-graphics-drivers-experimental-310

nvidia-graphics-drivers

nvidia-graphics-drivers-updates

nvidia-graphics-drivers-96

nvidia-graphics-drivers-tegra

Installation
Usually you will see a notification and/or an icon in the top panel, reminding you that restricted drivers are available.
restricted_drivers.jpg

By clicking the icon you will be taken to a dialog where you can choose which version you want to install, choose the recommended driver.
drivers_dialog.png

If you are using an older version of Ubuntu, or if you aren't notified about additional drivers, you can launch the installation yourself.
Go to Software & Updates -> Additional Drivers
Once the drivers are downloaded and installed, reboot your computer.
Note: In older version you had to go to System -> Administration -> Additional Drivers

Note: In older version of Ubuntu, Additional Drivers are called Hardware Drivers.

Note: In older version of Ubuntu, newer graphic adapters may not be supported with the repositories provided driver.

Note: In newer version of Ubuntu, older graphic adapters may not be supported with the repositories provided driver.

Removing Nouveau (advanced/expert users)
Nouveau, an open source driver, is installed by default. It's possible to remove it completely, but it is not necessary and therefore not recommended.
If you still desire to remove it, you can do so by entering the following command in a terminal:
sudo apt-get --purge remove xserver-xorg-video-nouveau
Installation without X / from the console
Ubuntu 14.04 and up
The jockey-text command was removed with the release of Ubuntu 14.04. You can now use ubuntu-drivers to get the list of packages for each driver, and then install the packages using apt-get. For example:
sudo ubuntu-drivers devices

== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==

vendor : NVIDIA Corporation
modalias : pci:v000010DEd00000DDAsv000017AAsd000021D1bc03sc00i00
model : GF106GLM [Quadro 2000M]
driver : xserver-xorg-video-nouveau - distro free builtin
driver : nvidia-304-updates - distro non-free
driver : nvidia-304 - distro non-free
driver : nvidia-331 - distro non-free recommended
driver : nvidia-331-updates - distro non-free

sudo apt-get install nvidia-331
Ubuntu 12.04
If you need to change drivers without the use of the X GUI, perhaps because those drivers are not installed, you can with the jockey-text command. For example:
jockey-text --help
jockey-text -l
jockey-text -e xorg:nvidia_current
Troubleshooting
Installation Fails
If the restricted driver remains unactivated after attempting to activate it in the Additional Drivers dialog, you may not have the appropriate linux headers installed to compile the driver. Ensure that the linux-headers-XXX and linux-restricted-modules-XXX packages are installed, where XXX matches the version of the kernel you are using.
If the activation hangs on download/install dialog, you can install the driver using System -> Administration -> Synaptic Package Manager, make sure you pick the latest driver version recommended by the Additional Drivers tool and all its dependencies. Then go to the Additional Drivers tool and activate the driver you just installed.
Driver Not Active
X has not been configured to use the new driver. Open a terminal, run sudo nvidia-xconfig, and restart X (reboot works).
If you have full disk encryption enabled you have to run the command
sudo update-initramfs -u
Boot Splash Screen Issues
Open up a Terminal and install the Startup-Manager:
sudo apt-get install startupmanager
Launch the Startup Manager from System -> Administration -> Startup-Manager.
In the Boot options tab, change the resolution to something your monitor can handle (1024x768 is usually enough for the boot screen to look nice).
Change the color depth to 24 bits and press the Close button, reboot your system.
Can't Save Settings
nvidia-settings can't write to xorg.conf if it hasn't been started with administration privileges. Make sure you start nvidia-settings with the following command:
gksudo nvidia-settings
Some text (for example in menu) is rendered incorrect
With a Ge Force 7600, after installation of the nvidia driver in Ubuntu 14.04 some text and icons are rendered incorrectly, sometimes content is displayed distorted in a 囗囗囗囗囗囗囗囗 instead of a rectanglar window, and X resets intermittently.
Using nouveau the XGA resolution 1024x768 is configured and works. However, manually changing to a different resolution with xrandr, etc. fails.
In order to address these issues, install nvidia-304-updates driver, and change the resolution from auto to something different in nvidia X server settings.

Suspend/Hibernation
If you use an old NVIDIA driver, hibernation & suspend may not work, there is a workaround however.
We need to edit xorg.conf, open a terminal and enter the following command:
gksudo gedit /etc/X11/xorg.conf
In the section called Section "Device" add Option "NvAGP" "1", you should end up with something like this:
Section "Device"
Identifier "my id"
Driver "my dr"
VendorName "my vendor"
BoardName "my board name"
Option "NvAGP" "1"
EndSection
Blacklist the intel_agp module from being loaded by the kernel. This is done by editing blacklist.conf, open a terminal and type:
gksudo gedit /etc/modprobe.d/blacklist.conf
Then add the following line:
blacklist intel_agp
Reboot your system.
Onboard Graphics Chipset
See this article.

Low/Missing Screen Resolutions
Often screen resolutions on offer are far lower than those offered with the open source driver. The NVIDIA binary driver seems to be very weak at reliably probing this information from the monitor and relies on additional information in xorg.conf.
To fix this you can add more resolutions by entering the following in a terminal:
xrandr --addmode S-video ...
Replace the dots with the desired resolution. For further details and potential workarounds see X config resolutions.
Low Resolution Icons and OS Features
If you have problems with low resolution icons, shortcuts and menus placed strangely, and especially desktop size not matching your monitor, this may be due to a bug with multiple monitor setup. If you've previously setup a second monitor and have it plugged in but not turned on, Ubuntu/Xubuntu may be counfounded by this. The simplest method to resolve this is to remove the redundant cable from your machine and reboot. Additionally, install arandr (GUI for xrandr editing) and setup two profiles, one with the secondary monitor and one without. Removal of redundant cable when not in use is nonetheless still recommended. This problem was experienced in Ubuntu and Xubuntu.
Screen Blanks/Monitor Turns Off
Using a laptop with a GeForce Go card, or connecting the sole display via DVI on a dual-head system sometimes results in the screen not receiving a picture. This is caused by the driver outputting video to the VGA port on the graphics card, instead of DVI.
The usual hint that you have this problem is when you hear the startup sound but nothing appears on the screen. If you do not hear any sound, you are more than likely experiencing unrelated problems.
This is a bug about displays on digital outputs being blank when using NVIDIA driver, and can be resolved by editing your /etc/X11/xorg.conf file:
Switch to the console by using ctrl+alt+F1, or reboot and select recovery mode from the GRUB menu.
Open and edit xorg.conf like this: sudo nano /etc/X11/xorg.conf.
Find the line that says: Section "Screen"
Insert a new line that says Option "UseDisplayDevice" "DFP".
Save the file. If you had to restart into recovery mode, type reboot, otherwise restart your display using sudo /etc/init.d/gdm restart.
Problems with Video Playback
If you have problems with video playback in e.g. mplayer, gxine, or mythtv frontend with a legacy card, it may be due to too high a color depth (e.g. using NT6 Vanta/Vanta LT "nvidia" driver, I experienced flickering vertical bars & blue screen flashing). To fix this, manually edit /etc/X11/xorg.conf and change DefaultDepth to 16.
Creating Application Profiles
nVidia X Server Settings has an application profiles editor much like the Windows counterpart (nVidia Control Pannel) that allows you to set special parameters per-application. For manual text file editing read the Application Profiles ReadMe included in the nVidia for Linux Driver ReadMe. It is quite detailed on where the file locations are, how to enable or disable application profiles completely and what arguments you can use.
For using the nVidia X Server Settings? Follow this basic guide (I'll use Quake 4 as an example)
Open up nVidia X Server Settings
Go to "Application Profiles"
Make sure the check box is selected for "Enable Application Profiles" otherwise the Application Profiles won't work.
Click the Add (+) Button for detection rules to "Add a Rule"
Make sure for "Rule Pattern" the feature will be used if "Process Name (procname)" is selected
For "Matches this string" put in the application name (in this example, quake4)
For "Rule Profile" click on "New Profile"
In the new popup window, change the profile name to something easy to reference to (in this example I'll name it the same as quake4app)
Now, enter any profile settings. You can find the full list in the Application Profiles ReadMe. (in this example, we would select "GLDoom3" from the drop-down menu list to create an SLI Profile for ID Tech 4 Engine-based games)
Change the value to whatever you'd like. (in this example, we would set "GLDoom3" Boolean value to "true")
Save and close the open windows for the Application profile and the detection rule. (The Add (+) button in the bottom right next to the cancel logo)
We've now created an application profile. One of these days I will list the different process names for ID Tech 4 engine-based games for Linux and their procname's so anyone could easily create working SLI Profiles for these games. I've attempted to use GLDoom3 on other game engines such as the Spark Engine used by Natural Selection 2... sadly it only made the game run at the speed of one GPU, still not enabling the second one to work in SLI outside the ID Tech 4 Engine...
For which application profile variables one can use please refer to OpenGL Environment Variables in the nVidia for Linux driver's ReadMe (link current to 343.22)
NOTE: The OpenGL Environment Variables are not all listed in the ReadMe. GLDoom3 for example is only discussed in the SLI portion of the driver's ReadMe.
SLI / Multi-GPU on Ubuntu(and Linux in general)
NOTE: This was last tested with nVidia 343.13 drivers... despite these drivers adding support for the GTX Titan Z, a Multi-GPU videocard it still does not support SLI... so the GTX Titan Z is reduced to a single GTX Titan in Linux... same goes for other nVidia Multi-GPU cards such as the GTX 690. sad
For more information, please read SLI & Multi-GPU section of the ReadMe included with nVidia's drivers for Linux.
Current limitations (last tested on 343.22) on nVidia's drivers are as follows:
Linux only support SLI & Multi-GPU (Two-GPUs-on-one cards such as the GTX 690) can be enabled, but only via commant promts in the Terminal.
Only works on desktop platforms, SLI on mobile GPU's is unsupported.
Only ID Tech 4 Engine games are officially supported in SLI by creating an "Application Profile" with GLDoom3 set to "true". Games on ID Tech 4 engine includes Quake 4, Enemy Territory: Quake Wars, Doom 3, Prey and Open Source games on ID Tech 4 include The Dark Mod.
GPUs with ECC enabled may not be used in an SLI configuration.
SLI on Quadro-based graphics cards always requires a video bridge.
TwinView is also not supported with SLI or Multi-GPU. Only one display can be used when SLI or Multi-GPU is enabled, with the exception of Mosaic.
If X is configured to use multiple screens and screen 0 has SLI or Multi-GPU enabled, the other screens configured to use the nvidia driver will be disabled. Note that if SLI or Multi-GPU is enabled, the GPUs used by that configuration will be unavailable for single GPU rendering.
Alternate Frame Rendering (AFR) and Split Frame Rendering (SFR) are supported in Linux. AFR2 is not supported nor is it planned for Linux.
Alternate Frame Rendering (AFR) is supported. This SLI mode uses each card to render one frame then the next card renders the following. For example, in two-way AFR, GPU1 renders frames 1, 3, 5, etc. and GPU2 renders 2, 4, 6, etc. Outside of the ID Tech 4 engine Alternate Frame Rendering does not work on any card other than the first which causes framerates to drop by 50%. This is a known bug and nVidia are currently working on this issue.
SLI Profiles are NOT included with the drivers unlike the Windows version of the nVidia drivers. They must be manually created for ID Tech 4 Engine-based games. To learn how to make them yourself, please read the Creating Application Profiles section of this wiki page.
Split Frame Rendering (SFR) is also supported. This mode uses the first GPU to render the top half of the screen, and the second GPU to render the bottom half. This mode also does not function correctly outside of ID Tech 4. It will still render the full screen, but only at the speed of a single GPU.
Alternate Frame Rendering mode 2 (AFR2) is NOT supported in Linux. This mode is opposite of Alternate Frame rendering by instead using the last GPU as the primary, and every GPU above it as the next in line. For example, in three-way AFR2? GPU3 renders frames 1, 4, 7, etc. GPU2 renders frames 2, 5, 8, etc. and GPU1 renders frames 3, 6, 9, etc. In Windows, AFR2 is the preferred SLI mode as it tends to yeild higher performance over AFR. My theory is because GPU1 is the primary card for video out, it uses a different GPU for the primary calculations it better balances the work load. I have not seen any documentation as to the specific reason AFR2 performs better.
Despite what was mentioned above, if you wish to try SLI here's how to enable it via the terminal:
Open up Terminal.
Use the following command of your choice: sli=on (enables SLI) sli=auto (Allows nvidia-xconfig to automatically enable SLI if it detects an SLI-ready setup) sli=afr (enables SLI in AFR mode) sli=sfr (enables SLI in SFR mode).
Terminal commands:
sudo nvidia-xconfig -sli=on
sudo nvidia-xconfig -sli=auto
sudo nvidia-xconfig -sli=afr
sudo nvidia-xconfig -sli=sfr
sudo nvidia-xconfig -sli=off
Put in your password
Reboot Ubuntu (sudo reboot via terminal or via the GUI)
Open up the "nVidia X Server Settings" program
Select any GPU in the list, and look for the screen output. If SLI is indeed enabled? It will say "(SLI)" at the end of the detected screen output.
The Only difference is if you have a Multi-GPU (such as the GTX 690) you change the argument of sli to multigpu. Terminal commands:
sudo nvidia-xconfig -multigpu=on
sudo nvidia-xconfig -multigpu=auto
sudo nvidia-xconfig -multigpu=afr
sudo nvidia-xconfig -multigpu=sfr
sudo nvidia-xconfig -multigpu=off
If you have Multi-GPU cards in your system in SLI (such as two GTX 690's with the appropriate SLI bridge) you just have to mix the commands together.Terminal commands:
sudo nvidia-xconfig -sli=on -multigpu=on
sudo nvidia-xconfig -sli=auto -multigpu=auto
sudo nvidia-xconfig -sli=afr -multigpu=afr
sudo nvidia-xconfig -sli=sfr -multigpu=sfr
sudo nvidia-xconfig -sli=off -multigpu=off
SLI Application Profiles for ID Tech 4 Engine Games on Ubuntu (and Linux in general)
The Application profile examples I have below are for:
Enemy Territory: Quake Wars (etqw-rthread.x86 & etqw.86)
Doom III (doom.x86)
Quake IV (quake4smp.x86 & quake4)
Prey (prey.x86)
The Dark Mod (thedarkmod.x86)
NOTE: This list was compiled with NVIDIA 343 drivers.
Essentially, just enable "GLDoom3" and also "GLThreadedOptimizations". One may also setup an "AlwaysOn" profile setting for "GLThreadedOptimizations" as an example of settings you can always have activated. It's up to you to leave it on or disable it since there's the chance it can affect your OpenGL performance negatively.
To use these application profiles, one way is via the file manager.
Open your File Manager.
go to your "Home" folder.
Tap "CTRL" and "H" to toggle hidden folders and files.
Go into the ".nv" folder.
Open the file "nvidia-application-profiles-rc" in a text editor (or if it doesn't exist, create the text file).
Copy and paste the following into the file and save (the last part with "alwaysapplied" is optional but is recommended for enabling Threaded Optimizations on all OpenGL apps). Some older apps might have compatibility issues but you can always make a custom application profile with the "GLThreadedOptimizations" set to "false"):
{
"rules": [
{
"pattern": {
"feature": "procname",
"matches": "prey.x86"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "procname",
"matches": "etqw-rthread.x86"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "procname",
"matches": "etqw.86"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "procname",
"matches": "quake4smp.x86"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "procname",
"matches": "quake4"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "procname",
"matches": "thedarkmod.x86"
},
"profile": "idtech4app"
},
{
"pattern": {
"feature": "true",
"matches": "alwayson"
},
"profile": "alwaysapplies"
}
],
"profiles": [
{
"name": "idtech4app",
"settings": [
{
"key": "GLDoom3",
"value": true
},
{
"key": "GLThreadedOptimizations",
"value": true
}
]
},
{
"name": "alwaysapplies",
"settings": [
{
"key": "GLThreadedOptimizations",
"value": true
}
]
}
]
}
Save and exit.
Open up the "nVidia X Server Settings" application.
Browse to "Application Profiles".
if the "nvidia-application-profiles-rc" didn't properly load the modified configuration? Click the "Reload" button. It looks like a green circle with two circular arrows.
Filing bug reports
NVIDIA driver from the Ubuntu repositories
If one is using a NVIDIA driver package from a supported Ubuntu repository (not downloaded from NVIDIA's website directly), first one would want to file a new report via a terminal:
ubuntu-bug xorg
Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.
As well, please ensure all of the below are tested and provided:
Is this an issue with the latest version downloaded directly from NVIDIA's website?
Did this happen with a prior version of the NVIDIA driver?
Did this issue happen in a prior release of Ubuntu?
If the issue is not reproducible in the version from NVIDIA's website, then the issue would be a downstream (Ubuntu) issue.
If the issue is reproducible in the version from NVIDIA's website, the next step is to report a bug upstream as per below.
Reporting an upstream bug
If either your downstream bug report is marked Triaged, or you are using the drivers from NVIDIA's website directly, one will want to file a bug report via the NVIDIA Bug Submissions website.
Product - This is going to be either GeForce Graphics or Quadro Graphics.
Choose OS - Linux/Other Unix
Product Name - This may be gathered by executing at a terminal
lspci -vvnn | grep "VGA "
Driver Version - This may be gathered by executing at a terminal:
cat /var/log/dmesg | grep -i nvidia
Question - This is where one would put click-for-click steps on how to reproduce this problem verbatim, as well as your operating system information gathered from a terminal:
lsb_release -rd
uname -a
Next, one would want to contact NVIDIA customer care via Live Chat in order to identify a WORKAROUND, and generate a trackable case number regarding your problem.
See Also
NvidiaManual - Guide to installing the official NVIDIA driver from the NVIDIA website on Ubuntu. Explains the drawbacks and benefits of manual installation and how to safely avoid conflicts with the Ubuntu provided NVIDIA binary drivers.
NvidiaMultiMonitors

DynamicMultiMonitor

NvidiaOnSonyLaptop

currently open NVIDIA binary driver bugs in launchpad - open bugs
www.nvidia.com NVIDIA's homepage for driver downloads, submit support cases, and post on their forums.
CategoryHardware CategoryX CategoryXwindowSystem CategoryVideo
BinaryDriverHowto/Nvidia (last edited 2017-03-09 10:11:52 by penalvch)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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