Ubuntu Server + Oclhashcat - Driver

[cheeseburger]

This question is in reference to the series of steps delineated in the "HOWTO: Ubuntu Server + AMD Catalyst + oclHashcat" tutorial. I've included a link below. I've been following this well-written tutorial exactly as authored, without deviation from the methods.

Unfortunately, I've encountered a problem that I'm unable to resolve on my own. When I attempt to install the driver, I encounter an error that my graphics card is not compatible with this driver. I believe this to be false. The driver is the correct revision. Could I be mistaken?

To give you better insight, I have transcribed the sequence of events immediately preceding this error.

1.) Downloaded driver

#curl --referer "http://support.amd.com/en-us/download/desktop?os=Linux+x86" -o amd-catalyst-14-9-linux-x86-x86-64.zip http://www2.ati.com/drivers/linux/amd-ca...x86-64.zip

2.) Unzipped driver package

#unzip amd-catalyst-14-9-linux-x86-x86-64.zip

3.) Run installer

#sh fglrx-14.301.1001/amd-driver-installer-14.301.1001-x86.x86_64.run

At this point, I'm greeted by a hybrid graphical user interface asking if I would like to:

a.) Generate Distribution Specific Driver Package

b.) Install Driver


I select install driver. Shortly thereafter, I encounter an error stating, "Your graphics adapter is not supported by this adapter. Installation will not proceed."

I'm using a 64-bit system.


I've also repeated the steps outlined above whilst using a 32-bit system with identical results. Thus far, the solution has eluded me.


Any help/insight will be tremendously appreciated. Thanks!

[epixoip]

What GPU do you have?

[cheeseburger]

Radeon 5970

[epixoip]

Hm, ok, that is quite strange. 5970 is absolutely supported by that driver. Is this a card that you've owned awhile and have used previously, or is this a card you recently acquired?

[cheeseburger]

It is indeed peculiar. This is a used GPU. The previous owner utilized it for bit coin mining. I'm beginning to believe this GPU may be defective. I have successfully configured this GPU and oclhashcat on a windows machine. My screen turns completely WHITE when I initiate a brute force attack via oclhashcat. A few days ago, I successfully configured this very GPU with The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) 1.0.9. At the time, I was utilizing pyrit to initiate a brute force attack. Similar outcome. The screen turned black. Whether using The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) or Windows, I can hear the GPU fan switch to full throttle immediately after issuing the brute force command. However, given there is no display, I'm unable to verify the validity of the execution of the previously mentioned command. This is my very first GPU; thus, I'm unsure how to independently verify its functionality. I had assumed that once plug in, and my monitor turns on, it was safe to assume the GPU was functional. I believe we can close this thread. Thank you for your help epixoip!

[cheeseburger]

Just thought I'd post this in case someone else may find this useful sometime in the future.

I re-enabled my Intel integrated graphics in the bios and booted into windows. When I issue a command to brute force via oclhashcat, I'm greeted with a windows notification stating the amd driver crashed and recovered. The GPU fan no longer engages to full throttle. With that said, I'm pleased to discover that oclhashcat is at least configured successfully.


WARN: ADL_Overdrive6_FanSpeed_Get(): -1

Device #1: Cypress, 1024MB, 725Mhz, 20MCU
Device #2: Cypress, 1024MB, 725Mhz, 20MCU

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c

Device #1: Kernel ./kernels/4098/m02500.Cypress_1573.4_1573.4 (VM).kernel (47160
4 bytes)
Device #1: Kernel ./kernels/4098/markov_le_v2.Cypress_1573.4_1573.4 (VM).kernel
(196024 bytes)
Device #1: Kernel ./kernels/4098/bzero.Cypress_1573.4_1573.4 (VM).kernel (33852
bytes)
Device #2: Kernel ./kernels/4098/m02500.Cypress_1573.4_1573.4 (VM).kernel (47160
4 bytes)
Device #2: Kernel ./kernels/4098/markov_le_v2.Cypress_1573.4_1573.4 (VM).kernel
(196024 bytes)
Device #2: Kernel ./kernels/4098/bzero.Cypress_1573.4_1573.4 (VM).kernel (33852
bytes)

Session.Name...: oclHashcat
Status.........: Running
Input.Mode.....: Mask (?d?d?d?d?d?d?d?d) [8]
Hash.Target....: 1234AB (00:11:22:33:44:55 <-> 66:77:88:99:10:11)
Hash.Type......: WPA/WPA2
Time.Started...: Tue Jan 01 01:48:28 2013 (2 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 0 H/s
Speed.GPU.#2...: 0 H/s
Speed.GPU.#*...: 0 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 0/100000000 (0.00%)
Skipped........: 0/0 (0.00%)
Rejected.......: 0/0 (0.00%)

[epixoip]

Heh 0 H/s. From everything you've described in your last two posts, that is a dead GPU.