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

**Quest** · 2015-02-23

yes that would explain some of my paranormal experience.

## Regular repositories
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 repositories
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

I didn't have a choice as the headers would not install without those. But now that's probly my problem. Go figure.

**staticn0de** · 2015-02-23

Edit: cudahashcat deb updated to 1.33 and includes PDF fix

https://forums.kali.org/showthread.p...ll=1#post35240

**Quest** · 2015-02-25

===============================CudaHashcat 1.31:
Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Base.....: Mask (?a?a?a?a) [4]
Input.Mod......: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 41186.6 kH/s
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 65c Temp, -1% Fan

Started: Thu Feb 19 22:09:59 2015
Stopped: Thu Feb 19 22:24:07 2015 <---- = 14mins

===============================CudaHashcat 1.33:

Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Left.....: Mask (?a?a?a?a) [4]
Input.Right....: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: Tue Feb 24 23:59:16 2015 (27 mins, 22 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 83355.9 kH/s <--- wut???
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 71c Temp, -1% Fan

Started: Tue Feb 24 23:59:16 2015
Stopped: Wed Feb 25 00:26:49 2015 <---- = 27mins

**staticn0de** · 2015-02-25

Originally Posted by Quest

===============================CudaHashcat 1.31:
Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Base.....: Mask (?a?a?a?a) [4]
Input.Mod......: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 41186.6 kH/s
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 65c Temp, -1% Fan

Started: Thu Feb 19 22:09:59 2015
Stopped: Thu Feb 19 22:24:07 2015 <---- = 14mins

===============================CudaHashcat 1.33:

Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Left.....: Mask (?a?a?a?a) [4]
Input.Right....: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: Tue Feb 24 23:59:16 2015 (27 mins, 22 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 83355.9 kH/s <--- wut???
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 71c Temp, -1% Fan

Started: Tue Feb 24 23:59:16 2015
Stopped: Wed Feb 25 00:26:49 2015 <---- = 27mins

Well,

Thanks.... unique? Unless my math is a bit off

I'll have a go when I finally get my pi 2 image to compile and see what I get.

**Quest** · 2015-02-25

so needless to say that I reverted back to 1.31

... in other X-files news ...

- I still have to populate my sources.list file with official repos, to install the headers, or I get this

root@kali:~# apt-get install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-3.18.0-kali1-amd64
E: Couldn't find any package by regex 'linux-headers-3.18.0-kali1-amd64'

- but when installed, the NVIDIA driver stops halfway with the message "unable to load kernel modules".

... the good news...

I will edit post#4 https://forums.kali.org/showthread.p...ll=1#post35270 with a mini howtoo do a OFF-Line installation with all links to the packages.

**staticn0de** · 2015-02-26

Originally Posted by Quest

so needless to say that I reverted back to 1.31

... in other X-files news ...

- I still have to populate my sources.list file with official repos, to install the headers, or I get this
- but when installed, the NVIDIA driver stops halfway with the message "unable to load kernel modules".

... the good news...

I will edit post#4 https://forums.kali.org/showthread.p...ll=1#post35270 with a mini howtoo do a OFF-Line installation with all links to the packages.

Good call on reverting. I still haven't tested it.

I suffer huge losses in speed with the newer CUDA myself, not so much anything else.

You must have an out of date repo. The headers install fine for me, without them it is no surprise that your modules won't build.

Go over to the Kali Linux mirror list and manually point at one which had the headers in it. I went looking and found one (I have my own local repo I use) so I often search for the up to date ones to mirror.

**Quest** · 2015-02-26

I installed Kali with no Internet connection, so that is why I have to populate the sources.list with official repos. So I don't know what's up with that. I will try some other stuff eventually. Now I'm just sick of reinstalling(though I don't need the guide anymore lolll).

post #4 https://forums.kali.org/showthread.p...ll=1#post35270 edited with download links. Still will have to test all of it whenever I get sorted out, as I could only test parts of it at a time.

**Quest** · 2015-02-26

standby to wrapup another .deb friend http://hashcat.net/forum/thread-4085....html#pid23493

Edit:

oye, now moved my posts to http://hashcat.net/forum/thread-4130.html

No fix, as it is "optimized for fast systems" !?

and that's me confused more then ever-------->

**Quest** · 2015-02-26

From the hashcat forum

IOW, replace example.dict with rockyou and everything is fine

**Lobster** · 2015-02-28

I'm having the "Unable to load kernel module" error when (trying numerous times) to install my Geforce GT 640M drivers on my laptop.

Attempting to install the driver version 346.47 on kernel 3.18.0, Kali 1.1.0.

I have followed every guide, to the word and freshly installed way to many times to retain 100% of my sanity. Should I wait for a new driver to be produced, or try something else?

**Quest** · 2015-03-01

Hi Lobster,

Try again and don't install the linux headers (step #5). It did work for me.

If not then, welcome to the nut house!

**staticn0de** · 2015-03-01

Installing the headers should not be an issue. There has been a few posts lately about failed installs and 404 errors with the repos. I'm thinking that a few of the mirrors are out of date and this is causing some partial installs or some failed installs.

The thing about uname -r to install a kernel is that is checks the current running kernel and installs the header based on that.

if you updated from an older kernal and didn't reboot, the command linux-headers-$(uname -r) will install the headers for the older kernel.

What do you see if you run any of the following

apt-get install --dry-run linux-headers-3.18.0-kali1-amd64
apt-cache search linux-headers

**Quest** · 2015-03-01

root@kali:~# apt-get install --dry-run linux-headers-3.18.0-kali1-amd64
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-3.18.0-kali1-amd64 is already the newest version.
linux-headers-3.18.0-kali1-amd64 set to manually installed.
The following package was automatically installed and is no longer required:
libafpclient0
Use 'apt-get autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@kali:~# apt-cache search linux-headers
linux-headers-3.18.0-kali1-all - All header files for Linux 3.18 (meta-package)
linux-headers-3.18.0-kali1-all-amd64 - All header files for Linux 3.18 (meta-package)
linux-headers-3.18.0-kali1-amd64 - Header files for Linux 3.18.0-kali1-amd64
linux-headers-3.18.0-kali1-common - Common header files for Linux 3.18.0-kali1
linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)

I'm thinking about butting out and jump a version or two untill 2.0 ... Anyways let me know if you want me to checkout anything friend

**staticn0de** · 2015-03-02

I ran into that "Unable to load kernel module" from the NVIDIA installer (completely randomly)

Looks like it's an issue with the installer not unloading the nouveau module.

Unload it yourself after stopping the gdm3 service with:

modprobe -r nouveau

and then run

./NVIDIA-Linux-x86_64-346.47.run --dkms -Z (note the big Z)

**HackerChai** · 2015-04-04

Hi staticn0de, I have ran into a similar problem but your solution did not seem to resolve it.

As I got the error "Unable to load kernel module", I decided to load the module myself which resulted in this:

modprobe -vv nvidia

insmod /lib/modules/3.18.0-kali3-amd64/kernel/drivers/video/nvidia.ko
libkmod: INFO ../libkmod/libkmod-module.c:829 kmod_module_insert_module: Failed to insert module '/lib/modules/3.18.0-kali3-amd64/kernel/drivers/video/nvidia.ko': No such device
ERROR: could not insert 'nvidia': No such device
libkmod: INFO ../libkmod/libkmod.c:319 kmod_unref: context 0x7f7bcd4a22c0 released

Do you have any idea what is wrong?

I have succeeded installing nvidia before so I think this is not a problem with having the wrong installer.

**Quest** · 2015-03-03

Works

I should have known. Especially since the NVIDIA install was warning me(sometimes) about nouveau.

That unsolved mystery solved, what is your take on the new cudaHashcat? I'm very skeptical about the makers(atom) claim that it works better and that everything is "fine", when the benchmark takes twice as long as before.

If anyone has comparative benchmark(any) between 1.31 and 1.33 please share. Still waiting for anyone saying that 1.33 runs better than 1.31

**staticn0de** · 2015-03-03

Originally Posted by Quest

Works

I should have known. Especially since the NVIDIA install was warning me(sometimes) about nouveau.

That unsolved mystery solved, what is your take on the new cudaHashcat? I'm very skeptical about the makers(atom) claim that it works better and that everything is "fine", when the benchmark takes twice as long as before.

If anyone has comparative benchmark(any) between 1.31 and 1.33 please share. Still waiting for anyone saying that 1.33 runs better than 1.31

Here is my comparision

Code:

cudahashcat 1.31 example wordlist.

Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Base.....: Mask (?a?a?a?a) [4]
Input.Mod......: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: 0 secs
Time.Estimated.: 0 secs
Speed.GPU.#1...: 62193.8 kH/s
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 70c Temp, -1% Fan

Started: Tue Mar  3 13:18:58 2015
Stopped: Tue Mar  3 13:25:21 2015 


cudahashcat 1.33
                    
Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Left.....: Mask (?a?a?a?a) [4]
Input.Right....: File (example.dict)
Hash.Target....: File (example0.hash)
Hash.Type......: MD5
Time.Started...: Tue Mar  3 13:28:33 2015 (12 mins, 15 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...:   185.8 MH/s
Recovered......: 2190/6494 (33.72%) Digests, 0/1 (0.00%) Salts
Progress.......: 136302297088/136302297088 (100.00%)
Skipped........: 0/136302297088 (0.00%)
Rejected.......: 0/136302297088 (0.00%)
HWMon.GPU.#1...: -1% Util, 66c Temp, -1% Fan

Started: Tue Mar  3 13:28:33 2015
Stopped: Tue Mar  3 13:40:52 2015

Decent difference there. It's clear that 1.31 is much faster than 1.33.

I'm using CUDA 6.0 and the latest NVIDIA driver (I get better performance on the older CUDA)

I'll put the 1.31 link back up again.

**Lobster** · 2015-03-03

Thank you staticn0de & Quest, I got it installed and it was the nouveau module causing the problem, I appreciate the help greatly.

I can now concentrate on obtaining my sanity once again!

**Quest** · 2015-03-03

atom basically says that 1.33 is faster in real life. When pointed out that a benchmark IS real life, he replied that it's just a script. Unfortunately I was never successful cracking a .hccap file with cudaHashcat, so I cannot compare the two versions. If someone does have such comparative sessions please post. I asked over at http://hashcat.net/ for anyone to post comparative benchmarks. No one did.

Ok you have me doubting about 6.5 now. What is your benchmark to test CUDA? The one we usually do with the "Result = PASS" ?

**Quest** · 2015-03-03

but wait... now that everything seems to be back to normal for installing the headers and NVIDIA, the GRUB boot menu has 4 entries..

Kali GNU/Linux, with Linux 3.18.0-kali3-amd64
Kali GNU/Linux, with Linux 3.18.0-kali3-amd64 (recovery mode)
Kali GNU/Linux, with Linux 3.18.0-kali1-amd64
Kali GNU/Linux, with Linux 3.18.0-kali1-amd64 (recovery mode)

can anyone point me to the form to signup for the nut house please?

**staticn0de** · 2015-03-04

Originally Posted by Quest

but wait... now that everything seems to be back to normal for installing the headers and NVIDIA, the GRUB boot menu has 4 entries..

can anyone point me to the form to signup for the nut house please?

No need for the nut house, run the following to remove the older entries.

Code:

apt-get remove --purge linux-headers-3.18.0-kali1-amd64 linux-headers-3.18.0-kali1-common linux-image-3.18.0-kali1-amd64

**Quest** · 2015-03-03

Record what you need now. If you don't get a login screen when you close gdm3, press [Ctrl]+[Alt]+[F1]

Code:

/etc/init.d/gdm3 stop

Unload the Nouveau module after stopping the gdm3 service with:

Code:

modprobe -r nouveau

Now the NVIDIA install.
cd ~

Code:

./NVIDIA*.run --dkms -Z

<--Cap [Z]

- Accept the EULA
- Nouveau disabled Yes
- Files written Ok
- Register the kernel Yes
- WARNING 32-bit libraries Ok
- Install the libvdpau libraries Ok
…the install will take place
x Run the nvidia-xconfig No
- Installation complete Ok

Code:

shutdown -r now

or [Ctrl]+[Alt]+[Del]

**HackerChai** · 2015-04-04

Ignore this duplicate

**Rarity** · 2015-04-05

No other monitors connected to my PC

dmesg | tail after first booting up then firing up Firefox

Code:

[   94.728930] nvidia: module license 'NVIDIA' taints kernel.
[   94.728933] Disabling lock debugging due to kernel taint
[   95.212018] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[   95.212452] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
[   95.212458] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  346.47  Thu Feb 19 18:56:03 PST 2015

OFF/ON

Code:

tee /proc/acpi/bbswitch <<<OFF
OFF
tee /proc/acpi/bbswitch <<<ON
ON
dmesg | tail
[  217.822484] bbswitch: device 0000:01:00.0 is in use by driver 'nvidia', refusing OFF

optirun glxgears/glxspheres64 gives me this after closing the window

Code:

(dmesg)[83635.389363] pci 0000:01:00.0: Refused to change power state, currently in D0

dmesg | tail of OFF/ON after using optiplex glxspheres64 or optiplex glxgears:

Code:

tee /proc/acpi/bbswitch <<<OFF
(dmesg)[ 163.870602] bbswitch: disabling discrete graphics
(dmesg)[ 163.870613] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
tee /proc/acpi/bbswitch <<<ON
(dmesg)[ 224.089459] bbswitch: enabling discrete graphics

xorg.conf.nvidia

Code:

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

optirun glxgears and optirun glxspheres64 works fine, but both glxgears and glxspheres64 are broken for me.

Let me know if you need anymore info.

**staticn0de** · 2015-04-15

Originally Posted by Rarity

No other monitors connected to my PC

dmesg | tail after first booting up then firing up Firefox

Code:

[   94.728930] nvidia: module license 'NVIDIA' taints kernel.
[   94.728933] Disabling lock debugging due to kernel taint
[   95.212018] nvidia 0000:01:00.0: enabling device (0000 -> 0003)
[   95.212452] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 1
[   95.212458] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  346.47  Thu Feb 19 18:56:03 PST 2015

OFF/ON

Code:

tee /proc/acpi/bbswitch <<<OFF
OFF
tee /proc/acpi/bbswitch <<<ON
ON
dmesg | tail
[  217.822484] bbswitch: device 0000:01:00.0 is in use by driver 'nvidia', refusing OFF

optirun glxgears/glxspheres64 gives me this after closing the window

Code:

(dmesg)[83635.389363] pci 0000:01:00.0: Refused to change power state, currently in D0

dmesg | tail of OFF/ON after using optiplex glxspheres64 or optiplex glxgears:

Code:

tee /proc/acpi/bbswitch <<<OFF
(dmesg)[ 163.870602] bbswitch: disabling discrete graphics
(dmesg)[ 163.870613] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140926/nsarguments-95)
tee /proc/acpi/bbswitch <<<ON
(dmesg)[ 224.089459] bbswitch: enabling discrete graphics

xorg.conf.nvidia

Code:

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

optirun glxgears and optirun glxspheres64 works fine, but both glxgears and glxspheres64 are broken for me.

Let me know if you need anymore info.

Hey there,

I was able to reproduce this and am working on a fix.

I reproduced it through a manual loading and uploading of the driver. I'll let you know how I go.

**Rarity** · 2015-05-31

Originally Posted by staticn0de

Hey there,

I was able to reproduce this and am working on a fix.

I reproduced it through a manual loading and uploading of the driver. I'll let you know how I go.

Hey static, any update on a fix? Let me know if there's anything I can do to contribute.

**Quest** · 2015-03-06

https://hashcat.net/forum/thread-4161.html

How to deal with small wordlists

With oclHashcat v1.32 we added the AMP kernel that compute the password candidates on GPU. That had one advantage and one disadvantage.

The advantage was that you can now get full cracking speed even for the faster ones of the slow hashes like md5crypt because there's no bottleneck on the candidate generator engine.

...

http://hashcat.net/forum/thread-4162.html

I've reproduced the case, it's actually slower. Thanks for reporting!

But no worries, I already found the reason and fixed it. The bitmaps were optimized to run faster on a different hashlist size (much smaller one), but I an see that hashlist size around 500k is what we deal most of the time.

so i dunno. Confusing. Went from "everything is normal" to "actually slower". Hopefully they will get it sorted out with 1.34

**freestaff** · 2015-03-07

modprobe -r nouveau
FATAL: nouveau is in use

how can i ?

**Quest** · 2015-03-15

so v1.1.0a solved all my kernel problems. All is back to normal.

Now we seem to have a new error message after running modprobe -r nouveau (with gdm3 being shut down)..

[ 872.758616] nouveau E[ PFIFO] [0000:01:00.0] SCHED_ERROR [ UNK00 ]
[ 872.758698] nouveau E[ PFIFO] [0000:01:00.0] ...
...

no consequence though. Everything installed

- Post#4 (off-line install) is good.
- Waiting for cHc 1.34. No one has reported better performances under 1.33 so that's an X-file

**Quest** · 2015-03-16

...in the latest news...

no one knows how to install or run maskprocessor/linux over @ http://hashcat.net/forum/

and their wiki is useless.

If anyone knows how to install maskprocessor in kali, let me know.

**staticn0de** · 2015-03-16

Hey quest, what fails for you when you try and install?

**Quest** · 2015-03-16

hi friend!

actually it's not to install it(like previously thought), but it's a dependency problem..

Code:

:~# cd /usr/share/cudahashcat/ && ./mp64.bin -q 3 -r 4 ?d?d?d?d?d?d?d?d?d?d

returns

Code:

./mp64.bin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./mp64.bin)

further inquiry indicates that wheezy uses 2.13. So I will try to modify my sources.list with a jessie repo to get libc6_2.19-15_amd64.deb and libc6-dev_2.19-15_amd64.deb, because to install those package manually got ugly.

I thought I was out of the woods with 1.1.0a... Never a dull moment i tell ya.

**staticn0de** · 2015-03-16

Try my custom deb:

https://mega.co.nz/#!NIslBaaL!tHP5tI...Enq8LzoEHIape8

test it with

mp64 -q 3 -r 4 ?d?d?d?d?d?d?d?d?d?d

**Quest** · 2015-03-16

it works, but why is it, if I move the mp64.bin into the cudahashcat dir I get this..

~# cd /usr/share/maskprocessor-0.73 && ./mp64.bin -q 3 -r 4 ?d?d?d?d?d?d?d?d?d
./mp64.bin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./mp64.bin)

That's my problem.

**staticn0de** · 2015-03-16

Why are you moving it into a new directory? The directory "cd /usr/share/maskprocessor-0.73" is not where that deb installs it

I move my mp64.bin file all over the place and it works fine each time. I compiled it with the kali native glibc.

If you are seeing that error, are you sure that you are using the file from my deb, and not the binary you can download off the web?

**Quest** · 2015-03-16

what I'm trying to do:

markov chains is very efficient at creating words, but still spews out things like "arocassse" or with numbers "aroca7999". The odds of 3 repetitions for a human generated password are slim to none. I'm trying to eliminate those useless words using maskprocessor with the arguments '-q' and '-r' as those options are not included with cudahashcat.

-q 3 = no more than 1 repetition. Ex: aa
-r 4 = no more than 3 of the same char. Ex: aXaXa

ok so it's pretty simple, but when trying to pipe maskprocessor in cudahashcat it doesn't work in linux.

One solution proposed was to place mp64 in the cudahashcat dir. That is why I was trying that.

That was my original syntax, and since I've tried many..

Code:

cd /usr/share/cudahashcat/usr/share/maskprocessor && ./mp64.bin -q 3 -r 4 ?d?d?d?d?d?d?d?d?d?d | cd /usr/share/cudahashcat/ && ./cudaHashcat64.bin -w 3 -t 10 -m 2500 /root/capture.hccap -a 3

**staticn0de** · 2015-03-17

Originally Posted by Quest

what I'm trying to do:

markov chains is very efficient at creating words, but still spews out things like "arocassse" or with numbers "aroca7999". The odds of 3 repetitions for a human generated password are slim to none. I'm trying to eliminate those useless words using maskprocessor with the arguments '-q' and '-r' as those options are not included with cudahashcat.

-q 3 = no more than 1 repetition. Ex: aa
-r 4 = no more than 3 of the same char. Ex: aXaXa

ok so it's pretty simple, but when trying to pipe maskprocessor in cudahashcat it doesn't work in linux.

One solution proposed was to place mp64 in the cudahashcat dir. That is why I was trying that.

That was my original syntax, and since I've tried many..

Code:

cd /usr/share/cudahashcat/usr/share/maskprocessor && ./mp64.bin -q 3 -r 4 ?d?d?d?d?d?d?d?d?d?d | cd /usr/share/cudahashcat/ && ./cudaHashcat64.bin -w 3 -t 10 -m 2500 /root/capture.hccap -a 3

Works here with the following syntax. Also, I saw your other thread about handshakes and I captured mine as soon as the deauth packet was sent so I don't know why you are having problems.

Code:

root@kali ~$ mp64 -q 3 -r 4 ?d?d?d?d?d?d?d?d?d?d  | optirun cudahashcat64 -m 2500 ~/out.hccap    2 ↵  
cudaHashcat v1.31 starting...

Device #1: GeForce GT 740M, 2047MB, 1032Mhz, 2MCU
Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4318/m02500.sm_35.64.ptx
Device #1: Kernel ./kernels/4318/bzero.64.ptx

Starting attack in stdin mode...

                                             
Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: TESTROUTER IM:AM:AC:AD:DR <-> SE:CE:RE:T:MA:CC)
Hash.Type......: WPA/WPA2
Time.Started...: Tue Mar 17 16:14:19 2015 (9 secs)
Speed.GPU.#1...:    15393 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 151552
Skipped........: 0
Rejected.......: 0
HWMon.GPU.#1...: -1% Util, 71c Temp, -1% Fan

                                             
Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: TESTROUTER IM:AM:AC:AD:DR <-> SE:CE:RE:T:MA:CC)
Hash.Type......: WPA/WPA2
Time.Started...: Tue Mar 17 16:14:19 2015 (19 secs)
Speed.GPU.#1...:    15435 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 303104
Skipped........: 0
Rejected.......: 0
HWMon.GPU.#1...: -1% Util, 75c Temp, -1% Fan
                                             
Session.Name...: cudaHashcat
Status.........: Aborted
Input.Mode.....: Pipe
Hash.Target....: TESTROUTER IM:AM:AC:AD:DR <-> SE:CE:RE:T:MA:CC)
Hash.Type......: WPA/WPA2
Time.Started...: Tue Mar 17 16:14:19 2015 (24 secs)
Speed.GPU.#1...:    15420 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 352256
Skipped........: 0
Rejected.......: 0
HWMon.GPU.#1...: -1% Util, 68c Temp, -1% Fan

Started: Tue Mar 17 16:14:19 2015
Stopped: Tue Mar 17 16:14:43 2015

**Quest** · 2015-03-18

Originally Posted by g0tmi1k

Great guide - keep up the good work.

Originally Posted by staticn0de

Works here with the following syntax.

yes and thanks. Basically I was trying to make it do something that it was not supposed to do, which is to keep the '-t' argument and limit char recurrence with 'r' and 'q'. That failed. The rest of my problems were just me having another linux esoteric experience.

Originally Posted by staticn0de

Also, I saw your other thread about handshakes..

that's another can of worms. Just read the last post from mmusket33. He's having a linux paranormal experience of his own

meh, it's interesting, and the nurses here in the nuthouse are nice..

**g0tmi1k** · 2015-03-17

Great guide - keep up the good work.

**staticn0de** · 2015-03-21

Originally Posted by g0tmi1k

Great guide - keep up the good work.

Thanks g0tmi1k, I do appreciate the comment.

**upinarms247365** · 2015-03-17

I have a new system that I plan to run the latest Kali 1.1.0, which has installed the GeForce GTX 970. This guide looks like a great reference for getting started, but considering this isn't a laptop with Optimus enabled I'm not sure this will work for me. I tried following blackmoreops instructions http://www.blackmoreops.com/2015/02/.../#comment-2758 , but keep getting a solid black screen w/o the cursor after my reboot (see comments in the link for reference to my comments there).

Has anyone been successful on a non-optimus with these instructions or have a different resource for the proper instructions? My Google-foo did not produce anything worth-while.

**staticn0de** · 2015-03-19

Originally Posted by upinarms247365

I have a new system that I plan to run the latest Kali 1.1.0, which has installed the GeForce GTX 970. This guide looks like a great reference for getting started, but considering this isn't a laptop with Optimus enabled I'm not sure this will work for me. I tried following blackmoreops instructions http://www.blackmoreops.com/2015/02/.../#comment-2758 , but keep getting a solid black screen w/o the cursor after my reboot (see comments in the link for reference to my comments there).

Has anyone been successful on a non-optimus with these instructions or have a different resource for the proper instructions? My Google-foo did not produce anything worth-while.

Hi there,

I don't have any nvidia cards in my desktop installs so I can't write a guide for you.

It should be much the same. As in, update fully, Install Kali Linux headers, chmod the nvidia installer, install the driver and then actually run nvidia-xconfig.

Include the - - dkms and - Z flag on the installer.

Edit: I had a look at BMO guide, without checking it is possible that the drivers from the repo are too old for your modern card.

Hit control + all + f2 for another console and check dmesg when it tries to load your nvidia module.

Otherwise, grab the nvidia installer from the nvidia website like the guide here uses.

**Quest** · 2015-03-21

1.34 http://hashcat.net/oclhashcat/

**ZeroTrace** · 2015-03-21

*Couldn't delete*

**ZeroTrace** · 2015-03-21

*Couldn't delete*

**staticn0de** · 2015-03-21

Originally Posted by Quest

1.34 http://hashcat.net/oclhashcat/

Thanks for linking Quest, I'm uploading a new deb now.

Edit:

Uploaded:

https://mega.co.nz/#!0Z9DHBob!0QA3cl...iBwBepiYgWZbew

MD5
e611e16ab1f3c42c5e98d3ef615a0cd4

**ZeroTrace** · 2015-03-21

Hello, I'm having some issues that I'm not entirely sure are actual issues. I've followed the install procedure to the letter, and glxspheres64 runs without issue. However When I reach the final step I reach an impasse. I've created a pastebin account, and did the troubleshooting steps (find it here: http://pastebin.com/cwpA6XNz )

Hardware:
Lenovo ideapad y580
Intel HD4000 integrated
Nvidia gtx 660M
Intel I7 quad core 64 bit

I'm assuming I could continue with the optional installs, however I'm loathe to continue without having dealt with the errors. Any assistance would be appreciated greatly.

Thank you

**staticn0de** · 2015-03-29

Originally Posted by ZeroTrace

Hello, I'm having some issues that I'm not entirely sure are actual issues. I've followed the install procedure to the letter, and glxspheres64 runs without issue. However When I reach the final step I reach an impasse. I've created a pastebin account, and did the troubleshooting steps (find it here: http://pastebin.com/cwpA6XNz )

Hardware:
Lenovo ideapad y580
Intel HD4000 integrated
Nvidia gtx 660M
Intel I7 quad core 64 bit

I'm assuming I could continue with the optional installs, however I'm loathe to continue without having dealt with the errors. Any assistance would be appreciated greatly.

Thank you

Try editing your /etc/default/grub file to include this line (it will already be there but update it so it matches)

GRUB_CMDLINE_LINUX_DEFAULT="quiet rcutree.rcu_idle_gp_delay=1"

and then run "update-grub" and restart

**Quest** · 2015-03-22

well thank you...

Are you sitting down right now? http://hashcat.net/oclhashcat/

**staticn0de** · 2015-03-22

Originally Posted by Quest

well thank you...

Are you sitting down right now? http://hashcat.net/oclhashcat/

And.... done! again.

On the plus side, I changed the compression type and reduced the file size by 20% which is awesome.

https://mega.co.nz/#!dN8ESI7D!-jxoTZ...SOnkrNvxpDuNNg

md5sum

ccdc7ebf4c4a947d14fa663a982e3c10

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

Thread Tools

Search Thread

Display

Hybrid View

ERROR: could not insert 'nvidia': No such device

GRUB boot menu

updated NVIDIA sequence (step #14)

probe of 0000:01:00.0 failed with error -1

probe of 0000:01:00.0 failed with error -1

Similar Threads

Nvidia GF 960M - struggling with drivers for X on Optimus enabled laptop

NVIDIA and CUDA with OPTIMUS

Kali Linux 1.05 nvidia optimus cuda and pyrit

Posting Permissions