I haven't personally used the guide you linked to but you should use that instead of this one. This how-to is specific for laptops that are Optimus enabled.Originally Posted by emrys
Member
I haven't personally used the guide you linked to but you should use that instead of this one. This how-to is specific for laptops that are Optimus enabled.
Junior Member
Hello! I have laptop lenovo y570, Kali Rollings 2016.2 4.8.0-kali2-amd64, 2 graphical chipsets :
1) Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller
2) VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 555M]
I want to combine resources of both graphical cards for brutforcing, but about two weeks I can't to install necessary drivers for nVidia. Who can helps me with new tutorials for kali rolling 2016.2 ?
PS : sorry for my english, is not my main language.
Junior Member
Rotor, I'm not sure if this will work as I have not tried it but I found this tutorial a few hours ago https://wheresmykeyboard.com/2016/10...016-2-rolling/. I do know the tutorial in this thread did not work for me as I came across a missing uri sources list error.
If anyone tries the about method let me know if it worked please as a few methods I tried made me have to completely reinstall Kali a few times.
Junior Member
unable to Complete and install the Toolkit. Is there anyway at the Dynamic Link step below to link to the cuda toolkit install from the repo (apt-get install nvidia-cuda-toolkit
####
Make sure this lines exist if not add to match in /etc/ld.so.conf
include /etc/ld.so.conf.d/*.conf
/usr/local/cuda-7.5/lib64
#####
Following errors with steps from
https://wheresmykeyboard.com/2016/10...016-2-rolling/
apt-get install dksm bbswitch-dkms <<-- no install from repo
apt-get build-dep bumblebee <<-----ISSUES
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
builddeps:bumblebee : Depends: dh-systemd (>= 1.4) but it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get install dh-systemd <<-------debhelper
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package dh-systemd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
debhelper
E: Package 'dh-systemd' has no installation candidate
apt-get install debhelper <<---------already the newest version
Reading package lists... Done
Building dependency tree
Reading state information... Done
debhelper is already the newest version (10.2.2).
debhelper set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
https://packages.debian.org/jessie/a...stemd/download
dpkg -i dh-systemd_1.22_all.deb <<----- dependency problems
Selecting previously unselected package dh-systemd.
(Reading database ... 364453 files and directories currently installed.)
Preparing to unpack dh-systemd_1.22_all.deb ...
Unpacking dh-systemd (1.22) ...
Replaced by files in installed package debhelper (10.2.2) ...
dpkg: dependency problems prevent configuration of dh-systemd:
debhelper (10.2.2) breaks dh-systemd (<< 1.38) and is installed.
Version of dh-systemd to be configured is 1.22.
dpkg: error processing package dh-systemd (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
dh-systemd
------------------------------------------------
sed -i 's/"Xorg"/"\/usr\/lib\/xorg\/Xorg"/' bumblebee-3.2.1/src/bbsecondary.h
sed: can't read bumblebee-3.2.1/src/bbsecondary.h: No such file or directory
-------------------------------
bumblebee-3.2.1/
bash: bumblebee-3.2.1/: No such file or directory
--------------------------
./cuda_7.5.18_linux.run --override compiler
Y/N/Y/Enter/Y/Enter/
Toolkit: Installation Failed
Warning: cannot find Toolkit in /usr/local/cuda-7.5. Use --toolkitpath to specify the toolkit location.
------------------------
sudo sh cuda_8.0.44_linux.run --override
Y/N/Y/Enter/Y/Enter/
Warning: cannot find Toolkit in /usr/local/cuda-8.0. Use --toolkitpath to specify the toolkit location.
sudo sh cuda_8.0.44_linux.run --override --toolkitpath
ERROR: toolkitpath: path must be absolute.
sudo sh cuda_8.0.44_linux.run --override --toolkitpath /usr/local/cuda-8.0/
ERROR: toolkitpath: path must be absolute.
sudo sh cuda_8.0.44_linux.run --override --/usr/local/cuda-8.0/
Unknown option: /usr/local/cuda-8.0/
Junior Member
This tutorial works on kali 2016.2 rolling and both nvidia and Cuda will install
PROBLEM THAT MAY ARISE WHILE INSTALLING
- bumblebee dont start itself
---- bumblebeed -D (to start it)
- Cuda installation problem(i installed it from run file)
-----libXi.so file missing
---sudo ln -s /usr/lib/x86_64-linux-gnu/libXi.so /usr/lib/libXi.so (jjust create link)
-----Can't locate InstallUtils.pm in @INC
---Do this it will work
1. unpack .run file ./cuda*.run --tar mxvf
2. copy InstallUtils.pm to /usr/lib/x86_64-linux-gnu/perl-base
3. export $PERL5LIB
Follow the steps provided in tutorial it will work
Junior Member
This is tempting but I'm a bit hesitant only because thrice it has forced me to completely reinstall Kali, my own fault for not creating a backup but I've hit a wall when it won't install the dep as well. I don't recall the repo source I used to get dep to install. Even though it worked once, I never was able to get it to set my Nvidia card as the main card for use.
Junior Member
I had issues with the cuda install from nvidia as well and ended up using the one from the repo.
apt-get install dksm bbswitch-dkms <---- theres a typo in his tutorial, it should be dkms not dksm
apt-get build-dep bumblebee <<-----ISSUES <--------- I had used a debian repo in my source list but not sure which one, wish I wrote it down because I wanted to try once more & reason why I forgot is in the next sentence.
I ended up trying his tutorial and it worked getting everything installed but my system still didn't recognize my nvidia card for certain things so I figured since I have a newer card it was a driver issue since bumblebee was installing older drivers so I tried installing the drivers from Nvidia and it ended up screwing up my login process and no matter what I did I couldn't get the system back to normal so I had to do a reinstall of Kali as a whole. I didn't write down the Debian repo I used because I wasn't entirely sure it mattered so after the fresh install I tried again and got the dependency error.
Junior Member
I had a 2010's GPU (a 330m notebook) does the cuda toolkit 7.5 support it?...The appropriate driver should be version 340.xx and on Nvidia page is listed they supports cuda toolkit 6.5
Junior Member
I succesfully installed Nvidia driver with Bumblebee and CUDA 8.0 but when I try to run optirun hashcat -b I get this error:
optirun glxgears output:hashcat (v3.30) starting in benchmark mode...
clGetDeviceIDs(): CL_DEVICE_NOT_FOUND
clGetDeviceIDs(): CL_DEVICE_NOT_FOUND
No devices found/left
Started: Fri Feb 24 16:01:02 2017
Stopped: Fri Feb 24 16:01:02 2017
optirun ./deviceQuery output:14130 frames in 5.0 seconds = 2825.824 FPS
./deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
Detected 1 CUDA Capable device(s)
Device 0: "GeForce GT 750M"
CUDA Driver Version / Runtime Version 8.0 / 8.0
CUDA Capability Major/Minor version number: 3.0
Total amount of global memory: 4038 MBytes (4233953280 bytes)
( 2) Multiprocessors, (192) CUDA Cores/MP: 384 CUDA Cores
GPU Max Clock rate: 1085 MHz (1.09 GHz)
Memory Clock rate: 900 Mhz
Memory Bus Width: 128-bit
L2 Cache Size: 262144 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(65536), 2D=(65536, 65536), 3D=(4096, 4096, 4096)
Maximum Layered 1D Texture Size, (num) layers 1D=(16384), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(16384, 16384), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 1 copy engine(s)
Run time limit on kernels: Yes
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): Yes
Device PCI Domain ID / Bus ID / location ID: 0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 8.0, CUDA Runtime Version = 8.0, NumDevs = 1, Device0 = GeForce GT 750M
Result = PASS
Junior Member
Try hashcat 3.10
Member
I had the same issue and fixed it .
first : I installed the driver 375.39 and cuda 8.0 from the repository . my GPU is Gt-740M
if you installed Cuda from the repository . it's saved as nvidia-cuda-toolkit in /usr/lib/nvidia-cuda-toolkit.
you need to create a symbolic link in /usr/local/ that points to the path of cuda-toolkit .
if you are not root add sudo .Code:ln -s /usr/lib/nvidia-cuda-toolkit /usr/local/cuda
follow the first post to set $PATH in bashrc and ld.so.conf path use cuda instead of cudaxxx version. because of the symlink above.
now the issue I came across was. in bumblebee.conf if I set the kernel-driver as nvidia-current . pyrit and hashcat don't work .
so I created a symbolic link (shortcut) to the kernel modules as nvidia and nvidia-uvm just like when you install it with the driver from Nvidia's website.
check your kernel version before running the commandsCode:ln -s /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-current.ko /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia.ko
then I changed the bumblebee.conf in kernel-driver add nvidia instead of nvidia-current.Code:ln -s /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-current-uvm.ko /lib/modules/4.9.0-kali3-amd64/updates/dkms/nvidia-uvm.ko
reboot and everything works . even with the latest hashcat version.
check withto see if the modules are well linked .Code:modinfo nvidia
another thing if you are having any issues with compiling cpyrit after you compiled pyrit (the main module)
in cpyrit folder change the line in setup.py to be like thisit will compile successfully .Code:nvcc_cmd = NVCC + bit_flag + ' -ccbin clang'\
Junior Member
I tried to followed the guide and apparently I have succeeded, since I'm getting a PASS result at the final steps.
However, I am unable to log into the machine using the default System X11, or neither GNOME and GNOME Classic. Only GNOME with WAYLAND works.
When I try to log in with the first 3 methods, after finish typing in my credentials I just got loop back into the login Username screen again. Note this is without bumblebee running since it does not automatically start on boot.
After starting bumblebee, right after finishing logging in the screen freeze, but I can still access tty. This is similar to when the Nvidia drivers were not installed correctly.
I have successfully installed official Nvidia driver previously to installing bumblebee, as I do not know if bumblebee need Nvidia drivers already in place to function or not. The guide that I followed to install official Nvidia drivers is here:
https://forums.kali.org/showthread.p...Optimus-laptop
So if anyone know what I should do please let me know. I appreciate it a lot.
Thank you staticn0de for an awesome guide and anyone who takes the time to help.
[SOLUTION:]
I have been able to solve this by following staticn0de post in this thread. All you need to do to be able to use X11 and GNOME again is deleting the file xorg.conf at /etc/X11/
There is still a slight issue however for those who wants to use GNOME on Wayland. If you login using Wayland, the terminal will have a black box around it. This problem is persistent before and after the GNOME fix I mentioned above. Though it is only a minor inconvenience and it only affects the terminal.
Last edited by chaopac; 2017-06-20 at 04:48.
Posting Permissions
