OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

Theoretically it should even fix card ordering of any sort, not just dual GPUs that are split up:


Here it is completely untested... so please test it  
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

EDIT: tested, doesn't work. Hold on...

Just use as per normal.

[JWU42]

CK - worth a git pull to test on linux machines as well?

None of mine are dual 5970 currently but that will soon change 

[-ck]

I haven't pushed it to the git tree. I have no idea if it works at all... since I don't even have a GPU that can mine at the moment still 

Ok I've added a git branch called "reorder". If you git pull and then "git checkout reorder" you can try it.

[-ck]

On further inspection this code won't work...

Back to the drawing board. 

[cablepair]

excuse me for being lazy but I keep seeing a lot of talk about 5970 , ive been too busy to keep up with the conversation - but if someone could tell me whats going on in respect  the 5970 development I would really appreciate it

my 5970 gets 380 mhash per core in windows 7 with the ccc 11.8

is it possible to do better?

thanks in advance for filling me in!

[Red Emerald]

excuse me for being lazy but I keep seeing a lot of talk about 5970 , ive been too busy to keep up with the conversation - but if someone could tell me whats going on in respect  the 5970 development I would really appreciate it

my 5970 gets 380 mhash per core in windows 7 with the ccc 11.8

is it possible to do better?

thanks in advance for filling me in!

Same hashrates as you except I am mining on linux. (My U is a little less than expected because I have p2pool as my secondary pool)

Code:

GPU 0:  72.5C 4349RPM | 380.7/379.8Mh/s | A:4693 R:243 HW:0 U: 5.01/m I: 8
GPU 1:  68.5C         | 377.9/377.6Mh/s | A:4644 R:241 HW:0 U: 4.95/m I: 8

[sveetsnelda]

Good news and bad news, ckolivas:

All of my previous 7970 testing was getting bottlenecked by CPU usage.  This is the reason why the hashrate fluctuated so heavily.  I enabled the other 2 cores on this rig and I'm getting much better results.  I usually leave 2 cores disabled and undervolt the CPU to save power.

Now that the other 2 cores are enabled, I can get around 633Mhash/sec with the poclbm kernel and the same clocks used in the other testing.  I say "around 630Mhash/sec" because the hash rate bounces around quite a bit due to the CPU still being bottlenecked.  If I only run CGMiner against 1 card, the hash rate starts around 610Mhash, gradually increases to 633, falls down again, etc etc.  Running CGMiner like this averaged 612Mhash/sec over 5 minutes.

I'll toy around with Phatk and the modified version you posted, and then report back.

[sveetsnelda]

(I had to use 13 for intensity to get this, BTW)

[sveetsnelda]

Turning intensity down to 9 makes CPU usage sink to almost nothing.  Increasing it to 10 (or above) completely saturates 1 core...

[DeathAndTaxes]

Turning intensity down to 9 makes CPU usage sink to almost nothing.  Increasing it to 10 (or above) completely saturates 1 core...

That was covered in the readme.  Simple solution use intensity 9 (or possibly .

[jjiimm_64]

Turning intensity down to 9 makes CPU usage sink to almost nothing.  Increasing it to 10 (or above) completely saturates 1 core...

That was covered in the readme.  Simple solution use intensity 9 (or possibly .

tru, but doesn't 79xx like the 10 ?  

I am about to try the poclbm for the first time with the 79....

edit:   YAAAAAHHHH

Code:

GPU 0:	70.0C	1763RPM 	31% | 	526.1/519.4Mh/s | 	1025Mhz 	1.17V 	A:24	R:0	HW:0	U:5.48/m 	I: 7
GPU 1:	67.0C	1448RPM 	25% | 	526.2/519.7Mh/s | 	1025Mhz 	1.17V 	A:33	R:1	HW:0	U:7.54/m 	I: 7
GPU 2:	68.0C	1332RPM 	25% | 	526.2/519.7Mh/s | 	1025Mhz 	1.17V 	A:35	R:2	HW:0	U:8.00/m 	I: 7
GPU 3:	72.0C	1763RPM 	33% | 	526.3/519.8Mh/s | 	1025Mhz 	1.17V 	A:25	R:1	HW:0	U:5.71/m 	I: 7

edit2:  looks like I need to add mem now to the webmon

[sveetsnelda]

That was covered in the readme.  Simple solution use intensity 9 (or possibly .

Pff.  Do you think I read manuals?     Yeah, I never saw that.  The problem is that the hash rate on the 7970s seem to still increase significantly when you turn the intensity above 9.  Other cards barely budge.

[jjiimm_64]

That was covered in the readme.  Simple solution use intensity 9 (or possibly .

Pff.  Do you think I read manuals?    Yeah, I never saw that.  The problem is that the hash rate on the 7970s seem to still increase significantly when you turn the intensity above 9.  Other cards barely budge.

do I have to get older bin files to get the hashrate your getting ?

I have never used poclbm before, so I dont have any  

GPU 1:   54.0C   3188RPM    50% |    557.5/559.0Mh/s |    1100Mhz    1020Mhz    1.17V    A:21   R:0   HW:0   U:7.15/m    I: 9


edit:  I set one of the cards to 10, getting only 1 Mh more then the 9's.

btw,  gpu-vddc did not change the voltage on the card.  were you able to change voltage.?  and please someone answer the 'older bin' question?

[-ck]

Okay, here is the first windows executable with PCI bus based reordering of GPU devices. Put it into an existing 2.1.2 installation.

Please test it out to see if it works and what it does to your advertised card order!

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Linux build works from "reorder" branch on git.

[freakfantom]

Okay, here is the first windows executable with PCI bus based reordering of GPU devices. Put it into an existing 2.1.2 installation.

Please test it out to see if it works and what it does to your advertised card order!

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Yes, it works fine on windows x64 3x6990. It seems to me the order of gpus is reversed, but I don't have any proof Just want to confirm that new exe is working.

[kano]

That was covered in the readme.  Simple solution use intensity 9 (or possibly .

Pff.  Do you think I read manuals?    Yeah, I never saw that.  The problem is that the hash rate on the 7970s seem to still increase significantly when you turn the intensity above 9.  Other cards barely budge.

do I have to get older bin files to get the hashrate your getting ?

I have never used poclbm before, so I dont have any  

GPU 1:   54.0C   3188RPM    50% |    557.5/559.0Mh/s |    1100Mhz    1020Mhz    1.17V    A:21   R:0   HW:0   U:7.15/m    I: 9


edit:  I set one of the cards to 10, getting only 1 Mh more then the 9's.

btw,  gpu-vddc did not change the voltage on the card.  were you able to change voltage.?  and please someone answer the 'older bin' question?

The bin files will of course be related to the opencl version you were running at the time the bin file was generated.
So it's not really older or newer, the performance figures anyone quotes will also be directly related to the opencl version they were using to generate the bin.

[-ck]

Okay, here is the first windows executable with PCI bus based reordering of GPU devices. Put it into an existing 2.1.2 installation.

Please test it out to see if it works and what it does to your advertised card order!

http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Yes, it works fine on windows x64 3x6990. It seems to me the order of gpus is reversed, but I don't have any proof Just want to confirm that new exe is working.

Thanks very much. Yes the order will often be reversed due to mobo+os+drivr discrepancies.. The order should now most accurately represent what is happening physically with the cards.

[The00Dustin]

I'm not using cgminer with any nvidia cards, but if it is supposed to support them, you might want to do this in your next update:

I have not tested Ufasoft or cgminer, but there's no problem with Phoenix.
(using Nvidia driver 285.62 with Win 7 64Bit)

Edit: Ufasoft 64Bit doesn't see the graphics card, 32Bit is working fine.

Fixed, please redownload Windows binary.

Really it seems a bug in CUDA. by some reason x64 CUDA incorrectly interprets following construct:

Code:

__constant uint L = 0x98c7e2a2;

Replaced to :

Code:

__constant uint L[1] = { 0x98c7e2a2 };

And it works now!

Note that a few pots up someone points out that that nvidia driver version breaks it in cgminer as well, implying that it is supposed to support them, and I don't know if this is Win only or not.

[BCMan]

 It's possible to set additional phatk2 commands like PLATFORM=1 BFI_INT WORKSIZE=256 AGGRESSION=12 FASTLOOP=False, etc? I lose performance without them , with Phoenix I've 223 mhash/s, with cgminer - 216 mhash/s.

[jake262144]

Of course it is.
Add those to your config file:

Code:

"intensity" : "9,9,8,9",
"vectors" : "2",
"worksize" : "64",

Intensity is the same as Aggression in phoenix nomanclature. With cgminer you are use a per-card value as shown in the example code. Don't use values hight than 9 unless using a 7970 card.
You don't need to specify BFI_INT, it's on by default.

Also, RTFM - that info is in the readme file and in the very first post of this thread.