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

[staticn0de]

Updated for Kali 2.0 Sana

Hey guys, I'm rewriting this to use the repo as Kali Sana looks to have up-to-date nvidia drivers straight out of the gate.

NVIDIA Driver 352.21
CUDA 7.5.18 (the repo has 6.0.37-5, it's a bit old so I'm manually installing 7.5.18)
VirtualGL 2.4.90
Pyrit v308 (optional)
cudaHashcat (optional)

Couple of points

1. This guide and all GPU passthrough software such as cuda_pyrit and cudahashcat will never work if run from within a Virtual Machine. Please don't post that it does not work for you in a VM because you should have read this.

2. I'm going to assume that you are either on a fresh install of Kali or have the skills to clean up any conflicting software.

3. I run 64bit software. If you don't, change the files you download to match what you use. (Edit: CUDA does not support 32bit anymore)

4. If you have any issues or if something does not work, follow the template linked here and post the results of all commands.

Lets get started.

1. Update Kali

apt-get update && apt-get upgrade && apt-get dist-upgrade

2. Download VirtualGL and install it. Grab the latest non-beta

http://sourceforge.net/projects/virtualgl/files/

Install with:
cd ~
dpkg -i virtualgl*.deb

3. Download CUDA 7.5. Grab the x64 or 14.04 *.run file (should be 1.1gb)

https://developer.nvidia.com/cuda-downloads

5. Install linux headers for your kernel

apt-get install linux-headers-$(uname -r)

6. Install dependencies we will need later. The first two are for CUDA and the last is for pyrit

apt-get install freeglut3-dev libxmu-dev libpcap-dev

7. Update system PATH. Notice that the PATH references CUDA 7.5. If you have a different version, change it to match.

nano ~/.bashrc

Add the following line and then save and close bashrc
export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-7.5/bin

8. Export the system path. We export the path from terminal so we can take advantage of it without restart. Run the following in terminal

export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-7.5/bin

9. Install bumblebee-nvidia and primus. Just press enter when the messages appear and ignore the warning about rrmod.

apt-get install bumblebee-nvidia primus

10. Edit the bumblebee config file so bumblebee knows we are using the NVIDIA driver. Change the 'Driver=' value. Should be line 22. The module from the repo driver is 'nvidia-current' but we set 'nvidia' here so that the nvidia section of bumblebee.conf is called.

nano +22 /etc/bumblebee/bumblebee.conf

Make it read:
Driver=nvidia

check line 55 and make sure it reads:
KernelDriver=nvidia-current

Save and close

11. Run the following and record the PCI address of your video card. It will look similar to 03:00.0

lspci | egrep 'VGA|3D'

12. Edit the xorg.conf.nvidia file so it knows the PCI address of your video card. Note that the last group of numbers is now seperated with a ":" instead of a ".". We are editing under the area 'Section "Device"'

nano /etc/bumblebee/xorg.conf.nvidia

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

14. Reboot

shutdown -r now

15. Now we have restarted, test the driver. glxsheres64 will test the driver and modinfo nvidia will show the version loaded.

optirun glxspheres64

modinfo nvidia

16. Prepare CUDA for install

cd ~
chmod +x cuda*.run

17. Run the CUDA install

./cuda*.run

Accept the EULA
Select yes to unsupported configuration
No to graphics driver
Yes to the toolkit
Accept default location
Yes to symbolic link
Yes to samples
Yes to default samples location
The toolkit will install

18. Set up the dynamic linker for CUDA. Notice that this is slightly different than the path added for .bashrc

nano /etc/ld.so.conf

Match the contents below

include /etc/ld.so.conf.d/*.conf
/usr/local/cuda-7.5/lib64

19. Excute the following to load our changes

ldconfig

20. Install libcuda1. You will get an incorrect driver version error if you don't.

apt-get install libcuda1

21. Build the NVIDIA samples so we can confirm CUDA is working with optirun

cd /root/NVIDIA_CUDA-7.5_Samples/1_Utilities/deviceQuery/
make

22. Run deviceQuery and then post your pass! If you see a pass, it all worked out! If not, follow the link at the start of the guide and post everything asked.

optirun ./deviceQuery

[staticn0de]

Optional Installs - cudaHashcat and Pyrit

This section is for optional installs. If you installed CUDA on Kali, Im tipping these are both applications you are interested in.

Points

1. If you have any issues installing any of this, post the complete output of any commands entered.

cudaHashcat

You have two options, download the archive from the hashcat website and install it manually (sorry, I'm not going into that. If you need instructions, check their wiki)

The second option is download my deb file. You can install it with a single command and then call cuda hashcat with either 'cudahashcat64' (for 64bit) or 'cudahashcat32' (for 32bit). Grab and install it from the link below.

Disclaimer
While some forum members make use of my deb, I am not a member of either the hashcat team or the Kali dev team. I could have edited the contents of the deb in any way (including maliciously). Take care when downloading from unknown sources. I provide no warranty and do not claim that it is fit for any purpose, including that which it is intended.

I repackaged the hashcat binary in accordance with their EULA so it would install easily on Kali. I also removed non-linux binaries.

1. cudahashcat 2.01

https://mega.nz/#!sZFngKJR!njrug2Y4nxs0aHemQg-SKKGAmXiK1XeALTtnP8IGYNU

dpkg -i cudahashcat-2.01.deb

2. cudahashcat 1.36

https://mega.co.nz/#!gAtAQDJY!x9FIs2ssQ66HmlXMdGDUiPI-l45el0dAFUpaGTm_P-0

dpkg -i cudahashcat-1.36.deb

3. cudahashcat 1.35

https://mega.co.nz/#!dN8ESI7D!-jxoTZBwVddzKZ2r0MuQ5T4sDJZ5NSOnkrNvxpDuNNg

dpkg -i cudahashcat-1.35.deb

4. cudahashcat 1.34

https://mega.co.nz/#!0Z9DHBob!0QA3clJqszGEExTKlKTBPLJEoDvXIiBwBepiYgWZbew

dpkg -i cudahashcat-1.34.deb

5. cudahashcat 1.33

https://mega.co.nz/#!oQNQhRyT!gTSxCEB5APkMgdaJl_k91h_9lgwK4LWUfwfTdGHAbEU

dpkg -i cudahashcat-1.33.deb

6. cudahashcat 1.31 (seems to be faster than 1.33)

https://mega.co.nz/#!kFMC2RQC!D1ccQYAwsWyGKD0CaV4W7n5Ghtc-YKFFxs7Qj1pgcw0

dpkg -i cudahashcat-1.31.deb

The deb sums are

cudahashcat 2.01
md5sum = 69a9289e05a6e4b25728d5738a48f76c

cudahashcat 1.36
md5sum = f4ea04116a8495ea3e850fc993220554

cudahashcat 1.35
md5sum = ccdc7ebf4c4a947d14fa663a982e3c10

cudahashcat 1.34
md5sum = e611e16ab1f3c42c5e98d3ef615a0cd4

cudahashcat 1.33
md5sum = 82f4975f02af1288de058c93552b981d

cudahashcat 1.31
md5sum = b753c393264b3c40e51f057a96f3f6e9

Test it with

optirun cudahashcat64 -t 32 -a 7 example0.hash ?a?a?a?a example.dict

To remove it

dpkg -r cudahashcat-2.01

and check the following directories and files are removed

/usr/bin/cudahashcat32 (file)
/usr/bin/cudahashcat64 (file)
/usr/share/cudahashcat (directory)

Pyrit

The following instructions are slightly modified from the pyrit google code page here

https://code.google.com/p/pyrit/wiki/Installation

1. Move to your home directory (I'm installing it there) and then check out the pyrit trunk

cd ~

svn checkout http://pyrit.googlecode.com/svn/trunk/ pyrit_svn

2. Build and install pyrit

cd pyrit_svn/pyrit/
python setup.py build
python setup.py install

3. Add CUDA support

cd ../cpyrit_cuda/
python setup.py build
python setup.py install

4. Test pyrit

optirun pyrit benchmark

[staticn0de]

Reporting your issues

Most issues people have are a simple typo in their config files. Double check them before posting. I know this is a lot of commands to go through, but many users are new and experience delays in posting. Not giving enough information can result in multiple day turn arounds.

1. Use the [*CODE] brackets to paste the output of commands (the open and close code brackets are [*CODE] and [*/CODE] without the *. Put all the text between them.

Commands to execute

1.

lspci | egrep 'VGA|3D'

2.

modprobe nvidia

3.

modprobe nvidia-uvm

4.

optirun glxspheres64

5.

dmesg | tail -n 100

6.

echo $PATH

7.

cat /etc/bumblebee/bumblebee.conf

8.

cat /etc/bumblebee/xorg.conf.nvidia

9.

service bumblebeed restart

10.

modinfo nvidia

11.

find 2> /dev/null / -name nvidia*.ko

[Quest]

Great guide staticn0de!

- This post edited with download links for an OFF-Line installation on Kali 1.1.0 -

Download CUDA, VirtualGL, Nvidia, CudaHashcat, from previous posts above.
This does not include Kali Linux updates or Headers. Just the extra packs required for this guide.
All links point to Debian wheezy(stable) packages whenever possible or equivalent/default.

• Scroll down the page at Debian and choose your architecture under "Download".
• Choose a server to download from.

All packs go in Home, the /root directory. Remove them when installation is done.
Install from root with

dpkg -i name.deb

(6.) Download and Install dependencies for CUDA and Pyrit.

freeglut3-dev
https://packages.debian.org/wheezy/freeglut3-dev

libxmu-headers
https://packages.debian.org/wheezy/libxmu-headers

libxmu-dev
https://packages.debian.org/wheezy/libxmu-dev

libpcap-dev
https://packages.debian.org/wheezy/libpcap-dev



(9.) Download and Install bumblebee and primus.

linux-headers (another "linux headers")(mine was linux-headers-amd64_3.18+63+kali2.1_amd64.deb)
http://ftp.tku.edu.tw/kali/pool/main/l/linux-latest/

dkms
https://packages.debian.org/wheezy/dkms

bbswitch-dkms
https://packages.debian.org/wheezy-b.../bbswitch-dkms

bumblebee
https://packages.debian.org/wheezy-backports/bumblebee

primus-libs
https://packages.debian.org/wheezy-b...ts/primus-libs

primus
https://packages.debian.org/wheezy-backports/primus



Optional. Download and Install Pyrit and add-on for Nvidia CUDA.

pyrit_svn 0.4.1-dev svn r308

From Linux, enter in a console;

svn checkout http://pyrit.googlecode.com/svn/trunk/ pyrit_svn

That will download a folder in /root (Home) named, pyrit_svn
That folder is pyrit 0.4.1 svn r308. You can then save that folder for later off-line installations.

Built and install Pyrit and add CUDA support.

cd pyrit_svn/pyrit/

python setup.py build

python setup.py install

cd ../cpyrit_cuda/

python setup.py build

python setup.py install

Total: 11 packs. 2,05 Mb

[staticn0de]

Great guide staticn0de!

Everyting worked well, until...




my output was


Any advice?

Many thanks staticn0de I'm getting closer!

I'm not sure what's causing that, but let's see if we can get you sorted out.

To start, run:
diff /usr/src/nvidia-current-331.67/Module.symvers /usr/src/nvidia-current-331.67/uvm/Module.symvers

Any feedback from the above command means you need to delete the Module.symvers from the folder on the right and copy from the directory on the left into the directory on the right again. Once copied, run make in the uvm/ folder and copy it to /lib/modules/3.14-kali1-amd64/updates/dkms/

Post the feedback from below:
echo $PATH

Post the feedback from:
cat /etc/modprobe.d/nvidia.conf

Post the feedback from:
ls /lib/modules/3.14-kali1-amd64/updates/dkms

Run modprobe nvidia-uvm and then run dmesg right after. Post the output in code brackets.

Run lsmod and post output in code brackets

You could also try modprobe nvidia and then modprobe nvidia-current and then modprobe nvidia-uvm

Edit: Some other cool stuff you could try is a:
depmod -a
modprobe nvidia-uvm

and then post the output of:
cat /lib/modules/3.14-kali1-amd64/modules.dep | grep -i nvidia

[Quest]

the odds are that it was the operator(me), though I would like to reassure you that I fallowed your guide precisely, on a fresh installation of Kali 1.0.7 x64. I can even point out a small mistake in a syntax(induced by LibreOffice auto correction)

First, install the linux headers. We need this so we can compile bbswitch later
apt-get install linux-headers-$(uname –r)

I did however strugeled alot with the nano console, as I did not know how to save changes. Save with F2, then Y, then "File Name to Write: xxxxxx, Enter

Last night I decided to re-install, so I will do it again, then if I still encounter the same problem, I will proceed with post#5 and report back.

Thank you my friend

[staticn0de]

Good pickup! I've fixed it now.

As for nano, control + x, then y and then enter will save your changes and then close the file.

[Quest]

Exact ame results as yesterday.

root@kali:~# rm /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
root@kali:~# cp /usr/src/nvidia-current-331.67/uvm/nvidia-uvm.ko /lib/modules/3.14-kali1-amd64/updates/dkms/
root@kali:~# modprobe nvidia-uvm
ERROR: could not insert 'nvidia_uvm': No such device

i ran into this last night when search for a possible solution. This is recent 2 May 2014. Could there be a bug with versions nvidia-graphics-drivers/331.67-1, nvidia-graphics-drivers/331.67-2, nvidia-graphics-drivers/331.79-1 ?

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=746643 OpenCL not supported by lastest NVIDIA driver



These are the my outputs:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630M] (rev ff)




root@kali:~# optirun glxspheres64 
Polygons in scene: 62464
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce GT 630M/PCIe/SSE2
243.416053 frames/sec - 204.644744 Mpixels/sec
246.672039 frames/sec - 207.382117 Mpixels/sec
195.415671 frames/sec - 164.289863 Mpixels/sec
170.460050 frames/sec - 143.309173 Mpixels/sec
171.786163 frames/sec - 144.424063 Mpixels/sec
167.925432 frames/sec - 141.178269 Mpixels/sec
166.438969 frames/sec - 139.928570 Mpixels/sec
168.091304 frames/sec - 141.317721 Mpixels/sec
171.926627 frames/sec - 144.542154 Mpixels/sec
170.618800 frames/sec - 143.442638 Mpixels/sec
168.957864 frames/sec - 142.046256 Mpixels/sec
174.145734 frames/sec - 146.407802 Mpixels/sec
172.519375 frames/sec - 145.040489 Mpixels/sec
169.868780 frames/sec - 142.812081 Mpixels/sec

 


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

Driver:   Not Selected
Toolkit:  Installed in /usr/local/cuda-5.5
Samples:  Installed in /root/NVIDIA_CUDA-5.5_Samples

* Please make sure your PATH includes /usr/local/cuda-5.5/bin

* Please make sure your LD_LIBRARY_PATH
*   for 32-bit Linux distributions includes /usr/local/cuda-5.5/lib
*   for 64-bit Linux distributions includes /usr/local/cuda-5.5/lib64:/lib
* OR
*   for 32-bit Linux distributions add /usr/local/cuda-5.5/lib
*   for 64-bit Linux distributions add /usr/local/cuda-5.5/lib64 and /lib
* to /etc/ld.so.conf and run ldconfig as root

* To uninstall CUDA, remove the CUDA files in /usr/local/cuda-5.5
* Installation Complete

Please see CUDA_Getting_Started_Linux.pdf in /usr/local/cuda-5.5/doc/pdf for detailed information on setting up CUDA.




root@kali:~# rm /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
root@kali:~# cp /usr/src/nvidia-current-331.67/uvm/nvidia-uvm.ko /lib/modules/3.14-kali1-amd64/updates/dkms/
root@kali:~# modprobe nvidia-uvm
ERROR: could not insert 'nvidia_uvm': No such device



- CONTENT OF dkms.conf -

# DKMS configuration for the NVIDIA kernel module.  -*- sh -*-

# The version is replaced at build time by dh_dkms invoked in debian/rules.
PACKAGE_NAME="nvidia-current"
PACKAGE_VERSION="331.67"

BUILT_MODULE_NAME[0]="nvidia"
DEST_MODULE_NAME[0]="$PACKAGE_NAME"
DEST_MODULE_LOCATION[0]="/updates/dkms"
AUTOINSTALL=yes

MAKE[0]="env CCACHE_DISABLE=1 \
    make -C . SYSSRC=${kernel_source_dir}"
CLEAN="make -C . SYSSRC=${kernel_source_dir} clean"

BUILT_MODULE_NAME[1]="nvidia-uvm"
BUILT_MODULE_LOCATION[1]="uvm/"
DEST_MODULE_LOCATION[1]="/updates/dkms"
MAKE[0]+="; env CCACHE_DISABLE=1 \
    make -C uvm SYSSRC=${kernel_source_dir}"
CLEAN+="; make -C uvm SYSSRC=${kernel_source_dir} clean"

- END OF CONTENT -





root@kali:~# diff /usr/src/nvidia-current-331.67/Module.symvers /usr/src/nvidia-current-331.67/uvm/Module.symvers
root@kali:~# 
NO FEEDBACK


root@kali:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin


root@kali:~# cat /etc/modprobe.d/nvidia.conf
alias nvidia nvidia-current
remove nvidia-current rmmod nvidia


root@kali:~# modprobe nvidia-uvm
ERROR: could not insert 'nvidia_uvm': No such device

root@kali:~#  lsmod 
Module                  Size  Used by
nls_utf8               12456  1 
nls_cp437              16553  1 
vfat                   17185  1 
fat                    57965  1 vfat
nfnetlink_log          17241  0 
nfnetlink              12989  1 nfnetlink_log
bbswitch               12866  0 
binfmt_misc            16949  1 
loop                   26605  0 
dm_crypt               22731  0 
joydev                 17108  0 
snd_hda_codec_hdmi     45004  1 
snd_hda_codec_realtek    54360  1 
snd_hda_codec_generic    59079  1 snd_hda_codec_realtek
btusb                  25619  0 
bluetooth             243618  2 btusb
6lowpan_iphc           16588  1 bluetooth
x86_pkg_temp_thermal    12965  0 
intel_powerclamp       17159  0 
arc4                   12543  2 
snd_hda_intel          39656  3 
i915                  743012  2 
snd_hda_codec          99921  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
iTCO_wdt               12831  0 
iTCO_vendor_support    12649  1 iTCO_wdt
snd_hwdep              13148  1 snd_hda_codec
lpc_ich                20768  0 
ir_rc6_decoder         12433  0 
ir_jvc_decoder         12433  0 
iwldvm                130998  0 
mac80211              488308  1 iwldvm
iwlwifi                87784  1 iwldvm
drm_kms_helper         39998  1 i915
drm                   240557  3 i915,drm_kms_helper
i2c_algo_bit           12751  1 i915
intel_rapl             17344  0 
snd_pcm                88538  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_timer              26606  1 snd_pcm
snd                    61039  14 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore              13026  1 snd
mei_me                 13446  0 
i2c_i801               16963  0 
mei                    50039  1 mei_me
i2c_core               24265  5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
cfg80211              436618  3 iwlwifi,mac80211,iwldvm
ir_sony_decoder        12435  0 
ir_sanyo_decoder       12437  0 
ir_lirc_codec          12675  0 
ir_mce_kbd_decoder     12574  0 
ir_nec_decoder         12433  0 
lirc_dev               16951  1 ir_lirc_codec
ir_rc5_decoder         12433  0 
coretemp               12854  0 
kvm_intel             138949  0 
kvm                   404503  1 kvm_intel
rc_rc6_mce             12396  0 
ene_ir                 21814  0 
rc_core                18235  12 lirc_dev,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,ene_ir,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder,rc_rc6_mce
psmouse                86464  0 
serio_raw              12849  0 
evdev                  17489  13 
rtsx_pci_ms            12802  0 
memstick               13696  1 rtsx_pci_ms
mxm_wmi                12515  0 
toshiba_acpi           18063  0 
sparse_keymap          12760  1 toshiba_acpi
rfkill                 18902  5 cfg80211,toshiba_acpi,bluetooth
toshiba_bluetooth      12641  0 
battery                13101  0 
processor              28221  0 
ac                     12678  0 
video                  17804  1 i915
thermal_sys            27685  4 video,intel_powerclamp,processor,x86_pkg_temp_thermal
wmi                    17339  2 toshiba_acpi,mxm_wmi
button                 12944  1 i915
ext4                  489943  1 
crc16                  12343  2 ext4,bluetooth
mbcache                13082  1 ext4
jbd2                   86788  1 ext4
dm_mod                 89276  1 dm_crypt
hid_generic            12393  0 
usbhid                 44481  0 
hid                    94062  2 hid_generic,usbhid
sg                     30043  0 
sr_mod                 21898  0 
cdrom                  39232  1 sr_mod
sd_mod                 44346  5 
crc_t10dif             12431  1 sd_mod
usb_storage            52037  4 
rtsx_pci_sdmmc         17076  0 
mmc_core               93950  1 rtsx_pci_sdmmc
crct10dif_pclmul       13348  1 
crct10dif_common       12356  2 crct10dif_pclmul,crc_t10dif
crc32_pclmul           12915  0 
crc32c_intel           21809  0 
ghash_clmulni_intel    12978  0 
ahci                   29195  0 
aesni_intel           151423  0 
libahci                27103  1 ahci
aes_x86_64             16719  1 aesni_intel
lrw                    12757  1 aesni_intel
gf128mul               12970  1 lrw
glue_helper            12690  1 aesni_intel
ablk_helper            12572  1 aesni_intel
cryptd                 14560  3 ghash_clmulni_intel,aesni_intel,ablk_helper
libata                169163  2 ahci,libahci
scsi_mod              186841  5 sg,usb_storage,libata,sd_mod,sr_mod
rtsx_pci               33623  2 rtsx_pci_ms,rtsx_pci_sdmmc
mfd_core               12601  2 lpc_ich,rtsx_pci
r8169                  64490  0 
mii                    12675  1 r8169
ehci_pci               12472  0 
xhci_hcd              111830  0 
ehci_hcd               48517  1 ehci_pci
usbcore               166472  6 btusb,usb_storage,ehci_hcd,ehci_pci,usbhid,xhci_hcd
usb_common             12440  1 usbcore
root@kali:~# 


root@kali:~# modprobe nvidia
root@kali:~# modprobe nvidia-current
ERROR: could not insert 'nvidia_current': No such device
root@kali:~# modprobe nvidia-uvm
ERROR: could not insert 'nvidia_uvm': No such device


root@kali:~# depmod -a
root@kali:~# 

root@kali:~# cat /lib/modules/3.14-kali1-amd64/modules.dep | grep -i nvidia
kernel/drivers/net/ethernet/nvidia/forcedeth.ko:
updates/dkms/nvidia-uvm.ko: updates/dkms/nvidia-current.ko kernel/drivers/i2c/i2c-core.ko
updates/dkms/nvidia-current.ko: kernel/drivers/i2c/i2c-core.ko

[staticn0de]

I don't believe a bug is causing this as It's working here. Like all things linux, it will be a one liner somewhere that will fix it.

Would you please post your /etc/bumblebee/bumblebee.conf and xorg.nvidia.conf in the same directory.

The way it works is that nvidia-uvm depends on the nvidia-current module. We know that works because you can use optirun glxspheres.

Did you have any useful dmesg feedback from after the modprobe?

Did you add the cuda libraries and then run ldconfig? I'm sure you did, but I was just going through the feedback you posted (I assume you omitted doing it because I didn't ask for it)

Hopefully we can get this sorted out soon

[Quest]

xD yes it definitely feels like the setup is missing a line somewhere.


Here is the output of bumblebee.conf and xorg.conf.nvidia..

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

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

I can't remember if I had any useful dmesg feedback from after the modprobe.

I did add the cuda libraries and then run ldconfig. Yes. I can reinstall again and copy the info from ldconfig and modprobe if need be.



Let me know if I can provide anything else for the investigation

[Quest]

you know what, everything is fine until that step..

Now to fix the nvidia-uvm module (You don't know this yet, but it's broken.)

cd /usr/src/nvidia-current-331.67
make

cp Module.symvers uvm/

cd uvm/
make

Can you confirm that:
1. capital 'M' in "Module.symvers uvm/" syntax
2. the nvidia-uvm module is really broken, and needs fixing

I will try without fixing tomorrow see what happens. Now I'm going to dream about using piryt and hashcat

[Quest]

Nevermind the above post.


After a 3rd reinstall. Same results.

Here are some interesting bits, that might have nothing to do with it(?)

root@kali:~# uname -r
3.14-kali1-amd64





depmod....

DKMS: install completed.
Setting up nvidia-driver (331.67-2kali1) ...
Setting up bumblebee-nvidia (3.2.1-4~bpo70+1) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in manual mode
[ ok ] Restarting bumblebeed: bumblebeed.
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.14-kali1-amd64
cryptsetup: WARNING: failed to detect canonical device of /dev/sdb5

331.67-2 !!?? There are two version of the same. Really?

root@kali:~# apt-get install nvidia-glx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  nvidia-glx
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 119 kB of archives.
After this operation, 158 kB of additional disk space will be used.
Get:1 http://http.kali.org/kali/ kali/non-free nvidia-glx amd64 331.67-2kali1 [119 kB]
Fetched 119 kB in 6s (19.1 kB/s)                                                                   
Selecting previously unselected package nvidia-glx.
(Reading database ... 343139 files and directories currently installed.)
Unpacking nvidia-glx (from .../nvidia-glx_331.67-2kali1_amd64.deb) ...
Setting up nvidia-glx (331.67-2kali1) ...
root@kali:~#

root@kali:~# apt-get install nvidia-glx
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  nvidia-glx
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 119 kB of archives.
After this operation, 158 kB of additional disk space will be used.
Get:1 http://http.kali.org/kali/ kali/non-free nvidia-glx amd64 331.67-2kali1 [119 kB]
Fetched 119 kB in 6s (19.1 kB/s)                                                                   
Selecting previously unselected package nvidia-glx.
(Reading database ... 343139 files and directories currently installed.)
Unpacking nvidia-glx (from .../nvidia-glx_331.67-2kali1_amd64.deb) ...
Setting up nvidia-glx (331.67-2kali1) ...
root@kali:~# 




root@kali:~# lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630M] (rev ff)
root@kali:~# 




root@kali:~# apt-get install libcuda1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  nvidia-smi
Suggested packages:
  nvidia-cuda-mps
Recommended packages:
  libcuda1-i386
The following NEW packages will be installed:
  libcuda1 nvidia-smi
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,688 kB of archives.
After this operation, 14.5 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://http.kali.org/kali/ kali/non-free libcuda1 amd64 331.67-2kali1 [5,480 kB]
Get:2 http://http.kali.org/kali/ kali/non-free nvidia-smi amd64 331.67-2kali1 [207 kB]             
Fetched 5,688 kB in 31s (178 kB/s)                                                                 
Selecting previously unselected package libcuda1:amd64.
(Reading database ... 343147 files and directories currently installed.)
Unpacking libcuda1:amd64 (from .../libcuda1_331.67-2kali1_amd64.deb) ...
Selecting previously unselected package nvidia-smi.
Unpacking nvidia-smi (from .../nvidia-smi_331.67-2kali1_amd64.deb) ...
Processing triggers for man-db ...
Setting up libcuda1:amd64 (331.67-2kali1) ... 
Setting up nvidia-smi (331.67-2kali1) ...
root@kali:~# 


CUDA 

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 ]: y
Install NVIDIA Accelerated Graphics Driver for Linux-x86_64 319.37? ((y)es/(n)o/(q)uit): n
Install the CUDA 5.5 Toolkit? ((y)es/(n)o/(q)uit): y
Enter Toolkit Location [ default is /usr/local/cuda-5.5 ]: 
Install the CUDA 5.5 Samples? ((y)es/(n)o/(q)uit): y
Enter CUDA Samples Location [ default is /root/NVIDIA_CUDA-5.5_Samples ]: 
Installing the CUDA Toolkit in /usr/local/cuda-5.5 ...

WAIT.............


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

Driver:   Not Selected
Toolkit:  Installed in /usr/local/cuda-5.5
Samples:  Installed in /root/NVIDIA_CUDA-5.5_Samples

* Please make sure your PATH includes /usr/local/cuda-5.5/bin

* Please make sure your LD_LIBRARY_PATH
*   for 32-bit Linux distributions includes /usr/local/cuda-5.5/lib
*   for 64-bit Linux distributions includes /usr/local/cuda-5.5/lib64:/lib
* OR
*   for 32-bit Linux distributions add /usr/local/cuda-5.5/lib
*   for 64-bit Linux distributions add /usr/local/cuda-5.5/lib64 and /lib
* to /etc/ld.so.conf and run ldconfig as root

* To uninstall CUDA, remove the CUDA files in /usr/local/cuda-5.5
* Installation Complete






root@kali:~# ldconfig
root@kali:~# 
NOTHING HAPPENS



AFTER SETUP I RUN optirun glxspheres64 again and...


root@kali:~# /etc/init.d/bumblebeed restart
[ ok ] Restarting bumblebeed: bumblebeed.
root@kali:~# optirun glxspheres64
[10223.471114] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

[10223.471198] [ERROR]Aborting because fallback start is disabled.
root@kali:~#

dmesg modprobe (Notice the interesting bit at the end):

root@kali:~# dmesg
CANNOT POST THE WHOLE THING  

...
[Package] (20131218/nsarguments-95)
[ 6170.453345] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6170.453385] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6176.843757] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6178.305207] bbswitch: disabling discrete graphics
[ 6178.305228] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6178.318591] pci 0000:01:00.0: Refused to change power state, currently in D0
[ 6550.299909] bbswitch: enabling discrete graphics
[ 6550.757766] bbswitch: disabling discrete graphics
[ 6550.757788] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.213529] bbswitch: enabling discrete graphics
[ 6561.651014] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
[ 6561.651157] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  331.67  Fri Apr  4 13:48:39 PDT 2014
[ 6561.681517] nvidia 0000:01:00.0: irq 49 for MSI/MSI-X
[ 6561.692369] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692454] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692501] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692543] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692584] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692624] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692690] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6561.692731] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6568.469916] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6657.371547] bbswitch: disabling discrete graphics
[ 6657.371569] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131218/nsarguments-95)
[ 6657.384771] pci 0000:01:00.0: Refused to change power state, currently in D0
[ 8142.331643] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
[ 8142.331723] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
[ 8142.331723] NVRM: installed in this system is not supported by the 331.67
[ 8142.331723] NVRM: NVIDIA Linux driver release.  Please see 'Appendix
[ 8142.331723] NVRM: A - Supported NVIDIA GPU Products' in this release's
[ 8142.331723] NVRM: README, available on the Linux driver download page
[ 8142.331723] NVRM: at www.nvidia.com.
[ 8142.331795] nvidia: probe of 0000:01:00.0 failed with error -1
[ 8142.331853] NVRM: The NVIDIA probe routine failed for 1 device(s).
[ 8142.331855] NVRM: None of the NVIDIA graphics adapters were initialized!
[ 8142.332042] NVRM: NVIDIA init module failed!
root@kali:~#

[Quest]

post too long continued here...

The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
installed in this system is not supported by the 331.67
NVIDIA Linux driver release. Please see 'Appendix
A - Supported NVIDIA GPU Products' in this release's
README, available on the Linux driver download page

OH really? Let's go and see...

http://us.download.nvidia.com/XFree8...rtedchips.html

Note that the list of supported GPU products provided below and on the driver download page is provided to indicate which GPUs are supported by a particular driver version. Some designs incorporating supported GPUs may not be compatible with the NVIDIA Linux driver: in particular, notebook and all-in-one desktop designs with switchable (hybrid) or Optimus graphics will not work if means to disable the integrated graphics in hardware are not available. Hardware designs will vary from manufacturer to manufacturer, so please consult with a system's manufacturer to determine whether that particular system is compatible.

10de:0de9 is not supported by the 331.67 NVIDIA Linux driver release

[rastamouse]

This worked perfectly for me. Thanks staticn0de.

[Quest]

Let me understand something here... Why are we working with driver 331.67, and only that version. Is it because of bumblebee? (I'm quite stubborn and still looking for a solution, even within an obvious failure framework).

In any case, thank you staticn0de

[staticn0de]

Let me understand something here... Why are we working with driver 331.67, and only that version. Is it because of bumblebee? (I'm quite stubborn and still looking for a solution, even within an obvious failure framework).

In any case, thank you staticn0de

Hi there Quest,

You don't have to use that driver version. That is just what is in the wheezy backports repo.

I have not tried a newer version on Kali (I've used 337 on Ubuntu with bumblebee - that had its own issues)

To install a newer version, you will need to add the Jessie or Sid repo.

Jessie is the testing repo and has the 337.19-1 driver under the name nvidia-driver or the transitional package Nvidia-glx.

Sid is the unstable repo and has nvidia 331.79-1 under the same names as that above.

These should work if you want to try them. I'm sure you understand how easily you can break Kali with unsupported repos (wheezy backports is not much better I'm sure)

deb http://http.debian.net/debian sid main contrib non-free

Or

deb http://http.debian.net/debian jessie main contrib non-free

[siste]

See this article I was very moved when I thank staticn 0. Thank you. notebook can be normal working the

[staticn0de]

For those interested, much to my amazement I was able to get Nvidia 340.24 working on Kali

root@kali:/proc/driver/nvidia# cat version
NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.24 Wed Jul 2 14:24:20 PDT 2014
GCC version: gcc version 4.7.2 (Debian 4.7.2-5)

It was a bit of an "unclean" install as I kind of had to force it on there, but glxspheres64 and optirun is working. I'll try and get CUDA 6 working and keep you posted. If I get it, i'll clean up the process and post that too.

Edit:

It's looking promising!

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.5, CUDA Runtime Version = 6.0, NumDevs = 1, Device0 = GeForce GT 740M
Result = PASS

[London]

staticn0de, thankyou for the work that went into this write up. It worked really well. I did have one issue but solved it here: https://wiki.archlinux.org/index.php/bumblebee

[Quest]

that's cool

even though most can figure it out for themselves, I was thinking that maybe(?) it would be nice to have all the command lines, and links to, an OFF_LINE installation. There's nothing wrong with this procedure as is, but we already DLing CUDA (and now probly new NVIDIA drivers), so maybe DL everything and than install?

I'm not a big fan of being dependent on the Internet for installations, for one, and I've had my connexion cut or network manager shut down my connexion while fallowing this guide more than once. Nothing bad happened as a result, but it made me think that I'd be better off-line.

So without changing this guide(because it works beautifully), an 'off-Line Annex' would be appreciated. Just a link in the first post pointing to another post with the command lines/links to firstly DL everything and then the command lines to install from Home *if I have everything I need in Home maybe the whole installation can be scripted hmmm [evil laugh]* Just saying.

[London]

staticn0de, thank you for the write-up!

I did everything succesfully and the tests worked, but I'm unsure about a few things.
1. If the nVidia driver automatically removes nouveau then why is there a xorg.conf.nouveau file in the /etc/bumblebee directory?
2. How can I make sure the nVidia driver is the default driver at startup?
3. Lastly, when I lsmod | grep nvidia there is no output, when I lsmod | grep nouveau there is also no output. Shouldn't at least one of them show something?

[staticn0de]

staticn0de, thank you for the write-up!

I did everything succesfully and the tests worked, but I'm unsure about a few things.
1. If the nVidia driver automatically removes nouveau then why is there a xorg.conf.nouveau file in the /etc/bumblebee directory?
2. How can I make sure the nVidia driver is the default driver at startup?
3. Lastly, when I lsmod | grep nvidia there is no output, when I lsmod | grep nouveau there is also no output. Shouldn't at least one of them show something?

Hi there, don't mistake my guide as making me an expert on bumblebee, but i'll try and answer your question.

1. The nvidia driver does not remove nouveau, bumblebee changes between the graphics card which includes disabling one driver and enabling the nvidia driver. Both remain on the system. The xorg.conf.nouveau does not matter as it is only called if you set driver=nouveau in the bumblebee.conf file.

2. You don't set nvidia to start at start up. The reason bumblebee is used is so you can benefit from the power saving of having the intel card in use when the graphics card is not needed. When you use optirun glxspheres64 (for example) the nvidia card is enabled which uses more power so that the graphicly demanding application has a performance boost.

3. Unless you have used optirun, the nvidia modules will not be loaded. For example, run the command lsmod | grep -i nvidia and you will receive nothing. Run optirun glxspheres64 and while it is running use lsmod | grep -i nvidia and it will display the nvidia modules are the driver has loaded to use the discrete card.

[London]

Thank you! that really brings it all together for me. I usually have to run the optispheres64 command twice before it works, but everything is working perfectly other than that. Really appreciate it!

[staticn0de]

that's cool

even though most can figure it out for themselves, I was thinking that maybe(?) it would be nice to have all the command lines, and links to, an OFF_LINE installation. There's nothing wrong with this procedure as is, but we already DLing CUDA (and now probly new NVIDIA drivers), so maybe DL everything and than install?

Hmmm I like the idea, it would save some effort. My concern is that bumblebee is a decent effort to compile and then install. That, and it has dependencies. And those dependencies have dependencies.Trying to install all them without a repo would be a pain.

On another note, if you can't go to the mountain, you can always bring the mountain to you. You could host your own repo on your local network. I've looked into it but Kali looks after it a little different to other distros where you can just clone them with rsync. If you had a local repo, you won't need the internet anymore. This clearly isn't the solution for everyone....

In short, I don't really have the time (and maybe not the skill!) to document the requirements for this as an offline install. Although, I'm about to type up the CUDA6 and NVIDIA 340.24 version and with the exception of bumblebee (not bumblebee-nvidia) it is an offline install. It's easier to install than what I already wrote as it does not need manual modifications to nvidia-uvm.ko.

[staticn0de]

The following will install the latest at the time (340.24) NVIDIA driver and latest CUDA (version 6) on Kali with
Bumblebee for Optimus laptops. Usual notes about clean installs and selecting either 32bit or 64bit depending on your
needs from the first page still apply.

First, update and upgrade Kali to latest
apt-get update && apt-get upgrade && apt-get dist-upgrade

Download VirtualGL
http://downloads.sourceforge.net/pro...se_mirror=ufpr

Download CUDA (this is V6 64bit)
http://developer.download.nvidia.com...7_linux_64.run

Download the nvidia*.run driver. Follow the bouncing ball to get what you need for your hardware
http://www.nvidia.com/Download/index.aspx?lang=en-us

Install VirtualGL
cd ~
dpkg -i virtualgl*.deb

Add the path for VirtualGL to .bashrc
nano ~/.bashrc
Add a line somewhere near the top that reads:
export PATH=$PATH:/opt/VirtualGL/bin

Export the path so we don't have to log out and in. Run the following from terminal
export PATH=$PATH:/opt/VirtualGL/bin

Install the linux headers
apt-get install linux-headers-$(uname -r)

Some dependencies for CUDA later
apt-get install freeglut3-dev libxmu-dev


Add the wheezy backports Repo (yes, still needed for bumblebee but not the NVIDIA driver)
nano /etc/apt/sources.list
Add the following line to the file and then save
deb http://ftp.debian.org/debian wheezy-backports main contrib non-free
apt-get update

Install bumblebee (not bumblebee-nvidia)
apt-get install bumblebee primus

Edit the bumblebee.conf file
nano /etc/bumblebee/bumblebee.conf

Change line 22 so it reads:
Driver=nvidia

We do not need to edit line 55 as the module the nvidia installer will build is called nvidia and not nvidia-current.

Save and close.

Run the following and record your PCI address for your video card. It will look similar to 03:00.0
lspci | egrep 'VGA|3D'

Edit xorg.conf.nvidia and add a line under the 'Section "Device"' area so that is matches what is shown below. Change the bus ID to match what you recorded previously and take note that you recored a . before the last number and it is now a ':'. You need the ':'.
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BusID "PCI:03:00:0"


Change NVIDIA installer permissions
cd ~
chmod +x NVIDIA*.run

You now need to close gdm3 because it can't be running for the driver install. Record what you need now. If you don't get a login screen when you close gdm3, press control + alt + F1
/etc/init.d/gdm3 stop

Now the install
cd ~
./NVIDIA*.run --dkms -z

Accept the EULA
Select yes to register the kernel module with DKMS
No to libs (unless you want them)
Ok to acknowledge the website libs
The install will take place
Do not run X-Config. Select NO.
The installer will close.

Restart kali with
shutdown -r now

When rebooted, run optirun glxspheres64 and confirm it's working. A 'modinfo nvidia' will show that you now have the 340.24 module loaded.

To install CUDA, chmod the installer first
cd ~
chmod +x cuda*.run

And now to install
./cuda*.run

Accept the EULA
Select yes to unsupporrted configuration
No to graphics driver
Yes to the toolkit
Accept default location
Yes to symbolic link
Yes to samples
Yes to default samples location
The toolkit will install

For the path, we will add a little more to what we defined for VirtualGL. It should look like this in your bashrc file
nano ~./bashrc
export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin

Run the following so we don't have to log out
export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin

Edit the following file so the contents match those shown below
nano /etc/ld.so.conf

include /etc/ld.so.conf.d/*.conf
/usr/local/cuda-6.0/lib64

Save and close

Run:
ldconfig

Build the nvidia samples

cd /root/NVIDIA_CUDA-6.0_Samples
make

Follow the steps from the second post to run the CUDA deviceQuery script and you should see pass.

Remember to remove or comment out the wheezy backports repo

[Quest]

root@kali:~/NVIDIA_CUDA-6.0_Samples/1_Utilities/deviceQuery# optirun ./deviceQuery
./deviceQuery Starting...

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

Detected 1 CUDA Capable device(s)

Device 0: "GeForce GT 630M"
  CUDA Driver Version / Runtime Version          6.5 / 6.0
  CUDA Capability Major/Minor version number:    2.1
  Total amount of global memory:                 2048 MBytes (2147155968 bytes)
  ( 2) Multiprocessors, ( 48) CUDA Cores/MP:     96 CUDA Cores
  GPU Clock rate:                                950 MHz (0.95 GHz)
  Memory Clock rate:                             900 Mhz
  Memory Bus Width:                              128-bit
  L2 Cache Size:                                 131072 bytes
  Maximum Texture Dimension Size (x,y,z)         1D=(65536), 2D=(65536, 65535), 3D=(2048, 2048, 2048)
  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: 32768
  Warp size:                                     32
  Maximum number of threads per multiprocessor:  1536
  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): (65535, 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 Bus ID / PCI location ID:           1 / 0
  Compute Mode:
     < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 6.5, CUDA Runtime Version = 6.0, NumDevs = 1, Device0 = GeForce GT 630M
Result = PASS
root@kali:~/NVIDIA_CUDA-6.0_Samples/1_Utilities/deviceQuery#

i have to tell ya, I've been meaning to do this now for over 7 months with a week of intense web search, and that last Howto above f i n a l l y did it!

Many thanks staticn0de ! =]

[staticn0de]

Hi Quest,

I'm happy to hear that. I'll update the first post so others know the newer drivers may work in lieu of the old.

Thanks for posting to let everyone know it worked for you.

[Quest]

That's my 'dummyproof' edited version of your guide.

Update and upgrade Kali to latest

apt-get update && apt-get upgrade && apt-get dist-upgrade

Downloads
You will need the files below (64 bit) I always go with 64bit as I am on Kali 64bit. Download in the Home folder or place them in the Home folder after.

CUDA 6.0.37 for Ubuntu 12.04 64Bit
http://developer.download.nvidia.com...7_linux_64.run
VirtualGL 2.3.3_amd64 for 64Bit
http://downloads.sourceforge.net/pro...se_mirror=ufpr
Nvidia 340.24
http://www.nvidia.com/Download/index.aspx?lang=en-us 

Install VirtualGL
cd ~

dpkg -i virtualgl*.deb

Add the path for VirtualGL to .bashrc

nano ~/.bashrc

Add a line somewhere at the top that reads:
export PATH=$PATH:/opt/VirtualGL/bin

Save the file(Ctrl+x, then Y, then Enter)

Export the path so we don't have to log out and in.

export PATH=$PATH:/opt/VirtualGL/bin

Install the linux headers

apt-get install linux-headers-$(uname -r)

Some dependencies for CUDA for later

apt-get install freeglut3-dev libxmu-dev

Add the wheezy backports Repo (yes, still needed for bumblebee but not the NVIDIA driver)
Go to Computer > File System > etc > apt > souces.list, and open it with Leafpad, and add the following line to the file and then save.
deb http://ftp.debian.org/debian wheezy-backports main contrib non-free

apt-get update

Install bumblebee (not bumblebee-nvidia)

apt-get install bumblebee primus

Edit the bumblebee.conf file

nano /etc/bumblebee/bumblebee.conf

Change line 22 so it reads:
Driver=nvidia

Run the following and record your PCI address for your video card. It will look similar to 03:00.0 (yours might be different)

lspci | egrep 'VGA|3D'

Edit xorg.conf.nvidia 

nano /etc/bumblebee/xorg.conf.nvidia

add a line under the 'Section "Device"' area so that is matches what is shown below. Change the bus ID to match what you recorded previously and take note that you recored a . before the last number and it is now a ':'. You need the ':'.

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

Restart bumblebee with the following and ignore any ERROR/FAIL warnings

/etc/init.d/bumblebeed restart

Change NVIDIA installer permissions
cd ~

chmod +x NVIDIA*.run

You now need to close gdm3 because it can't be running for the driver install. 
Record what you need now. If you don't get a login screen when you close gdm3, press control + alt + F1

/etc/init.d/gdm3 stop

Now the NVIDIA install
cd ~

./NVIDIA*.run --dkms -z

-Accept the EULA
-Select yes to register the kernel module with DKMS
-No to libs (unless you want them)
-Ok to acknowledge the website libs
The install will take place...
-Do not run X-Config. Select NO.
The installer will close. 

Restart kali with

shutdown -r now 

or Ctrl+Alt+Del

When rebooted, run 

optirun glxspheres64

A 'modinfo nvidia' will show that you now have the 340.24 module loaded.

modinfo nvidia

To install CUDA, chmod the installer first
cd ~

chmod +x cuda*.run

And now to install CUDA

./cuda*.run

-Accept the EULA (Tab then, accept)
-Select yes to unsupported configuration
-No to graphics driver
-Yes to the toolkit
-Accept default location (press Enter only)
-Yes to symbolic link
-Yes to samples
-Yes to default samples location (press Enter only)
The toolkit will install...

For the path, we will add a little more to what we defined for VirtualGL earlier.

nano ~/.bashrc

 It should look like this in your bashrc file 
 export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin

Run the following so we don't have to log out

export PATH=$PATH:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin

Edit the following file so the contents match those shown below

nano /etc/ld.so.conf

Contents:
include /etc/ld.so.conf.d/*.conf
add /usr/local/cuda-6.0/lib64

Save and close

Run

ldconfig

Build the nvidia samples

cd /root/NVIDIA_CUDA-6.0_Samples

make

cd 1_Utilities/deviceQuery

optirun ./deviceQuery

You should see Result = PASS!

Now, I know you want to see it in action so the next part we'll install Pyrit.

First, remove the Wheezy repo. 
You may either comment out the line we added or delete it.
Computer > File System > etc > apt > souces.list,
Save the file. 

apt-get update

Checkout Pyrit

svn checkout http://pyrit.googlecode.com/svn/trunk/ pyrit_svn

Install required libraries and add CUDA support

apt-get install libpcap-dev

cd pyrit_svn/pyrit/

python setup.py build

python setup.py install

cd ../cpyrit_cuda/

python setup.py build

python setup.py install

Now, what we have been waiting for this entire time. Lets see it work.

optirun pyrit benchmark

as a side note, after all this my Kali installation went from a little less then 8Gb to 11Gb. Interesting...

[barni123]

Run the command below to confirm that bumblebee is working
optirun glxspheres64

Hi,
I have the following problem: when I enter this last command optirun glxspheres64, my screen goes totally black and my nvidia vgas start to run on full speed (vents go on full throttle) and after 20s my laptop shuts down. I suppose my hardware causes the peoblem, I have 3VGAs: the integrated intel hd4400, and 2 nvidia gt750M. I don't want to use SLI, I only want to use one VGA which makes me able to change the kali's resolution to fullhd.

[johnnyinc]

Hi staticn0de and all,

I have problems with bumblebee, my gear is: Lenovo thinkpad T440p with geforce 730m card.

My source.list file:

## Regular Updates
deb http://http.kali.org/kali kali main non-free contrib
deb http://security.kali.org/kali-security kali/updates main contrib non-free

## Source Updates
deb-src http://http.kali.org/kali kali main non-free contrib
deb-src http://security.kali.org/kali-security kali/updates main contrib non-free

## Bumblebee
#deb http://ftp.debian.org/debian wheezy-blackports main contrib non-free

The last entry is commented out I'm deleting the comment before installing bumblebee primus and apt-get update

With above configuration of source list I have an error while apt-get update && apt-get upgrade -y && apt-get dist-update -y:

Errors were encountered while processing:
Linux-image-3.14-kali1-amd64
extlinux
E: Sub-process /usr/bin/dpkg returned an error code (1)

After Configuring bumblebee.conf and xorg.conf.nvidia and restarting bumblebeed service which fails I did /etc/init.d/gdm3 stop and i receive the following error:

bash: /etc/init.d/gdm3: cannot execute binary file

I need to hard restart the laptop and after this me kali installation totally breaks. I have an error while booting:

The root filesystem is currently mounted in read-only mode. A maintenece will now be started. After performing system maintenance, press Ctrl+D to terminate the maintenance shell and restart the system...

If You need more additional info on the behavior or configuration files please let me know.
If you have any ideas whats wrong Please let me know

[staticn0de]

Hi,
I have the following problem: when I enter this last command optirun glxspheres64, my screen goes totally black and my nvidia vgas start to run on full speed (vents go on full throttle) and after 20s my laptop shuts down. I suppose my hardware causes the peoblem, I have 3VGAs: the integrated intel hd4400, and 2 nvidia gt750M. I don't want to use SLI, I only want to use one VGA which makes me able to change the kali's resolution to fullhd.

Hi there,

I've been doing some reading on SLI (I have just about the cheapest laptop I could buy so I don't have it) and it requires a little extra configuration in the /etc/bumblebee/xorg.conf.nvidia file.

So, when you run the command:

lspci | grep VGA

You should see two nvidia cards with two BusID. You will need to configure both within the /etc/bumblebee/xorg.conf.nvidia file.

So, within that file, add those BusIDs under the Device section. After that, you need to find the section which includes a bunch of "Option" settings (bottom of the file). Add a new line with:

Option "SLI" "AA"

Read more about it here, it's writen for arch but the config files are the same. https://wiki.archlinux.org/index.php...A#Enabling_SLI

Did you use the latest Nvidia 340 drivers or did you install the ones from the first post? If you tried the first post, try the latest drivers.

[staticn0de]

Hi staticn0de and all,

I have problems with bumblebee, my gear is: Lenovo thinkpad T440p with geforce 730m card.

My source.list file:

## Regular Updates
deb http://http.kali.org/kali kali main non-free contrib
deb http://security.kali.org/kali-security kali/updates main contrib non-free

## Source Updates
deb-src http://http.kali.org/kali kali main non-free contrib
deb-src http://security.kali.org/kali-security kali/updates main contrib non-free

## Bumblebee
#deb http://ftp.debian.org/debian wheezy-blackports main contrib non-free

The last entry is commented out I'm deleting the comment before installing bumblebee primus and apt-get update

With above configuration of source list I have an error while apt-get update && apt-get upgrade -y && apt-get dist-update -y:

Errors were encountered while processing:
Linux-image-3.14-kali1-amd64
extlinux
E: Sub-process /usr/bin/dpkg returned an error code (1)

After Configuring bumblebee.conf and xorg.conf.nvidia and restarting bumblebeed service which fails I did /etc/init.d/gdm3 stop and i receive the following error:

bash: /etc/init.d/gdm3: cannot execute binary file

I need to hard restart the laptop and after this me kali installation totally breaks. I have an error while booting:

The root filesystem is currently mounted in read-only mode. A maintenece will now be started. After performing system maintenance, press Ctrl+D to terminate the maintenance shell and restart the system...

If You need more additional info on the behavior or configuration files please let me know.
If you have any ideas whats wrong Please let me know

Edit Again: After all that is below, I did reinstall the packages autoremove removed with the exception of libplrpc-perl as it was not in the repo.

apt-get install libnet-daemon-perl memtest86+ syslinux-themes-debian syslinux-themes-debian-wheezy

Everything works with the exception of memtest86 (but that is a known bug as I am EFI booting)

Edit:

Ok, so I an update (see next post) and had the same error. It's not related to bumblebee or nvidia (it's a repo issue)

Boot into Kali recovery mode and run:

apt-get autoremove

After that, reboot. Should be back in Kali.

Run

apt-get update && apt-get upgrade

and you should have no more errors.

The following are the packages which were removed under my apt-get autoremove. I have not tried reinstalling them yet.

libnet-daemon-perl libplrpc-perl memtest86+ syslinux-themes-debian syslinux-themes-debian-wheezy

From looking at the packages which were updated just before all this happened, I'd hazard a guess and say updating either of the following caused the broken package

syslinux or syslinux-common

[staticn0de]

Edit: Sorted in previous post


I just ran an apt-get upgrade and received the same:

Setting up syslinux-common (3:6.03~pre1+dfsg-1kali3) ...
Setting up syslinux (3:6.03~pre1+dfsg-1kali3) ...
Setting up extlinux (3:6.03~pre1+dfsg-1kali3) ...
P: Checking for EXTLINUX directory... found.
/boot/vmlinuz-3.14-kali1-amd64
P: Writing config for /boot/vmlinuz-3.14-kali1-amd64...
P: Updating /boot/extlinux/linux.cfg...
I: os-proper disabled in /etc/default/extlinux: Skipping /boot/extlinux/os-proper.cfg
E: /usr/share/EXTLINUX/themes/debian: No such file or directory
dpkg: error processing extlinux (--configure):
subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:
extlinux
E: Sub-process /usr/bin/dpkg returned an error code (1)

Seems like the repo has bad packages

[johnnyinc]

Thank You staticn0de

apt-get autoremove cleared the issue but it still not resolve the bumblebee problem. I have now the following problems:

After stoping gdm3 I receive the following error messages non stop:
[ 835.063840] ata6.00: status: { DRDY }
[ 835.638286] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 835.736372] ata6.00: irq_stat 0x40000001
[ 835.762738] ata6.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 30
[ 835.638286] res 50/00:03:00:12:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[ 837.036379] ata6.00: status: { DRDY }
And so on and so on

I have rebooted the laptop and install nVidia driver in recovery mode after install and reboot i have issued the command: optirun glxspheres64 and receive the following error:
[ 42.235078] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
[ 42.235176] [ERROR]Aborting because fallback start is disabled

Do You have any ideas whats the case ?
Thank You so much for Your help.

[staticn0de]

Thank You staticn0de

apt-get autoremove cleared the issue but it still not resolve the bumblebee problem. I have now the following problems:

After stoping gdm3 I receive the following error messages non stop:
[ 835.063840] ata6.00: status: { DRDY }
[ 835.638286] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 835.736372] ata6.00: irq_stat 0x40000001
[ 835.762738] ata6.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 30
[ 835.638286] res 50/00:03:00:12:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[ 837.036379] ata6.00: status: { DRDY }
And so on and so on

I have rebooted the laptop and install nVidia driver in recovery mode after install and reboot i have issued the command: optirun glxspheres64 and receive the following error:
[ 42.235078] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver
[ 42.235176] [ERROR]Aborting because fallback start is disabled

Do You have any ideas whats the case ?
Thank You so much for Your help.

Few things,

That may be a hard drive error. Check your hard drive smart stats and run a test.

Otherwise, did bumblebee install correctly?

I'll need some information. Post the results of the following commands

uname -r

cat /etc/modprobe.d/bumblebee.conf

Run optirun glxspheres64 and then run

dmesg

lspci | egrep 'VGA|3D'

What version of Kali are you using?

Are you 32bit or 64bit?

The important part is you have this in your /etc/modprobe.d/bumblebee.conf file

blacklist nouveau

[Rarity]

Hey n0de, thanks for this write up! There's one problem I'm experiencing:

The drivers are correctly installed when I check 'modinfo nvidia', but when I run the command 'optirun glxspheres64' I get the error:

[ 2037.152986] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please

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

When I check lspci | egrep "VGA|3D" it comes back as a 3D controller, not VGA. Not sure if that matters when configuring /etc/bumblebee/xorg.conf.nvidia

Also, I noticed in your updated post you didn't include

Now install the nvidia drivers
apt-get install nvidia-glx

Are there not certain dependencies needed from this? Cause even when I run glxspheres64 I get

Polygons in scene: 62464
Xlib:  extension "GLX" missing on display ":0.0".
ERROR (603): Could not obtain RGB visual with requested properties

Thanks again!! I'm looking forward to finally getting my video card recognized.

[staticn0de]

Hey n0de, thanks for this write up! There's one problem I'm experiencing:

The drivers are correctly installed when I check 'modinfo nvidia', but when I run the command 'optirun glxspheres64' I get the error:

[ 2037.152986] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please

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

When I check lspci | egrep "VGA|3D" it comes back as a 3D controller, not VGA. Not sure if that matters when configuring /etc/bumblebee/xorg.conf.nvidia

Also, I noticed in your updated post you didn't include



Are there not certain dependencies needed from this? Cause even when I run glxspheres64 I get

Polygons in scene: 62464
Xlib:  extension "GLX" missing on display ":0.0".
ERROR (603): Could not obtain RGB visual with requested properties

Thanks again!! I'm looking forward to finally getting my video card recognized.

Hey there,

nvidia-glx is not required for the second install. This is a transitional package to install the older drivers.

That being said, i'm going to need a lot more information from you to help.

use the [CODE] brackets to paste the output of commands (the code close bracket is a [*/CODE] without the *. Put all the text between them.

run optirun glxspheres64 and then paste the output of the command below. The last 30 lines or so.

dmesg

Paste your /etc/bumblebee/bumblebee.conf

Paste your /etc/bumblebee/xorg.nvidia.conf

Paste the output of

lspci | egrep 'VGA|3D'

Paste the output of

modinfo nvidia

and

modinfo nvidia-uvm

and

echo $PATH

Paste the output of

find 2> /dev/null / -name nvidia*.ko

That should do for a start

[Rarity]

Thanks for the quick reply, but I won't be able to respond until later tonight. I'll edit this once I can.

[Quest]

Hi staticn0de!

so everything was working fine, but then when I tried to use cowpatty/pyrit/crunch with FrankenScript, I get an error..
"ERROR: could not insert 'nvidia': No such device"

So then I ran some tests, and I cannot run optirun glxspheres64 anymore!? Here are the outputs...

root@kali:~# optirun glxspheres64
[ 3086.847274] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

[ 3086.847338] [ERROR]Aborting because fallback start is disabled.
root@kali:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.14-kali1-amd64 ([email protected]) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.14.5-1kali1 (2014-06-07)
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.14-kali1-amd64 root=UUID=df2555ed-577b-46d4-b82c-bae880f39864 ro quiet
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
SNIP
[ 2809.151223]  [<ffffffff814efb08>] ? page_fault+0x28/0x30
[ 2809.151228]  [<ffffffff810d81e1>] ? SyS_init_module+0xb1/0xe0
[ 2809.151234]  [<ffffffff814f7879>] ? system_call_fastpath+0x16/0x1b
[ 2809.151237] ---[ end trace a26dc4680320df79 ]---
[ 2809.151431] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
[ 2809.151474] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
[ 2809.151474] NVRM: installed in this system is not supported by the 340.24
[ 2809.151474] NVRM: NVIDIA Linux driver release.  Please see 'Appendix
[ 2809.151474] NVRM: A - Supported NVIDIA GPU Products' in this release's
[ 2809.151474] NVRM: README, available on the Linux driver download page
[ 2809.151474] NVRM: at www.nvidia.com.
[ 2809.151553] nvidia: probe of 0000:01:00.0 failed with error -1
[ 2809.151961] NVRM: The NVIDIA probe routine failed for 1 device(s).
[ 2809.151964] NVRM: None of the NVIDIA graphics adapters were initialized!
[ 2809.151966] [drm] Module unloaded
[ 2809.152095] NVRM: NVIDIA init module failed!
[ 3085.254654] ------------[ cut here ]------------
[ 3085.254666] WARNING: CPU: 4 PID: 6853 at /build/kalibuild-linux_3.14.5-1kali2-amd64-igeTGG/linux-3.14.5/fs/proc/generic.c:315 proc_register+0xd8/0x170()
[ 3085.254669] proc_dir_entry 'driver/nvidia' already registered
[ 3085.254670] Modules linked in: nvidia(PO+) nls_utf8 nls_cp437 vfat fat ctr ccm nfnetlink_log nfnetlink bbswitch(O) binfmt_misc loop 
SNIP
[ 3085.254767] CPU: 4 PID: 6853 Comm: modprobe Tainted: P        W  O 3.14-kali1-amd64 #1 Debian 3.14.5-1kali1
[ 3085.254769] Hardware name: TOSHIBA Satellite P850/QFKAA, BIOS 1.90 08/21/2012
[ 3085.254771]  0000000000000000 0000000000000009 ffffffff814e9b1e ffff8802235afbe8
[ 3085.254776]  ffffffff810639d6 ffff880224ed9680 ffff8802230a2175 ffff8802230a2100
[ 3085.254780]  ffff880226501b80 0000000000000000 ffffffff81063ab5 ffffffff81718cc0
[ 3085.254784] Call Trace:
[ 3085.254795]  [<ffffffff814e9b1e>] ? dump_stack+0x41/0x51
[ 3085.254802]  [<ffffffff810639d6>] ? warn_slowpath_common+0x86/0xb0
[ 3085.254807]  [<ffffffff81063ab5>] ? warn_slowpath_fmt+0x45/0x50
[ 3085.254813]  [<ffffffff811fe238>] ? proc_register+0xd8/0x170
[ 3085.254819]  [<ffffffff811fe3db>] ? proc_mkdir_data+0x4b/0x70
[ 3085.254925]  [<ffffffffa0d764f9>] ? nv_register_procfs+0x39/0x1b0 [nvidia]
[ 3085.254994]  [<ffffffffa1c06286>] ? nvidia_init_module+0x286/0x79d [nvidia]
[ 3085.255061]  [<ffffffffa1c067ac>] ? nv_drm_init+0xf/0xf [nvidia]
[ 3085.255126]  [<ffffffffa1c067ac>] ? nv_drm_init+0xf/0xf [nvidia]
[ 3085.255191]  [<ffffffffa1c0682e>] ? nvidia_frontend_init_module+0x82/0x854 [nvidia]
[ 3085.255198]  [<ffffffff8100218a>] ? do_one_initcall+0x10a/0x160
[ 3085.255203]  [<ffffffff81057b74>] ? set_memory_nx+0x44/0x50
[ 3085.255210]  [<ffffffff810d7903>] ? load_module+0x1ac3/0x22f0
[ 3085.255215]  [<ffffffff810d3d90>] ? show_initstate+0x50/0x50
[ 3085.255221]  [<ffffffff811668b5>] ? map_vm_area+0x25/0x40
[ 3085.255229]  [<ffffffff814efb08>] ? page_fault+0x28/0x30
[ 3085.255234]  [<ffffffff810d81e1>] ? SyS_init_module+0xb1/0xe0
[ 3085.255240]  [<ffffffff814f7879>] ? system_call_fastpath+0x16/0x1b
[ 3085.255242] ---[ end trace a26dc4680320df7a ]---
[ 3085.255404] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=none
[ 3085.255442] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:0de9)
[ 3085.255442] NVRM: installed in this system is not supported by the 340.24 <---!? all tests were fine before
[ 3085.255442] NVRM: NVIDIA Linux driver release.  Please see 'Appendix
[ 3085.255442] NVRM: A - Supported NVIDIA GPU Products' in this release's
[ 3085.255442] NVRM: README, available on the Linux driver download page
[ 3085.255442] NVRM: at www.nvidia.com.
[ 3085.255501] nvidia: probe of 0000:01:00.0 failed with error -1
[ 3085.256058] NVRM: The NVIDIA probe routine failed for 1 device(s).
[ 3085.256064] NVRM: None of the NVIDIA graphics adapters were initialized!
[ 3085.256067] [drm] Module unloaded
[ 3085.256272] NVRM: NVIDIA init module failed!
root@kali:~# lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 630M] (rev a1)
root@kali:~# modinfo nvidia
filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
alias:          char-major-195-*
version:        340.24
supported:      external
license:        NVIDIA
alias:          pci:v000010DEd00000E00sv*sd*bc04sc80i00*
alias:          pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        drm,i2c-core
vermagic:       3.14-kali1-amd64 SMP mod_unload modversions 
parm:           NVreg_Mobile:int
parm:           NVreg_ResmanDebugLevel:int
parm:           NVreg_RmLogonRC:int
parm:           NVreg_ModifyDeviceFiles:int
parm:           NVreg_DeviceFileUID:int
parm:           NVreg_DeviceFileGID:int
parm:           NVreg_DeviceFileMode:int
parm:           NVreg_RemapLimit:int
parm:           NVreg_UpdateMemoryTypes:int
parm:           NVreg_InitializeSystemMemoryAllocations:int
parm:           NVreg_RMEdgeIntrCheck:int
parm:           NVreg_UsePageAttributeTable:int
parm:           NVreg_MapRegistersEarly:int
parm:           NVreg_RegisterForACPIEvents:int
parm:           NVreg_CheckPCIConfigSpace:int
parm:           NVreg_EnablePCIeGen3:int
parm:           NVreg_EnableMSI:int
parm:           NVreg_MemoryPoolSize:int
parm:           NVreg_RegistryDwords:charp
parm:           NVreg_RmMsg:charp
parm:           NVreg_AssignGpus:charp
root@kali:~# modinfo nvidia-uvm
filename:       /lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
supported:      external
license:        MIT
depends:        nvidia
vermagic:       3.14-kali1-amd64 SMP mod_unload modversions 
root@kali:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/VirtualGL/bin:/usr/local/cuda-6.0/bin
root@kali:~# find 2> /dev/null / -name nvidia*.ko
/lib/modules/3.14-kali1-amd64/updates/dkms/nvidia.ko
/lib/modules/3.14-kali1-amd64/updates/dkms/nvidia-uvm.ko
/var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia.ko
/var/lib/dkms/nvidia/340.24/3.14-kali1-amd64/x86_64/module/nvidia-uvm.ko
root@kali:~# 

Edit:

root@kali:~# modprobe nvidia
ERROR: could not insert 'nvidia': No such device
root@kali:~#

root@kali:~# optirun pyrit benchmark
[ 5141.410827] [ERROR]Cannot access secondary GPU - error: Could not load GPU driver

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

so it would appear that nothing works, when everything was working before. weird

Edit2:

Nevermind. I've reinstalled the image of my Kali installation, and all tests passed like before. A likely reason for the above problems is that I set my swapiness to 0 after the installation(?) I cannot see anything else that might have caused that.

Now I will do tests to try to make cowpatty/pyrit/crunch work in real life...

Edit3: Everything works, and swapiness set to 0 had nothing to do with my previous problems. So I have no idea what caused it. I'm suspecting an update(?)

[cru-z]

Dude u are the best, perfect tut!!!!

go ahead dude!

love u!

[Quest]

yes really, he saved me from 2months of searching/testing. Good to know that there are ppl like that outhere. Sharp contrast with the rest. "linux community" is an oxymoron.



For those who want to install oclHashcat

Download oclHashcat 1.01 (508Mb) to your Home folder.
http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/

Install oclHashcat

dpkg -i oclhashcat*.deb

Test CudaHashcat(GeForce)

cd /usr/share/oclhashcat/ 

./cudaHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict

[staticn0de]

yes really, he saved me from 2months of searching/testing. Good to know that there are ppl like that outhere. Sharp contrast with the rest. "linux community" is an oxymoron.



For those who want to install oclHashcat

Download oclHashcat 1.01 (508Mb) to your Home folder.
http://ftp.tku.edu.tw/kali/pool/non-free/o/oclhashcat/

Install oclHashcat

dpkg -i oclhashcat*.deb

Test CudaHashcat(GeForce)

cd /usr/share/oclhashcat/ 

./cudaHashcat.bin -t 32 -a 7 example0.hash ?a?a?a?a example.dict

Hey there quest,

oclhashcat is in the kali repos (version 1.01) so there is no need to download the .deb file.

oclhashcat from the repo also includes the cudahashcat which is what all us nvidia users are after anyway.

I'm currently trying to get the new hashcat working on kali but it has this habit of breaking other things when I get it to work....

[Quest]

Hi friend,

Yes it's in the Kali repo root@kali:~# apt-get install oclhashcat but that is still 508Mb to download every time for every installation. I much prefer to get it once and keep it, otherwise it never ends.

Speaking of. My Kali installation is now at 14Gb with all this. So this howto alone(including Kali updates) gets about 5Gb of archives if I'm not mistaken.

Good luck with the R&D

[staticn0de]

Hi friend,

Yes it's in the Kali repo root@kali:~# apt-get install oclhashcat but that is still 508Mb to download every time for every installation. I much prefer to get it once and keep it, otherwise it never ends.

Speaking of. My Kali installation is now at 14Gb with all this. So this howto alone(including Kali updates) gets about 5Gb of archives if I'm not mistaken.

Good luck with the R&D

If you have a computer that stays on all the time, like a media server - take a look at apt-cacher.

It stores stuff that is downloaded from a repo locally. This way, you don't have to download it from the repo each time as it will come from your local server. A lot easier and faster than trying to mirror the repo.

[nekromantik]

Used this guide and installed bumblebee and cuda with pyrit. thanks
but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
Cant boot into kali only windows.

[staticn0de]

Used this guide and installed bumblebee and cuda with pyrit. thanks
but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
Cant boot into kali only windows.

Used this guide and installed bumblebee and cuda with pyrit. thanks
but now I have issue, after restarting laptop (dual boot 1.08 with win 8.1) I choose Kali or Kali recovery in grub and it stays on blank screen.
Cant boot into kali only windows.

Hi there,

Can you press CTRL + ALT + F1 and reach a terminal?

Is it blank screen or do you have a blinking cursor?

That is the typical symptom for if the laptop was not restarted after installing the NVIDIA drivers (after stopping gdm3) or x-config was run. I say this because you should not have been able to install CUDA without a restart and you have said you installed everything up to pyrit and then could not restart without a blank screen.

If you can reach terminal, run

cd ~
./NVIDIA*.run --uninstall

and then apt-get purge nvidia* bumblebee* primus*

and restart

[nekromantik]

Hi there,

Can you press CTRL + ALT + F1 and reach a terminal?

Is it blank screen or do you have a blinking cursor?

That is the typical symptom for if the laptop was not restarted after installing the NVIDIA drivers (after stopping gdm3) or x-config was run. I say this because you should not have been able to install CUDA without a restart and you have said you installed everything up to pyrit and then could not restart without a blank screen.

If you can reach terminal, run

cd ~
./NVIDIA*.run --uninstall

and then apt-get purge nvidia* bumblebee* primus*

and restart

Hi

No I dont get a blinking cursor.
So ctl alt F1 dont work.

Can only access grub menu and edit grub parameters pressing e key.

[nab]

Hi staticn0de!
First, thank for your guide. it helped me a lot. The result show pass.
But i don't know is it working? I see in system setting->details: it don't show graphics driver!
Then i tried test:
glxinfo | grep -i "direct rendering"
It show:
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".

Is it problem?

[staticn0de]

Hi staticn0de!
First, thank for your guide. it helped me a lot. The result show pass.
But i don't know is it working? I see in system setting->details: it don't show graphics driver!
Then i tried test:
glxinfo | grep -i "direct rendering"
It show:
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".

Is it problem?

Hi there,

Prefix your command with optirun.

If you have a pass from the cuda device detect script the driver is working. You must prefix commands which require the driver to be loaded with optirun.

The nvidia card is disabled during normal use to save power. Optirun enables it for the duration the program running needs it

[nab]

Hi there,

Prefix your command with optirun.

If you have a pass from the cuda device detect script the driver is working. You must prefix commands which require the driver to be loaded with optirun.

The nvidia card is disabled during normal use to save power. Optirun enables it for the duration the program running needs it

Oh, it working. thank you.
And one more thing i can't understand. nvidia-settings require me do nvdia-xconfig. If i do , X server can't start and i have to remove xorg.conf. it like cycle! (sr my bad english)