Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 660. (Read 5806103 times)

hero member
Activity: 1162
Merit: 500
So what's the damage? Well on the 7970 at 1200/1050 clocks, which was getting 694MHash, it's now getting 711Mhash. The 7970 has this unusual behaviour where the hashrate slowly rises for the first 5-10 minutes.

Besides "-k poclbm", which other command line options do I have to use to get optimal results on the 7970?
hero member
Activity: 518
Merit: 500
Quote from: TheHarbinger
950/180  Do the math.

It doesnt work out to a nice round number. But I just tried.
5870 @ 950/300 : 432.4
5870 @ 950/180 : ~441-442
5870 @ 950/170 : ~442

Not a quantum leap, but still quite a nice boost!

So I tried another 5870 that runs at 1 GHz applying the same memory clock and same ratio and a few other speeds:

5870 @1000/300: 454.7
5870 @1000/200: ~459
5870 @1000/190: ~460
5870 @1000/180: ~460
5870 @1000/150: ~454

Smaller boost than at 950. Not too sure what to make of it, but there is nothing wrong with getting a few extra MH while consuming less power Smiley

Note these results were obtained testing just a few minutes on each setting, dont take it as gospel


legendary
Activity: 3586
Merit: 1099
Think for yourself
Maybe nobody cares, but I should notice anyway.
Version 2.0.8 (win32) is last that works fast and effective. My 5850 gives 350 MH/s and I'm happy with the speed. All later versions (I tried every one of them) under the same conditions (cmdline options are the same) give just 308 MH/s
Any ideas?

Yes, you upgraded your video drivers. Thats the root cause. The reason your old copy of cgminer still works faster, is because it contains a cached/compiled copy of the .BIN file generated with your old drivers and sdk. If you were to reinstall 2.0.8 you will likely get the same lousy hashrate.

See here:
https://bitcointalksearch.org/topic/help-with-cgminer-and-5870s2-btc-bounty-solved-63383

Thanks! You saved my brain from explosion)

So, if the description is accurate you should be able to copy the .bin files from your fast 2.0.8 to the current version and get the higher hash rate.
Sam
newbie
Activity: 78
Merit: 0
i finally went back to my parents house and pluged a display to my ubuntu machine (the one i updated from 10.04 to 10.11 using ssh, in order to be able to use cgminer instead of phoenix, and ended up with a non working rig Tongue )

The problem was that the latest drivers, at least with the 2.4 sdk, cause some error / segmentation fault.

I thought that was because i was running with ssh -X, but that was not the case.

I then installed the latest one from synaptic (older than the newst one from AMD website) and all was fine.

ps: i updated to the latest from whatever i was using on 10.04, because the ones from 10.04 were not installable on 10.11 (they were some older drivers).

Also, upgrading had disabled the autologin, but i had no way of knowing that xD
sr. member
Activity: 378
Merit: 250
Why is it so damn hot in here?
Yeah would be good if we knew that magical memory clock / core clock ratio for 5870s !

950/180  Do the math.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Nice, I tried this poclbm kernel but it crashes cgminer on startup for me. I have two 7970s and a 6950 in my system though.
There's a problem with multiple different kernels running in the current cgminer release. This will be fixed on the next release.
hero member
Activity: 556
Merit: 500
Working on the 7970 tuning, I have tried to port both the diapolo and diablo kernels to cgminer. Alas neither of them are actually working yet, so instead I started modifying the existing poclbm kernel in cgminer to improve throughput. This should work on other GPUs as well as the 7970, but I have no idea if it's better or worse than phatk.

When it's released it will get a new date/version number, but I haven't changed the number right now so that people can download it now and give it a try:
https://raw.github.com/ckolivas/cgminer/kernels/poclbm120203.cl

Remember to delete any .bin files and if you're not on a 7970 with the latest cgminer, you'll have to tell it to use that kernel with -k poclbm.

So what's the damage? Well on the 7970 at 1200/1050 clocks, which was getting 694MHash, it's now getting 711Mhash. The 7970 has this unusual behaviour where the hashrate slowly rises for the first 5-10 minutes.

Nice, I tried this poclbm kernel but it crashes cgminer on startup for me. I have two 7970s and a 6950 in my system though.
hero member
Activity: 560
Merit: 500
I have just switched to CGminer and have 3 of my 4 cards running at their usual speed ~360 MH/s but the card with the monitor connected is getting 260 MH/s

I tried using the "-I 9,9,9,9" intensity setting but nothing changes.

Anyone have any hints? They were all running at 360 MH/s in GUI miner until the bug hit.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
My signal to noise ratio is extremely low with messages coming from everywhere and forum questions and so on, so I'm going to once more stop replying to anything that other people can answer. Thanks to the others who contribute to this thread.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
If that came from anyone else I would have laughed at it.

I heard people posting about it before and myself have found the same but the Mhash/s gains and temp drops are usually (at least to me) too negligible to pay too much attention to it.
On a 6970 it was 20 Mhash.

20 MHash/s over worst possible ratio of mem:core or over settings of an overclocked and tweaked card?
Sorry it was at 960, not 920.
Watching the trend in hashrate rise as I increased engine clock speed, I noticed a larger-than expected rise at 955 and then it peaked at 960. The hashrate was 20 higher there than I would have expected. Even though one of the cards goes as high as 985, it was faster at 960 than at 985 so I left it at 960 where it ran cooler and faster. It was only the other card that got to 990 when it started exceeding the values at 960.
hero member
Activity: 518
Merit: 500
Yeah would be good if we knew that magical memory clock / core clock ratio for 5870s !
member
Activity: 71
Merit: 10
Maybe nobody cares, but I should notice anyway.
Version 2.0.8 (win32) is last that works fast and effective. My 5850 gives 350 MH/s and I'm happy with the speed. All later versions (I tried every one of them) under the same conditions (cmdline options are the same) give just 308 MH/s
Any ideas?

Yes, you upgraded your video drivers. Thats the root cause. The reason your old copy of cgminer still works faster, is because it contains a cached/compiled copy of the .BIN file generated with your old drivers and sdk. If you were to reinstall 2.0.8 you will likely get the same lousy hashrate.

See here:
https://bitcointalksearch.org/topic/help-with-cgminer-and-5870s2-btc-bounty-solved-63383

Thanks! You saved my brain from explosion)
legendary
Activity: 3472
Merit: 1727
If that came from anyone else I would have laughed at it.

I heard people posting about it before and myself have found the same but the Mhash/s gains and temp drops are usually (at least to me) too negligible to pay too much attention to it.
On a 6970 it was 20 Mhash.

20 MHash/s over worst possible ratio of mem:core or over settings of an overclocked and tweaked card?
legendary
Activity: 3586
Merit: 1099
Think for yourself
OK, so I take it that I can no longer copy the .bin files from previous versions of CGMiner?
I can't get 2.2.3 to generate them.
Sam
Change the datestamp on your old bins to the new dates. That will do it. One day, just one day, I'd like for that fucking failed to build bug to go away. Maybe next release!  Roll Eyes

That worked.

I keep hoping it will go away sometime too.  While I was messing with this I found that the .bin files I've been using aren't from the 2.0.0 build but from 1.6.2.  Don't know if that matters or not at this point.
Thanks,
Sam
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
If that came from anyone else I would have laughed at it.

I heard people posting about it before and myself have found the same but the Mhash/s gains and temp drops are usually (at least to me) too negligible to pay too much attention to it.
On a 6970 it was 20 Mhash.
legendary
Activity: 3472
Merit: 1727
If that came from anyone else I would have laughed at it.

I heard people posting about it before and myself have found the same but the Mhash/s gains and temp drops are usually (at least to me) too negligible to pay too much attention to it.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Note that there are "sweet spots" in hash rate. After you've found the top speed, try going down by 5 at a time. Sometimes you'll find a magic Mhz where it suddenly jumps up.

If that came from anyone else I would have laughed at it. But since its you, Ill have to believe it, but is it not more likely the reason is not so much the clockspeed as such, as the ratio between GPU and memory clock? IOW, rather than reducing your GPU clock, perhaps try increasing the memory clock a little bit?
Indeed, but there is a -125 or -150 difference limit and we're trying to run memory as low as possible. So the equation works out best in energy terms at the lower memory clock where you hit the right ratio difference between mem and engine, wherever that is.
hero member
Activity: 518
Merit: 500
Note that there are "sweet spots" in hash rate. After you've found the top speed, try going down by 5 at a time. Sometimes you'll find a magic Mhz where it suddenly jumps up.

If that came from anyone else I would have laughed at it. But since its you, Ill have to believe it, but is it not more likely the reason is not so much the clockspeed as such, as the ratio between GPU and memory clock? IOW, rather than reducing your GPU clock, perhaps try increasing the memory clock a little bit?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
So what's the damage? Well on the 7970 at 1200/1050 clocks, which was getting 694MHash, it's now getting 711Mhash. The 7970 has this unusual behaviour where the hashrate slowly rises for the first 5-10 minutes.
Beautiful.  I'm running this on 2 of my boxes and seeing substantial increases.  I'm getting about a 3.3% increase on the overclocked box.  What's really weird is that I saw a 6.5% increase on the box that's only overclocked by 75 mhz.  Heh.  Weird.  I'll take it though.
After an overnight run:
GPU 0:  73.0C 4743RPM | 708.1/706.7Mh/s | A:4454 R:7 HW:0 U: 9.83/m I:11
So I'll call the actual rate 707

Note that there are "sweet spots" in hash rate. After you've found the top speed, try going down by 5 at a time. Sometimes you'll find a magic Mhz where it suddenly jumps up. That happened at 920 on my 6970s for example. Maybe that's what you're experiencing.
hero member
Activity: 642
Merit: 500
So what's the damage? Well on the 7970 at 1200/1050 clocks, which was getting 694MHash, it's now getting 711Mhash. The 7970 has this unusual behaviour where the hashrate slowly rises for the first 5-10 minutes.
Beautiful.  I'm running this on 2 of my boxes and seeing substantial increases.  I'm getting about a 3.3% increase on the overclocked box.  What's really weird is that I saw a 6.5% increase on the box that's only overclocked by 75 mhz.  Heh.  Weird.  I'll take it though.
Jump to: