01-18-2018, 07:32 PM
ok i used \$ and its loaded now
THX!
philsmd: thx for tip!
testing
THX!
philsmd: thx for tip!
testing
13 gpu issue
|
01-18-2018, 07:32 PM
ok i used \$ and its loaded now
THX! philsmd: thx for tip! testing
And final questions...
this is v3 wallet with scrypt... so no chance amd 8 gb ram will work (because CU?) with that... right? 1080 will work because use SM and is better but not much faster? How about ryzen cpu ? or new i9 ? im trying -D 1 ... but segmention faults on my cpu... ------------------------------------------------- i switch pc and now i have: hashcat (v4.0.1-84-g7c1fb01) starting... OpenCL Platform #1: Advanced Micro Devices, Inc. ================================================ * Device #1: Intel(R) Core(TM) i7-3840QM CPU @ 2.80GHz, 7937/31748 MB allocatable, 8MCU OpenCL Platform #2: NVIDIA Corporation ====================================== * Device #2: Quadro K1000M, skipped. and i want to try device 1 cpu when i tried hash and dictoniary... its trying to start but Hashes: 1 digests; 1 unique digests, 1 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Rules: 1 Applicable optimizers: * Zero-Byte * Single-Hash * Single-Salt Password length minimum: 0 Password length maximum: 256 Watchdog: Temperature abort trigger set to 90c Initializing device kernels and memory...Segmentation fault when u try quadro gpu it loads dictrionary... but exhausted... to low gpu memory... but why CPU doesnt work? when i start default i see this: * Device #1: Not a native Intel OpenCL runtime. Expect massive speed loss. You can use --force to override, but do not report related errors. * Device #2: This hardware has outdated CUDA compute capability (3.0). For modern OpenCL performance, upgrade to hardware that supports CUDA compute capability version 5.0 (Maxwell) or higher. * Device #2: WARNING! Kernel exec timeout is not disabled. This may cause "CL_OUT_OF_RESOURCES" or related errors. To disable the timeout, see: https://hashcat.net/q/timeoutpatch maybe this is a problem?
01-18-2018, 11:18 PM
There are a lot of warnings in your output.
Starting from the timeout patch problem to the "Not a native Intel OpenCL runtime" error. It's not a good idea to ignore all warnings and don't try to fix them. Intel has a dedicated OpenCL Runtime (not SDK!) page where you can download the Intel OpenCL Runtime for your CPU. I also just noticed that this confusion about -D/-d might come from blogs like this one: https://stealthsploit.com/2018/01/04/eth...pu-vs-cpu/ There are a lot of people trying exactly that, i.e. run -D 12 or something like that even through it makes absoultely no sense if you read the --help output (-D only allows 3 different values 1, 2 or 3 and this values are not for the device selection but for the type selection). Therefore in my opinion the whole article (all the -D x recommendation etc) needs to be fixed. Maybe someone can contact the author before we get flooded with several "problems" like this one (see original post of this thread). |
« Next Oldest | Next Newest »
|