Topic: DiabloMiner GPU Miner - page 10. (Read 866572 times)

I guess it's possible, but if it was going to overheat, wouldn't it have done it during the summer?
My office stays a bit warm (78F+/-) but is pretty constant throughout the year.
AB and GPU-Z report full burn temps of around 74c, but maybe they aren't monitoring the VRMs?

Wow, I wonder if your VRMs are overheating. My 7970 sometimes overheats to the point that the machine hangs on boot at 1125 on really hot days, so maybe thats what happened with you.

Elmojo,

If your card has two BIOSes, switch to non-writable one, boot see if GPU-Z can read it.
Backup that BIOS, switch to read/write BIOS, flash it with backup.  See if this stabilizes your
system.  I've had similar issues, I flashed all my cards with BIOS images from techpowerup.com

I had to switch the BIOS way back when I first got the card. I'm not sure which one it's set on now.
At the time, there were no BIOS images for that card, but I'll look and see if there's anything new.
Do I want a particular BIOS or just any of the ones listed that match my card model and brand?
Which tool is best for flashing the HD7970?

Hey folks, need a little help here.
I'm running Diablo on my 7970 and it's been working great, up until recently.
For background, my card is water cooled, and runs at 1187/850, yielding about 715mH/s on average. It's been super stable, until...
About a week ago, my miner suddenly stopped. I tried restarting it, but it just crashed every time.
I then noticed that Afterburner and GPU-Z were no longer reporting the clocks, they both just said 0.0000.
At this point, I spent several hours trying to reinstall my GPU drivers, which was a nightmare in itself.
I was FINALLY able to get the AMD drivers installed by stripping the old drivers out, sweeping the remnants with Driver Sweeper, and reinstalling the Beta 12.9 drivers.
I tried unstalling 12.8 WHQL, but they wouldn't run any of my miners, just kept giving errors.
At this point, I can mine, but Diablo crashes much more frequently than before. The big problem is that when it does crash, I can't restart it.
When I try, it says something about "no OpenCL devices found". I have to actually reboot the system, at which point it will go back to mining, for a while.
Not sure where to go with this, but it's getting awfully frustrating and is costing me money in lost revenue.
Anyone got any ideas where to start?
Thanks in advance,
Elmojo

DiabloMiner won't switch if the pool is still up. As long as your pool never goes down, you don't have an issue.

-p first,xxx works for most people

DiabloMiner will never support fpga or asic mining unless someone makes raw USB access not suck in Java. If you want that, use cgminer, it's essentially DiabloMiner ported to C.

".. or immediately if connection is refused" ---you mean for example "...cant connect to server.." ? some times some pool have "...cant connect to server.." 20 sec in my test ((

100 minutes was chosen because it is optimal as it is the average length of downtime spent on unplanned maintenance inside of a data center. ----   so i can or not reduce 100min?   for me is very important ((
                  After what time diablo go back to first pool ?

Pools that don't use passwords allow anything in the password field.--- i must use "-p first pas," or "-p first pas" -with comma or not?


will you support "asic mining" in future? I and many people hope , that you will support. Thx for realy good product!

DiabloMiner switches pools after about 15 seconds or immediately if connection is refused.

100 minutes was chosen because it is optimal as it is the average length of downtime spent on unplanned maintenance inside of a data center.

Pools that don't use passwords allow anything in the password field.

Questions about  multipool.

how much time after "there is no answer from first pool" diablo go to the second pool?

"DiabloMiner will automatically return to the first pool every 100 minutes." ----how i can reduce "100 minutes" ?

"-u foo,bar -p baz,quux -o pool1,pool2 -r 3336,3337" ---what if i dont have password on second pool?

Interesting. I'd recommend every OSX user upgrade to Mountain Lion, but GPU mining is kinda dead anyhow now that ASIC is going to blow difficulty up in the next 3-4 months.

Updated my binary to the latest as of today, now getting 345Mh/s

Thats almost as fast as what a 5870 should be without bfi_int, so OSX is slowly catching up to the real world.

Im seeing an increase of about 50mh/s on average going from Lion to Mountain Lion with a stock 5870

Went from 245 (pitiful for a 5870) to 302mh/s

Still not fantastic, but nice on stock for OSX.

Just a heads up I guess.

Roger that

You should always use the newest Catalyst and not install an SDK on top. You're also talking a 1% change, thats the margin of error of measurement from different Catalyst versions.

Hi!

Thanks Diablo for a great miner, I'm using it on windows 7 64-bit and it works great mining with a 6970 and a 5970.

I resently reinstalled windows and went from catalyst 12.3 to 12.6, and notised that my Mhash/s had dropped from 1026 to 1015.

Should I uninstall my SDK, and install a previous version? or go back to catalyst 12.3? Not sure if I have SDK 2.6 or 2.7, all it says is version 10.0.938.1 in catalyst install manager.

The bug is in the proxy, most proxies screw up "long poll" type connections, but you usually see it only in ajax webapps. You can ignore the error, but I suggest you don't use a proxy.

Hello!
I am using DiabloMiner throw the proxy UserGate 2.8.
There is a screenshot of working (working like waves):


Other miners are working throw proxy without problems.
DiabloMiner without proxy works very good.
This is bug? How to solve this problem?

Sorry for my bad english.

This. "." is always in your path in Windows.

You don't need the "./" in windows.