RX VEGA unboxing - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Misc (https://hashcat.net/forum/forum-15.html) +--- Forum: Hardware (https://hashcat.net/forum/forum-13.html) +--- Thread: RX VEGA unboxing (/thread-6739.html) Pages:
1
2
|
RX VEGA unboxing - aprizm - 07-30-2017 https://www.youtube.com/watch?v=twkZz5WyVJs Can't wait to see the benchmarks on that badboy. From what I have gathered the price will be around 900-1600 USD depending if you want the water-cooled version.
RE: RX VEGA unboxing - atom - 07-30-2017 I got some ROCm benchmarks from a User but only for MD4, it's a bit slower than a 1080Ti: Quote:Hashtype: MD4 1080Ti: Quote:Hashtype: MD4 Would also like to see comparisons of other modes RE: RX VEGA unboxing - kjs - 07-30-2017 These are for Vega FE (but RX should be similar IMHO): $ uname -a Linux X10SDV16C 4.11.0-kfd-compute-rocm-rel-1.6-115 #1 SMP Sat Jul 22 17:28:42 CDT 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarchecurity-9.20160110ubuntu0.2-amd64ecurity-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial $ ./hashcat --opencl-info hashcat (v3.6.0-268-g332396a) starting... OpenCL Info: Platform ID #1 Vendor : Advanced Micro Devices, Inc. Name : AMD Accelerated Parallel Processing Version : OpenCL 2.0 AMD-APP (2450.0) Device ID #1 Type : GPU Vendor ID : 1 Vendor : Advanced Micro Devices, Inc. Name : gfx900 Version : OpenCL 1.2 Processor(s) : 64 Clock : 1600 Memory : 12276/16368 MB allocatable OpenCL Version : OpenCL C 2.0 Driver Version : 1.1 (HSA,LC) Platform ID #2 Vendor : Intel(R) Corporation Name : Intel(R) OpenCL Version : OpenCL 1.2 LINUX Device ID #2 Type : CPU Vendor ID : 8 Vendor : Intel(R) Corporation Name : Intel(R) Xeon(R) CPU D-1587 @ 1.70GHz Version : OpenCL 1.2 (Build 25) Processor(s) : 32 Clock : 1700 Memory : 1969/7876 MB allocatable OpenCL Version : OpenCL C 1.2 Driver Version : 1.2.0.25 $ /opt/rocm/bin/rocm-smi -a -d 1 ==================== ROCm System Management Interface ==================== ================================================================================ GPU[1] : GPU ID: 0x6863 ================================================================================ ================================================================================ GPU[1] : Temperature: 48.0c ================================================================================ ================================================================================ GPU[1] : GPU Clock Level: 7 (1600Mhz) GPU[1] : GPU Memory Clock Level: 3 (945Mhz) ================================================================================ ================================================================================ GPU[1] : Fan Level: 35 (13.73)% ================================================================================ ================================================================================ GPU[1] : Current PowerPlay Level: high ================================================================================ ================================================================================ GPU[1] : Current OverDrive value: 0% ================================================================================ ================================================================================ GPU[1] : Minimum SCLK: 1528MHz GPU[1] : Minimum MCLK: 0MHz GPU[1] : Activity threshold: 0% GPU[1] : Hysteresis Up: 0ms GPU[1] : Hysteresis Down: 0ms ================================================================================ ================================================================================ GPU[1] : Average GPU Power: 18.0 W ================================================================================ ================================================================================ GPU[1] : Supported GPU clock frequencies on GPU1 GPU[1] : 0: 852Mhz GPU[1] : 1: 991Mhz GPU[1] : 2: 1138Mhz GPU[1] : 3: 1269Mhz GPU[1] : 4: 1348Mhz GPU[1] : 5: 1440Mhz GPU[1] : 6: 1528Mhz GPU[1] : 7: 1600Mhz * GPU[1] : GPU[1] : Supported GPU Memory clock frequencies on GPU1 GPU[1] : 0: 167Mhz GPU[1] : 1: 500Mhz GPU[1] : 2: 800Mhz GPU[1] : 3: 945Mhz * GPU[1] : ================================================================================ ==================== End of ROCm SMI Log ==================== $ sudo ./hashcat -b -d 1 hashcat (v3.6.0-268-g332396a) starting in benchmark mode... Benchmarking uses hand-optimized kernel code by default. You can use it in your cracking session by setting the -O option. Note: Using optimized kernel code limits the maximum supported password length. To disable the optimized kernel code in benchmark mode, use the -w option. OpenCL Platform #1: Advanced Micro Devices, Inc. ================================================ * Device #1: gfx900, 12276/16368 MB allocatable, 64MCU OpenCL Platform #2: Intel(R) Corporation ======================================== * Device #2: Intel(R) Xeon(R) CPU D-1587 @ 1.70GHz, skipped. Hashtype: MD4 Speed.Dev.#1.....: 48956.1 MH/s (87.43ms) Hashtype: MD5 Speed.Dev.#1.....: 24784.3 MH/s (86.35ms) Hashtype: Half MD5 Speed.Dev.#1.....: 15315.8 MH/s (69.80ms) Hashtype: SHA1 Speed.Dev.#1.....: 8843.6 MH/s (60.17ms) Hashtype: SHA-256 Speed.Dev.#1.....: 3887.2 MH/s (68.74ms) Hashtype: SHA-384 Speed.Dev.#1.....: 543.1 MH/s (60.77ms) Hashtype: SHA-512 Speed.Dev.#1.....: 549.9 MH/s (60.00ms) Hashtype: SHA-3 (Keccak) Speed.Dev.#1.....: 441.9 MH/s (74.81ms) Hashtype: SipHash * Device #1: ATTENTION! OpenCL kernel self-test failed. Your device driver installation is probably broken. See also: https://hashcat.net/faq/wrongdriver Speed.Dev.#1.....: 17980.5 MH/s (59.40ms) Hashtype: Skip32 (PT = $salt, key = $pass) Speed.Dev.#1.....: 10699.8 MH/s (1.28ms) Hashtype: RIPEMD-160 Speed.Dev.#1.....: 5421.0 MH/s (98.34ms) Hashtype: Whirlpool Speed.Dev.#1.....: 561.3 MH/s (58.78ms) Hashtype: GOST R 34.11-94 Speed.Dev.#1.....: 502.3 MH/s (65.72ms) Hashtype: GOST R 34.11-2012 (Streebog) 256-bit Speed.Dev.#1.....: 126.1 MH/s (131.19ms) Hashtype: GOST R 34.11-2012 (Streebog) 512-bit Speed.Dev.#1.....: 126.0 MH/s (131.24ms) Hashtype: DES (PT = $salt, key = $pass) Speed.Dev.#1.....: 24001.5 MH/s (89.03ms) Hashtype: 3DES (PT = $salt, key = $pass) Speed.Dev.#1.....: 390.5 MH/s (85.62ms) Hashtype: phpass, WordPress (MD5), phpBB3 (MD5), Joomla (MD5) Speed.Dev.#1.....: 7252.3 kH/s (70.15ms) Hashtype: scrypt Speed.Dev.#1.....: 370.4 kH/s (2132.59ms) Hashtype: PBKDF2-HMAC-MD5 Memory access fault by GPU node-1 on address 0x742479000. Reason: Page not present or supervisor privilege. Aborted (core dumped) --- < Unfortunately the benchmark stopped here :/, but here a few more selected hashtypes I've benchmarked seperately > --- Hashtype: WPA/WPA2 Speed.Dev.#1.....: 410.5 kH/s (77.25ms) Hashtype: NTLM Speed.Dev.#1.....: 49044.4 MH/s (87.27ms) Hashtype: bcrypt $2*$, Blowfish (Unix) Speed.Dev.#1.....: 21686 H/s (45.65ms) Hashtype: Bitcoin/Litecoin wallet.dat Speed.Dev.#1.....: 2507 H/s (65.23ms) Hashtype: Ethereum Wallet, PBKDF2-HMAC-SHA256 Speed.Dev.#1.....: 6022 H/s (84.04ms) I also have a Vega FE Liquid coming in the next few days and will post benchmarks of that card then. RE: RX VEGA unboxing - cpu_pirate - 08-15-2017 Bumping this, new cards are in hands now. I managed to grab 2 RX Vega 64's on launch day, they will arrive 8/17/17. I was hoping to build a duel mining / cracking machine, but looks like the cards are kind of poop at mining at the moment so I'll be sticking the 2 in with probably 1080Ti's for now. I'll post a benchmark once I get them in, have no experience with AMD in linux so it will be a learning curve to get them optimized to hash. RE: RX VEGA unboxing - Wolfman - 08-16-2017 Could you try the mining driver as well, and see if it effects the results for Hashcat? https://hothardware.com/news/amd-radeon-rx-vega-mining-block-chain-ethereum RE: RX VEGA unboxing - cpu_pirate - 08-16-2017 Seems like a no brainier ... bot I don't know if I will be installing these in a windows box .. we will see. RE: RX VEGA unboxing - bbanelli - 08-16-2017 Here are quick results of Vega64 Liquid (courtesy of PcEkspert E-zine) Code: Microsoft Windows [Version 10.0.15063] It stopped on "DPAPI masterkey file v1 and v2" test for some reason, didn't have time to see what's wrong... RE: RX VEGA unboxing - cpu_pirate - 08-16-2017 Thanks for the bench, right on par with the 1080, so not bad! That's a big step for AMD IMO. RE: RX VEGA unboxing - bbanelli - 08-16-2017 (08-16-2017, 04:05 PM)cpu_pirate Wrote: Thanks for the bench, right on par with the 1080, so not bad! That's a big step for AMD IMO.I think so as well. Hopefully, new drivers will increase performance and stability as well. BTW, if anyone is interested, I have created a short executable for parsing hashcat benchmarks into CSV format. Basically, you can take your CLI output, save it to file and parse it with software. It can parse up to 9 separate devices, any version of hashcat is supported. You merely start it, chose your hashcat benchmark output file (like the ones in this thread) and get CSV out of it. It is very simple so it has no support for file naming of output or any other features. You can see some examples below. http://imgur.com/wHzc6sr http://imgur.com/0GemZQQ Download link Windows x64: https://drive.google.com/open?id=0BwSyHhd25zZhbEVsMDM3ZmhJZFU VirusTotal report: https://www.virustotal.com/en/file/ebf7537147fa5d162cc29610d824628e55eb40b1972578cc9491b47c7c66ff5f/analysis/1502907535/ Download link Linux x64: https://drive.google.com/open?id=0BwSyHhd25zZhc3RQdEVTNllXS0k VirusTotal report: https://www.virustotal.com/en/file/b560cac31467cf7b0b24697c05d5c56c9e8cc9fce0a1895ebeb764999a488499/analysis/1502908021/ RE: RX VEGA unboxing - cpu_pirate - 08-17-2017 Looks like your post was not just stock clocks I am able to reach your numbers with 10% OC on my card but it appears to be a driver crash and hashcat just hangs on the "DPAPI masterkey file v1 and v2" test for whatever reason requiring a reboot in win 10, I have replicated this multiple times on different bios and drivers .. going to try the "blockchain" beta drivers now and will report back. |