Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Segmentation fault on Mesa and AMDGPU
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am an Arch Linux user and attempted to run hashcat on my R9 290. However, on both the AMDGPU and Mesa drivers I am given this message:

Code:
hashcat (v3.00) starting in benchmark-mode...

OpenCL Platform #1: Mesa
========================
- Device #1: AMD HAWAII (DRM 2.43.0, LLVM 3.8.0), 256/1024 MB allocatable, 40MCU

Hashtype: MD4

Segmentation fault (core dumped)

I attempted to install the catalyst drivers this morning to no avail. As well, I have installed the opencl-mesa, opencl-headers, and ocl-icd packages in order to enable opencl support. I was under the impression that the Mesa drivers were working, is there something I'm missing?
Yes, hashcat fully supports them. But they are very unstable and therefore they often crash.

To verify it's not hashcat, compile hashcat from sources with DEBUG=1 make and then run the same command from gdb. You will find that it crashes somewhere in the Mesa libraries.

For your Hawaii GPU, which is propably a 290 or 290x, you need to stick to AMD drivers 15.12.
(07-15-2016, 10:16 AM)atom Wrote: [ -> ]Yes, hashcat fully supports them. But they are very unstable and therefore they often crash.

To verify it's not hashcat, compile hashcat from sources with DEBUG=1 make and then run the same command from gdb. You will find that it crashes somewhere in the Mesa libraries.

For your Hawaii GPU, which is propably a 290 or 290x, you need to stick to AMD drivers 15.12.

I see, well gdb gives me this so I guess it is just the mesa drivers 
Code:
- Device #1: AMD HAWAII (DRM 2.43.0, LLVM 3.8.0), 256/1024 MB allocatable, 40MCU

Hashmode: 900
- Device #1: build_opts '-I /root/hashcat/OpenCL -D VENDOR_ID=2147483648 -D CUDA_ARCH=0 -D VECT_SIZE=4 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=3 -D DGST_R2=2 -D DGST_R3=1 -D DGST_ELEM=4 -D KERN_TYPE=900 -D _unroll -cl-std=CL1.1'

- Device #1: Kernel /root/hashcat/kernels/m00900_a3.6cbd0b42.kernel (83722 bytes)
- Device #1: Kernel /root/hashcat/kernels/markov_le.6cbd0b42.kernel (19444 bytes)
Hashtype: MD4

[New Thread 0x7fffbaf84700 (LWP 13147)]

Thread 3 "hashcat" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffbaf84700 (LWP 13147)]
0x00007fffd0efc8c8 in ?? () from /usr/lib/gallium-pipe/pipe_radeonsi.so
I do own a r9 290 though and did attempt to install the Catalyst drivers. I was under the impression that they had been deprecated by most distros, is it still feasible to have them on a modern system?
Yes, that's true. You have either switch to windows, buy a new gpu with amdgpu-pro support or stick to an older distribution. Thanks AMD Smile