Pages:
Author

Topic: DiabloMiner GPU Miner - page 23. (Read 866596 times)

legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 08, 2012, 08:09:48 AM
Question: I have an iMac with a 6750M.  This is what I am getting in diablominer and btcguild.
-w 128 -v 2 or -w 64

After 7-10 minutes it has 1-3 shares, and 5-10 hardware errors.  It was running at 14-20 mhash/s.  Then it will crash the system.  Is there anything I am doing wrong or is it a mac problem?  It is also OSX 10.7 (Lion).





See the op post. You need to also use -na.
member
Activity: 108
Merit: 10
March 08, 2012, 03:45:15 AM
I didnt overclock them alot because they are in standard closed case.
This is just my test box to test stuff on it. I was in cuba for 14 days (no internet there) so im testing all this new drivers and miners now i thought performance would improve but now its like this..

Other rigs are in custom built cases with 4x7970 clocked higher and get around 660 as i do not want temps to exceed 65°C.

Any1 knows whats wrong? Or how do i roll back to old drivers?

Woah dude, 65c is too low. 85c is the standard max safe temp for Radeons that aren't mobile. People have almost hit 800 mhash at full overclock potential.

Still, not sure why you should be having problems. You didn't accidentally install SDK 2.6 on top of 12.2 did you? Also, which 12.2, there are several. Try the new 12.3RC release.

Well I didnt dare to leave them alone running at 85°C for 14 days..
I just downloaded 12.2 from ati.com and installed whole package.

edit: installing 12.3 rc doesnt help
full member
Activity: 149
Merit: 100
March 07, 2012, 11:54:17 PM
Question: I have an iMac with a 6750M.  This is what I am getting in diablominer and btcguild.
-w 128 -v 2 or -w 64

After 7-10 minutes it has 1-3 shares, and 5-10 hardware errors.  It was running at 14-20 mhash/s.  Then it will crash the system.  Is there anything I am doing wrong or is it a mac problem?  It is also OSX 10.7 (Lion).



full member
Activity: 155
Merit: 100
March 07, 2012, 10:25:24 PM
I didnt overclock them alot because they are in standard closed case.
This is just my test box to test stuff on it. I was in cuba for 14 days (no internet there) so im testing all this new drivers and miners now i thought performance would improve but now its like this..

Other rigs are in custom built cases with 4x7970 clocked higher and get around 660 as i do not want temps to exceed 65°C.

Any1 knows whats wrong? Or how do i roll back to old drivers?

Woah dude, 65c is too low. 85c is the standard max safe temp for Radeons that aren't mobile. People have almost hit 800 mhash at full overclock potential.

Still, not sure why you should be having problems. You didn't accidentally install SDK 2.6 on top of 12.2 did you? Also, which 12.2, there are several. Try the new 12.3RC release.

My thoughts exactly!
Unless you are trying to sleep next to your mining rigs, I'd use 85 at your max temp also.
Diablo, I'm curious about why you mentioned installing SDK 2.6. Isn't that the one we should be using for 7970s?
I'm running the 8.96 Feb 28th drivers from guru3d, and am getting 708Mh/s on water at 55c, 1190 core, 850 mem.
Before I installed the water block, I was running at ~675 at 85c, 52% fan, 1125 core (I think), 1000 mem.
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 07, 2012, 07:41:38 PM
I didnt overclock them alot because they are in standard closed case.
This is just my test box to test stuff on it. I was in cuba for 14 days (no internet there) so im testing all this new drivers and miners now i thought performance would improve but now its like this..

Other rigs are in custom built cases with 4x7970 clocked higher and get around 660 as i do not want temps to exceed 65°C.

Any1 knows whats wrong? Or how do i roll back to old drivers?

Woah dude, 65c is too low. 85c is the standard max safe temp for Radeons that aren't mobile. People have almost hit 800 mhash at full overclock potential.

Still, not sure why you should be having problems. You didn't accidentally install SDK 2.6 on top of 12.2 did you? Also, which 12.2, there are several. Try the new 12.3RC release.
member
Activity: 108
Merit: 10
March 07, 2012, 07:37:40 PM
I didnt overclock them alot because they are in standard closed case.
This is just my test box to test stuff on it. I was in cuba for 14 days (no internet there) so im testing all this new drivers and miners now i thought performance would improve but now its like this..

Other rigs are in custom built cases with 4x7970 clocked higher and get around 660 as i do not want temps to exceed 65°C.

Any1 knows whats wrong? Or how do i roll back to old drivers?
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 07, 2012, 07:36:17 PM
Installed catalyst 12.2 and new diablominer and now i get 840MH/s on 2x 7970 instead of 1250 MH/s.. wtf?

I'd also be concerned about why you were only getting ~625 per card before.
I was getting 675-ish, even before I installed my water block.
Sounds like there may be other issues at work...

Well, from what I've heard, on 12.2, people get about 560 at stock clocks. Has this changed?
full member
Activity: 155
Merit: 100
March 07, 2012, 06:58:44 PM
Installed catalyst 12.2 and new diablominer and now i get 840MH/s on 2x 7970 instead of 1250 MH/s.. wtf?

I'd also be concerned about why you were only getting ~625 per card before.
I was getting 675-ish, even before I installed my water block.
Sounds like there may be other issues at work...
member
Activity: 108
Merit: 10
March 07, 2012, 06:36:44 PM
nope.. :/

edit: now i also get same low mh/s on older diablominer which before gave me 1250..
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 07, 2012, 06:34:55 PM
Installed catalyst 12.2 and new diablominer and now i get 840MH/s on 2x 7970 instead of 1250 MH/s.. wtf?

Forgot to turn -na off?
member
Activity: 108
Merit: 10
March 07, 2012, 06:29:18 PM
Installed catalyst 12.2 and new diablominer and now i get 840MH/s on 2x 7970 instead of 1250 MH/s.. wtf?
full member
Activity: 155
Merit: 100
March 06, 2012, 03:03:15 PM
Great, thanks for the clarification!
I'll just leave it on 128 until I see a reason to change then.
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 06, 2012, 02:58:50 PM
On another note, is there any benefit to one work size over another, if the hashrate is the same?
I can run -w 256 or -w 128, and get ~705Mh/s either way. Is there any reason to keep experimenting?

It exists just because some really are faster. If its not for you, just choose the largest (which is 256 on any AMD hardware).

That's what I was wondering, is there any reason to use a larger or smaller work size, apart from any speed differences?
For example, does a small work size reduce the risk of stales? Does a larger work size use less wattage?
I don't think it has anything to do with either of those things, that was just an example of the type of difference it might make.
Why do I feel like I'm not asking this right....?
I guess I'm asking if, apart from hashing speed, work size has any effect on any other part of the total process?

It doesn't change anything outwards. The hardware itself has optimum ways of using work, and even though 4 wavefronts (64*4 = -w 256) is supposed to be always optimum if you have enough registers (at -v 2, we do, higher -vs, not so much although -v 2,1 fits on vliw5 hardware (but not vliw4)).

Its just that for some reason some people are faster on -w 128, and they shouldn't be. They just are. Might as well abuse it while you can.
full member
Activity: 155
Merit: 100
March 06, 2012, 01:59:05 PM
On another note, is there any benefit to one work size over another, if the hashrate is the same?
I can run -w 256 or -w 128, and get ~705Mh/s either way. Is there any reason to keep experimenting?

It exists just because some really are faster. If its not for you, just choose the largest (which is 256 on any AMD hardware).

That's what I was wondering, is there any reason to use a larger or smaller work size, apart from any speed differences?
For example, does a small work size reduce the risk of stales? Does a larger work size use less wattage?
I don't think it has anything to do with either of those things, that was just an example of the type of difference it might make.
Why do I feel like I'm not asking this right....?
I guess I'm asking if, apart from hashing speed, work size has any effect on any other part of the total process?
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 06, 2012, 01:41:43 PM
On another note, is there any benefit to one work size over another, if the hashrate is the same?
I can run -w 256 or -w 128, and get ~705Mh/s either way. Is there any reason to keep experimenting?

It exists just because some really are faster. If its not for you, just choose the largest (which is 256 on any AMD hardware).
full member
Activity: 155
Merit: 100
March 06, 2012, 09:41:57 AM
On another note, is there any benefit to one work size over another, if the hashrate is the same?
I can run -w 256 or -w 128, and get ~705Mh/s either way. Is there any reason to keep experimenting?
full member
Activity: 155
Merit: 100
March 06, 2012, 09:40:47 AM
You only need a -u -p and edit bitcoin.conf if you intend to solo mine.

Aha! I new it was something simple, just could put my finger on it.
I used the flags you suggested, and it works great. FYI, the port is 9333, not 9933. Smiley
I'm now hashing in P2Pool. So far, my payout seems really weak, but I know P2P works a little differently than most pools, with higher personal difficulty and such.
I'll give it a couple days, then go back to Eclipse if it doesn't start paying similarly.
I was getting about 0.3-0.4 BTC per 24 hr on Eclipse, so we'll see....

Thanks for your help and the awesome miner!
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 06, 2012, 03:34:23 AM
Dear OSX users:

Apparently OSX not only requires -w 64 to work, but it also requires -na to work as well.
legendary
Activity: 1162
Merit: 1000
DiabloMiner author
March 06, 2012, 03:12:40 AM
I use P2Pool, but it works fine here. What arguments are you using? Because it should be -o localhost -r 9932, no -u or -p required

Really? The guide I read said I had to put in a user and pwd, and tie it to the bitcoin.conf file.
I'll try it without extra tags and see if that works better.
Thanks!

You only need a -u -p and edit bitcoin.conf if you intend to solo mine.
full member
Activity: 155
Merit: 100
March 05, 2012, 11:08:27 PM
I use P2Pool, but it works fine here. What arguments are you using? Because it should be -o localhost -r 9932, no -u or -p required

Really? The guide I read said I had to put in a user and pwd, and tie it to the bitcoin.conf file.
I'll try it without extra tags and see if that works better.
Thanks!
Pages:
Jump to: