02-02-2013, 10:58 PM
Thread titles says it all.
I have 13.1 installed, working fine. It works with everything except hashcat.
Now, I'm not saying hashcat is at fault here. I know AMD/ATI drivers are very often complete crap when it comes to things like this. But my video card has more than 512MB of memory... though I am thinking that may be caused by running in X (Mint 14/Cinnamon).
I've searched Google, these forums and even tried Google Groups. I've found -nothing- telling me why this is happening. Heck, there are even threads here complaining about this very error happening on 12.6 and 12.8 with people.
The card is a Radeon HD 6870 with 1024MB of RAM. It games fine (both native games and games under WINE).
Any help appreciated.
Also, I've already seen the "let's send a complaint letter to AMD" thread. While I am all for that (and have done), it doesn't help my immediate problem.
Thanks.
I have 13.1 installed, working fine. It works with everything except hashcat.
Code:
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 16 loops, 8 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Barts, 512MB, 900Mhz, 14MCU
STOP! Unsupported or bad installed GPU driver version detected!
You need -exactly- Catalyst v13.1 for very good reasons
Now, I'm not saying hashcat is at fault here. I know AMD/ATI drivers are very often complete crap when it comes to things like this. But my video card has more than 512MB of memory... though I am thinking that may be caused by running in X (Mint 14/Cinnamon).
I've searched Google, these forums and even tried Google Groups. I've found -nothing- telling me why this is happening. Heck, there are even threads here complaining about this very error happening on 12.6 and 12.8 with people.
The card is a Radeon HD 6870 with 1024MB of RAM. It games fine (both native games and games under WINE).
Any help appreciated.
Also, I've already seen the "let's send a complaint letter to AMD" thread. While I am all for that (and have done), it doesn't help my immediate problem.
Thanks.