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

[btc_artist]

Con, thanks for the hard work on the 5970/fan issue.

Also, the new API commands look awesome.  I have a slick web interface for displaying information (with the previous API), now I'll plan to expand it to take advantage of the new API commands.  Once it's ready, I'll share it with everyone.

[1714834985]

1714834985

[1714834985]

1714834985

[-ck]

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

[Roadhog2k5]

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

Pretty slow at stock settings. 390mh/s about, and it's not producing valid shares.

[-ck]

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

Pretty slow at stock settings. 390mh/s about, and it's not producing valid shares.

I hope you deleted any .bins first. That means it's not working at all then. Oh well guess I wait till I get one myself to figure out wtf is wrong.

[Roadhog2k5]

I committed a little more 79x0 specific code and built a windows binary. Again, no idea if it works, nor if it performs, but here is a windows build:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Just drop it into a 2.1.2 directory, replacing the existing exe.

Pretty slow at stock settings. 390mh/s about, and it's not producing valid shares.

I hope you deleted any .bins first. That means it's not working at all then. Oh well guess I wait till I get one myself to figure out wtf is wrong.

Yeah, I downloaded the fresh 2.1.2 and unpacked it to its own directory. Then I just put the EXE in you posted. Any specific settings you want me to try?

[-ck]

Yeah, I downloaded the fresh 2.1.2 and unpacked it to its own directory. Then I just put the EXE in you posted. Any specific settings you want me to try?

Try combinations manually with other vectors and worksize, -v 1, -v 2, -v 4, -w 64 -w 128 , -w 256
But if it fails by default there's a good change it's simply broken for now.

Oh and start it with -D -T and post output please?

[Roadhog2k5]

Yeah, I downloaded the fresh 2.1.2 and unpacked it to its own directory. Then I just put the EXE in you posted. Any specific settings you want me to try?

Try combinations manually with other vectors and worksize, -v 1, -v 2, -v 4, -w 64 -w 128 , -w 256
But if it fails by default there's a good change it's simply broken for now.

Oh and start it with -D -T and post output please?

I tried the vectors, -v 2, and -v 4, result in <100mh/s speeds. -w doesn't seem to affect the speed any.

Here is -D -T
http://pastebin.com/pNYkeAHh

[sveetsnelda]

I'm getting some pretty weird results.  Here is some food for thought.  Keep in mind I'm running these at 1075Mhz:

I get about 440 per GPU if I make sure to specify the poclbm kernel, --vectors 1, and a worksize of 256.  Here's the odd thing though -- the only way to get this is to have the intensity maxed at 10.  If I use 9, the hash rate drops by over 100Mhash/sec.

Here's where it gets even more weird.  If I move the mouse all over the place or move a window all over the place to make the GPU a little more busy, hashrate goes *up*.  I get about 495 per GPU and can get them to bump past 500 for short periods of time.

To top it off...?  After doing this, the hashrate doesn't go back down when I stop screwing with the GUI.  It stays steady.  There's some sort of throttling going on and I'm guessing CGMiner isn't keeping the cards busy enough.  Is it possible to make the intensity even more aggressive and see if this makes a difference?

[sveetsnelda]

Also, I'm not sure why Roadhog isn't getting valid shares.  Mine are.

[-ck]

Interesting. Redownload the .exe, I've made a few minor changes and now you can increase intensity to 14. The other thing to try is increase the threads from 2 to 3 or more with -g 3

oops hang on, intensity doesnt work yet, but try -g 3

Now it should work (redownload exe).

[jjiimm_64]

I'm getting some pretty weird results.  Here is some food for thought.  Keep in mind I'm running these at 1075Mhz:

I get about 440 per GPU if I make sure to specify the poclbm kernel, --vectors 1, and a worksize of 256.  Here's the odd thing though -- the only way to get this is to have the intensity maxed at 10.  If I use 9, the hash rate drops by over 100Mhash/sec.

Here's where it gets even more weird.  If I move the mouse all over the place or move a window all over the place to make the GPU a little more busy, hashrate goes *up*.  I get about 495 per GPU and can get them to bump past 500 for short periods of time.

To top it off...?  After doing this, the hashrate doesn't go back down when I stop screwing with the GUI.  It stays steady.  There's some sort of throttling going on and I'm guessing CGMiner isn't keeping the cards busy enough.  Is it possible to make the intensity even more aggressive and see if this makes a difference?

How about trying more threads?  I haven't downloaded yet

[sveetsnelda]

Interesting. Redownload the .exe, I've made a few minor changes and now you can increase intensity to 14. The other thing to try is increase the threads from 2 to 3 or more with -g 3

Increasing the thread count to 3 definitely smooths out the hashrate, but it doesn't increase it.

I just thought of something else.  I haven't seen anyone else mention it yet, but I noticed when I'm using Diablominer and I run Afterburner, my hash rate slows down dramatically until I close it.  It's like the hardware polling that Afterburner does actually interrupts the GPU.  Is there a way to turn off ADL polling?  Edit:  Why yes -- there is.

Intensity still seemed to be capped at 10 on that binary (unless it lets you change it but doesn't show the change?)

If it were intensity related, I'm sure adding more threads would have cleared it up though.     Probably no need to recompile again to test it.

Another thing that is odd is the hash rate (not the long average) seems to increase very slowly with time before capping.  In other words, I run cgminer and get anywhere from 400 to 430 per card.  Once I let it run for a good 5 minutes or so, they eventually get up to around 460 and stop rising.  It takes ages to get there though.

Lastly, the GPUs tend to all hash at significantly different rates until cgminer has run for a long enough period of time.  There are 4 GPUs in this rig and they'll differ by 10 percent or so between cards until it has run a while.

[sveetsnelda]

I tried running with --no-adl and there was little to no change.  Bah.  I thought that would be it.

[sveetsnelda]

Unrelated -- I tried to compile cgminer in Windows last night.  You weren't kidding.  Pain in the ass.  I finally got everything to configure and almost everything complied, and then I ran into some screwy incompatibilities between the Windows SDK Winsock includes and the Winsock includes supplied by MinGW.  It was a brutal night.  Props for getting the thing to run in Windows in the first place without a substantial rewrite. 

[-ck]

Thanks. By the way, I reuploaded the exe after that first message so perhaps you got the dud build. Please try re-downloading it.

Increasing threads is nothing like increasing intensity so it will not have the same effect.

Finally, we are never going to get there with the poclbm kernel. The one it is loading is ancient and numerous improvements have happened since then, most of which are in the phatk kernel. Unless I can get the existing phatk kernel working it's going to be nigh on useless trying to mine on 79x0 until I can create an entirely new kernel...

[sveetsnelda]

Ah.  Gotcha.  I'll give it another go.

I see.  I just assumed if a GPU wasn't at full utilization, a 2nd thread would be able to chew up the unused cycles.  I've never written anything for OpenCL though, so I certainly don't claim to fully understand it.

Well, in that case, there's another thing to sort out that doesn't make any damn sense (of course).  The phatk kernel doesn't always run on GPU0.  It's fairly random.  It always runs on the other 3 cards every time.  CGMiner pauses with a message about closing other apps that use the GPU (like Afterburner).  If I close CGMiner and restart it with the same command line, it'll run.  It's probably 50/50.  The poclbcm kernel seems to always compile/run.

Also, all shares created with the phatk kernel are invalid and just get marked as hardware errors.

[sveetsnelda]

Starting CGMiner with 14 intensity (with poclbm) causes all of the cards to start at just above 500Mhash/sec and slowly creep down to around 420Mhash.  It seems to have no effect when using the phatk kernel.

[-ck]

Ah.  Gotcha.  I'll give it another go.Well, in that case, there's another thing to sort out that doesn't make any damn sense (of course).  The phatk kernel doesn't always run on GPU0.  It's fairly random.  It always runs on the other 3 cards every time.  CGMiner pauses with a message about closing other apps that use the GPU (like Afterburner).  If I close CGMiner and restart it with the same command line, it'll run.  It's probably 50/50.  

Yes this is the never ending mindfuck that is windows creating a binary that reports size zero after it's built. Then it changes its mind and works the next time around. It's a bug that's plagued cgminer on windows for 6 months now and makes no sense whatsoever to anyone.

[-ck]

Further investigation reveals the phatk kernel included with the current cgminer basically ONLY works with the  bfi int patching. That means the kernel itself needs fixing to even work in its current intended form, so there's still some work to go... However for those brave, at least you have an exe you can use with the kernel and you can delete the .bin files and manually fiddle with the code in the phatk*.cl file included. Other kernels taken from other projects diablo, diapolo, phoenix etc will NOT under ANY circumstances work directly as the API is different so don't waste your time trying that.

[kano]

Further investigation reveals the phatk kernel included with the current cgminer basically ONLY works with the  bfi int patching. That means the kernel itself needs fixing to even work in its current intended form, so there's still some work to go... However for those brave, at least you have an exe you can use with the kernel and you can delete the .bin files and manually fiddle with the code in the phatk*.cl file included. Other kernels taken from other projects diablo, diapolo, phoenix etc will NOT under ANY circumstances work directly as the API is different so don't waste your time trying that.

... and of course if anyone was confused about the domain of that statement - it is of course only referring to the new 7970 cards
Nothing else.