(Guide) Installing Nvidia + Bumblebee + CUDA for Optimus enabled Laptops

[moy44]

I got to step 15 but couldn't get optirun to work.
In the guide it doesn't look like we are disabling nouveau anywhere, shouldn't this cause a conflict with the Nvidia driver loading?

root@DEFNOTKALI:~# lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 3D controller: NVIDIA Corporation GK104M [GeForce GTX 870M] (rev a1)

root@DEFNOTKALI:~# modprobe nvidia

root@DEFNOTKALI:~# modprobe nvidia-uvm

root@DEFNOTKALI:~# optirun glxspheres64
[  146.023065] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[  146.023114] [ERROR]Could not connect to bumblebee daemon - is it running?

root@DEFNOTKALI:~# /etc/init.d/bumblebeed start
[ ok ] Starting bumblebeed (via systemctl): bumblebeed.service.

root@DEFNOTKALI:~# optirun glxspheres64
[  166.013170] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 

[  166.013201] [ERROR]Aborting because fallback start is disabled.

root@DEFNOTKALI:~# dmesg | tail -n 100
[    8.332790] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
[    8.333960] ACPI: Video Device [PEGP] (multi-head: yes  rom: yes  post: no)
[    8.333964] ACPI Error: [\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)
[    8.333968] ACPI Error: Method parse/execution failed [\_SB.PCI0.PEG0.PEGP.DD02._BCL] (Node ffff8802270e2220), AE_NOT_FOUND (20150930/psparse-542)
[    8.334106] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:5e/LNXVIDEO:00/input/input16
[    8.335503] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    8.335609] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input17
...
[    8.373529] intel_rapl: Found RAPL domain package
...
[    8.373580] intel_rapl: RAPL package 0 domain dram locked by BIOS
[    8.396062] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
[    8.540116] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    8.540124] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
[    8.553731] fbcon: inteldrmfb (fb0) is primary device
[    8.587479] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    8.599189] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input18
[    8.599255] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input19
[    8.599310] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input20
[    8.865906] Netfilter messages via NETLINK v0.30.
[    9.768266] Console: switching to colour frame buffer device 400x112
[    9.776747] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   17.625014] fuse init (API version 7.23)
[  132.106742] nvidia: module license 'NVIDIA' taints kernel.
[  132.106746] Disabling lock debugging due to kernel taint
[  132.114807] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
[  132.114995] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
[  132.114998] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 PST 2016
[  138.579100] nvidia_uvm: Loaded the UVM driver, major device number 247
[  163.380537] bbswitch: version 0.8
[  163.380544] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[  163.380549] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[  163.380560] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  163.380653] bbswitch: detected an Optimus _DSM function
[  163.380667] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[  163.383584] nvidia_uvm: Unregistered the UVM driver
[  163.400337] [drm] Module unloaded
[  163.437393] bbswitch: disabling discrete graphics
[  163.437408] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  163.452106] pci 0000:01:00.0: Refused to change power state, currently in D0
[  165.457270] bbswitch: enabling discrete graphics
[  166.007073] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
[  166.007077] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 PST 2016

root@DEFNOTKALI:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin:/usr/local/cuda-7.5/bin

root@DEFNOTKALI:~# cat /etc/bumblebee/bumblebee.conf 
# Configuration file for Bumblebee. Values should **not** be put between quotes

## Server options. Any change made in this section will need a server restart
# to take effect.
[bumblebeed]
# The secondary Xorg server DISPLAY number
VirtualDisplay=:8
# Should the unused Xorg server be kept running? Set this to true if waiting
# for X to be ready is too long and don't need power management at all.
KeepUnusedXServer=false
# The name of the Bumbleblee server group name (GID name)
ServerGroup=bumblebee
# Card power state at exit. Set to false if the card shoud be ON when Bumblebee
# server exits.
TurnCardOffAtExit=false
# The default behavior of '-f' option on optirun. If set to "true", '-f' will
# be ignored.
NoEcoModeOverride=false
# The Driver used by Bumblebee server. If this value is not set (or empty),
# auto-detection is performed. The available drivers are nvidia and nouveau
# (See also the driver-specific sections below)
Driver=nvidia
# Directory with a dummy config file to pass as a -configdir to secondary X
XorgConfDir=/etc/bumblebee/xorg.conf.d

## Client options. Will take effect on the next optirun executed.
[optirun]
# Acceleration/ rendering bridge, possible values are auto, virtualgl and
# primus.
Bridge=auto
# The method used for VirtualGL to transport frames between X servers.
# Possible values are proxy, jpeg, rgb, xv and yuv.
VGLTransport=proxy
# List of paths which are searched for the primus libGL.so.1 when using
# the primus bridge
PrimusLibraryPath=/usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus
# Should the program run under optirun even if Bumblebee server or nvidia card
# is not available?
AllowFallbackToIGC=false

# Driver-specific settings are grouped under [driver-NAME]. The sections are
# parsed if the Driver setting in [bumblebeed] is set to NAME (or if auto-
# detection resolves to NAME).
# PMMethod: method to use for saving power by disabling the nvidia card, valid
# values are: auto - automatically detect which PM method to use
#         bbswitch - new in BB 3, recommended if available
#       switcheroo - vga_switcheroo method, use at your own risk
#             none - disable PM completely
# https://github.com/Bumblebee-Project/Bumblebee/wiki/Comparison-of-PM-methods

## Section with nvidia driver specific options, only parsed if Driver=nvidia
[driver-nvidia]
# Module name to load, defaults to Driver if empty or unset
KernelDriver=nvidia-current
PMMethod=auto
# colon-separated path to the nvidia libraries
LibraryPath=/usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia
# comma-separated path of the directory containing nvidia_drv.so and the
# default Xorg modules path
XorgModulePath=/usr/lib/nvidia,/usr/lib/xorg/modules
XorgConfFile=/etc/bumblebee/xorg.conf.nvidia

## Section with nouveau driver specific options, only parsed if Driver=nouveau
[driver-nouveau]
KernelDriver=nouveau
PMMethod=auto
XorgConfFile=/etc/bumblebee/xorg.conf.nouveau

root@DEFNOTKALI:~# cat /etc/bumblebee/xorg.conf.nvidia 
Section "ServerLayout"
    Identifier  "Layout0"
    Option      "AutoAddDevices" "false"
    Option      "AutoAddGPU" "false"
EndSection

Section "Device"
    Identifier  "DiscreteNvidia"
    Driver      "nvidia"
    VendorName  "NVIDIA Corporation"
    BusID       "PCI:01:00:0"

#   If the X server does not automatically detect your VGA device,
#   you can manually set it here.
#   To get the BusID prop, run `lspci | egrep 'VGA|3D'` and input the data
#   as you see in the commented example.
#   This Setting may be needed in some platforms with more than one
#   nvidia card, which may confuse the proprietary driver (e.g.,
#   trying to take ownership of the wrong device). Also needed on Ubuntu 13.04.
#   BusID "PCI:01:00:0"

#   Setting ProbeAllGpus to false prevents the new proprietary driver
#   instance spawned to try to control the integrated graphics card,
#   which is already being managed outside bumblebee.
#   This option doesn't hurt and it is required on platforms running
#   more than one nvidia graphics card with the proprietary driver.
#   (E.g. Macbook Pro pre-2010 with nVidia 9400M + 9600M GT).
#   If this option is not set, the new Xorg may blacken the screen and
#   render it unusable (unless you have some way to run killall Xorg).
    Option "ProbeAllGpus" "false"

    Option "NoLogo" "true"
    Option "UseEDID" "false"
    Option "UseDisplayDevice" "none"
EndSection

root@DEFNOTKALI:~# service bumblebeed restart

root@DEFNOTKALI:~# modinfo nvidia
modinfo: ERROR: Module nvidia not found.

root@DEFNOTKALI:~# find 2> /dev/null / -name nvidia*.ko
/var/lib/dkms/nvidia-current/352.79/4.4.0-kali1-amd64/x86_64/module/nvidia-current.ko
/var/lib/dkms/nvidia-current/352.79/4.4.0-kali1-amd64/x86_64/module/nvidia-current-uvm.ko
/lib/modules/4.4.0-kali1-amd64/updates/dkms/nvidia-current.ko
/lib/modules/4.4.0-kali1-amd64/updates/dkms/nvidia-current-uvm.ko

[Davide3i]

Here we're back again.
After installing the last Kali version (2016.1), I'm finding impossible to install the nVidia drivers with the guide in the first post: simply, like other users said, the guide is not applying from the step 15.
Someone found a way to make Kali work with those **** graphic drivers?

[acostagera]

So after 4 clean installs of Kali 2016 and two days trying to get this working. I was able to get the nvidia drivers installed on my laptop. I use some of the steps from this thread and some from http://fixmynix.com/install-and-conf...bee-in-debian/. At first I was getting:

root@KALI:~# optirun glxspheres64
[ 146.023065] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 146.023114] [ERROR]Could not connect to bumblebee daemon - is it running?

Tried something else, then I got:

root@DEFNOTKALI:~# optirun glxspheres64
[ 166.013170] [ERROR]Cannot access secondary GPU - error: [XORG] (EE)

Finally got it to work and the following is a history of the commands I ended up using. For virtualgl and Cuda this assumes you downloaded from the links in the first post and the files are located in your Downloads folder.

apt-get update
apt-get upgrade
apt-get dist-upgrade
apt-get update
apt-get upgrade
modprobe -r nouveau
modprobe -r vga_switcheroo
apt-get install gcc make linux-headers-$(uname -r)
apt-get install dksm bbswitch-dkms
apt-get install dkms bbswitch-dkms
modprobe bbswitch load_state=0

Created /etc/modprobe.d/nouveau-blacklist.conf and added "blacklist nouveau" with out quotes

nano /etc/modprobe.d/nouveau-blacklist.conf

Added "bbswitch load_state=0" with out quotes to /etc/modules

nano /etc/modules

apt-get install nvidia-kernel-dkms nvidia-xconfig nvidia-settings
apt-get install nvidia-vdpau-driver vdpau-va-driver mesa-utils
apt-get install bumblebee-nvidia
sudo dpkg -i /root/Downloads/virtualgl_2.5_amd64.deb
usermod -aG bumblebee $USER
service bumblebeed restart
apt-get install devscripts
apt-get build-dep bumblebee
apt-get source bumblebee
sed -i 's/"Xorg"/"\/usr\/lib\/xorg\/Xorg"/' bumblebee-3.2.1/src/bbsecondary.h
bumblebee-3.2.1/
dpkg-buildpackage -us -uc -nc
dpkg -i ../bumblebee_3.2.1-10_amd64.deb
service bumblebeed restart
reboot

Uncommented BusID "PCI:01:00:0" and replace the 1 with the number you get from lspci

nano /etc/bumblebee/xorg.conf.nvidia

service bumblebeed restart
optirun -v -b virtualgl -c jpeg glxgears
apt-get install freeglut3-dev libxmu-dev libpcap-dev

Add "export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-7.5/bin" to the end of .bashrc without quotes.

nano ~/.bashrc

export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-7.5/bin
optirun -v -b virtualgl -c jpeg glxgears
optirun -vv glxgears
chmod +x Downloads/cuda_7.5.18_linux.run
./Downloads/cuda_7.5.18_linux.run --override compiler

Make sure this lines exist if not add to match in /etc/ld.so.conf
include /etc/ld.so.conf.d/*.conf
/usr/local/cuda-7.5/lib64

nano /etc/ld.so.conf

ldconfig
apt-get install libcuda1
cd /root/NVIDIA_CUDA-7.5_Samples/1_Utilities/deviceQuery/
make
optirun ./deviceQuery

Hope this is of use to some you that have been having problems.

[Quest]

Thanks for sharing acostagera

Side note: This thread is going on its second year and I still can't believe how much of a circus it is to install a driver and related GPU acceleration programs. For you nVidia/oclHashcat/Windows users, here is a mini howtoo, because sometimes it's better to switch OS for certain operations, rather than checking-in a nuthouse.

- Download and install CUDA,
https://developer.nvidia.com/cuda-downloads
(That will also install the version compatible nVidia driver).

- Download Hashcat GUI,
https://hashkiller.co.uk/hashcat-gui.aspx
No install. Decompress in C: inside a folder named 'HashcatGUI'
C:\HashcatGUI

- Download oclHashcat
http://hashcat.net/oclhashcat/
No install. Decompress inside the previously created 'HashcatGUI' folder.
C:\HashcatGUI\cudaHashcat-2.01

- Place your desired .cap file inside the cap2hccap folder and rename it 'wpa.cap'
C:\HashcatGUI\cap2hccap\wpa.cap

- Start App.HashcatGUI.exe
C:\HashcatGUI\App.HashcatGUI.exe
Hash File > Click on '...' and navigate to C:\HashcatGUI\cap2hccap\, and select your 'wpa.cap'. That will automatically create a hccap file.
C:\HashcatGUI\cap2hccap\wpa.hccap

- See '7 Hashcat GUI setup.jpg' for the rest of options.

7 Hashcat GUI setup.jpg

* Once the main Hashcat/oclHashcat interface setup, Commands > Generate, to see the resulting command line!!

* [Ctrl]+[C] in the CMD window to stop at any time.

[underscore]

thx for sharing your findings acostagera. After struggling 2 days with exactly the same problems this saved my day


Now i'm stuck on adding CUDA support by building CPyrit. Following step 3 of the first post. gcc-5 isn't supported. It gives me below output:
Is there any way to build CPyrit with another gcc-version?

root@kali:/home/pyrit_svn/cpyrit_cuda# python setup.py build
running build
running build_ext
Compiling CUDA module using nvcc 7.5, V7.5.17...
Executing '/usr/local/cuda/bin/nvcc -m64 --host-compilation C -Xcompiler "-fPIC" --ptx ./_cpyrit_cudakernel.cu'
nvcc warning : option 'host-compilation' has been deprecated
In file included from /usr/local/cuda/bin/..//include/cuda_runtime.h:76:0,
from <command-line>:0:
/usr/local/cuda/bin/..//include/host_config.h:115:2: error: #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
#error -- unsupported GNU version! gcc versions later than 4.9 are not supported!

Edit (fix)

To prevent this error just uncomment line 115 in: /usr/local/cuda/include/host_config.h

//#error -- unsupported GNU version! gcc versions later than 4.9 are not supported!

Now the GPU will be recognized using:

optirun pyrit benchmark

root@kali:~/cpyrit-cuda-0.4.0# optirun pyrit benchmark
Pyrit 0.4.0 (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+

Running benchmark (28184.1 PMKs/s)... -

Computed 28184.12 PMKs/s total.
#1: 'CUDA-Device #1 'GeForce GTX 860M'': 27098.4 PMKs/s (RTT 2.8)
#2: 'CPU-Core (SSE2)': 489.2 PMKs/s (RTT 3.2)
#3: 'CPU-Core (SSE2)': 494.4 PMKs/s (RTT 3.2)
#4: 'CPU-Core (SSE2)': 504.2 PMKs/s (RTT 3.2)
#5: 'CPU-Core (SSE2)': 503.8 PMKs/s (RTT 3.2)
#6: 'CPU-Core (SSE2)': 496.8 PMKs/s (RTT 3.2)
#7: 'CPU-Core (SSE2)': 498.6 PMKs/s (RTT 3.2)
#8: 'CPU-Core (SSE2)': 500.7 PMKs/s (RTT 3.2)
root@kali:~/cpyrit-cuda-0.4.0#

[Davide3i]

So after 4 clean installs of Kali 2016 and two days trying to get this working. I was able to get the nvidia drivers installed on my laptop. I use some of the steps from this thread and some from http://fixmynix.com/install-and-conf...bee-in-debian/.

I tried with your mini-guide, but still no luck for me, acostagera: the infamous

[  816.077860] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 

[  816.077915] [ERROR]Aborting because fallback start is disabled.

error is still getting me.

[Walrix]

root@kali:~# lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 21)
01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce 920M] (rev a1)
root@kali:~# modprobe nvidia
root@kali:~# modprobe nvidia-uvm

I have restarted bumblebeed. Included code before restart

root@kali:~# optirun glxspheres64
[ 7543.790109] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 7543.790269] [ERROR]Could not connect to bumblebee daemon - is it running?
root@kali:~# service bumblebeed restart
root@kali:~# optirun glxspheres64
[ 6973.249397] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 

[ 6973.249733] [ERROR]Aborting because fallback start is disabled.

http://pastebin.com/gBAKijSf
rest of output

I have done everything as said until "run optirun glxspheres64", which shown me error right up there.

[arslan2012]

root@kali:~# lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 21)
01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce 920M] (rev a1)
root@kali:~# modprobe nvidia
root@kali:~# modprobe nvidia-uvm

I have restarted bumblebeed. Included code before restart

root@kali:~# optirun glxspheres64
[ 7543.790109] [ERROR]The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect.
[ 7543.790269] [ERROR]Could not connect to bumblebee daemon - is it running?
root@kali:~# service bumblebeed restart
root@kali:~# optirun glxspheres64
[ 6973.249397] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 

[ 6973.249733] [ERROR]Aborting because fallback start is disabled.

http://pastebin.com/gBAKijSf
rest of output

I have done everything as said until "run optirun glxspheres64", which shown me error right up there.

gedit /etc/bumblebee/bumblebee.conf
change VirtualDisplay=:8 to VirtualDisplay=:0

[akhtar4ever]

Hey
I am getting error while running the command "modinfo nvidia"
Below is the error:

root@babc:~# modprobe nvidia
modprobe: ERROR: ../libkmod/libkmod-module.c:809 kmod_module_insert_module() could not find module by name='nvidia'
modprobe: ERROR: could not insert 'nvidia': Function not implemented
root@abc:~# modprobe nvidia-uvm
modprobe: FATAL: Module nvidia-uvm not found.


Please let me know how to proceed. I am stuck with this issue.
Thanks

[xklathos]

Hey guys i do encounter a problem with my CUDA installation everything seems to work fine but /usr/local/cuda-7.5 is not there also examples and such are missing. optirun gives me output but i have to restart bumblebeed service in every reboot. So my first question is to resolve bumblebeed service problem and second is about CUDA output given below whether or not it is a problem.

-------------------------------------------------------------
Do you accept the previously read EULA? (accept/decline/quit): accept
You are attempting to install on an unsupported configuration. Do you wish to continue? ((y)es/(n)o) [ default is no ]: yes
Install NVIDIA Accelerated Graphics Driver for Linux-x86_64 352.39? ((y)es/(n)o/(q)uit): no
Install the CUDA 7.5 Toolkit? ((y)es/(n)o/(q)uit): yes
Enter Toolkit Location [ default is /usr/local/cuda-7.5 ]: 
Do you want to install a symbolic link at /usr/local/cuda? ((y)es/(n)o/(q)uit): y
Install the CUDA 7.5 Samples? ((y)es/(n)o/(q)uit): y
Enter CUDA Samples Location [ default is /root ]: /usr/share/CUDA/
Error: unsupported compiler: 6.1.1. Use --override to override this check.
Missing recommended library: libXi.so

Error: cannot find Toolkit in /usr/local/cuda-7.5

===========
= Summary =
===========

Driver:   Not Selected
Toolkit:  Installation Failed. Using unsupported Compiler.
Samples:  Cannot find Toolkit in /usr/local/cuda-7.5

[k0desys]

Hey guys i do encounter a problem with my CUDA installation everything seems to work fine but /usr/local/cuda-7.5 is not there also examples and such are missing. optirun gives me output but i have to restart bumblebeed service in every reboot. So my first question is to resolve bumblebeed service problem and second is about CUDA output given below whether or not it is a problem.

-------------------------------------------------------------
Do you accept the previously read EULA? (accept/decline/quit): accept
You are attempting to install on an unsupported configuration. Do you wish to continue? ((y)es/(n)o) [ default is no ]: yes
Install NVIDIA Accelerated Graphics Driver for Linux-x86_64 352.39? ((y)es/(n)o/(q)uit): no
Install the CUDA 7.5 Toolkit? ((y)es/(n)o/(q)uit): yes
Enter Toolkit Location [ default is /usr/local/cuda-7.5 ]: 
Do you want to install a symbolic link at /usr/local/cuda? ((y)es/(n)o/(q)uit): y
Install the CUDA 7.5 Samples? ((y)es/(n)o/(q)uit): y
Enter CUDA Samples Location [ default is /root ]: /usr/share/CUDA/
Error: unsupported compiler: 6.1.1. Use --override to override this check.
Missing recommended library: libXi.so

Error: cannot find Toolkit in /usr/local/cuda-7.5

===========
= Summary =
===========

Driver:   Not Selected
Toolkit:  Installation Failed. Using unsupported Compiler.
Samples:  Cannot find Toolkit in /usr/local/cuda-7.5

The problem of Bumblebeed service not autostarting is due to kali network policy.
Kali wil by default disallow autostarting services. Have a look at the link for the solution

http://docs.kali.org/policy/kali-lin...rvice-policies

[emrys]

Hello There Mates,

Please anyone let me know if I can install everything nvidia latest drivers +cuda+bumble bee etc using this guide on my Nvidia GTX 970 GPU system or should I just install nvidia driver file ( .run file ) and cuda instead using this guide https://forums.kali.org/showthread.p...and-oclHashcat

[Rarity]

emrys, is your laptop Optimus enabled? (aka a dedicated graphics card in combination with an integrated one).

[emrys]

emrys, is your laptop Optimus enabled? (aka a dedicated graphics card in combination with an integrated one).

Actually Im not using Laptop but a Desktop PC
Following is the Configuration of my PC

CPU : Intel i7 4770k

GPU : Nvidia GTX 970

MOBO : Asus Maximus HEro VII

120GB SSD 4TB HDD

So the Computer has both the internal integrated intel graphics as well as a dedicated GPU GTX 970 and im using the GPU

[Rarity]

Actually Im not using Laptop but a Desktop PC
Following is the Configuration of my PC

CPU : Intel i7 4770k

GPU : Nvidia GTX 970

MOBO : Asus Maximus HEro VII

120GB SSD 4TB HDD

So the Computer has both the internal integrated intel graphics as well as a dedicated GPU GTX 970 and im using the GPU

I haven't personally used the guide you linked to but you should use that instead of this one. This how-to is specific for laptops that are Optimus enabled.

[rotor]

Hello! I have laptop lenovo y570, Kali Rollings 2016.2 4.8.0-kali2-amd64, 2 graphical chipsets :

1) Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller
2) VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 555M]

I want to combine resources of both graphical cards for brutforcing, but about two weeks I can't to install necessary drivers for nVidia. Who can helps me with new tutorials for kali rolling 2016.2 ?

PS : sorry for my english, is not my main language.

[Bu5h1d0]

Rotor, I'm not sure if this will work as I have not tried it but I found this tutorial a few hours ago https://wheresmykeyboard.com/2016/10...016-2-rolling/. I do know the tutorial in this thread did not work for me as I came across a missing uri sources list error.

If anyone tries the about method let me know if it worked please as a few methods I tried made me have to completely reinstall Kali a few times.

[H3xCmd]

Rotor, I'm not sure if this will work as I have not tried it but I found this tutorial a few hours ago https://wheresmykeyboard.com/2016/10...016-2-rolling/. I do know the tutorial in this thread did not work for me as I came across a missing uri sources list error.

If anyone tries the about method let me know if it worked please as a few methods I tried made me have to completely reinstall Kali a few times.

unable to Complete and install the Toolkit. Is there anyway at the Dynamic Link step below to link to the cuda toolkit install from the repo (apt-get install nvidia-cuda-toolkit

####
Make sure this lines exist if not add to match in /etc/ld.so.conf
include /etc/ld.so.conf.d/*.conf
/usr/local/cuda-7.5/lib64
#####

Following errors with steps from
https://wheresmykeyboard.com/2016/10...016-2-rolling/

apt-get install dksm bbswitch-dkms <<-- no install from repo

apt-get build-dep bumblebee <<-----ISSUES
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
builddeps:bumblebee : Depends: dh-systemd (>= 1.4) but it is not installable
E: Unable to correct problems, you have held broken packages.

apt-get install dh-systemd <<-------debhelper

Reading package lists... Done
Building dependency tree
Reading state information... Done
Package dh-systemd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
debhelper

E: Package 'dh-systemd' has no installation candidate

apt-get install debhelper <<---------already the newest version
Reading package lists... Done
Building dependency tree
Reading state information... Done
debhelper is already the newest version (10.2.2).
debhelper set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.


https://packages.debian.org/jessie/a...stemd/download
dpkg -i dh-systemd_1.22_all.deb <<----- dependency problems

Selecting previously unselected package dh-systemd.
(Reading database ... 364453 files and directories currently installed.)
Preparing to unpack dh-systemd_1.22_all.deb ...
Unpacking dh-systemd (1.22) ...
Replaced by files in installed package debhelper (10.2.2) ...
dpkg: dependency problems prevent configuration of dh-systemd:
debhelper (10.2.2) breaks dh-systemd (<< 1.38) and is installed.
Version of dh-systemd to be configured is 1.22.

dpkg: error processing package dh-systemd (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
dh-systemd


------------------------------------------------
sed -i 's/"Xorg"/"\/usr\/lib\/xorg\/Xorg"/' bumblebee-3.2.1/src/bbsecondary.h
sed: can't read bumblebee-3.2.1/src/bbsecondary.h: No such file or directory

-------------------------------
bumblebee-3.2.1/
bash: bumblebee-3.2.1/: No such file or directory

--------------------------
./cuda_7.5.18_linux.run --override compiler
Y/N/Y/Enter/Y/Enter/
Toolkit: Installation Failed
Warning: cannot find Toolkit in /usr/local/cuda-7.5. Use --toolkitpath to specify the toolkit location.

------------------------
sudo sh cuda_8.0.44_linux.run --override
Y/N/Y/Enter/Y/Enter/
Warning: cannot find Toolkit in /usr/local/cuda-8.0. Use --toolkitpath to specify the toolkit location.

sudo sh cuda_8.0.44_linux.run --override --toolkitpath
ERROR: toolkitpath: path must be absolute.

sudo sh cuda_8.0.44_linux.run --override --toolkitpath /usr/local/cuda-8.0/
ERROR: toolkitpath: path must be absolute.

sudo sh cuda_8.0.44_linux.run --override --/usr/local/cuda-8.0/
Unknown option: /usr/local/cuda-8.0/

[Bu5h1d0]

I had issues with the cuda install from nvidia as well and ended up using the one from the repo.

apt-get install dksm bbswitch-dkms <---- theres a typo in his tutorial, it should be dkms not dksm
apt-get build-dep bumblebee <<-----ISSUES <--------- I had used a debian repo in my source list but not sure which one, wish I wrote it down because I wanted to try once more & reason why I forgot is in the next sentence.
I ended up trying his tutorial and it worked getting everything installed but my system still didn't recognize my nvidia card for certain things so I figured since I have a newer card it was a driver issue since bumblebee was installing older drivers so I tried installing the drivers from Nvidia and it ended up screwing up my login process and no matter what I did I couldn't get the system back to normal so I had to do a reinstall of Kali as a whole. I didn't write down the Debian repo I used because I wasn't entirely sure it mattered so after the fresh install I tried again and got the dependency error.

[unknown1995]

Hello! I have laptop lenovo y570, Kali Rollings 2016.2 4.8.0-kali2-amd64, 2 graphical chipsets :

1) Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller
2) VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 555M]

I want to combine resources of both graphical cards for brutforcing, but about two weeks I can't to install necessary drivers for nVidia. Who can helps me with new tutorials for kali rolling 2016.2 ?

PS : sorry for my english, is not my main language.

This tutorial works on kali 2016.2 rolling and both nvidia and Cuda will install
PROBLEM THAT MAY ARISE WHILE INSTALLING
- bumblebee dont start itself
---- bumblebeed -D (to start it)
- Cuda installation problem(i installed it from run file)
-----libXi.so file missing
---sudo ln -s /usr/lib/x86_64-linux-gnu/libXi.so /usr/lib/libXi.so (jjust create link)
-----Can't locate InstallUtils.pm in @INC
---Do this it will work
1. unpack .run file ./cuda*.run --tar mxvf
2. copy InstallUtils.pm to /usr/lib/x86_64-linux-gnu/perl-base
3. export $PERL5LIB

Follow the steps provided in tutorial it will work

[Bu5h1d0]

This tutorial works on kali 2016.2 rolling and both nvidia and Cuda will install
PROBLEM THAT MAY ARISE WHILE INSTALLING
- bumblebee dont start itself
---- bumblebeed -D (to start it)
- Cuda installation problem(i installed it from run file)
-----libXi.so file missing
---sudo ln -s /usr/lib/x86_64-linux-gnu/libXi.so /usr/lib/libXi.so (jjust create link)
-----Can't locate InstallUtils.pm in @INC
---Do this it will work
1. unpack .run file ./cuda*.run --tar mxvf
2. copy InstallUtils.pm to /usr/lib/x86_64-linux-gnu/perl-base
3. export $PERL5LIB

Follow the steps provided in tutorial it will work

This is tempting but I'm a bit hesitant only because thrice it has forced me to completely reinstall Kali, my own fault for not creating a backup but I've hit a wall when it won't install the dep as well. I don't recall the repo source I used to get dep to install. Even though it worked once, I never was able to get it to set my Nvidia card as the main card for use.

[itanon]

I had a 2010's GPU (a 330m notebook) does the cuda toolkit 7.5 support it?...The appropriate driver should be version 340.xx and on Nvidia page is listed they supports cuda toolkit 6.5

[Cricco95]

I succesfully installed Nvidia driver with Bumblebee and CUDA 8.0 but when I try to run optirun hashcat -b I get this error:

hashcat (v3.30) starting in benchmark mode...

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

No devices found/left

Started: Fri Feb 24 16:01:02 2017
Stopped: Fri Feb 24 16:01:02 2017

optirun glxgears output:

14130 frames in 5.0 seconds = 2825.824 FPS

optirun ./deviceQuery output:

./deviceQuery Starting...

CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "GeForce GT 750M"
CUDA Driver Version / Runtime Version 8.0 / 8.0
CUDA Capability Major/Minor version number: 3.0
Total amount of global memory: 4038 MBytes (4233953280 bytes)
( 2) Multiprocessors, (192) CUDA Cores/MP: 384 CUDA Cores
GPU Max Clock rate: 1085 MHz (1.09 GHz)
Memory Clock rate: 900 Mhz
Memory Bus Width: 128-bit
L2 Cache Size: 262144 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096)
Maximum Layered 1D Texture Size, (num) layers 1D=(16384), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(16384, 16384), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 1 copy engine(s)
Run time limit on kernels: Yes
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): Yes
Device PCI Domain ID / Bus ID / location ID: 0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 8.0, CUDA Runtime Version = 8.0, NumDevs = 1, Device0 = GeForce GT 750M
Result = PASS

[x5ctf]

Try hashcat 3.10

[bahha]

I succesfully installed Nvidia driver with Bumblebee and CUDA 8.0 but when I try to run optirun hashcat -b I get this error:



optirun glxgears output:



optirun ./deviceQuery output:

I had the same issue and fixed it .
first : I installed the driver 375.39 and cuda 8.0 from the repository . my GPU is Gt-740M
if you installed Cuda from the repository . it's saved as nvidia-cuda-toolkit in /usr/lib/nvidia-cuda-toolkit.
you need to create a symbolic link in /usr/local/ that points to the path of cuda-toolkit .

ln -s /usr/lib/nvidia-cuda-toolkit  /usr/local/cuda

if you are not root add sudo .
follow the first post to set $PATH in bashrc and ld.so.conf path use cuda instead of cudaxxx version. because of the symlink above.

now the issue I came across was. in bumblebee.conf if I set the kernel-driver as nvidia-current . pyrit and hashcat don't work .
so I created a symbolic link (shortcut) to the kernel modules as nvidia and nvidia-uvm just like when you install it with the driver from Nvidia's website.

ln -s /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-current.ko /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia.ko

check your kernel version before running the commands

ln -s /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-current-uvm.ko /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-uvm.ko

then I changed the bumblebee.conf in kernel-driver add nvidia instead of nvidia-current.
reboot and everything works . even with the latest hashcat version.
check with

modinfo nvidia

to see if the modules are well linked .

another thing if you are having any issues with compiling cpyrit after you compiled pyrit (the main module)
in cpyrit folder change the line in setup.py to be like this

  nvcc_cmd = NVCC + bit_flag + ' -ccbin clang'\

it will compile successfully .

[chaopac]

I tried to followed the guide and apparently I have succeeded, since I'm getting a PASS result at the final steps.

However, I am unable to log into the machine using the default System X11, or neither GNOME and GNOME Classic. Only GNOME with WAYLAND works.
When I try to log in with the first 3 methods, after finish typing in my credentials I just got loop back into the login Username screen again. Note this is without bumblebee running since it does not automatically start on boot.

After starting bumblebee, right after finishing logging in the screen freeze, but I can still access tty. This is similar to when the Nvidia drivers were not installed correctly.

I have successfully installed official Nvidia driver previously to installing bumblebee, as I do not know if bumblebee need Nvidia drivers already in place to function or not. The guide that I followed to install official Nvidia drivers is here:

https://forums.kali.org/showthread.p...Optimus-laptop

So if anyone know what I should do please let me know. I appreciate it a lot.

Thank you staticn0de for an awesome guide and anyone who takes the time to help.

[SOLUTION:]

I have been able to solve this by following staticn0de post in this thread. All you need to do to be able to use X11 and GNOME again is deleting the file xorg.conf at /etc/X11/

There is still a slight issue however for those who wants to use GNOME on Wayland. If you login using Wayland, the terminal will have a black box around it. This problem is persistent before and after the GNOME fix I mentioned above. Though it is only a minor inconvenience and it only affects the terminal.