Legacy hardware won't cut it(HD 5970)

[iahiMsogarD]

Hello there,
story time, based on these Benchmarks, i went on ebay like sites and found that the AMD HD 5970 had the best ratio for hash/s/dollar which was about 2300 hash/s/dollar (wpa2).

The problem: Hashcat just wont run on the GPU

What i have tried:
OS: Win7, Win8.1
Driver:Crimsom 15.12,16.2.1 Beta, Catalyst 15.7.1
(all the combinations of os and drivers from above)

On the latest and greatest driver 16.2.1, hashcat won run on the GPU, wont even acknowledge the existence of the GPU, it will just start to hash on the CPU.

Other versions will spew the "cl_platform_not_found_khr" error.

1.Does anybody have or know a stable and working combination of drivers and OSes for HD 5970?

2.(Better question) Should i ditch Windows for some real OS like some distro of unix?

[undeath]

AMD dropped opencl support for that device years ago. It's useless for hashcat.

[iahiMsogarD]

Is there any oclHashcat, driver, OS combo that it could work on?
As if it was 2010 the current year?

My only hope right now it to replicate the results of the unknown user that submitted those results back in the day

[tacohashcat]

Use old drivers with an old version of hashcat?
older versions: https://hashcat.net/forum/thread-5668.html
Edit: and older AMD drivers: http://support.amd.com/en-us/download/de...7%20-%2064 (those are Win7 64bit)

[iahiMsogarD]

As suggested by tacohashcat (thanks) i tried older versions of the AMD drivers and hashcat (for some reason i couldn't run oclHashcat)
but i went a step further and tried more combinations of drivers and hashcats and those are the results:

Driver V    HC    H/s for WPA/WPA2
13.12      3         43665
              3.1       43409          
              3.2       14258
              3.3       17611
              3.4       14017
              3.5       16408
              3.6       17459
              4.0       82394
              4.1       48897
                     
                     
14.4        3          64553
              3.1       64269
              3.2       18104
              3.3       18028
              3.4       19421
              3.5       17396
              3.6       17915
              4.0       86673
              4.1       86575
                     
14.9        3         45342
              3.1       50588
              3.2       22578
              3.3       22796
              3.4       23194
              3.5       23039
              3.6       22676
              4.0       39085
              4.1       73966
                     
14.12      3          48925
              3.1       50138
              3.2       23137
              3.3       23367
              3.4       23043
              3.5       23215
              3.6       22989
              4.0       73375
              4.1       49069
                     
15.7        3          52451
              3.1       58559
              3.2       18850
              3.3       20017
              3.4       22076
              3.5       21513
              3.6       22670
              4.0       80399
              4.1       93113 --highest
                     
15.7.1     3          58635
              3.1       54142
              3.2       23176
              3.3       23386
              3.4       22569
              3.5       22469
              3.6       23365
              4.0       92142
              4.1       60199
                     
16.2.1     3          -cpu-only
              3.1       -cpu-only
              3.2       -cpu-only
              3.3       -cpu-only
              3.4       -cpu-only
              3.5       -cpu-only
              3.6       -cpu-only
              4.0       -cpu-only
              4.1       -cpu-only
(Win7 x64 - HD5970)

Does anybody know whats the matter with AMD and this inconsistent support of openCL?
And why hashcat 3.2-3.6 seems to have taken a performance hit? Is it "normal" or is there a flaw in my tests?

[atom]

That's the typical behaviour with the drivers. They often change the optimization settings in the JiT compiler. Sometimes the driver then optimizes something to the bad, so it becomes slower than if it would let the code stay as-is. Too bad you can't use the rocm drivers with the hd5970, it's simply too old. My tip: get rid of it.

[Flomac]

One reason why AMD and hashcat are not the most proper combo.

[iahiMsogarD]

Thanks for the responses, i think it would be for the better to get rid of them.