DiabloMiner GPU Miner

[DiabloD3]

DiabloMiner-Linux noob question, sorry if it's been asked, but I couldn't find anything anywhere on this forum or google regarding this error. I downloaded python-jsonrpc and ran setup.py, installed the SDK and drivers, etc, when I run Diablo I get this:

DM isn't written in python.

user@HOST:~/DiabloMiner$ ./DiabloMiner-Linux.sh -u user.worker -p password -o api2.bitcoin.cz -r 8332
[2/23/12 11:12:09 PM] Started                                               
[2/23/12 11:12:09 PM] Connecting to: http://api2.bitcoin.cz:8332/           
[2/23/12 11:12:09 PM] Using AMD Accelerated Parallel Processing OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)

You should be using 2.6 now.

[2/23/12 11:12:09 PM] ERROR: Cannot connect to api2.bitcoin.cz: Bitcoin returned unparsable JSON
[2/23/12 11:12:10 PM] BFI_INT patching enabled, disabling hardware check errors
[2/23/12 11:12:10 PM] Added Turks (#1) (6 CU, local work size of 256)       
[2/23/12 11:12:11 PM] ERROR: Cannot connect to api2.bitcoin.cz: Bitcoin returned unparsable JSON

Did I screw up and forget to install something important?

Hrm, dunno. It shouldn't do that. I wonder if slush screwed something up with his pool.

[ShadesOfMarble]

How many hw errors are ok for a 7970? I currently have 0,17% (52/29410) hw errors, card running overclocked (1125 Mhz) and undervolted (1100 mV).
Everything running stable for >2 days now.

Significant errors like that is insane.  Set stock clocks and volts and see if it still does it, if it does its a driver bug, if it doesn't, you overclocked too far. You shouldn't see more than 1 or 2 HW errors per 10k shares give or take, if it starts skyrocketing you went too far.

With stock clock/voltage I now have 10/1738 hw errors... so still way too much. What does this mean now? I'm using the latest driver (12.2 pre-cert), latest DM, Windows 7 32-bit.

Can I ignore the hw errors and just live with a higher reject rate or is there something I should/can/must do?

[DiabloD3]

How many hw errors are ok for a 7970? I currently have 0,17% (52/29410) hw errors, card running overclocked (1125 Mhz) and undervolted (1100 mV).
Everything running stable for >2 days now.

Significant errors like that is insane.  Set stock clocks and volts and see if it still does it, if it does its a driver bug, if it doesn't, you overclocked too far. You shouldn't see more than 1 or 2 HW errors per 10k shares give or take, if it starts skyrocketing you went too far.

With stock clock/voltage I now have 10/1738 hw errors... so still way too much. What does this mean now? I'm using the latest driver (12.2 pre-cert), latest DM, Windows 7 32-bit.

Can I ignore the hw errors and just live with a higher reject rate or is there something I should/can/must do?

What GPU temp?

[ShadesOfMarble]

Between 80-85°C

[Joshwaa]

Between 80-85°C

There is something wrong with your card or you do not have adequate cooling. Mine never go over 74C and Im clocked higher than you. Are you controlling your fan or are you leaving it to the card to control?

[ShadesOfMarble]

I have 4 cards installed in an open case, so there is not much room to breathe
I'm on manual fan control because on auto the temp goes all the way up to 90°C...

[Joshwaa]

I have 4 cards installed in an open case, so there is not much room to breathe
I'm on manual fan control because on auto the temp goes all the way up to 90°C...

Do you have some 120 fans you could help feed the cards with? What case is it?

[ShadesOfMarble]

Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors...
(I have to drive to the remote location and spend much time I need somewhere else...)

One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story

Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?!

[Joshwaa]

Temp along with voltage would be my guess. unless you ASIC quality is above 68% your volts are too low for that clock and that will give you plenty of HW errors. What is your quality on your cards?

[ShadesOfMarble]

Temp along with voltage would be my guess. unless you ASIC quality is above 68% your volts are too low for that clock and that will give you plenty of HW errors.

I'm running stock settings now and still getting hw errors

What is your quality on your cards?

Sorry, can't say atm. Last time I started GPU-Z crashed the machine and I had to drive to the remote location and reset it :/

[Elmojo]

Temp along with voltage would be my guess. unless you ASIC quality is above 68% your volts are too low for that clock and that will give you plenty of HW errors. What is your quality on your cards?

Mine is 81.7%, which I gather is good?
I was getting a few HW errors last night, until I raised the voltage a bit from .965v to 1.00v

[Joshwaa]

Temp along with voltage would be my guess. unless you ASIC quality is above 68% your volts are too low for that clock and that will give you plenty of HW errors.

I'm running stock settings now and still getting hw errors

What is your quality on your cards?

Sorry, can't say atm. Last time I started GPU-Z crashed the machine and I had to drive to the remote location and reset it :/

Ok if your at stock and still getting errors I would go to safe mode remove all drivers. Do not let windows install drivers for you. then run the 12.2 pre installation. Maybe even update your java.
That would be a good place to start.

[Joshwaa]

Temp along with voltage would be my guess. unless you ASIC quality is above 68% your volts are too low for that clock and that will give you plenty of HW errors. What is your quality on your cards?

Mine is 81.7%, which I gather is good?
I was getting a few HW errors last night, until I raised the voltage a bit from .965v to 1.00v

Anything over 75 is good IMO. My cards run 1.012v (1.505v mem you can turn it down in AB not good if gaming though) 1160gpu/1000mem one is 79.8 and other is 80.7%. I am happy. I have not seen any 90% cards yet out of the 6 I have.

[DiabloD3]

Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors...
(I have to drive to the remote location and spend much time I need somewhere else...)

One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story

Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?!

Its not. 85c is the maximum safe limit for 24/7 mining, the cards can survive up to 120c for short periods of time without damage.

What arguments are you using? None and/or just -v 1 -w 256?

[someone703]

Read somewhere that you can game while using Diablo miner in the background.

Do games run smoothly as if you weren't actually mining (ie. only using spare clock cycles on mining or something to that effect)?  Or will there be some noticeable degradation in gaming performance?

Also, apparently all optimizations are for SDK2.6 only now.  Will I be getting the kind of hash rates using Diablo + SDK2.6 that I would with CGMiner + SDK2.1?

From OP:

SDK 2.4 supports everything 2.1 does, plus:
Any 6xxx-like VLIW5 (aka Barts): 6790, 68xx, 69xxM
Any 6xxx-like VLIW4 (aka Caicos, Turks, Cayman): 64xx, 65xx, 66xx, 69xx, 64xxM, 66xxM, 67xxM
Any Fusion APU VLIW5 (aka Wrestler, WinterPark): 62xx, 63xx, 64xx

SDK 2.6 supports everything 2.4 does, plus:
79xx GCN

[ShadesOfMarble]

Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors...
(I have to drive to the remote location and spend much time I need somewhere else...)

One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story

Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?!

Its not. 85c is the maximum safe limit for 24/7 mining, the cards can survive up to 120c for short periods of time without damage.

What arguments are you using? None and/or just -v 1 -w 256?

I'm using -v1 -w256. Also note this is a "mixed" setup (5xxx, 6xxx and 7970) so I have to run two instances of DM. I don't know if this is relevant, but the 2nd instance is causing 50% load on a dualcore (affinity set to both cores, so it does not look like the "classic" cpu-bug)

[tinman951]

Read somewhere that you can game while using Diablo miner in the background.

Do games run smoothly as if you weren't actually mining (ie. only using spare clock cycles on mining or something to that effect)?  Or will there be some noticeable degradation in gaming performance?

Also, apparently all optimizations are for SDK2.6 only now.  Will I be getting the kind of hash rates using Diablo + SDK2.6 that I would with CGMiner + SDK2.1?

I have run Battlefied 3 while mining with one 5770 clocked at 900Mhz.  Usually I get ~195mhash/s but I can still get about 80Mh/s with BF3 running at "high" on game settings.
Also using AMD 965 3.4Ghz, but not for mining.

[DiabloD3]

Read somewhere that you can game while using Diablo miner in the background.

Do games run smoothly as if you weren't actually mining (ie. only using spare clock cycles on mining or something to that effect)?  Or will there be some noticeable degradation in gaming performance?

Also, apparently all optimizations are for SDK2.6 only now.  Will I be getting the kind of hash rates using Diablo + SDK2.6 that I would with CGMiner + SDK2.1?

From OP:

SDK 2.4 supports everything 2.1 does, plus:
Any 6xxx-like VLIW5 (aka Barts): 6790, 68xx, 69xxM
Any 6xxx-like VLIW4 (aka Caicos, Turks, Cayman): 64xx, 65xx, 66xx, 69xx, 64xxM, 66xxM, 67xxM
Any Fusion APU VLIW5 (aka Wrestler, WinterPark): 62xx, 63xx, 64xx

SDK 2.6 supports everything 2.4 does, plus:
79xx GCN

You shouldn't mine in the background, drivers still do not have any sort of priority system. Even setting like -f 1000 will still cause slower games and destroy your hashrate in the process.

cgminer now ships with my kernel, so if you're using my kernel on cgminer (it supports several) you should still use 2.6. My old kernel on 2.1 vs my new kernel on 2.6 is basically tied for speed on VLIW5, faster vs 2.5 on VLIW5 and VLIW6, and faster on GCN.

[DiabloD3]

Thanks guys, but I don't have much motivation to lower the temps unless that's the reason for the hw errors...
(I have to drive to the remote location and spend much time I need somewhere else...)

One of my rigs has a 230mm fan blowing on the cards from the side, maybe I'll get another one and put it in my second rig, but as I said, all this stuff costs time. My mining operation already is consuming much of it in the last weeks, because fans began to fail and I had to issue some RMAs... different story

Card is running @ 74°C now and still getting hw errors (4/800)... I'm not really convinced that temperature is my problem, is it?!

Its not. 85c is the maximum safe limit for 24/7 mining, the cards can survive up to 120c for short periods of time without damage.

What arguments are you using? None and/or just -v 1 -w 256?

I'm using -v1 -w256. Also note this is a "mixed" setup (5xxx, 6xxx and 7970) so I have to run two instances of DM. I don't know if this is relevant, but the 2nd instance is causing 50% load on a dualcore (affinity set to both cores, so it does not look like the "classic" cpu-bug)

Huh, I wonder if its an obscure driver bug. Almost no one runs DM more than once. Try just running once instance instead, the one for the 7970 only.

[ShadesOfMarble]

Ok, running one instance with -v1 -w256 now.

Interestingly performance isn't much worse (was 1626 mh/s with two instances, one with -v1 -w256 for gcn and one with -v2 -w128 for vliw), now with one instance I get 1604 mh/s...

CPU usage is still strange, though: 50% on a dualcore, affinity set to *both* cores. If I would run into the classic cpu bug, it should consume 100% of the cpu, right?!

And as I wrote this, TDR triggered on one of the 5850... ouch. Can this be caused by different vector/worksize settings? (Never used -v1 -w256 on the 5850 before)