Bitcoin Forum

Hello all,

In the process of my mining and overclocking experimentation I've managed to cripple my 5970. Basically the first core locks as soon as it leaves the idle state, making it useless for hooking a monitor to it. I still mine on the second core, which gives me ~300MHs at default clocks and low memory, using phoenix on ubuntu. I have replaced it today with a new (to me, that is) one and don't feel like building a new rig for it :)

So, you'll get a Saphire branded 5970 that you can mine with, provided you only use the second core. I can push it to 800Mhz without issues, except for the deafening sound of the stupid stock cooler. If you wanna you can also get the original box, the Dirt 2 voucher and the selection of connectors that came with it.

I offer no warranty whatsoever but am willing to take the card back for the price paid (except for shipping) if it doesn't behave like advertised. It's some 2.5Kg total with box and all, so expect 9 btc shipping to Europe, probably 1.5~2x that to the US. Have no base price, bid away.

Oh, and since I crippled it I have been mining non-stop, and that was some 2~3 months ago, so I'm pretty confident it will do good by the new owner.

i bid 10 btc

I have the same problem with my 5970  :-\. Gigabyte by chance?

Nope, Saphire. But the problem is, I believe, bad VRM, basically overheated to death. The card does at times operate the first core for a bit, so the GPU is certainly fine.

I'll bid 12.5 BTC

Maybe I'll peel off the heatsink and take a look. Gigabyte's giving me a hard time on my RMA even though I ran it stock clocks. They said the serial number is not my region even though I bought it from Newegg. Plus, last time it took them 3 months to RMA my 8800GT. This is probably the last Gigabyte product I'm buying.

Depending on the amount of damage it might be possible to get it mining again.

Does it run fgl_glxgears on the damaged core?

If so then try this,

launch fgl_glxgears on that core, once it is running start the miner on that core, if it runs, then swiftly kill the gears process ... if it does get mining like this it may be prone to locking if it pauses too long between submitting shares (it drops back to idle and locks on relaunch) ... to prevent this run two instances of the miner on the same core and it will hardly ever find itself paused back to idle again ... unless you are unlucky (shares submitted from both process simultaneously or pool not responding)

A little bump... if you've bid and are still interested please restate your bid, as the exchange rates have changed quite a bit. Shipping will be ~€30 for Europe (~$43). Probably close to twice that for US.


I can't get fgl_glxgears to work even on the other card with 2 good cores. I'm using a simple ubuntu server with manually installed X and drivers, so maybe I'm missing something.

Hmmm, if you have the fglrx drivers installed and pointing the adapter at a relevant display it should run ... what's the error message?

No error, in fact I can list the devices on a display just fine. The thing might be running, but I see no output on the monitor, and it might very well just be an issue with the xorg.conf settings. I had to move my computer to the garage (too hot now to keep it around) and I don't really have a place to put the monitor right away. I'll retry in the next few days when I get a moment.

You should see some output like
$ fgl_glxgears
Using GLX_SGIX_pbuffer
66 frames in 5.0 seconds = 13.200 FPS
.
.
.

if it is running. If it is on display adapter of the monitor screen it will also pop-up a window with madly spinning gears.

You can change adapters which run the code by doing the

$export DISPLAY=:0.X ; fgl_glxgears

where X is the adapter you want to run on .... (0 is normally the default display adapter attached to the screen but hard to know without knowing you set-up config, etc).

Didn't get anything on running it passed the "Using GLX_SGIX_pbuffer"

But to be honest I don't think the thing is honoring the sub display number or the driver is still trying for all cores. I used both "export DISPLAY=:0.0" and "fgl_glxgears -display :0.0" and both hang just the same, but if I *remove* the crippled card from the system it runs perfect. I'm guessing it is trying to access everything on bootstrapping and hangs?