john-users - Nvidia CUDA drivers

Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Fri, 31 Jul 2015 11:37:25 +0200
From: Luis Rocha <luiscrocha@...il.com>
To: john-users@...ts.openwall.com
Subject: Nvidia CUDA drivers

Hello All,

I am trying to test some small Nvidia GPU on Ubuntu with CUDA drivers and
JtR but for some reason its failing. Thought to reach out to you guys to
see if anyone has any idea on what could be the problem



lrocha@...e8:~/JohnTheRipper/run$ lspci -v | grep NVI
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 300] (rev
a2) (prog-if 00 [VGA controller])
02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 300] (rev
a2) (prog-if 00 [VGA controller])


I installed the drivers using:
apt-get install libcuda1-331 nvidia-cuda-dev nvidia-cuda-toolkit


lrocha@...e8:~/JohnTheRipper/run$ nvopencc -v
NVIDIA (R) CUDA Open64 Compiler
Cuda compilation tools, release 5.5, V5.5.0
Built on 2013-07-17
Open64 Compiler Suite: Version 4.1
Built on: 2013-07-17
Thread model: posix
GNU gcc version 3.4.5 (Open64 4.2 driver)


and compiled the latest JtR community version with the following settings:

Configured for building John the Ripper jumbo:

Target CPU .................................. x86_64 AVX, 64-bit LE
AES-NI support .............................. depends on OpenSSL
Target OS ................................... linux-gnu
Cross compiling ............................. no
Legacy arch header .......................... x86-64.h

Optional libraries/features found:
Fuzzing test ................................ no
Experimental code ........................... no
OpenMPI support (default disabled) .......... no
Fork support ................................ yes
OpenMP support .............................. yes (not for fast formats)
OpenCL support .............................. yes
CUDA support ................................ yes
Generic crypt(3) format ..................... yes
Rexgen (extra cracking mode) ................ no
GMP (PRINCE mode and faster SRP formats) .... no
PCAP (vncpcap2john and SIPdump) ............. no
Z (pkzip format, gpg2john) .................. yes
BZ2 (gpg2john extra decompression logic) .... yes
128-bit integer (faster PRINCE mode) ........ yes
Memory map (share/page large files) ......... yes

Development options (these may hurt performance when enabled):
Memdbg memory debugging settings ............ disabled
AddressSanitizer ("ASan") ................... disabled
UndefinedBehaviorSanitizer ("UbSan") ........ disabled


Now, when I try to see the Cuda devices I always an abnormal number of CUDA
devices found and more surprising it changes every time .... and the Device
name is always gibberish

lrocha@...e8:~/JohnTheRipper/run$ ./john --list=cuda-devices | more
35436117 CUDA devices found:
CUDA Device #0
Name:                          U�..

lrocha@...e8:~/JohnTheRipper/run$ ./john --list=cuda-devices | more
46810709 CUDA devices found:
CUDA Device #0
Name:                          UF�.



Any idea what could be?

Thanks
Luis
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.