[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

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 revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howtos:hardware:nvidia_optimus [2014/03/08 22:52 (UTC)] – tommychowtos:hardware:nvidia_optimus [2014/10/09 07:03 (UTC)] – Added automated installer info. 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.
 +
 +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 51:
 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 66:
  
 === 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 72: Line 96:
 === VirtualGL === === VirtualGL ===
 <note warning> <note warning>
-Although VirtualGL (and it's 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).
 </note> </note>
 1. Build and install: libjpeg-turbo (32-bit compatibility available) 1. Build and install: libjpeg-turbo (32-bit compatibility available)
Line 133: Line 157:
  
 <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 series. In 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 a 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 reasons. A specific kernel configuration, a specific nvidia driver against a specific kernel version amongst other possibilities. Generally 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>
  
Line 166: Line 190:
 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>
  

Trace:

howtos:hardware:nvidia_optimus ()