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

[-ck]

Wasn't there a scrypt readme somewhere? I can't find it anymore 

No scrypt support any more.

[jmc1517]

So, having returned from holiday leaving "ymmv" running unattended for 2 weeks, I found 1 reported zombie and another 4 or 5 AMUs which had a very low WU, and had obviously been doing nothing for a while.  While I was away I was monitoring my pool hash rate and noticed that it slowly dropped from an expected 11 Gh/s to around 9.x over the two weeks which ties in with the above findings.

I restarted "ymmv" but got several random LEDs coming full on for a few seconds at a time then going off again. Obviously not happy, so I then reverted to running 3.5.1 which ran perfectly and has been doing so all night with no zombies and all WU's between 4.6 - 4.8.  This build is so stable!

I guess I will try 3.8.3 next unless there are other suggestions?

[randoint]

Just curious as to if anyone has tried this with Klondike units. The change log didn't provide specific references to them and I'm not home to test it out.

[kslavik]

Capitalising on the fact that I saw that dud cores are better disabled, here's an experimental binary that tunes things fairly aggressively:

http://ck.kolivas.org/apps/cgminer/kncminer/cgminer

First it enables all cores on startup (so it can take a while before it starts mining!)
Then it will disable cores after only 3 hw errors in a row, but staggers disabling of cores 5 seconds apart.
Then it tries re-enabling cores after only another minute, but staggers re-enabling them.
If the cores fail 3 times in a row, they're decommissioned at that point.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2

Was it done on purpose? Can we get it back, please?

[os2sam]

Random quote that appears to have nothing to do with the actual question.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2
Was it done on purpose? Can we get it back, please?

Did you try a valid command?

[MrTeal]

Is there a way to force cgminer to ignore a specific device? I use a FTDI based USB to serial convertor to control an RS232 Power Distribution Unit. It doesn't seem to affect the mining, but it's pretty annoying to have constant Incorrect Driver messages scroll across the screen.

[soapmodem]

Random quote that appears to have nothing to do with the actual question.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2
Was it done on purpose? Can we get it back, please?

Did you try a valid command?

This version of cgminer takes 10-15 seconds to boot up, because of the enabling of cores beforehand (presumably)...  'screen -rd' works, you just have to wait a while for it to launch.

Also, ckolivas, would it be possible to make available the previous kncminer 3.8.2 (without the tuning)? I was getting better hashrates overall on both of my machines with that one, for whatever reason. Thanks.

[kslavik]

Random quote that appears to have nothing to do with the actual question.

Seems like API is disabled in this version with the following message:
Invalid command
cgminer 3.8.2
Was it done on purpose? Can we get it back, please?

Did you try a valid command?

This version of cgminer takes 10-15 seconds to boot up, because of the enabling of cores beforehand (presumably)...  'screen -rd' works, you just have to wait a while for it to launch.

Also, ckolivas, would it be possible to make available the previous kncminer 3.8.2 (without the tuning)? I was getting better hashrates overall on both of my machines with that one, for whatever reason. Thanks.

I'm trying the same commands as I did with version 3.8.1 like "pools", "summary", and others

[os2sam]

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

[-ck]

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

That's bad, mmkay. Some code screw up on my part. Got some more output so I can figure out where the fuckage happened?

[os2sam]

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

That's bad, mmkay. Some code screw up on my part. Got some more output so I can figure out where the fuckage happened?

Well here's a screen capture.

I had moved the Jalapeno to an old low power machine and got this.  On my normal rig it works fine.  So I'm not sure it's not a problem on my old machine.

Code:

 cgminer version 3.8.3 - Started: [2013-11-23 22:47:12]
----------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:9  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 23  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 4 with stratum as user os2sam_Jalape
 Block: 6eb3b7ad...  Diff:609M  Started: [22:47:12]  Best share: 0
----------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 25C 3.49V |  0.000/ 0.000h/s | A:0 R:0 HW:9 WU:0.0/m
----------------------------------------------------------------------------

 [2013-11-23 22:47:02] Started cgminer 3.8.3
 [2013-11-23 22:47:10] Probing for an alive pool
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 2
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 4
 [2013-11-23 22:47:12] Network diff set to 609M
 [2013-11-23 22:47:13] hex2bin scan failed
 [2013-11-23 22:47:13] Pool 2 slow/down or URL or credentials invalid
 [2013-11-23 22:47:14] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:16] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:18] hex2bin scan failed
 [2013-11-23 22:47:19] hex2bin scan failed
 [2013-11-23 22:47:22] BAJ0: empty result (INPROCESS:10x0aCOUNT:20x0a9FF7FB8
A5F26106934BA7BA68FEB1F1D693B8B1`636DD791B2F53AAAE3CEDB,FEA0DFDF529185321907
,00x0a57C7A36DC1291`574DA63990BBCC160x00) ignored
 [2013-11-23 22:47:31] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored
 [2013-11-23 22:47:39] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored

[-ck]

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

That's bad, mmkay. Some code screw up on my part. Got some more output so I can figure out where the fuckage happened?

Well here's a screen capture.

I had moved the Jalapeno to an old low power machine and got this.  On my normal rig it works fine.  So I'm not sure it's not a problem on my old machine.

Code:

 cgminer version 3.8.3 - Started: [2013-11-23 22:47:12]
----------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:9  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 23  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 4 with stratum as user os2sam_Jalape
 Block: 6eb3b7ad...  Diff:609M  Started: [22:47:12]  Best share: 0
----------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 25C 3.49V |  0.000/ 0.000h/s | A:0 R:0 HW:9 WU:0.0/m
----------------------------------------------------------------------------

 [2013-11-23 22:47:02] Started cgminer 3.8.3
 [2013-11-23 22:47:10] Probing for an alive pool
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 2
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 4
 [2013-11-23 22:47:12] Network diff set to 609M
 [2013-11-23 22:47:13] hex2bin scan failed
 [2013-11-23 22:47:13] Pool 2 slow/down or URL or credentials invalid
 [2013-11-23 22:47:14] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:16] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:18] hex2bin scan failed
 [2013-11-23 22:47:19] hex2bin scan failed
 [2013-11-23 22:47:22] BAJ0: empty result (INPROCESS:10x0aCOUNT:20x0a9FF7FB8
A5F26106934BA7BA68FEB1F1D693B8B1`636DD791B2F53AAAE3CEDB,FEA0DFDF529185321907
,00x0a57C7A36DC1291`574DA63990BBCC160x00) ignored
 [2013-11-23 22:47:31] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored
 [2013-11-23 22:47:39] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored

Ah I see. The BAJ should only respond with text data that is in hexadecimal form and is sending back corrupted data that is not so it can't decipher the messages. Might happen on startup with an indeterminate device state with old data or with usb corruption.

[os2sam]

What does

hex2bin scan failed

mean?  Using 3.8.3 with my Jalapeno.
Sam

That's bad, mmkay. Some code screw up on my part. Got some more output so I can figure out where the fuckage happened?

Well here's a screen capture.

I had moved the Jalapeno to an old low power machine and got this.  On my normal rig it works fine.  So I'm not sure it's not a problem on my old machine.

Code:

 cgminer version 3.8.3 - Started: [2013-11-23 22:47:12]
----------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:9  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 23  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 4 with stratum as user os2sam_Jalape
 Block: 6eb3b7ad...  Diff:609M  Started: [22:47:12]  Best share: 0
----------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 25C 3.49V |  0.000/ 0.000h/s | A:0 R:0 HW:9 WU:0.0/m
----------------------------------------------------------------------------

 [2013-11-23 22:47:02] Started cgminer 3.8.3
 [2013-11-23 22:47:10] Probing for an alive pool
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 2
 [2013-11-23 22:47:12] Pool 0 difficulty changed to 4
 [2013-11-23 22:47:12] Network diff set to 609M
 [2013-11-23 22:47:13] hex2bin scan failed
 [2013-11-23 22:47:13] Pool 2 slow/down or URL or credentials invalid
 [2013-11-23 22:47:14] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:15] hex2bin scan failed
 [2013-11-23 22:47:16] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:17] hex2bin scan failed
 [2013-11-23 22:47:18] hex2bin scan failed
 [2013-11-23 22:47:19] hex2bin scan failed
 [2013-11-23 22:47:22] BAJ0: empty result (INPROCESS:10x0aCOUNT:20x0a9FF7FB8
A5F26106934BA7BA68FEB1F1D693B8B1`636DD791B2F53AAAE3CEDB,FEA0DFDF529185321907
,00x0a57C7A36DC1291`574DA63990BBCC160x00) ignored
 [2013-11-23 22:47:31] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored
 [2013-11-23 22:47:39] BAJ0: empty result (INPROCESS:00x0aCOUN0x00) ignored

Ah I see. The BAJ should only respond with text data that is in hexadecimal form and is sending back corrupted data that is not so it can't decipher the messages. Might happen on startup with an indeterminate device state with old data or with usb corruption.

So it sounds like it's not a CGMiner problem then.  So I'll just keep it on my regular rig until I build a newer, more current machine.
Thanks,
Sam

[-ck]

So, having returned from holiday leaving "ymmv" running unattended for 2 weeks, I found 1 reported zombie and another 4 or 5 AMUs which had a very low WU, and had obviously been doing nothing for a while.  While I was away I was monitoring my pool hash rate and noticed that it slowly dropped from an expected 11 Gh/s to around 9.x over the two weeks which ties in with the above findings.

I restarted "ymmv" but got several random LEDs coming full on for a few seconds at a time then going off again. Obviously not happy, so I then reverted to running 3.5.1 which ran perfectly and has been doing so all night with no zombies and all WU's between 4.6 - 4.8.  This build is so stable!

I guess I will try 3.8.3 next unless there are other suggestions?

3.8.3 is the next one to test...

[-ck]

Thank you for the update.

Do you think this version should help with my USB device in use issue?

I use Raspberry PI and ASIC Butterfly 30 GHs.

I have configured auto start of cgminer 3.8.2, which works perfectly.

But it always reports "USB device in use" type of message, if I remove power cord and put it back in this case. (My test of auto recovery.)
I need to manually delete /tmp/cgminer-usb-1-4 file then to cgminer be able to access the ASIC USB device.

Could you advice how to automate process the way that the cgminer will always have access to USB device?

It's supposed to be automated... Seems to be that the restart never works on these devices. Only quit followed by starting cgminer again does. Are you using the restart command or doing quit followed by starting it again?

EDIT: Are you SURE there isn't another cgminer running? That's what that's there for in the first place...

[jmc1517]

So, having returned from holiday leaving "ymmv" running unattended for 2 weeks, I found 1 reported zombie and another 4 or 5 AMUs which had a very low WU, and had obviously been doing nothing for a while.  While I was away I was monitoring my pool hash rate and noticed that it slowly dropped from an expected 11 Gh/s to around 9.x over the two weeks which ties in with the above findings.

I restarted "ymmv" but got several random LEDs coming full on for a few seconds at a time then going off again. Obviously not happy, so I then reverted to running 3.5.1 which ran perfectly and has been doing so all night with no zombies and all WU's between 4.6 - 4.8.  This build is so stable!

I guess I will try 3.8.3 next unless there are other suggestions?

3.8.3 is the next one to test...

Started the test of cgminer-3.8.3 at 13:57. First zombie (AMU20) appeared briefly at 14:05 but it auto-started working again as AMU34.  Two more zombies appeared at 14:12 and 14:24 (AMU10 and AMU13) and they did not recover.

I stopped the test at 14:49 as there didn't seem to be much point in continuing.  The previous run of 3.5.1 was rock-solid for 13 hours, and I've included a screenshot of it at the top of logfile-3.8.3.  All looks well with that run to me - no anomalies.  Unfortunately I didn't manage to produce a screenshot of 3.8.3 before stopping it as the CMD window seemed to be continually refreshing and it wouldn't "hold" a selection to enable copying.

Logfile is here (without --debug):
  https://dl.dropboxusercontent.com/u/44240170/logfile-3.8.3.txt

Back to 3.5.1 for the time being then...

[hhs99]

I have a machine with 2 nvidia cards in it and i get this when I try to run it. I want to play around with cgminer before my new cards get here.

cgminer: /usr/lib/nvidia-current/libOpenCL.so.1: no version information available (required by cgminer)
 [2013-11-24 14:06:06] Error -1001: clGetPlatformsIDs failed (no OpenCL SDK installed?)
 [2013-11-24 14:06:06] clDevicesNum returned error, no GPUs usable             
 [2013-11-24 14:06:06] 0 GPU devices max detected
 [2013-11-24 14:06:06] USB all: found 10 devices - listing known devices       
 [2013-11-24 14:06:06] No known USB devices

[mdude77]

I have a machine with 2 nvidia cards in it and i get this when I try to run it. I want to play around with cgminer before my new cards get here.

cgminer: /usr/lib/nvidia-current/libOpenCL.so.1: no version information available (required by cgminer)
 [2013-11-24 14:06:06] Error -1001: clGetPlatformsIDs failed (no OpenCL SDK installed?)
 [2013-11-24 14:06:06] clDevicesNum returned error, no GPUs usable             
 [2013-11-24 14:06:06] 0 GPU devices max detected
 [2013-11-24 14:06:06] USB all: found 10 devices - listing known devices       
 [2013-11-24 14:06:06] No known USB devices

cgminer no longer supports GPU mining.  you need an earlier version for that. 

M

[hhs99]

Im using 3.1.3045 from the ubuntu ppa

[-ck]

Started the test of cgminer-3.8.3 at 13:57. First zombie (AMU20) appeared briefly at 14:05 but it auto-started working again as AMU34.  Two more zombies appeared at 14:12 and 14:24 (AMU10 and AMU13) and they did not recover.

I stopped the test at 14:49 as there didn't seem to be much point in continuing.  The previous run of 3.5.1 was rock-solid for 13 hours, and I've included a screenshot of it at the top of logfile-3.8.3.  All looks well with that run to me - no anomalies.  Unfortunately I didn't manage to produce a screenshot of 3.8.3 before stopping it as the CMD window seemed to be continually refreshing and it wouldn't "hold" a selection to enable copying.

Logfile is here (without --debug):
  https://dl.dropboxusercontent.com/u/44240170/logfile-3.8.3.txt

Back to 3.5.1 for the time being then...

Thanks for that. Here is your next test please

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