<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></meta>
<meta http-equiv="X-UA-Compatible" content="IE=edge"></meta>
<meta name="copyright" content="(C) Copyright 2005"></meta>
<meta name="DC.rights.owner" content="(C) Copyright 2005"></meta>
<meta name="DC.Type" content="concept"></meta>
<meta name="DC.Title" content="NVIDIA CUDA Getting Started Guide for Linux"></meta>
<meta name="abstract" content="The installation instructions for the CUDA Toolkit on Linux."></meta>
<meta name="description" content="The installation instructions for the CUDA Toolkit on Linux."></meta>
<meta name="DC.Coverage" content="Getting Started Guides"></meta>
<meta name="DC.subject" content="CUDA Linux, CUDA Linux requirements, CUDA Linux supported versions, CUDA Linux gcc, CUDA Linux install toolkit, CUDA Linux GPU, CUDA Linux download, CUDA Linux install verification, CUDA Linux examples, CUDA Linux binaries"></meta>
<meta name="keywords" content="CUDA Linux, CUDA Linux requirements, CUDA Linux supported versions, CUDA Linux gcc, CUDA Linux install toolkit, CUDA Linux GPU, CUDA Linux download, CUDA Linux install verification, CUDA Linux examples, CUDA Linux binaries"></meta>
<meta name="DC.Format" content="XHTML"></meta>
<meta name="DC.Identifier" content="abstract"></meta>
<link rel="stylesheet" type="text/css" href="../common/formatting/commonltr.css"></link>
<link rel="stylesheet" type="text/css" href="../common/formatting/site.css"></link>
<title>Getting Started Linux :: CUDA Toolkit Documentation</title>
<!--[if lt IE 9]>
<script src="../common/formatting/html5shiv-printshiv.min.js"></script>
<![endif]-->
<script type="text/javascript" charset="utf-8" src="../common/scripts/tynt/tynt.js"></script>
<script type="text/javascript" charset="utf-8" src="../common/formatting/jquery.min.js"></script>
<script type="text/javascript" charset="utf-8" src="../common/formatting/jquery.ba-hashchange.min.js"></script>
<script type="text/javascript" charset="utf-8" src="../common/formatting/jquery.scrollintoview.min.js"></script>
<script type="text/javascript" src="../search/htmlFileList.js"></script>
<script type="text/javascript" src="../search/htmlFileInfoList.js"></script>
<script type="text/javascript" src="../search/nwSearchFnt.min.js"></script>
<script type="text/javascript" src="../search/stemmers/en_stemmer.min.js"></script>
<script type="text/javascript" src="../search/index-1.js"></script>
<script type="text/javascript" src="../search/index-2.js"></script>
<script type="text/javascript" src="../search/index-3.js"></script>
<link rel="canonical" href="http://docs.nvidia.com/cuda/cuda-getting-started-guide-for-linux/index.html"></link>
<link rel="stylesheet" type="text/css" href="../common/formatting/qwcode.highlight.css"></link>
</head>
<body>
<header id="header"><span id="company">NVIDIA</span><span id="site-title">CUDA Toolkit Documentation</span><form id="search" method="get" action="search">
<input type="text" name="search-text"></input><fieldset id="search-location">
<legend>Search In:</legend>
<label><input type="radio" name="search-type" value="site"></input>Entire Site</label>
<label><input type="radio" name="search-type" value="document"></input>Just This Document</label></fieldset>
<button type="reset">clear search</button>
<button id="submit" type="submit">search</button></form>
</header>
<div id="site-content">
<nav id="site-nav">
<div class="category closed"><a href="../index.html" title="The root of the site.">CUDA Toolkit
v6.5</a></div>
<div class="category"><a href="index.html" title="Getting Started Linux">Getting Started Linux</a></div>
<ul>
<li>
<div class="section-link"><a href="#introduction">1. Introduction</a></div>
<ul>
<li>
<div class="section-link"><a href="#system-requirements">1.1. System Requirements</a></div>
<ul>
<li>
<div class="section-link"><a href="#x86-32-bit-support">1.1.1. x86 32-bit Support</a></div>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#about-this-document">1.2. About This Document</a></div>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#pre-installation-actions">2. Pre-installation Actions</a></div>
<ul>
<li>
<div class="section-link"><a href="#verify-you-have-cuda-enabled-system">2.1. Verify You Have a CUDA-Capable GPU</a></div>
</li>
<li>
<div class="section-link"><a href="#verify-you-have-supported-version-of-linux">2.2. Verify You Have a Supported Version of Linux</a></div>
</li>
<li>
<div class="section-link"><a href="#verify-that-gcc-is-installed">2.3. Verify the System Has gcc Installed</a></div>
</li>
<li>
<div class="section-link"><a href="#choose-installation-method">2.4. Choose an Installation Method</a></div>
</li>
<li>
<div class="section-link"><a href="#download-nvidia-driver-and-cuda-software">2.5. Download the NVIDIA CUDA Toolkit</a></div>
</li>
<li>
<div class="section-link"><a href="#handle-uninstallation">2.6. Handle Conflicting Installation Methods</a></div>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#package-manager-installation">3. Package Manager Installation</a></div>
<ul>
<li>
<div class="section-link"><a href="#package-manager-overview">3.1. Overview</a></div>
</li>
<li>
<div class="section-link"><a href="#redhat-installation">3.2. Redhat/CentOS</a></div>
</li>
<li>
<div class="section-link"><a href="#fedora-installation">3.3. Fedora</a></div>
</li>
<li>
<div class="section-link"><a href="#sles-installation">3.4. SLES</a></div>
</li>
<li>
<div class="section-link"><a href="#suse-installation">3.5. OpenSUSE</a></div>
</li>
<li>
<div class="section-link"><a href="#ubuntu-installation">3.6. Ubuntu</a></div>
</li>
<li>
<div class="section-link"><a href="#l4t-installation">3.7. L4T</a></div>
</li>
<li>
<div class="section-link"><a href="#package-manager-additional">3.8. Additional Package Manager Capabilities</a></div>
<ul>
<li>
<div class="section-link"><a href="#package-manager-packages">3.8.1. Available Packages</a></div>
</li>
<li>
<div class="section-link"><a href="#package-manager-upgrades">3.8.2. Package Upgrades</a></div>
</li>
</ul>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#runfile">4. Runfile Installation</a></div>
<ul>
<li>
<div class="section-link"><a href="#runfile-pre-installation">4.1. Pre-installation Setup</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-prereqs">4.2. Prerequisites</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-contents">4.3. Contents</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-kill-gui">4.4. Graphical Interface Shutdown</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-installation">4.5. Installation</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-nouveau">4.6. Interaction with Nouveau</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-libraries">4.7. Extra Libraries</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-verifications">4.8. Verifications</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-start-gui">4.9. Graphical Interface Restart</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-post-installation">4.10. Post-installation Setup</a></div>
</li>
<li>
<div class="section-link"><a href="#runfile-uninstallation">4.11. Uninstallation</a></div>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#cross-arm">5. Cross-build Environment for ARM</a></div>
<ul>
<li>
<div class="section-link"><a href="#cross-installation">5.1. Cross-build Installation for ARM</a></div>
</li>
<li>
<div class="section-link"><a href="#cross-samples">5.2. Cross Samples</a></div>
</li>
<li>
<div class="section-link"><a href="#cross-nsight">5.3. Nsight Eclipse Edition</a></div>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#post-installation-actions">6. Post-installation Actions</a></div>
<ul>
<li>
<div class="section-link"><a href="#environment-setup">6.1. Environment Setup</a></div>
</li>
<li>
<div class="section-link"><a href="#install-samples">6.2. (Optional) Install Writable Samples</a></div>
</li>
<li>
<div class="section-link"><a href="#verify-installation">6.3. Verify the Installation</a></div>
<ul>
<li>
<div class="section-link"><a href="#verify-driver">6.3.1. Verify the Driver Version</a></div>
</li>
<li>
<div class="section-link"><a href="#compiling-examples">6.3.2. Compiling the Examples</a></div>
</li>
<li>
<div class="section-link"><a href="#running-binaries">6.3.3. Running the Binaries</a></div>
</li>
</ul>
</li>
</ul>
</li>
<li>
<div class="section-link"><a href="#faq">7. Frequently Asked Questions</a></div>
</li>
<li>
<div class="section-link"><a href="#additional-considerations">8. Additional Considerations</a></div>
</li>
</ul>
</nav>
<div id="resize-nav"></div>
<nav id="search-results">
<h2>Search Results</h2>
<ol></ol>
</nav>
<div id="contents-container">
<div id="breadcrumbs-container">
<div id="release-info">Getting Started Linux
(<a href="../../pdf/CUDA_Getting_Started_Linux.pdf">PDF</a>)
-
v6.5
(<a href="https://developer.nvidia.com/cuda-toolkit-archive">older</a>)
-
Last updated August 1, 2014
-
<a href="mailto:cudatools@nvidia.com?subject=CUDA Toolkit Documentation Feedback: Getting Started Linux">Send Feedback</a>
-
<span class="st_facebook"></span><span class="st_twitter"></span><span class="st_linkedin"></span><span class="st_reddit"></span><span class="st_slashdot"></span><span class="st_tumblr"></span><span class="st_sharethis"></span></div>
</div>
<article id="contents">
<div class="topic nested0" id="abstract"><a name="abstract" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#abstract" name="abstract" shape="rect">NVIDIA CUDA Getting Started Guide for Linux</a></h2>
<div class="body conbody"></div>
</div>
<div class="topic concept nested0" id="introduction"><a name="introduction" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#introduction" name="introduction" shape="rect">1. Introduction</a></h2>
<div class="body conbody">
<p class="p">CUDA<sup>®</sup> is a parallel computing platform and programming model invented by NVIDIA. It enables dramatic increases in computing performance
by harnessing the power of the graphics processing unit (GPU).
</p>
<div class="p">CUDA was developed with several design goals in mind:
<ul class="ul">
<li class="li">Provide a small set of extensions to standard programming languages, like C, that enable a straightforward implementation
of parallel algorithms. With CUDA C/C++, programmers can focus on the task of parallelization of the algorithms rather than
spending time on their implementation.
</li>
<li class="li">Support heterogeneous computation where applications use both the CPU and GPU. Serial portions of applications are run on
the CPU, and parallel portions are offloaded to the GPU. As such, CUDA can be incrementally applied to existing applications.
The CPU and GPU are treated as separate devices that have their own memory spaces. This configuration also allows simultaneous
computation on the CPU and GPU without contention for memory resources.
</li>
</ul>
CUDA-capable GPUs have hundreds of cores that can collectively run thousands of computing threads. These cores have shared
resources including a register file and a shared memory. The on-chip shared memory allows parallel tasks running on these
cores to share data without sending it over the system memory bus.
</div>
<p class="p">This guide will show you how to install and check the correct operation of the CUDA development tools.</p>
</div>
<div class="topic concept nested1" id="system-requirements"><a name="system-requirements" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#system-requirements" name="system-requirements" shape="rect">1.1. System Requirements</a></h3>
<div class="body conbody">
<div class="p">To use CUDA on your system, you will need the following installed:
<ul class="ul">
<li class="li">CUDA-capable GPU</li>
<li class="li">A supported version of Linux with a gcc compiler and toolchain</li>
<li class="li">NVIDIA CUDA Toolkit (available at <a class="xref" href="http://developer.nvidia.com/cuda-downloads" target="_blank" shape="rect">http://developer.nvidia.com/cuda-downloads</a>)
</li>
</ul>
</div>
<p class="p">The CUDA development environment relies on tight integration with the host development
environment, including the host compiler and C runtime libraries, and is therefore only
supported on distribution versions that have been qualified for this CUDA Toolkit release.
</p>
<div class="tablenoborder">
<table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all">
<caption><span class="tablecap">Table 1. Native Linux Distribution Support in CUDA <span class="keyword">6.5</span></span></caption>
<thead class="thead" align="left">
<tr class="row">
<th class="entry" valign="top" width="NaN%" id="d54e155" rowspan="1" colspan="1">Distribution </th>
<th class="entry" align="center" valign="top" width="NaN%" id="d54e158" rowspan="1" colspan="1">x86_64</th>
<th class="entry" align="center" valign="top" width="NaN%" id="d54e161" rowspan="1" colspan="1">x86(*)</th>
<th class="entry" align="center" valign="top" width="NaN%" id="d54e164" rowspan="1" colspan="1">ARMv7</th>
<th class="entry" valign="top" width="NaN%" id="d54e167" rowspan="1" colspan="1">Kernel</th>
<th class="entry" valign="top" width="NaN%" id="d54e171" rowspan="1" colspan="1">GCC</th>
<th class="entry" valign="top" width="NaN%" id="d54e174" rowspan="1" colspan="1">GLIBC</th>
<th class="entry" valign="top" width="NaN%" id="d54e177" rowspan="1" colspan="1">ICC(**)</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">Fedora 20</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.12.0</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.8.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.18</td>
<td class="entry" rowspan="11" valign="middle" width="NaN%" headers="d54e177" colspan="1">14.0.1</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">CentOS 6.x</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">2.6.32</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.4.7</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.12</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">CentOS 5.5+</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">2.6.18</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.1.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.5</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">OpenSUSE 13.1</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.11.6</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.8</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.18</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">RHEL 6.x</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">2.6.32</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.4.7</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.12</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">RHEL 5.5+</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">2.6.18</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.1.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.5</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">SUSE SLES 11 SP3</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.0.76</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.3.4</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.11.3</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">Ubuntu 14.04</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">YES</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.13</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.8.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.19</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">Ubuntu 12.04</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.2.0</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.6</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.15</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">SteamOS 1.0-beta</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">NO</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.10.11</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.7.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.17</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e155" rowspan="1" colspan="1">L4T r21.1</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e158" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e161" rowspan="1" colspan="1">NO</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e164" rowspan="1" colspan="1">YES</td>
<td class="entry" valign="top" width="NaN%" headers="d54e167" rowspan="1" colspan="1">3.10.24</td>
<td class="entry" valign="top" width="NaN%" headers="d54e171" rowspan="1" colspan="1">4.8.2</td>
<td class="entry" valign="top" width="NaN%" headers="d54e174" rowspan="1" colspan="1">2.19</td>
</tr>
</tbody>
</table>
</div>
<div class="tablenoborder">
<table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all">
<caption><span class="tablecap">Table 2. Cross-build Environment Linux Distribution Support in CUDA <span class="keyword">6.5</span></span></caption>
<thead class="thead" align="left">
<tr class="row">
<th class="entry" valign="top" width="NaN%" id="d54e485" rowspan="1" colspan="1">Host Distribution (x86_64)</th>
<th class="entry" align="center" valign="top" width="NaN%" id="d54e488" rowspan="1" colspan="1">Targeting x86(*)</th>
<th class="entry" align="center" valign="top" width="NaN%" id="d54e491" rowspan="1" colspan="1">Targeting ARMv7</th>
</tr>
</thead>
<tbody class="tbody">
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e485" rowspan="1" colspan="1">Ubuntu 14.04</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e488" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e491" rowspan="1" colspan="1">YES</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e485" rowspan="1" colspan="1">Ubuntu 12.04</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e488" rowspan="1" colspan="1">DEPRECATED</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e491" rowspan="1" colspan="1">DEPRECATED</td>
</tr>
<tr class="row">
<td class="entry" valign="top" width="NaN%" headers="d54e485" rowspan="1" colspan="1">SteamOS 1.0-beta</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e488" rowspan="1" colspan="1">YES</td>
<td class="entry" align="center" valign="top" width="NaN%" headers="d54e491" rowspan="1" colspan="1">NO</td>
</tr>
</tbody>
</table>
</div>
<p class="p">
(*) x86 support is limited. See the <a class="xref" href="index.html#x86-32-bit-support" shape="rect">x86 32-bit Support</a> section for details.
</p>
<p class="p">
(**) ICC support is limited to x86_64 only
</p>
</div>
<div class="topic concept nested2" id="x86-32-bit-support"><a name="x86-32-bit-support" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#x86-32-bit-support" name="x86-32-bit-support" shape="rect">x86 32-bit Support</a></h3>
<div class="body conbody">
<div class="p">
Support for x86 32-bit applications on x86 and x86_64 Linux is limited to use with:
<ul class="ul">
<li class="li">GeForce GPUs with Kepler or higher architecture</li>
<li class="li">CUDA Driver</li>
<li class="li">CUDA Runtime (cudart)</li>
<li class="li">CUDA Math Library (math.h)</li>
<li class="li">CUDA C++ Compiler (nvcc)</li>
<li class="li">CUDA Development Tools</li>
</ul>
Support for this configuration is only available in the .run file installer.
</div>
</div>
</div>
</div>
<div class="topic concept nested1" id="about-this-document"><a name="about-this-document" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#about-this-document" name="about-this-document" shape="rect">1.2. About This Document</a></h3>
<div class="body conbody">
<p class="p">This document is intended for readers familiar with the Linux environment and the compilation of C programs from the command
line. You do not need previous experience with CUDA or experience with parallel computation. Note: This guide covers installation
only on systems with X Windows installed.
</p>
<div class="note note"><span class="notetitle">Note:</span> Many commands in this document might require <em class="ph i">superuser</em> privileges. On most distributions of Linux, this will require you to log in as root. For systems that have enabled the sudo
package, use the sudo prefix for all necessary commands.
</div>
</div>
</div>
</div>
<div class="topic concept nested0" id="pre-installation-actions"><a name="pre-installation-actions" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#pre-installation-actions" name="pre-installation-actions" shape="rect">2. Pre-installation Actions</a></h2>
<div class="body conbody">
<div class="p">Some actions must be taken before the CUDA Toolkit and Driver can be installed on Linux:
<ul class="ul">
<li class="li">Verify the system has a CUDA-capable GPU.</li>
<li class="li">Verify the system is running a supported version of Linux.</li>
<li class="li">Verify the system has gcc installed.</li>
<li class="li">Download the NVIDIA CUDA Toolkit.</li>
<li class="li">Handle conflicting installation methods.</li>
</ul>
</div>
<div class="note note"><span class="notetitle">Note:</span> You can override the install-time prerequisite checks by running the installer with the -override flag. Remember that the
prerequisites will still be required to use the NVIDIA CUDA Toolkit.
</div>
</div>
<div class="topic concept nested1" id="verify-you-have-cuda-enabled-system"><a name="verify-you-have-cuda-enabled-system" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#verify-you-have-cuda-enabled-system" name="verify-you-have-cuda-enabled-system" shape="rect">2.1. Verify You Have a CUDA-Capable GPU</a></h3>
<div class="body conbody">
<p class="p">To verify that your GPU is CUDA-capable, go to your distribution's equivalent of System Properties, or, from the command line,
enter:
</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> lspci | grep -i nvidia</pre><p class="p">If you do not see any settings, update the PCI hardware database that Linux maintains by entering <samp class="ph codeph">update-pciids</samp> (generally found in <samp class="ph codeph">/sbin</samp>) at the command line and rerun the previous <samp class="ph codeph">lspci</samp> command.
</p>
<p class="p">If your graphics card is from NVIDIA and it is listed in <a class="xref" href="http://developer.nvidia.com/cuda-gpus" target="_blank" shape="rect">http://developer.nvidia.com/cuda-gpus</a>, your GPU is CUDA-capable.
</p>
<p class="p">The Release Notes for the CUDA Toolkit also contain a list of supported products.</p>
</div>
</div>
<div class="topic concept nested1" id="verify-you-have-supported-version-of-linux"><a name="verify-you-have-supported-version-of-linux" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#verify-you-have-supported-version-of-linux" name="verify-you-have-supported-version-of-linux" shape="rect">2.2. Verify You Have a Supported Version of Linux</a></h3>
<div class="body conbody">
<p class="p">The CUDA Development Tools are only supported on some specific distributions of Linux. These are listed in the CUDA Toolkit
release notes.
</p>
<p class="p">To determine which distribution and release number you're running, type the following at the command line:</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> uname -m && cat /etc/*release</pre><p class="p">You should see output similar to the following, modified for your particular system:</p><pre class="pre screen" xml:space="preserve">x86_64
Red Hat Enterprise Linux Workstation release 6.0 (Santiago)</pre><p class="p">The <samp class="ph codeph">x86_64</samp> line indicates you are running on a 64-bit system. The remainder gives information about your distribution.
</p>
</div>
</div>
<div class="topic concept nested1" id="verify-that-gcc-is-installed"><a name="verify-that-gcc-is-installed" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#verify-that-gcc-is-installed" name="verify-that-gcc-is-installed" shape="rect">2.3. Verify the System Has gcc Installed</a></h3>
<div class="body conbody">
<p class="p">The <samp class="ph codeph">gcc</samp> compiler is required for development using the CUDA Toolkit. It is not required for running CUDA applications. It is generally
installed as part of the Linux installation, and in most cases the version of gcc installed with a supported version of Linux
will work correctly.
</p>
<p class="p">To verify the version of gcc installed on your system, type the following on the command line:</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> gcc --version</pre><p class="p">If an error message displays, you need to install the <dfn class="term">development tools</dfn> from your Linux distribution or obtain a version of <samp class="ph codeph">gcc</samp> and its accompanying toolchain from the Web.
</p>
</div>
</div>
<div class="topic concept nested1" id="choose-installation-method"><a name="choose-installation-method" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#choose-installation-method" name="choose-installation-method" shape="rect">2.4. Choose an Installation Method</a></h3>
<div class="body conbody">
<p class="p">
The CUDA Toolkit can be installed using either of two different
installation mechanisms: distribution-specific packages, or a
distribution-independent package. The distribution-independent
package has the advantage of working across a wider set of Linux
distributions, but does not update the distribution's native package
management system. The distribution-specific packages interface
with the distribution's native package management system. It is
recommended to use the distribution-specific packages, where possible.
</p>
<div class="note note"><span class="notetitle">Note:</span>
Distribution-specific packages and repositories are not provided for Redhat 5.
For Redhat 5, the stand-alone installer must be used.
</div>
<div class="note note"><span class="notetitle">Note:</span> Standalone installers are not provided for the ARMv7 release. For both
native ARMv7 as well as cross development, the toolkit must be installed using the
distribution-specific installer.
See the <a class="xref" href="index.html#cross-installation" shape="rect">Cross-build Environment for ARM</a> installation section for more details.
</div>
</div>
</div>
<div class="topic concept nested1" id="download-nvidia-driver-and-cuda-software"><a name="download-nvidia-driver-and-cuda-software" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#download-nvidia-driver-and-cuda-software" name="download-nvidia-driver-and-cuda-software" shape="rect">2.5. Download the NVIDIA CUDA Toolkit</a></h3>
<div class="body conbody">
<p class="p">The NVIDIA CUDA Toolkit is available at <a class="xref" href="http://developer.nvidia.com/cuda-downloads" target="_blank" shape="rect">http://developer.nvidia.com/cuda-downloads</a>.
</p>
<p class="p">Choose the platform you are using and download the NVIDIA CUDA Toolkit</p>
<p class="p">The CUDA Toolkit contains the CUDA driver and tools needed to create, build and run a CUDA application as well as libraries,
header files, CUDA samples source code, and other resources.
</p>
<div class="section">
<h3 class="title sectiontitle">Download Verification</h3>
<p class="p">The download can be verified by comparing the MD5 checksum posted at <a class="xref" href="http://developer.nvidia.com/cuda-downloads/checksums" target="_blank" shape="rect">http://developer.nvidia.com/cuda-downloads/checksums</a> with that of the downloaded file. If either of the checksums differ, the downloaded file is corrupt and needs to be downloaded
again.
</p>
<div class="p">To calculate the MD5 checksum of the downloaded file, run the following:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> md5sum <file></pre></div>
</div>
</div>
</div>
<div class="topic concept nested1" id="handle-uninstallation"><a name="handle-uninstallation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#handle-uninstallation" name="handle-uninstallation" shape="rect">2.6. Handle Conflicting Installation Methods</a></h3>
<div class="body conbody">
<p class="p">
Before installing CUDA, any previously installations that could conflict should be uninstalled. This will not affect systems
which have not had CUDA installed previously, or systems where the installation method has been preserved (RPM/Deb vs. Runfile).
See the following charts for specifics.
</p>
<div class="tablenoborder">
<table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all">
<caption><span class="tablecap">Table 3. CUDA Toolkit Installation Compatibility Matrix</span></caption>
<tbody class="tbody">
<tr class="row">
<td class="entry" rowspan="2" colspan="2" align="center" valign="top"> </td>
<td class="entry" colspan="2" align="center" valign="top" rowspan="1">Installed Toolkit Version == X.Y</td>
<td class="entry" colspan="2" align="center" valign="top" rowspan="1">Installed Toolkit Version != X.Y</td>
</tr>
<tr class="row">
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">run</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">run</td>
</tr>
<tr class="row">
<td class="entry" rowspan="2" align="center" valign="top" colspan="1">Installing Toolkit Version X.Y</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">Uninstall Run</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">No Action</td>
</tr>
<tr class="row">
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">run</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">Uninstall RPM/Deb</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">Uninstall Run</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" align="center" valign="top" rowspan="1" colspan="1">No Action</td>
</tr>
</tbody>
</table>
</div>
<div class="tablenoborder">
<table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all">
<caption><span class="tablecap">Table 4. NVIDIA Driver Installation Compatibility Matrix</span></caption>
<tbody class="tbody">
<tr class="row">
<td class="entry" rowspan="2" colspan="2" valign="top"> </td>
<td class="entry" colspan="2" valign="top" rowspan="1">Installed Driver Version == X.Y</td>
<td class="entry" colspan="2" valign="top" rowspan="1">Installed Driver Version != X.Y</td>
</tr>
<tr class="row">
<td class="entry" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" valign="top" rowspan="1" colspan="1">run</td>
<td class="entry" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" valign="top" rowspan="1" colspan="1">run</td>
</tr>
<tr class="row">
<td class="entry" rowspan="2" valign="top" colspan="1">Installing Driver Version X.Y</td>
<td class="entry" valign="top" rowspan="1" colspan="1">RPM/Deb</td>
<td class="entry" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" valign="top" rowspan="1" colspan="1">Uninstall Run</td>
<td class="entry" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" valign="top" rowspan="1" colspan="1">Uninstall Run</td>
</tr>
<tr class="row">
<td class="entry" valign="top" rowspan="1" colspan="1">run</td>
<td class="entry" valign="top" rowspan="1" colspan="1">Uninstall RPM/Deb</td>
<td class="entry" valign="top" rowspan="1" colspan="1">No Action</td>
<td class="entry" valign="top" rowspan="1" colspan="1">Uninstall RPM/Deb</td>
<td class="entry" valign="top" rowspan="1" colspan="1">No Action</td>
</tr>
</tbody>
</table>
</div>
<div class="p">
Use the following command to uninstall a Toolkit runfile installation:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo /usr/local/cuda-X.Y/bin/uninstall_cuda_X.Y.pl</pre>
Use the following command to uninstall a Driver runfile installation:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo /usr/bin/nvidia-uninstall</pre>
Use the following commands to uninstall a RPM/Deb installation:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get --purge remove <package_name> # Ubuntu
<strong class="ph b">$</strong> sudo yum remove <package_name> # Fedora/Redhat/CentOS
<strong class="ph b">$</strong> sudo zypper remove <package_name> # OpenSUSE/SLES</pre></div>
</div>
</div>
</div>
<div class="topic concept nested0" id="package-manager-installation"><a name="package-manager-installation" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#package-manager-installation" name="package-manager-installation" shape="rect">3. Package Manager Installation</a></h2>
<div class="body conbody"></div>
<div class="topic concept nested1" id="package-manager-overview"><a name="package-manager-overview" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#package-manager-overview" name="package-manager-overview" shape="rect">3.1. Overview</a></h3>
<div class="body conbody">
<p class="p">
The Package Manager installation interfaces with your system's package management system.
When using RPM or Deb, the downloaded package is a repository package.
Such a package only informs the package manager where to find the actual installation packages, but will not install them.
</p>
<p class="p">
If those packages are available in an online repository, they will be automatically downloaded in a later step. Otherwise,
the repository package also installs a local repository containing the installation packages on the system.
Whether the repository is available online or installed locally, the installation procedure is identical and made of several
steps.
</p>
<div class="p">
Distribution-specific instructions detail how to install CUDA:
<ul class="ul">
<li class="li"><a class="xref" href="index.html#redhat-installation" shape="rect">Redhat/CentOS</a></li>
<li class="li"><a class="xref" href="index.html#fedora-installation" shape="rect">Fedora</a></li>
<li class="li"><a class="xref" href="index.html#sles-installation" shape="rect">SLES</a></li>
<li class="li"><a class="xref" href="index.html#suse-installation" shape="rect">OpenSUSE</a></li>
<li class="li"><a class="xref" href="index.html#ubuntu-installation" shape="rect">Ubuntu</a></li>
<li class="li"><a class="xref" href="index.html#l4t-installation" shape="rect">L4T</a></li>
</ul>
</div>
<p class="p">
Finally, some helpful <a class="xref" href="index.html#package-manager-additional" shape="rect">package manager capabilities</a> are detailed.
</p>
<p class="p">
These instructions are for native development only. For cross development, see the <a class="xref" href="index.html#cross-arm" shape="rect">Cross-build environment for ARM</a> section.
</p>
</div>
</div>
<div class="topic concept nested1" id="redhat-installation"><a name="redhat-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#redhat-installation" name="redhat-installation" shape="rect">3.2. Redhat/CentOS</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Satisfy DKMS dependency</strong><p class="p">
The NVIDIA driver RPM packages depend on other external packages, such as DKMS and libvdpau.
Those packages are only available on third-party repositories, such as <a class="xref" href="http://fedoraproject.org/wiki/EPEL" target="_blank" shape="rect">EPEL</a>.
Any such third-party repositories must be added to the package manager repository database before installing the NVIDIA driver
RPM packages, or missing dependencies will prevent the installation from proceeding.
</p>
</li>
<li class="li"><strong class="ph b">Address custom xorg.conf, if applicable</strong><p class="p">
The driver relies on an automatically generated xorg.conf file at /etc/X11/xorg.conf. If a custom-built xorg.conf file is
present, this functionality will be disabled and the driver may not work.
You can try removing the existing xorg.conf file, or adding the contents of /etc/X11/xorg.conf.d/00-nvidia.conf to the xorg.conf
file. The xorg.conf file will most likely need manual tweaking for systems with a non-trivial GPU configuration.
</p>
</li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo rpm --install cuda-repo-<distro>-<version>.<architecture>.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Clean Yum repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum clean expire-cache</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda</pre></div>
<div class="p">
If the i686 libvdpau package dependency fails to install, try using the following steps to fix the issue:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> yumdownloader libvdpau.i686
<strong class="ph b">$</strong> sudo rpm -U --oldpackage libvdpau*.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Add libcuda.so symbolic link, if necessary</strong><p class="p">
The libcuda.so library is installed in the /usr/lib{,64}/nvidia directory. For pre-existing projects which use libcuda.so,
it may be useful to add a symbolic link from libcuda.so in the /usr/lib{,64} directory.
</p>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="fedora-installation"><a name="fedora-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#fedora-installation" name="fedora-installation" shape="rect">3.3. Fedora</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Address custom xorg.conf, if applicable</strong><p class="p">
The driver relies on an automatically generated xorg.conf file at /etc/X11/xorg.conf. If a custom-built xorg.conf file is
present, this functionality will be disabled and the driver may not work.
You can try removing the existing xorg.conf file, or adding the contents of /etc/X11/xorg.conf.d/00-nvidia.conf to the xorg.conf
file. The xorg.conf file will most likely need manual tweaking for systems with a non-trivial GPU configuration.
</p>
</li>
<li class="li"><strong class="ph b">Satisfy Akmods dependency</strong><p class="p">
The NVIDIA driver RPM packages depend on the Akmods framework which is provided by the <a class="xref" href="http://rpmfusion.org/Configuration" target="_blank" shape="rect">RPMFusion free repository</a>.
The RPMFusion free repository must be added to the package manager repository database before installing the NVIDIA driver
RPM packages, or missing dependencies will prevent the installation from proceeding.
</p>
</li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo rpm --install cuda-repo-<distro>-<version>.<architecture>.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Clean Yum repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum clean expire-cache</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda</pre>
The CUDA driver installation may fail if the RPMFusion non-free repository is enabled. In this case, CUDA installations should
temporarily disable the RPMFusion non-free repository:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum --disablerepo="rpmfusion-nonfree*" install cuda</pre></div>
<div class="p">
If also installing the <samp class="ph codeph">gpu-deployment-kit</samp> package, the <samp class="ph codeph">cuda</samp> and <samp class="ph codeph">gpu-deployment-kit</samp> packages should be either installed using separate instances of <samp class="ph codeph">yum</samp>:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda
<strong class="ph b">$</strong> sudo yum install gpu-deployment-kit</pre>
Or, installed while also specifying the <samp class="ph codeph">cuda-drivers</samp> package:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda cuda-drivers gpu-deployment-kit</pre>
If a system has installed both packages with the same instance of <samp class="ph codeph">yum</samp>, some driver components may be missing. Such an installation can be corrected by running:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda-drivers</pre></div>
<div class="p">
If the i686 libvdpau package dependency fails to install, try using the following steps to fix the issue:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> yumdownloader libvdpau.i686
<strong class="ph b">$</strong> sudo rpm -U --oldpackage libvdpau*.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Add libcuda.so symbolic link, if necessary</strong><p class="p">
The libcuda.so library is installed in the /usr/lib{,64}/nvidia directory. For pre-existing projects which use libcuda.so,
it may be useful to add a symbolic link from libcuda.so in the /usr/lib{,64} directory.
</p>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="sles-installation"><a name="sles-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#sles-installation" name="sles-installation" shape="rect">3.4. SLES</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo rpm --install cuda-repo-<distro>-<version>.<architecture>.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Refresh Zypper repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo zypper refresh</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo zypper install cuda</pre></div>
<div class="p">
The driver is provided in multiple packages, nvidia-gfxG03-kmp-desktop, nvidia-gfxG03-kmp-default, nvidia-gfxG03-kmp-trace,
and their Unified Memory variants. When installing cuda, the correct driver packages should also be specified. Without doing
this, zypper will select packages that may not work on the system.
Run the following to detect the flavor of kernel and install cuda with the appropriate driver packages:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> uname -r
3.4.6-2.10-<flavor>
<strong class="ph b">$</strong> sudo zypper install cuda nvidia-gfxG03-kmp-<flavor> \
nvidia-uvm-gfxG03-kmp-<flavor></pre></div>
</li>
<li class="li"><strong class="ph b">Add the user to the video group</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo usermod -a -G video <username></pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA Samples GL dependencies</strong><p class="p">
The CUDA Samples package on SLES does not include dependencies on GL and X11 libraries as these are provided in the SLES SDK.
These packages must be installed separately, depending on which samples you want to use.
</p>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="suse-installation"><a name="suse-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#suse-installation" name="suse-installation" shape="rect">3.5. OpenSUSE</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo rpm --install cuda-repo-<distro>-<version>.<architecture>.rpm</pre></div>
</li>
<li class="li"><strong class="ph b">Refresh Zypper repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo zypper refresh</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo zypper install cuda</pre></div>
<div class="p">
The driver is provided in multiple packages, nvidia-gfxG03-kmp-desktop, nvidia-gfxG03-kmp-default, nvidia-gfxG03-kmp-trace,
and their Unified Memory variants. When installing cuda, the correct driver packages should also be specified. Without doing
this, zypper will select packages that may not work on the system.
Run the following to detect the flavor of kernel and install cuda with the appropriate driver packages:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> uname -r
3.4.6-2.10-<flavor>
<strong class="ph b">$</strong> sudo zypper install cuda nvidia-gfxG03-kmp-<flavor> \
nvidia-uvm-gfxG03-kmp-<flavor></pre></div>
</li>
<li class="li"><strong class="ph b">Add the user to the video group</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo usermod -a -G video <username></pre></div>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="ubuntu-installation"><a name="ubuntu-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#ubuntu-installation" name="ubuntu-installation" shape="rect">3.6. Ubuntu</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="note note"><span class="notetitle">Note:</span> When using a proxy server with aptitude, ensure that <samp class="ph codeph">wget</samp> is set up to use the same proxy settings before installing the cuda-repo package.
</div>
<div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo dpkg -i cuda-repo-<distro>_<version>_<architecture>.deb</pre></div>
</li>
<li class="li"><strong class="ph b">Update the Apt repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get update</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get install cuda</pre></div>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="l4t-installation"><a name="l4t-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#l4t-installation" name="l4t-installation" shape="rect">3.7. L4T</a></h3>
<div class="body conbody">
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo dpkg -i cuda-repo-<distro>_<version>_<architecture>.deb</pre></div>
</li>
<li class="li"><strong class="ph b">Update the Apt repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get update</pre></div>
</li>
<li class="li"><strong class="ph b">Install CUDA Toolkit</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get install cuda-toolkit-<span class="keyword">6</span>-<span class="keyword">5</span></pre></div>
</li>
<li class="li"><strong class="ph b">Add the user to the video group</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo usermod -a -G video <username></pre></div>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="package-manager-additional"><a name="package-manager-additional" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#package-manager-additional" name="package-manager-additional" shape="rect">3.8. Additional Package Manager Capabilities</a></h3>
<div class="body conbody">
<p class="p">Below are some additional capabilities of the package manager that users can take advantage of.</p>
</div>
<div class="topic concept nested2" id="package-manager-packages"><a name="package-manager-packages" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#package-manager-packages" name="package-manager-packages" shape="rect">3.8.1. Available Packages</a></h3>
<div class="body conbody">
<p class="p">
The recommended installation package is the <samp class="ph codeph">cuda</samp> package.
This package will install the full set of other CUDA packages required for native development and should cover most scenarios.
</p>
<p class="p">
The <samp class="ph codeph">cuda</samp> package installs all the available packages for native developments.
That includes the compiler, the debugger, the profiler, the math libraries,...
For x86_64 patforms, this also include NSight Eclipse Edition and the visual profiler
It also includes the NVIDIA driver package.
</p>
<p class="p">
On supported platforms, the <samp class="ph codeph">cuda-cross-armhf</samp>
package installs all the packages required for cross-platform development on ARMv7. The libraries and header
files of the ARMv7 display driver package are also installed to enable the cross compilation of ARMv7 applications.
The <samp class="ph codeph">cuda-cross-armhf</samp> package does not install the native display driver.
</p>
<p class="p">
The packages installed by the packages above can also be installed individually by specifying their names explicitly.
The list of available packages be can obtained with:
</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> yum --disablerepo="*" --enablerepo="cuda*" list available # RedHat & Fedora
<strong class="ph b">$</strong> zypper packages -r cuda # OpenSUSE & SLES
<strong class="ph b">$</strong> cat /var/lib/apt/lists/*cuda*Packages | grep "Package:" # Ubuntu</pre></div>
</div>
<div class="topic concept nested2" id="package-manager-upgrades"><a name="package-manager-upgrades" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#package-manager-upgrades" name="package-manager-upgrades" shape="rect">3.8.2. Package Upgrades</a></h3>
<div class="body conbody">
<p class="p">
The <samp class="ph codeph">cuda</samp> package points to the latest stable release of the CUDA Toolkit.
When a new version is available, use the following commands to upgrade the toolkit and driver:
</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda # RedHat & Fedora
<strong class="ph b">$</strong> sudo zypper install cuda # OpenSUSE & SLES
<strong class="ph b">$</strong> sudo apt-get install cuda # Ubuntu</pre><p class="p">
The <samp class="ph codeph">cuda-cross-armhf</samp> package can also be upgraded in the same manner.
</p>
<p class="p">
The cuda-drivers package points to the latest driver release available in the CUDA repository.
When a new version is available, use the following commands to upgrade the driver:
</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo yum install cuda-drivers # RedHat & Fedora
<strong class="ph b">$</strong> sudo zypper install cuda-drivers \
nvidia-gfxG03-kmp-<flavor> \
nvidia-uvm-gfxG03-kmp-<flavor> # OpenSUSE & SLES
<strong class="ph b">$</strong> sudo apt-get install cuda-drivers # Ubuntu</pre><p class="p">
Some desktop environments, such as GNOME or KDE, will display an notification alert when new packages are available.
</p>
<p class="p">
To avoid any automatic upgrade, and lock down the toolkit installation to the X.Y release, install the <samp class="ph codeph">cuda-X-Y</samp> or <samp class="ph codeph">cuda-cross-armhf-X-Y</samp> package.
</p>
<p class="p">
Side-by-side installations are supported.
For instance, to install both the X.Y CUDA Toolkit and the X.Y+1 CUDA Toolkit, install the <samp class="ph codeph">cuda-X.Y</samp> and <samp class="ph codeph">cuda-X.Y+1</samp> packages.
</p>
</div>
</div>
</div>
</div>
<div class="topic concept nested0" id="runfile"><a name="runfile" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#runfile" name="runfile" shape="rect">4. Runfile Installation</a></h2>
<div class="body conbody">
<p class="p">
This section describes the installation and configuration of CUDA when using the standalone installer.
</p>
</div>
<div class="topic concept nested1" id="runfile-pre-installation"><a name="runfile-pre-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-pre-installation" name="runfile-pre-installation" shape="rect">4.1. Pre-installation Setup</a></h3>
<div class="body conbody">
<p class="p">Before the stand-alone installation can be run, perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></p>
</div>
</div>
<div class="topic concept nested1" id="runfile-prereqs"><a name="runfile-prereqs" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-prereqs" name="runfile-prereqs" shape="rect">4.2. Prerequisites</a></h3>
<div class="body conbody">
<p class="p">
If you have already installed a standalone CUDA driver and desire to keep using it, you need to make sure it meets the minimum
version requirement for the toolkit.
This requirement can be found in the <a class="xref" href="http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html" target="_blank" shape="rect">CUDA Toolkit release notes</a>.
With many distributions, the driver version number can be found in the graphical interface menus under <samp class="ph codeph">Applications > System Tools > NVIDIA X Server Settings.</samp>.
On the command line, the driver version number can be found by running <samp class="ph codeph">/usr/bin/nvidia-settings</samp>.
</p>
</div>
</div>
<div class="topic concept nested1" id="runfile-contents"><a name="runfile-contents" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-contents" name="runfile-contents" shape="rect">4.3. Contents</a></h3>
<div class="body conbody">
<p class="p">
The standalone installer can install any combination of the NVIDIA Driver (that includes the CUDA Driver), the CUDA Toolkit,
or the CUDA Samples.
If needed, each individual installer can be extracted by using the <samp class="ph codeph">-extract=/absolute/path/to/extract/location/</samp>.
The extraction path must be an absolute path.
</p>
<p class="p">
The CUDA Toolkit installation includes a read-only copy of the CUDA Samples.
The read-only copy is used to create a writable copy of the CUDA Samples at some other location at any point in time.
To create this writable copy, use the <samp class="ph codeph">cuda-install-samples-<span class="keyword">6</span>.<span class="keyword">5</span>.sh</samp> script provided with the toolkit.
It is equivalent to installing the CUDA Samples with the standalone installer.
</p>
</div>
</div>
<div class="topic concept nested1" id="runfile-kill-gui"><a name="runfile-kill-gui" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-kill-gui" name="runfile-kill-gui" shape="rect">4.4. Graphical Interface Shutdown</a></h3>
<div class="body conbody">
<p class="p">
Exit the GUI if you are in a GUI environment by pressing <span class="ph uicontrol">Ctrl-Alt-Backspace</span>.
Some distributions require you to press this sequence twice in a row; others have disabled it altogether in favor of a command
such as <samp class="ph codeph">sudo service lightdm stop</samp>.
Still others require changing the system runlevel using a command such as <samp class="ph codeph">/sbin/init 3</samp>
Consult your distribution's documentation to find out how to properly exit the GUI.
This step is only required in the event that you want to install the NVIDIA Display Driver included in the standalone installer.
</p>
</div>
</div>
<div class="topic concept nested1" id="runfile-installation"><a name="runfile-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-installation" name="runfile-installation" shape="rect">4.5. Installation</a></h3>
<div class="body conbody">
<p class="p">
To install any combination of the driver, toolkit, and the samples, simply execute the .run script.
The installation of the driver requires the script to be run with root privileges.
Depending on the target location, the toolkit and samples installations may also require root privileges.
</p>
<p class="p">
By default, the toolkit and the samples will install under <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span></samp> and <samp class="ph codeph">$(HOME)/NVIDIA_CUDA-<span class="keyword">6.5</span>_Samples</samp>, respectively.
In addition, a symbolic link is created from <samp class="ph codeph">/usr/local/cuda</samp> to <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span></samp>.
The symbolic link is created in order for existing projects to automatically make use of the newly installed CUDA Toolkit.
</p>
<p class="p">
If the target system includes both an integrated GPU (iGPU) and a discrete GPU (dGPU), the --no-opengl-libs option must be
used.
Otherwise, the openGL library used by the graphics driver of the iGPU will be overwritten and the GUI will not work.
In addition, the xorg.conf update at the end of the installation must be declined.
</p>
<div class="note note"><span class="notetitle">Note:</span> Installing Mesa may overwrite the <samp class="ph codeph">/usr/lib/libGL.</samp>so that was previously installed by the NVIDIA driver,
so a reinstallation of the NVIDIA driver might be required after installing these libraries.
</div>
</div>
</div>
<div class="topic concept nested1" id="runfile-nouveau"><a name="runfile-nouveau" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-nouveau" name="runfile-nouveau" shape="rect">4.6. Interaction with Nouveau</a></h3>
<div class="body conbody">
<div class="p">
The Nouveau drivers may be installed into your root filesystem (initramfs) and may cause the Display Driver installation to
fail.
To fix the situation, the initramfs image must be rebuilt with:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
<strong class="ph b">$</strong> sudo dracut /boot/initramfs-$(uname -r).img $(uname -r)</pre>
if Grub2 is used as the bootloader, the <samp class="ph codeph">rdblacklist=nouveau nouveau.modeset=0</samp> line must be added at the end of the GRUB_CMDLINE_LINUX entry in /etc/default/grub.
Then, the Grub configuration must be remade by running: <pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo grub2-mkconfig -o /boot/grub2/grub.cfg</pre>
Once this is done, the machine must be rebooted and the installation attempted again.
</div>
</div>
</div>
<div class="topic concept nested1" id="runfile-libraries"><a name="runfile-libraries" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-libraries" name="runfile-libraries" shape="rect">4.7. Extra Libraries</a></h3>
<div class="body conbody">
<p class="p">
If you wish to build <em class="ph i">all</em> the samples, including those with graphical rather than command-line interfaces, additional system libraries or headers may
be required.
While every Linux distribution is slightly different with respect to package names and package installation procedures,
the libraries and headers most likely to be necessary are OpenGL (e.g., Mesa), GLU, GLUT, and X11 (including Xi, Xmu, and
GLX).
</p>
<div class="p">
On Ubuntu, those can be installed as follows:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get install freeglut3-dev build-essential libx11-dev libxmu-dev libxi-dev libgl1-mesa-glx libglu1-mesa libglu1-mesa-dev</pre></div>
</div>
</div>
<div class="topic concept nested1" id="runfile-verifications"><a name="runfile-verifications" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-verifications" name="runfile-verifications" shape="rect">4.8. Verifications</a></h3>
<div class="body conbody">
<p class="p">
Check that the device files<samp class="ph codeph">/dev/nvidia*</samp> exist and have the correct (0666) file permissions.
These files are used by the CUDA Driver to communicate with the kernel-mode portion of the NVIDIA Driver.
Applications that use the NVIDIA driver, such as a CUDA application or the X server (if any), will normally automatically
create these files
if they are missing using the <dfn class="term">setuid</dfn><samp class="ph codeph">nvidia-modprobe</samp> tool that is bundled with the NVIDIA Driver.
Some systems disallow setuid binaries, however, so if these files do not exist, you can create them manually
either by running the command <samp class="ph codeph">nvidia-smi</samp> as root at boot time or by using a startup script such as the one below:
</p><pre xml:space="preserve">#!/bin/bash
/sbin/modprobe nvidia
if [ "$?" -eq 0 ]; then
# Count the number of NVIDIA controllers found.
NVDEVS=`lspci | grep -i NVIDIA`
N3D=`echo "$NVDEVS" | grep "3D controller" | wc -l`
NVGA=`echo "$NVDEVS" | grep "VGA compatible controller" | wc -l`
N=`expr $N3D + $NVGA - 1`
for i in `seq 0 $N`; do
mknod -m 666 /dev/nvidia$i c 195 $i
done
mknod -m 666 /dev/nvidiactl c 195 255
else
exit 1
fi
/sbin/modprobe nvidia-uvm
if [ "$?" -eq 0 ]; then
# Find out the major device number used by the nvidia-uvm driver
D=`grep nvidia-uvm /proc/devices | awk '{print $1}'`
mknod -m 666 /dev/nvidia-uvm c $D 0
else
exit 1
fi</pre></div>
</div>
<div class="topic concept nested1" id="runfile-start-gui"><a name="runfile-start-gui" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-start-gui" name="runfile-start-gui" shape="rect">4.9. Graphical Interface Restart</a></h3>
<div class="body conbody">
<p class="p">
Restart the GUI environment using the command <samp class="ph codeph">startx</samp>, <samp class="ph codeph">init 5</samp>, <samp class="ph codeph">sudo service lightdm start</samp>, or the equivalent command on your system.
</p>
</div>
</div>
<div class="topic concept nested1" id="runfile-post-installation"><a name="runfile-post-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-post-installation" name="runfile-post-installation" shape="rect">4.10. Post-installation Setup</a></h3>
<div class="body conbody">
<p class="p">Once the stand-alone installation is complete, be sure to perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></p>
</div>
</div>
<div class="topic concept nested1" id="runfile-uninstallation"><a name="runfile-uninstallation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#runfile-uninstallation" name="runfile-uninstallation" shape="rect">4.11. Uninstallation</a></h3>
<div class="body conbody">
<div class="p">To uninstall the CUDA Toolkit, run the uninstallation script provided in the bin directory of the toolkit. By default, it
is located in <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span>/bin</samp>:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo /usr/local/cuda-<span class="keyword">6.5</span>/bin/uninstall_cuda_<span class="keyword">6.5</span>.pl</pre></div>
<div class="p">To uninstall the NVIDIA Driver, run <samp class="ph codeph">nvidia-uninstall</samp>:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo /usr/bin/nvidia-uninstall</pre></div>
</div>
</div>
</div>
<div class="topic concept nested0" id="cross-arm"><a name="cross-arm" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#cross-arm" name="cross-arm" shape="rect">5. Cross-build Environment for ARM</a></h2>
<div class="body conbody">
<p class="p">
Cross-ARM development is only supported on Ubuntu systems, and is only provided via the Package Manager installation process.
</p>
<p class="p">
Due to the supported ARMv7 native platforms being Ubuntu 14.04 based, we recommend selecting Ubuntu 14.04 as your cross development
platform. This selection helps prevent host/target incompatibilities, such as GCC or GLIBC version mismatches.
</p>
</div>
<div class="topic concept nested1" id="cross-installation"><a name="cross-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#cross-installation" name="cross-installation" shape="rect">5.1. Cross-build Installation for ARM</a></h3>
<div class="body conbody">
<p class="p">
Some of the following steps may have already been performed as part of the <a class="xref" href="index.html#ubuntu-installation" shape="rect">native Ubuntu installation</a>. Such steps can safely be skipped.
</p>
<p class="p">
These steps should be performed on the x86_64 host system, rather than the ARMv7 target system. To install the native CUDA
Toolkit on the target ARMv7 system, refer to the native <a class="xref" href="index.html#ubuntu-installation" shape="rect">Ubuntu</a> and <a class="xref" href="index.html#l4t-installation" shape="rect">L4T</a> installation sections.
</p>
<ol class="ol">
<li class="li">
Perform the <a class="xref" href="index.html#pre-installation-actions" shape="rect"> pre-installation actions.</a></li>
<li class="li"><strong class="ph b">Enable armhf foreign architecture</strong><p class="p">
The armhf foreign architecture must be enabled in order to install the cross-armhf toolkit. To enable armhf as a foreign architecture,
the following commands must be executed:
</p>
<div class="p">
On Ubuntu 12.04,
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo sh -c \
'echo "foreign-architecture armhf" >> /etc/dpkg/dpkg.cfg.d/multiarch'
<strong class="ph b">$</strong> sudo apt-get update</pre></div>
<div class="p">On Ubuntu 14.04,
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo dpkg --add-architecture armhf
<strong class="ph b">$</strong> sudo apt-get update</pre></div>
</li>
<li class="li"><strong class="ph b">Install repository meta-data</strong><div class="note note"><span class="notetitle">Note:</span> When using a proxy server with aptitude, ensure that <samp class="ph codeph">wget</samp> is set up to use the same proxy settings before installing the cuda-repo package.
</div>
<div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo dpkg -i cuda-repo-<distro>_<version>_<architecture>.deb</pre></div>
</li>
<li class="li"><strong class="ph b">Update the Apt repository cache</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get update</pre></div>
</li>
<li class="li"><strong class="ph b">Install the cross-ARM CUDA Toolkit</strong><div class="p"><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> sudo apt-get install cuda-cross-armhf</pre></div>
</li>
<li class="li">
Perform the <a class="xref" href="index.html#post-installation-actions" shape="rect"> post-installation actions.</a></li>
</ol>
</div>
</div>
<div class="topic concept nested1" id="cross-samples"><a name="cross-samples" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#cross-samples" name="cross-samples" shape="rect">5.2. Cross Samples</a></h3>
<div class="body conbody">
<p class="p">
When cross-compiling an ARM CUDA application, nvcc must be able to find any libraries used, or be told to ignore missing symbols.
One of the following methods should be chosen when cross-compiling the CUDA Samples. Regardless of which option is chosen,
<samp class="ph codeph">ARMv7=1</samp> should always be used.
</p>
</div>
<div class="topic concept nested2" id="targetfs"><a name="targetfs" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#targetfs" name="targetfs" shape="rect">TARGET_FS</a></h3>
<div class="body conbody">
<div class="p">
The most reliable method to cross-compile the CUDA Samples is to use the TARGET_FS variable. To do so, mount the target's
filesystem on the host, say at <samp class="ph codeph">/mnt/target</samp>. This is typically done using <samp class="ph codeph">exportfs</samp>. In cases where <samp class="ph codeph">exportfs</samp> is unavailable, it is sufficient to copy the target's filesystem to <samp class="ph codeph">/mnt/target</samp>. To cross-compile a sample, execute:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> make ARMv7=1 TARGET_FS=/mnt/target</pre></div>
</div>
</div>
<div class="topic concept nested2" id="copy-libs"><a name="copy-libs" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#copy-libs" name="copy-libs" shape="rect">Copying Libraries</a></h3>
<div class="body conbody">
<div class="p">
If the TARGET_FS option is not available, the libraries used should be copied from the target system to the host system, say
at <samp class="ph codeph">/opt/target/libs</samp>. If the sample uses GL, the GL headers must also be copied, say at <samp class="ph codeph">/opt/target/include</samp>. The linker must then be told where the libraries are with the <samp class="ph codeph">-rpath-link</samp> and/or <samp class="ph codeph">-L</samp> options. For samples which use GL, HEADER_SEARCH_PATH must be set. For example, to cross-compile a sample which uses GL,
execute:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> make ARMv7=1 \
EXTRA_LDFLAGS="-rpath-link=/opt/target/libs -L/opt/target/libs" \
GLPATH=/opt/target/libs \
HEADER_SEARCH_PATH=/opt/target/include</pre></div>
</div>
</div>
<div class="topic concept nested2" id="ignore-symbols"><a name="ignore-symbols" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#ignore-symbols" name="ignore-symbols" shape="rect">Ignore Symbol Detection</a></h3>
<div class="body conbody">
<div class="p">
If neither of the above options are available, the linker can be told to ignore unresolved symbols. The samples should be
forced to build using SAMPLE_ENABLED, and any library inclusion (<samp class="ph codeph">-lfoo</samp>) should be removed from the Makefiles. To perform such a build, execute:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> make ARMv7=1 \
EXTRA_LDFLAGS="--unresolved-symbols=ignore-in-object-files" \
SAMPLE_ENABLED=1</pre></div>
</div>
</div>
</div>
<div class="topic concept nested1" id="cross-nsight"><a name="cross-nsight" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#cross-nsight" name="cross-nsight" shape="rect">5.3. Nsight Eclipse Edition</a></h3>
<div class="body conbody">
<p class="p">
Nsight Eclipse Edition supports cross-platform development. See the <a class="xref" href="http://docs.nvidia.com/cuda/nsight-eclipse-edition-getting-started-guide/index.html#remote-development" target="_blank" shape="rect">Nsight Eclipse Edition Getting Started Guide</a> for more details.
</p>
</div>
</div>
</div>
<div class="topic concept nested0" id="post-installation-actions"><a name="post-installation-actions" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#post-installation-actions" name="post-installation-actions" shape="rect">6. Post-installation Actions</a></h2>
<div class="body conbody">
<div class="p">Some actions must be taken after installing the CUDA Toolkit and Driver before they can be completely used:
<ul class="ul">
<li class="li">Setup evironment variables.</li>
<li class="li">Install a writable copy of the CUDA Samples.</li>
<li class="li">Verify the installation.</li>
</ul>
</div>
</div>
<div class="topic concept nested1" id="environment-setup"><a name="environment-setup" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#environment-setup" name="environment-setup" shape="rect">6.1. Environment Setup</a></h3>
<div class="body conbody">
<p class="p">The <samp class="ph codeph">PATH</samp> variable needs to include <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span>/bin</samp></p>
<p class="p">The <samp class="ph codeph">LD_LIBRARY_PATH</samp> variable needs to contain <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span>/lib64</samp> on a 64-bit system, and <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span>/lib</samp> on a 32-bit ARM system
</p>
<ul class="ul">
<li class="li">
<p class="p">To change the environment variables for 64-bit operating systems:</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> export PATH=/usr/local/cuda-<span class="keyword">6.5</span>/bin:$PATH
<strong class="ph b">$</strong> export LD_LIBRARY_PATH=/usr/local/cuda-<span class="keyword">6.5</span>/lib64:$LD_LIBRARY_PATH</pre></li>
<li class="li">
<p class="p">To change the environment variables for 32-bit ARM operating systems:</p><pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> export PATH=/usr/local/cuda-<span class="keyword">6.5</span>/bin:$PATH
<strong class="ph b">$</strong> export LD_LIBRARY_PATH=/usr/local/cuda-<span class="keyword">6.5</span>/lib:$LD_LIBRARY_PATH</pre></li>
</ul>
</div>
</div>
<div class="topic concept nested1" id="install-samples"><a name="install-samples" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#install-samples" name="install-samples" shape="rect">6.2. (Optional) Install Writable Samples</a></h3>
<div class="body conbody">
<div class="p">
In order to modify, compile, and run the samples, the samples must be installed with write permissions. A convenience installation
script is provided:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> cuda-install-samples-<span class="keyword">6.5</span>.sh <dir></pre>
This script is installed with the cuda-samples-<span class="keyword">6</span>-<span class="keyword">5</span> package. The cuda-samples-<span class="keyword">6</span>-<span class="keyword">5</span> package installs only a read-only copy in /usr/local/cuda-<span class="keyword">6.5</span>/samples.
</div>
</div>
</div>
<div class="topic concept nested1" id="verify-installation"><a name="verify-installation" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#verify-installation" name="verify-installation" shape="rect">6.3. Verify the Installation</a></h3>
<div class="body conbody">
<p class="p">Before continuing, it is important to verify that the CUDA toolkit can find and communicate correctly with the CUDA-capable
hardware. To do this, you need to compile and run some of the included sample programs.
</p>
<div class="note note"><span class="notetitle">Note:</span> Ensure the PATH and LD_LIBRARY_PATH variables are <a class="xref" href="index.html#runfile-installation" shape="rect">set correctly</a>.
</div>
</div>
<div class="topic concept nested2" id="verify-driver"><a name="verify-driver" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#verify-driver" name="verify-driver" shape="rect">6.3.1. Verify the Driver Version</a></h3>
<div class="body conbody">
<p class="p">If you installed the driver, verify that the correct version of it is installed.</p>
<div class="p">This can be done through your System Properties (or equivalent) or by executing the command
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> cat /proc/driver/nvidia/version</pre>
Note that this command will not work on an iGPU/dGPU system.
</div>
</div>
</div>
<div class="topic concept nested2" id="compiling-examples"><a name="compiling-examples" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#compiling-examples" name="compiling-examples" shape="rect">6.3.2. Compiling the Examples</a></h3>
<div class="body conbody">
<p class="p">The version of the CUDA Toolkit can be checked by running <samp class="ph codeph">nvcc -V</samp> in a terminal window. The <samp class="ph codeph">nvcc</samp> command runs the compiler driver that compiles CUDA programs. It calls the <samp class="ph codeph">gcc</samp> compiler for C code and the NVIDIA PTX compiler for the CUDA code.
</p>
<p class="p">The NVIDIA CUDA Toolkit includes sample programs in source form. You should compile them by changing to <samp class="ph codeph">~/NVIDIA_CUDA-<span class="keyword">6.5</span>_Samples</samp> and typing <samp class="ph codeph">make</samp>. The resulting binaries will be placed under <samp class="ph codeph">~/NVIDIA_CUDA-<span class="keyword">6.5</span>_Samples/bin</samp>.
</p>
</div>
</div>
<div class="topic concept nested2" id="running-binaries"><a name="running-binaries" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#running-binaries" name="running-binaries" shape="rect">6.3.3. Running the Binaries</a></h3>
<div class="body conbody">
<p class="p">After compilation, find and run <samp class="ph codeph">deviceQuery</samp> under <samp class="ph codeph">~/NVIDIA_CUDA-<span class="keyword">6.5</span>_Samples</samp>. If the CUDA software is installed and configured correctly, the output for <samp class="ph codeph">deviceQuery</samp> should look similar to that shown in <a class="xref" href="index.html#running-binaries__valid-results-from-sample-cuda-devicequery-program" shape="rect">Figure 1</a>.
</p>
<div class="fig fignone" id="running-binaries__valid-results-from-sample-cuda-devicequery-program"><a name="running-binaries__valid-results-from-sample-cuda-devicequery-program" shape="rect">
<!-- --></a><span class="figcap">Figure 1. Valid Results from deviceQuery CUDA Sample</span><br clear="none"></br><div class="imagecenter"><img class="image imagecenter" src="graphics/valid-results-from-sample-cuda-devicequery-program.png" width="550" alt="Valid Results from deviceQuery CUDA Sample."></img></div><br clear="none"></br></div>
<p class="p">The exact appearance and the output lines might be different on your system. The important outcomes are that a device was
found (the first highlighted line), that the device matches the one on your system (the second highlighted line), and that
the test passed (the final highlighted line).
</p>
<p class="p">If a CUDA-capable device and the CUDA Driver are installed but <samp class="ph codeph">deviceQuery</samp> reports that no CUDA-capable devices are present, this likely means that the <samp class="ph codeph">/dev/nvidia*</samp> files are missing or have the wrong permissions.
</p>
<div class="p">On systems where <samp class="ph codeph">SELinux</samp> is enabled, you might need to temporarily disable this security feature to run <samp class="ph codeph">deviceQuery</samp>. To do this, type:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> setenforce 0</pre>
from the command line as the <dfn class="term">superuser</dfn>.
</div>
<p class="p">Running the <samp class="ph codeph">bandwidthTest</samp> program ensures that the system and the CUDA-capable device are able to communicate correctly. Its output is shown in <a class="xref" href="index.html#running-binaries__valid-results-from-sample-cuda-bandwidthtest-program" shape="rect">Figure 2</a>.
</p>
<div class="fig fignone" id="running-binaries__valid-results-from-sample-cuda-bandwidthtest-program"><a name="running-binaries__valid-results-from-sample-cuda-bandwidthtest-program" shape="rect">
<!-- --></a><span class="figcap">Figure 2. Valid Results from bandwidthTest CUDA Sample</span><br clear="none"></br><div class="imagecenter"><img class="image imagecenter" src="graphics/valid-results-from-sample-cuda-bandwidthtest-program.png" width="550" alt="Valid Results from bandwidthTest CUDA Sample."></img></div><br clear="none"></br></div>
<p class="p">Note that the measurements for your CUDA-capable device description will vary from system to system. The important point is
that you obtain measurements, and that the second-to-last line (in <a class="xref" href="index.html#running-binaries__valid-results-from-sample-cuda-bandwidthtest-program" shape="rect">Figure 2</a>) confirms that all necessary tests passed.
</p>
<p class="p">Should the tests not pass, make sure you have a CUDA-capable NVIDIA GPU on your system and make sure it is properly installed.
</p>
<p class="p">If you run into difficulties with the link step (such as libraries not being found), consult the <cite class="cite">Linux Release Notes</cite> found in the <samp class="ph codeph">doc</samp> folder in the CUDA Samples directory.
</p>
</div>
</div>
</div>
</div>
<div class="topic concept nested0" id="faq"><a name="faq" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#faq" name="faq" shape="rect">7. Frequently Asked Questions</a></h2>
<div class="topic concept nested1" id="faq1"><a name="faq1" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq1" name="faq1" shape="rect">How do I install the Toolkit in a different location?</a></h3>
<div class="body conbody">
<div class="p">
The Runfile installation asks where you wish to install the Toolkit and the Samples during an interactive install. If installing
using a non-interactive install, you can use the --toolkitpath and --samplespath parameters to change the install location:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> ./runfile.run --silent \
--toolkit --toolkitpath=/my/new/toolkit \
--samples --samplespath=/my/new/samples</pre></div>
<div class="p">
The RPM packages don't support custom install locations though the package managers (Yum and Zypper), but it is possible to
install the RPM packages in custom locations using rpm's --relocate parameter:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> rpm --install --relocate /usr/local/cuda-<span class="keyword">6.5</span>=/my/new/toolkit rpmpackage.rpm</pre></div>
<div class="p">
The Deb packages don't support custom install locations through the package manager (apt), but it is possible to install the
Deb packages in custom locations using dpkg's --instdir parameter:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> dpkg --instdir=/my/new/toolkit --install debpackage.deb</pre></div>
<div class="p">
For RPM and Deb packages, you will need to install the packages in the correct order of dependency; normally the package managers
take care of this automatically. For example, if package "foo" has a dependency on package "bar", you should install package
"bar" first, and package "foo" second. You can check the dependencies of a RPM or Deb package as follows:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> rpm -qRp rpmpackage.rpm
<strong class="ph b">$</strong> dpkg -I debpackage.deb | grep Depends</pre></div>
</div>
</div>
<div class="topic concept nested1" id="faq2"><a name="faq2" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq2" name="faq2" shape="rect">Why do I see "nvcc: No such file or directory" when I try to build a CUDA application?</a></h3>
<div class="body conbody">
<div class="p">
Your PATH environment variable is not set up correctly. Ensure that your PATH includes the bin directory where you installed
the Toolkit, usually /usr/local/cuda-<span class="keyword">6.5</span>/bin.
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> export PATH=/usr/local/cuda-<span class="keyword">6.5</span>/bin:$PATH</pre></div>
</div>
</div>
<div class="topic concept nested1" id="faq3"><a name="faq3" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq3" name="faq3" shape="rect">Why do I see "error while loading shared libraries: <lib name>: cannot open shared object file: No such file or directory"
when I try to run a CUDA application that uses a CUDA library?</a></h3>
<div class="body conbody">
<div class="p">
Your LD_LIBRARY_PATH environment variable is not set up correctly. Ensure that your LD_LIBRARY_PATH includes the lib and/or
lib64 directory where you installed the Toolkit, usually /usr/local/cuda-<span class="keyword">6.5</span>/lib{,64}:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> export LD_LIBRARY_PATH=/usr/local/cuda-<span class="keyword">6.5</span>/lib:$LD_LIBRARY_PATH</pre></div>
</div>
</div>
<div class="topic concept nested1" id="faq4"><a name="faq4" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq4" name="faq4" shape="rect">How can I extract the contents of the installers?</a></h3>
<div class="body conbody">
<div class="p">
The Runfile can be extracted into the standalone Toolkit, Samples and Driver Runfiles by using the --extract parameter. These
standalone Runfiles can be further extracted by running:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> ./runfile.run --tar mxvf</pre></div>
<div class="p">
The RPM packages can be extracted by running:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> rpm2cpio rpm_package.rpm | cpio -idmv</pre></div>
<div class="p">
The Deb packages can be extracted by running:
<pre class="pre screen" xml:space="preserve"><strong class="ph b">$</strong> dpkg-deb -x deb_package.deb output_dir</pre></div>
</div>
</div>
<div class="topic concept nested1" id="faq5"><a name="faq5" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq5" name="faq5" shape="rect">How can I tell X to ignore a GPU for compute-only use?</a></h3>
<div class="body conbody">
<p class="p">
To make sure X doesn't use a certain GPU for display, you need to specify which <strong class="ph b">other</strong> GPU to use for display. This is done by editing the xorg.conf file located at /etc/xorg/xorg.conf.
</p>
<div class="p">
You will need to add a section that resembles the following to your xorg.conf file:
<pre class="pre screen" xml:space="preserve">Section "Device"
Identifier "Device0"
Driver "driver_name"
VendorName "vendor_name"
BusID "bus_id"
EndSection
</pre>
The exact details of what you will need to add differ on a case-by-case basis. For example, if you have two NVIDIA GPUs and
you want the first GPU to be used for display, you would replace "driver_name" with "nvidia", "vendor_name" with "NVIDIA Corporation"
and "bus_id" with the Bus ID of the GPU.
</div>
<p class="p">
The Bus ID will resemble "PCI:00:02.0" and can be found by running <samp class="ph codeph">lspci</samp>.
</p>
</div>
</div>
<div class="topic concept nested1" id="faq6"><a name="faq6" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#faq6" name="faq6" shape="rect">Why doesn't the cuda-repo package install the CUDA Toolkit and Drivers?</a></h3>
<div class="body conbody">
<p class="p">
When using RPM or Deb, the downloaded package is a repository package.
Such a package only informs the package manager where to find the actual installation packages, but will not install them.
</p>
<p class="p">
See the <a class="xref" href="index.html#package-manager-overview" shape="rect">Package Manager Installation</a> section for more details.
</p>
</div>
</div>
</div>
<div class="topic concept nested0" id="additional-considerations"><a name="additional-considerations" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#additional-considerations" name="additional-considerations" shape="rect">8. Additional Considerations</a></h2>
<div class="body conbody">
<p class="p">Now that you have CUDA-capable hardware and the NVIDIA CUDA Toolkit installed, you can examine and enjoy the numerous included
programs. To begin using CUDA to accelerate the performance of your own applications, consult the <cite class="cite">CUDA C Programming Guide</cite>, located in <samp class="ph codeph">/usr/local/cuda-<span class="keyword">6.5</span>/doc</samp>.
</p>
<p class="p">A number of helpful development tools are included in the CUDA Toolkit to assist you as you develop your CUDA programs, such
as NVIDIA<sup>®</sup> Nsight™ Eclipse Edition, NVIDIA Visual Profiler, cuda-gdb, and cuda-memcheck.
</p>
<p class="p">For technical support on programming questions, consult and participate in the developer forums at <a class="xref" href="http://developer.nvidia.com/cuda/" target="_blank" shape="rect">http://developer.nvidia.com/cuda/</a>.
</p>
</div>
</div>
<div class="topic concept nested0" id="notices-header"><a name="notices-header" shape="rect">
<!-- --></a><h2 class="title topictitle1"><a href="#notices-header" name="notices-header" shape="rect">Notices</a></h2>
<div class="topic reference nested1" id="notice"><a name="notice" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#notice" name="notice" shape="rect"></a></h3>
<div class="body refbody">
<div class="section">
<h3 class="title sectiontitle">Notice</h3>
<p class="p">ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND
SEPARATELY, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE
WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS
FOR A PARTICULAR PURPOSE.
</p>
<p class="p">Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the
consequences of use of such information or for any infringement of patents or other rights of third parties that may result
from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications
mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information
previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems
without express written approval of NVIDIA Corporation.
</p>
</div>
</div>
</div>
<div class="topic reference nested1" id="trademarks"><a name="trademarks" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#trademarks" name="trademarks" shape="rect"></a></h3>
<div class="body refbody">
<div class="section">
<h3 class="title sectiontitle">Trademarks</h3>
<p class="p">NVIDIA and the NVIDIA logo are trademarks or registered trademarks of NVIDIA Corporation
in the U.S. and other countries. Other company and product names may be trademarks of
the respective companies with which they are associated.
</p>
</div>
</div>
</div>
<div class="topic reference nested1" id="copyright-past-to-present"><a name="copyright-past-to-present" shape="rect">
<!-- --></a><h3 class="title topictitle2"><a href="#copyright-past-to-present" name="copyright-past-to-present" shape="rect"></a></h3>
<div class="body refbody">
<div class="section">
<h3 class="title sectiontitle">Copyright</h3>
<p class="p">© <span class="ph">2009</span>-<span class="ph">2014</span> NVIDIA
Corporation. All rights reserved.
</p>
<p class="p">This product includes software developed by the Syncro Soft SRL (http://www.sync.ro/).</p>
</div>
</div>
</div>
</div>
<hr id="contents-end"></hr>
</article>
</div>
</div>
<script language="JavaScript" type="text/javascript" charset="utf-8" src="../common/formatting/common.min.js"></script>
<script language="JavaScript" type="text/javascript" charset="utf-8" src="../common/scripts/google-analytics/google-analytics-write.js"></script>
<script language="JavaScript" type="text/javascript" charset="utf-8" src="../common/scripts/google-analytics/google-analytics-tracker.js"></script>
<script type="text/javascript">var switchTo5x=true;</script><script type="text/javascript" src="http://w.sharethis.com/button/buttons.js"></script><script type="text/javascript">stLight.options({publisher: "998dc202-a267-4d8e-bce9-14debadb8d92", doNotHash: false, doNotCopy: false, hashAddressBar: false});</script></body>
</html>
distrib
>
Mageia
>
5
>
x86_64
>
media
>
nonfree-release
>
by-pkgid
>
d44b02ea46d82d6a48df31bbd1a088f3
>
files
>
1122
