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

[jborkl]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

[pekv2]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

Oh, ok. I was under the impression there was an actual summary that is suppose to show e.g. B 1 or B 2 so on so forth.

[K1773R]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

its scrypt, not sha256d

[pekv2]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

its scrypt, not sha256d

So atm, I am mining with sha256d? and not scrypt?

[Marrs]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

Oh, ok. I was under the impression there was an actual summary that is suppose to show e.g. B 1 or B 2 so on so forth.

There IS a summary. You can query it through the API.

First, you need to enable the API by including these lines in your config file:

Code:

"api-listen" : true,
"api-network" : true,
"api-port" : "4028",

Then, if you have java installed on your system, cd into the cgminer directory, then run the following:

Code:

java API summary

That will output something like this:

Code:

Attempting to send 'summary' to 127.0.0.1:4028
Answer='STATUS=S,When=1364416953,Code=11,Msg=Summary,Description=cgminer 2.11.3|SUMMARY,Elapsed=937,MHS av=27.94,Found Blocks=0,Getworks=67,Accepted=6,Rejected=0,Hardware Errors=0,Utility=0.38,Discarded=124,Stale=0,Get Failures=0,Local Work=318,Remote Failures=0,Network Blocks=3,Total MH=26176.6840,Work Utility=0.38,Difficulty Accepted=6.00000000,Difficulty
Rejected=0.00000000,Difficulty Stale=0.00000000,Best Share=7| '[STATUS] =>
(
   [STATUS] => S
   [When] => 1364416953
   [Code] => 11
   [Msg] => Summary
   [Description] => cgminer 2.11.3
)
[SUMMARY] =>
(
   [0] => SUMMARY
   [Elapsed] => 937
   [MHS av] => 27.94
   [Found Blocks] => 0
   [Getworks] => 67
   [Accepted] => 6
   [Rejected] => 0
   [Hardware Errors] => 0
   [Utility] => 0.38
   [Discarded] => 124
   [Stale] => 0
   [Get Failures] => 0
   [Local Work] => 318
   [Remote Failures] => 0
   [Network Blocks] => 3
   [Total MH] => 26176.6840
   [Work Utility] => 0.38
   [Difficulty Accepted] => 6.00000000
   [Difficulty Rejected] => 0.00000000
   [Difficulty Stale] => 0.00000000
   [Best Share] => 7
)

As you can see, this includes the Found Blocks.

summary is actually the default command for the java API example class, so you could leave out the summary argument if that was all you wanted to do. For more information about using the API, read the API-README.txt file in cgminer directory or github.
[/code]

[pekv2]

If your best share was above the listed diff of 5.13m, then you found a block. Otherwise it does not matter

Oh, ok. I was under the impression there was an actual summary that is suppose to show e.g. B 1 or B 2 so on so forth.

There IS a summary. You can query it through the API.

First, you need to enable the API by including these lines in your config file:

Code:

"api-listen" : true,
"api-network" : true,
"api-port" : "4028",

Then, if you have java installed on your system, cd into the cgminer directory, then run the following:

Code:

java API summary

That will output something like this:

Code:

Attempting to send 'summary' to 127.0.0.1:4028
Answer='STATUS=S,When=1364416953,Code=11,Msg=Summary,Description=cgminer 2.11.3|SUMMARY,Elapsed=937,MHS av=27.94,Found Blocks=0,Getworks=67,Accepted=6,Rejected=0,Hardware Errors=0,Utility=0.38,Discarded=124,Stale=0,Get Failures=0,Local Work=318,Remote Failures=0,Network Blocks=3,Total MH=26176.6840,Work Utility=0.38,Difficulty Accepted=6.00000000,Difficulty
Rejected=0.00000000,Difficulty Stale=0.00000000,Best Share=7| '[STATUS] =>
(
   [STATUS] => S
   [When] => 1364416953
   [Code] => 11
   [Msg] => Summary
   [Description] => cgminer 2.11.3
)
[SUMMARY] =>
(
   [0] => SUMMARY
   [Elapsed] => 937
   [MHS av] => 27.94
   [Found Blocks] => 0
   [Getworks] => 67
   [Accepted] => 6
   [Rejected] => 0
   [Hardware Errors] => 0
   [Utility] => 0.38
   [Discarded] => 124
   [Stale] => 0
   [Get Failures] => 0
   [Local Work] => 318
   [Remote Failures] => 0
   [Network Blocks] => 3
   [Total MH] => 26176.6840
   [Work Utility] => 0.38
   [Difficulty Accepted] => 6.00000000
   [Difficulty Rejected] => 0.00000000
   [Difficulty Stale] => 0.00000000
   [Best Share] => 7
)

As you can see, this includes the Found Blocks.

summary is actually the default command for the java API example class, so you could leave out the summary argument if that was all you wanted to do. For more information about using the API, read the API-README.txt file in cgminer directory or github.
[/code]

Oh, Marrs, thank you, I would have never found this out on my own, I was getting so confused, well done. I will now have java installed just for this summary, thanks.

Here is a tip for you and who ever else that I picked up along the way of PCing. Hit shift then right click in the directory, run cmd here, it will open a cmd window cd'd already to that directory.

[Fiyasko]

*headache* So is all this new stuff just for 7970's? Or would a 7950 suffice...
Im running 2.10.4 right now and im wondering if i'll notice any benefit to upgrading all my miners (some use 5xxx 6xxx) or if just my 7950 will benefit.
Would a 7950 show a hashrate increase if i was to update to 2.11.3?

Just make another directory, put new mniner into it, copy config files, run and see...

AWEUHG c'mon I really dont want install the newer cgminer on all my machines just as a test *headdesk* Thats why i asked if i should expect any kind of boost of any kind

[Marrs]

I will now have java installed just for this summary, thanks.

You don't need Java. That was just an example using the Java API sample that ships with cgminer.

All you need is to be able to send data to the network port that you enabled the API listener on.

If you have a Linux box handy, you could do this instead:

Code:

echo -n "summary" | nc ip.address.of.cgminer 4028

[pekv2]

I will now have java installed just for this summary, thanks.

You don't need Java. That was just an example using the Java API sample that ships with cgminer.

All you need is to be able to send data to the network port that you enabled the API listener on.

If you have a Linux box handy, you could do this instead:

Code:

echo -n "summary" | nc ip.address.of.cgminer 4028

oh. Thank you Marrs. Without you guys, im a rock.

I'm good to go.

Code:

[0] => SUMMARY
[Elapsed] => 1970
[MHS av] => 0.77
[Found Blocks] => 0
[Getworks] => 51
[Accepted] => 312
[Rejected] => 5
[Hardware Errors] => 0
[Utility] => 9.50
[Discarded] => 98
[Stale] => 0
[Get Failures] => 0
[Local Work] => 220
[Remote Failures] => 0
[Network Blocks] => 22
[Total MH] => 1517.2895
[Work Utility] => 762.77
[Difficulty Accepted] => 24656.00000000
[Difficulty Rejected] => 384.00000000
[Difficulty Stale] => 0.00000000
[Best Share] => 37735

[Scratch]

Hey all,

LTC head normally, trying out a little bit of BTC just for kicks and because its applies to PPC too.

Setup:
Q6600 @3.5Ghz
8GB DDR3
7870 Joker
5770 PMD1G

Win764
CGminer 2.11.3
Cat 13.2

Trying to mine but 5770 is just throwing hardware errors "GPU1: invalid nonce - HW error". Temps are fine. Tried adjusted clocks, nada. Works fine on LTC, 200kH.

Can anyone suggest a solution and optimal clock settings to start with?

[os2sam]

Trying to mine but 5770 is just throwing hardware errors "GPU1: invalid nonce - HW error". Temps are fine. Tried adjusted clocks, nada. Works fine on LTC, 200kH.

Can anyone suggest a solution and optimal clock settings to start with?

My 5770 is set to Engine 920 and Mem 250.  I used to run it at 935 to 940 but with stratum and later versions of CG Miner I had to lower it to 920.  I'm also on catalyst 12.1.

[xorxor]

when mining on 4 gpu rig, on difficulty 1 , im geting such crash on internet reconnect :


   APPCRASH
   cgminer.exe
ver   0.0.0.0
time   514557a8
module   libusb-1.0.dll
ver   1.0.9.0
time   51132051
code   c0000005
exept.   00001e07
os   6.1.7600.2.0.0.256.1

 1:   0a9e
 2:   0a9e372d3b4ad19135b953a78882e789
 3:   0a9e
 4:   0a9e372d3b4ad19135b953a78882e789


windows 7 64; drv 13.1; sdk 2.7; cgminer 2.11.3; --scrypt, 2x 5970, getwork + LP, with failover set on stratum

 when on other pools, that have higher diff, rig is stable.

[-ck]

when mining on 4 gpu rig, on difficulty 1 , im geting such crash on internet reconnect :


   APPCRASH
   cgminer.exe
ver   0.0.0.0
time   514557a8
module   libusb-1.0.dll
ver   1.0.9.0
time   51132051
code   c0000005
exept.   00001e07
os   6.1.7600.2.0.0.256.1

 1:   0a9e
 2:   0a9e372d3b4ad19135b953a78882e789
 3:   0a9e
 4:   0a9e372d3b4ad19135b953a78882e789


windows 7 64; drv 13.1; sdk 2.7; cgminer 2.11.3; --scrypt, 2x 5970, getwork + LP, with failover set on stratum

 when on other pools, that have higher diff, rig is stable.

It looks like you are submitting lots of shares, your miner has disconnected 47 times due to an unstable pool/connection, cgminer has cached shares in the hope of resubmitting them when it reconnects with stratum, and then crashed due to running out of resources to spawn another thread trying to submit more shares. The amount of shares at diff1 on scrypt is obscene, choose a sensible pool.

[xorxor]

when mining on 4 gpu rig, on difficulty 1 , im geting such crash on internet reconnect :
   APPCRASH
(.................)

It looks like you are submitting lots of shares, your miner has disconnected 47 times due to an unstable pool/connection, cgminer has cached shares in the hope of resubmitting them when it reconnects with stratum, and then crashed due to running out of resources to spawn another thread trying to submit more shares. The amount of shares at diff1 on scrypt is obscene, choose a sensible pool.

im kinda geting paid to test this new pool, but first thing I said on the spot 5 second  from start :  "diff 16 man!"

[kano]

Hi Kano,

I was trying to upgrade from 2.7.6 to 2.11.3

I followed your procedure to update BFL device driver to WinUSB.  Downloaded zadig (for Windows 7), run it as administrator.
I got an error installing WinUSB driver.  Here is the Zadig debug log:

http://www.petermoss.com/akbash/zadig_install_log

Can you add FTDI driver support as an option?  As it is now, I can only use 2.10.5 version.

You'll have to ask the zadig devs.

The FTDI driver blocks direct USB access with libusb, that is why WinUSB is required.

[Luke-Jr]

Hi Kano,

I was trying to upgrade from 2.7.6 to 2.11.3

I followed your procedure to update BFL device driver to WinUSB.  Downloaded zadig (for Windows 7), run it as administrator.
I got an error installing WinUSB driver.  Here is the Zadig debug log:

http://www.petermoss.com/akbash/zadig_install_log

Can you add FTDI driver support as an option?  As it is now, I can only use 2.10.5 version.

You'll have to ask the zadig devs.

The FTDI driver blocks direct USB access with libusb, that is why WinUSB is required.

You mean libusb just requires a non-standard driver on Windows.
It does on Linux, too, but libusb has a feature to request the standard driver shutdown (which you're using).

Thankfully, people who want sane FPGA/ASIC support can continue to use BFGMiner, the original FPGA/ASIC miner.
Who knows why anyone still uses your troll fork.

[-ck]

CGMiner has nanosleep and sleep declared, which fucks the build for x86_64-w64-mingw32. Also, pthreads are not listed in the dependencies, and there is no option in configure to specify the prefix for pthreads.

We don't support building for w64 since it serves no useful advantage over 32 bit windows builds.

Iin fact ming w64 is an unstable development branch and 64 bit builds use more ram and are less reliable.

[Luke-Jr]

CGMiner has nanosleep and sleep declared, which fucks the build for x86_64-w64-mingw32. Also, pthreads are not listed in the dependencies, and there is no option in configure to specify the prefix for pthreads.

We don't support building for w64 since it serves no useful advantage over 32 bit builds.

BFGMiner has w64-related bugs fixed and officially supported.

[kano]

CGMiner has nanosleep and sleep declared, which fucks the build for x86_64-w64-mingw32. Also, pthreads are not listed in the dependencies, and there is no option in configure to specify the prefix for pthreads.

We don't support building for w64 since it serves no useful advantage over 32 bit builds.

BFGMiner has w64-related bugs fixed and officially supported.

However, please note that BFGMiner is well known to brick mining hardware. Avoid it.
Stay with cgminer, it works on that hardware that the crappy BFGMiner clone bricks.

[Luke-Jr]

CGMiner has nanosleep and sleep declared, which fucks the build for x86_64-w64-mingw32. Also, pthreads are not listed in the dependencies, and there is no option in configure to specify the prefix for pthreads.

We don't support building for w64 since it serves no useful advantage over 32 bit builds.

BFGMiner has w64-related bugs fixed and officially supported.

However, please note that BFGMiner is well known to brick mining hardware. Avoid it.

As usual, this is a lie.