Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howtos:hardware:nvidia_optimus [2014/03/11 20:05 (UTC)]
sycamorex [Installing Bumblebee] s/it's/its/
howtos:hardware:nvidia_optimus [2015/04/24 06:03 (UTC)] (current)
tommyc
Line 20: Line 20:
 ==== Installing Bumblebee ==== ==== Installing Bumblebee ====
 ---- ----
 +=== The Automated Way ===
 +There is a new, automated way of installing Bumblebee thanks to Slacker: Ryan McQuen.
 +<note warning>​USE AT YOUR OWN RISK!
 +If you have modified the SlackBuilds in any way, this script may not be for you.</​note>​
 +
 +You can run this as root:
 +<​code>​
 +curl https://​raw.githubusercontent.com/​ryanpcmcquen/​linuxTweaks/​master/​slackware/​crazybee.sh | sh
 +</​code>​
 +
 +Alternatively you can download the script and run it as root on your system directly.
 +
 +This script detects multilib, creates the necessary group, adds users and applies the necessary /​etc/​rc.d/​rc.local entries and also comes with a stable option which can be used by passing this instead:
 +
 +<​code>​
 +curl https://​raw.githubusercontent.com/​ryanpcmcquen/​linuxTweaks/​master/​slackware/​crazybee.sh | STABLE=yes sh
 +</​code>​
 +
 +It also uses upgradepkg'​s %%--%%reinstall %%--%%install-new features for use after kernel upgrades.
 +=== The Manual Way ===
 === Getting the SlackBuilds === === Getting the SlackBuilds ===
 A fellow Slacker, jgeboski, originally provided SlackBuilds that mostly follow the [[http://​www.slackbuilds.org/​guidelines/​|SlackBuilds.org]] requirements for Bumblebee. Now, another Slacker has taken over where he has left off on his own [[https://​github.com/​WhiteWolf1776/​Bumblebee-SlackBuilds|github repo]]. Remember to check which directory you're in first, as they will be downloaded to that directory. Assuming you're ready, the SlackBuilds can simply be git cloned as such. Then we're going to change into the new directory and begin the build process. A fellow Slacker, jgeboski, originally provided SlackBuilds that mostly follow the [[http://​www.slackbuilds.org/​guidelines/​|SlackBuilds.org]] requirements for Bumblebee. Now, another Slacker has taken over where he has left off on his own [[https://​github.com/​WhiteWolf1776/​Bumblebee-SlackBuilds|github repo]]. Remember to check which directory you're in first, as they will be downloaded to that directory. Assuming you're ready, the SlackBuilds can simply be git cloned as such. Then we're going to change into the new directory and begin the build process.
Line 35: Line 55:
 There is a README file, but you probably won't be reading it as you're reading this instead, so we're basically going to post it here. There is a README file, but you probably won't be reading it as you're reading this instead, so we're basically going to post it here.
  
-=== Getting the Dependencies ​=== +=== Getting the Source Files === 
-The dependencies, as with all SlackBuilds,​ must be downloaded manually and placed into their respective directories. ​However ​the SLACKBUILDS.TXT file does give links for the downloads ​as well as their MD5SUMs to make sure the files were not corrupt. You can use the provided script to download them and check them against their MD5SUM for corruption, like this:+The source files, as with all SlackBuilds,​ must be downloaded manually and placed into their respective directories. ​Amongst ​the repos are a SLACKBUILDS.TXT file that does give links for the source files as well as their MD5SUMs to make sure the files were not corrupt. You can use the provided script to download them and check them against their MD5SUM for corruption, like this:
 <code sh> <code sh>
 ./​download.sh ./​download.sh
Line 50: Line 70:
  
 === Building and Installing Bumblebee'​s Core === === Building and Installing Bumblebee'​s Core ===
-1. Build and install: bbswitch (optional but highly recommended), libbsd and bumblebee in order as you go.+1. Build and install: bbswitch (optional but highly recommended).
 <​code>​ <​code>​
 # cd bbswitch # You don't actually need to ''​cd''​ as root, but who wants to ''​su''​ all the time? # cd bbswitch # You don't actually need to ''​cd''​ as root, but who wants to ''​su''​ all the time?
 # ./​bbswitch.SlackBuild # ./​bbswitch.SlackBuild
 # upgradepkg --install-new bbswitch-*.t?​z # upgradepkg --install-new bbswitch-*.t?​z
 +</​code>​
 +
 +2. Build and install: libbsd (required).
 +<​code>​
 # cd ../libbsd # cd ../libbsd
 # ./​libbsd.SlackBuild # ./​libbsd.SlackBuild
 # upgradepkg --install-new libbsd-*.t?​z # upgradepkg --install-new libbsd-*.t?​z
 +</​code>​
 +
 +3. Build and install: bumblebee (obviously required).
 +<​code>​
 # cd ../​bumblebee # cd ../​bumblebee
 # ./​bumblebee.SlackBuild # ./​bumblebee.SlackBuild
Line 69: Line 97:
 <​note>​Bumblebee can use either primusrun (requires a mesa rebuild in Slackware 14.0 and below) or bumblebee'​s own optirun. Take your pick which one you would like to use (or you can install both). Each one has their own advantages and disadvantages. <​note>​Bumblebee can use either primusrun (requires a mesa rebuild in Slackware 14.0 and below) or bumblebee'​s own optirun. Take your pick which one you would like to use (or you can install both). Each one has their own advantages and disadvantages.
 </​note>​ </​note>​
 +
 +=== Primus ===
 +Primus, like optirun (instructions below) can be used to run your desired program via bumblebee. Primus also comes with a COMPAT32 option as well.
 +
 +<note warning>
 +If you are using Slackware 14.0 or older you need to rebuild mesa. The new github repository does not offer a SlackBuild for mesa to support Slackware 14.0 or older. Therefore you must use Slackware 14.1 or newer, or rebuild mesa manually with a different script. One can choose to use the old repository and simply update the SlackBuild script appropriately,​ or add ''​%%--%%enable-shared-glapi''​ into a mesa.SlackBuild from the source of a newer Slackware version.
 +<​code>​
 +# # For the old repository, one would have done:
 +# cd ../mesa
 +# ./​mesa.SlackBuild
 +</​code>​
 +mesa does not have a COMPAT32 option because it is an official Slackware package, but you can easily create the compat32 package after creating the original package by using:
 +<​code>​
 +# ./​mesa-compat32.SlackBuild # Only in the old repository
 +</​code>​
 +</​note>​
 +
 +1. Build and install: primus
 +<​code>​
 +# cd ../primus
 +# ./​primus.SlackBuild
 +# upgradepkg --install-new primus-*.t?​z
 +</​code>​
 +<​code>​
 +# COMPAT32=yes ./​primus.SlackBuild
 +</​code>​
  
 === VirtualGL === === VirtualGL ===
 +VirtualGL provides support for optirun that also allows one to run programs via bumblebee. However, it is recommended that one uses primusrun for a few reasons. ​
 <note warning> <note warning>
 Although VirtualGL (and its dependency libjpeg-turbo) are still supported by the Bumblebee project and maintained by their developers, the new github repo does not include SlackBuild scripts for these packages. This section is for the old github repository that was once maintained by jgeboski. If you would like to use VirtualGL (e.g. you're in one of the rare cases where VirtualGL provides better performance than primus) then you can use your own personal SlackBuilds or the old ones (although the old SlackBuilds will be out-of-date). Although VirtualGL (and its dependency libjpeg-turbo) are still supported by the Bumblebee project and maintained by their developers, the new github repo does not include SlackBuild scripts for these packages. This section is for the old github repository that was once maintained by jgeboski. If you would like to use VirtualGL (e.g. you're in one of the rare cases where VirtualGL provides better performance than primus) then you can use your own personal SlackBuilds or the old ones (although the old SlackBuilds will be out-of-date).
Line 98: Line 153:
 <​code>​ <​code>​
 # COMPAT32=yes ./​VirtualGL.SlackBuild # COMPAT32=yes ./​VirtualGL.SlackBuild
-</​code>​ 
- 
-=== Primus === 
-Primus is another program designed to be used much like optirun. However, primus does not require VirtualGL (and therefore will not require libjpeg-turbo as well) but only requires mesa with %%--%%enable-shared-glapi (Slackware 14.0 and below must have mesa rebuilt). Primus also comes with a COMPAT32 option as well. 
- 
-<note warning> 
-The new github repository does not offer a SlackBuild for mesa to support Slackware 14.0 or older. Therefore you must use Slackware 14.1 or newer, or rebuild mesa manually with a different script. One can choose to use the old repository and simply update the SlackBuild script appropriately,​ or add ''​%%--%%enable-shared-glapi''​ into a mesa.SlackBuild from the source of a newer Slackware version. 
-<​code>​ 
-# # For the old repository, one would have done: 
-# cd ../mesa 
-# ./​mesa.SlackBuild 
-</​code>​ 
-mesa does not have a COMPAT32 option because it is an official Slackware package, but you can easily create the compat32 package after creating the original package by using: 
-<​code>​ 
-# ./​mesa-compat32.SlackBuild # Only in the old repository 
-</​code>​ 
-</​note>​ 
- 
-1. Build and install: primus 
-<​code>​ 
-# cd ../primus 
-# ./​primus.SlackBuild 
-# upgradepkg --install-new primus-*.t?​z 
-</​code>​ 
-<​code>​ 
-# COMPAT32=yes ./​primus.SlackBuild 
 </​code>​ </​code>​
  
Line 129: Line 158:
 If you want to use the nVidia proprietary drivers, you must not use nouveau, as the drivers interfere with each other. This can be prevented by removing nouveau, installing xf86-video-nouveau-blacklist from /extra, or blacklisting nouveau manually. If you want to use the nVidia proprietary drivers, you must not use nouveau, as the drivers interfere with each other. This can be prevented by removing nouveau, installing xf86-video-nouveau-blacklist from /extra, or blacklisting nouveau manually.
  
-<​note>​ 
 This part is entirely optional. Slackware 13.37 and above comes with xf86-video-nouveau,​ the open source nVidia graphics card drivers. If you are using this, you do not need the closed source proprietary nVidia drivers. However, if you wish to use the closed source drivers, then install the packages listed in this section before going on. This part is entirely optional. Slackware 13.37 and above comes with xf86-video-nouveau,​ the open source nVidia graphics card drivers. If you are using this, you do not need the closed source proprietary nVidia drivers. However, if you wish to use the closed source drivers, then install the packages listed in this section before going on.
  
 <note warning> <note warning>
-Some nvidia driver versions are incompatible with certain kernel versions. One example is nvidia's 319.32 ​driver ​and the 3.10.* kernel ​seriesIn order to use the official proprietary ​nvidia ​319.32 ​driver with the 3.10.* kernel series, one had to apply this patch: http://​sprunge.us/​UaaH or use a newer version of the driver that does support ​the kernel version. You can also [[http://​www.slackbuilds.org/​faq/#​version_update|follow the SlackBuilds.org guideline ​when newer version ​is out and the maintainer has not updated it]].+Some nvidia driver versions are incompatible with certain kernel versions ​and vice versa (some kernel versions are incompatible with some nvidia driver ​versions) for various reasonsA specific ​kernel ​configuration,​ a specific nvidia driver against a specific kernel version amongst other possibilitiesGenerally it is best to use the nvidia driver ​package provided along with the kernel ​packages provided by your Slackware ​version. You can also [[http://​www.slackbuilds.org/​faq/#​version_update|follow the SlackBuilds.org guideline]] for manually updating ​a version ​of some software yourself
 </​note>​ </​note>​
  
-1Build and installlibvdpau ​(Now required to assist in building the newer nvidia-bumblebee packages)+<​note>​If you are using Slackware 14.1 or older, you will need to install libvdpau. Newer Slackware versions now ship libvdpau.
 <​code>​ <​code>​
 # cd ../libvdpau # cd ../libvdpau
Line 142: Line 170:
 # upgradepkg --install-new libvdpau-*.t?​z # upgradepkg --install-new libvdpau-*.t?​z
 </​code>​ </​code>​
 +</​note>​
  
-2. Build and install: nvidia-bumblebee+1. Build and install: nvidia-bumblebee
 <code sh> <code sh>
 # cd ../​nvidia-bumblebee # cd ../​nvidia-bumblebee
Line 153: Line 182:
 </​code>​ </​code>​
  
-3. Build and install: nvidia-kernel+2. Build and install: nvidia-kernel
 <code sh> <code sh>
 # cd ../​nvidia-kernel # cd ../​nvidia-kernel
Line 159: Line 188:
 # upgradepkg --install-new nvidia-kernel-*.t?​z # upgradepkg --install-new nvidia-kernel-*.t?​z
 </​code>​ </​code>​
-<​code>​ 
-# COMPAT32=yes ./​nvidia-kernel.SlackBuild # Only for 32-bit compatible binaries and libraries on an x86_64 based system. 
-</​code>​ 
-</​note>​ 
 ==== Post-Installation ==== ==== Post-Installation ====
 Excellent. Now we're ready to do some post-installation setup. The bumblebee package provided us with an rc.bumblebee script in /etc/rc.d where the other startup scripts are also located. Remember to make this script executable and, if you so desire, start it! Excellent. Now we're ready to do some post-installation setup. The bumblebee package provided us with an rc.bumblebee script in /etc/rc.d where the other startup scripts are also located. Remember to make this script executable and, if you so desire, start it!
 <​code>​ <​code>​
-# chmod +x /​etc/​rc.d/​rc.bumblebee +# chmod +x /​etc/​rc.d/​rc.bumblebeed 
-# /​etc/​rc.d/​rc.bumblebee ​start+# /​etc/​rc.d/​rc.bumblebeed ​start
 </​code>​ </​code>​
  
 If you would like bumblebee to autostart with the system, you can add the following to /​etc/​rc.d/​rc.local:​ If you would like bumblebee to autostart with the system, you can add the following to /​etc/​rc.d/​rc.local:​
 <code sh> <code sh>
-[ -x /​etc/​rc.d/​rc.bumblebee ​] && /​etc/​rc.d/​rc.bumblebee ​start+[ -x /​etc/​rc.d/​rc.bumblebeed ​] && /​etc/​rc.d/​rc.bumblebeed ​start
 </​code>​ </​code>​
  
 You can even go a step further by having bumblebee stop with your system by adding the following lines to /​etc/​rc.d/​rc.local_shutdown. You can create this file if it does not exist. You can even go a step further by having bumblebee stop with your system by adding the following lines to /​etc/​rc.d/​rc.local_shutdown. You can create this file if it does not exist.
 <code sh> <code sh>
-[ -x /​etc/​rc.d/​rc.bumblebee ​] && /​etc/​rc.d/​rc.bumblebee ​stop+[ -x /​etc/​rc.d/​rc.bumblebeed ​] && /​etc/​rc.d/​rc.bumblebeed ​stop
 </​code>​ </​code>​
  

In Other Languages
QR Code
QR Code howtos:hardware:nvidia_optimus (generated for current page)