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

[-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...

[1713869878]

1713869878

[1713869878]

1713869878

[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

[faraway]

The last cgminer version doesn't support scrypt anymore. Is there a fork somewhere adding back the opencl support, and updating the software?

[jedimstr]

The last cgminer version doesn't support scrypt anymore. Is there a fork somewhere adding back the opencl support, and updating the software?

Scrypt oriented Forks are being discussed on the Litecoin forms. I believe Wolf has his initial pass available for testing. https://forum.litecoin.net/index.php/topic,6994.0.html

[nov]

Configured autostart works this way.

-We need to edit autostart with this command: sudo nano /etc/xdg/lxsession/LXDE/autostart
-At the end add the line: @/usr/bin/lxterminal --geometry=90x35 -e cgminer (The parameter "geometry" is to set the size of CGMiner, so adjust the parameter to your needs)

Then if I remove power cord from Raspberry PI and Butterfly device, simulating problem with electricity.
Then after put power cord back and reboot, the "USB device in use" is displayed in CGMiner.

And I need to remotely login with TightVNC to Rasperry PI and remove the file /tmp/cgminer-usb-1-4 to allow CGMiner access to the connected Butterfly USB device.
Then CGMiner finds and uses the device.


This issue prevents auto start to work properly, since delete of the file is needed.

I tried even to try autodelete such file prior start of the CGMiner, during reboot.

But it somehow did not help.

I am currently using Minepeon distro and CGMiner there.

There seems not to be the observed issue.

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?

[-ck]

Configured autostart works this way.

-We need to edit autostart with this command: sudo nano /etc/xdg/lxsession/LXDE/autostart
-At the end add the line: @/usr/bin/lxterminal --geometry=90x35 -e cgminer (The parameter "geometry" is to set the size of CGMiner, so adjust the parameter to your needs)

Then if I remove power cord from Raspberry PI and Butterfly device, simulating problem with electricity.
Then after put power cord back and reboot, the "USB device in use" is displayed in CGMiner.

And I need to remotely login with TightVNC to Rasperry PI and remove the file /tmp/cgminer-usb-1-4 to allow CGMiner access to the connected Butterfly USB device.
Then CGMiner finds and uses the device.


This issue prevents auto start to work properly, since delete of the file is needed.

I tried even to try autodelete such file prior start of the CGMiner, during reboot.

But it somehow did not help.

I am currently using Minepeon distro and CGMiner there.

There seems not to be the observed issue.

That sounds suspiciously like you actually have 2 cgminers running at once without knowing it. The file is a red herring by the way and not the actual problem.

[-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

And to follow:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-fff.exe

[stridergt]

I am using minepeon (cgminer3.6.4) with a Jalapeno and observing that DAcc (Difficulty Accepted) is 60-85% when mining with the eligius pool and 100-105% when mining with BTCguild. (both pools had min difficulty set to auto, but even when I changed BTCguild to 8+GH/s, the difference in percentage roughly stayed the same)
Can someone elaborate a bit on the Dacc calculation and the difference I am observing between the two pools, does it affect my share contribution accordingly???
I checked github, but I was a bit lost. I also asked at the minepeon forum but the dev just parsed the DAcc value and could not elaborate on the calculation method.

Thank you in advance

[jmc1517]

Thanks for that. Here is your next test please

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

And to follow:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-fff.exe

[/quote]

OK, Started the next test of cgminer-rst at 16:46.  First zombie (AMU11) at 21:07 after about 5 hours.  Test stopped at 21:31.  Note that the previous run of 3.5.1 ran for about 16 hours, again with no apparent flaws. Final status included at the start of the "rst" logfile for reference.  I am not logging runs of 3.5.1 but can do if it would reveal anything useful for comparison.

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

Next started cgminer-fff at 21:35. First zombie appeared at 22:10. Test stopped at 22:13.

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

Back to 3.5.1 again...

[-ck]

Next started cgminer-fff at 21:35. First zombie appeared at 22:10. Test stopped at 22:13.

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

Can you try fff again and this time when it gets into the loop of errors, enable debug in the display menu and continue logging for a bit please?

[CustomDesigned]

This code is provided entirely free of charge by the programmer in his spare
time so donations would be greatly appreciated. Please consider donating to the
address below.

Con Kolivas <kernel@kolivas.org>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

---

Primary developer/maintainer for cgminer: https://bitcointalk.org/index.php?topic=28402.0  148KkS2vgVi4VzUi4JcKzM2PMaMVPi3nnq

Why are there two bitcoin addresses?  Which one do I send a (small) donation to?  When I get "over the size limit", do I always need to pay the transaction fee, or does waiting a while also work?  UPDATE: waiting a while works.  I sent to the 15qS... address - hope that is correct.

[-ck]

This code is provided entirely free of charge by the programmer in his spare
time so donations would be greatly appreciated. Please consider donating to the
address below.

Con Kolivas <kernel@kolivas.org>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

---

Primary developer/maintainer for cgminer: https://bitcointalk.org/index.php?topic=28402.0  148KkS2vgVi4VzUi4JcKzM2PMaMVPi3nnq

Why are there two bitcoin addresses?  Which one do I send a (small) donation to?  When I get "over the size limit", do I always need to pay the transaction fee, or does waiting a while also work?

I like to keep track of whether donations are from the source code or from the forum, thanks! Whether you should send a transaction fee or not is determined entirely by bitcoind. If you choose not to, it can take ages to go through or potentially may never do so.

[jmc1517]

Next started cgminer-fff at 21:35. First zombie appeared at 22:10. Test stopped at 22:13.

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

Can you try fff again and this time when it gets into the loop of errors, enable debug in the display menu and continue logging for a bit please?

OK, done.  Aside: The previous overnight run of 3.5.1 went for 14 hours, no faults.

Started cgminer-fff again.  After about 3 hours I got several LEDs full on for a few seconds. Two of them went out and resumed mining but the 3rd appeared in the display as a zombie.  I was sitting next to the PC at the time, so turned on debug straight away.  I left it running for a further 5 minutes then stopped it.

Logfile here, but I suspect it's not going to help:
  https://dl.dropboxusercontent.com/u/44240170/logfile-fff2.txt

And...... Back to 3.5.1 again :/

[CustomDesigned]

Logfile here, but I suspect it's not going to help:
  https://dl.dropboxusercontent.com/u/44240170/logfile-fff2.txt

And...... Back to 3.5.1 again :/

This from 3.8.3 may give a clue:
 [2013-11-26 11:54:02] SEM: Icarus USB open failed '/tmp/cgminer-usb-1-58' err (24) Too many open files

It revives the zombies until it runs out of file descriptors on unix.  Maybe some similar resource exhaustion is happening on Windows?

Summary of runtime statistics:

 [2013-11-26 11:54:14] Started at [2013-11-23 11:22:25]
 [2013-11-26 11:54:14] Pool: http://api.polmine.pl:8347
 [2013-11-26 11:54:14] Runtime: 72 hrs : 31 mins : 49 secs
 [2013-11-26 11:54:14] Average hashrate: 1298.2 Megahash/s
 [2013-11-26 11:54:14] Solved blocks: 0
 [2013-11-26 11:54:14] Best share difficulty: 204K
 [2013-11-26 11:54:14] Share submissions: 47169
 [2013-11-26 11:54:14] Accepted shares: 46323
 [2013-11-26 11:54:14] Rejected shares: 846
 [2013-11-26 11:54:14] Accepted difficulty shares: 76307
 [2013-11-26 11:54:14] Rejected difficulty shares: 919
 [2013-11-26 11:54:14] Reject ratio: 1.8%
 [2013-11-26 11:54:14] Hardware errors: 837
 [2013-11-26 11:54:14] Utility (accepted shares / min): 10.64/min               
 [2013-11-26 11:54:14] Work Utility (diff1 shares solved / min): 13.76/min

 [2013-11-26 11:54:14] Stale submissions discarded due to new blocks: 0         
 [2013-11-26 11:54:14] Unable to get work from server occasions: 0               
 [2013-11-26 11:54:14] Work items generated locally: 130566
 [2013-11-26 11:54:14] Submitting work remotely delay occasions: 0               
 [2013-11-26 11:54:14] New blocks detected on network: 508

[-ck]

his from 3.8.3 may give a clue:
 [2013-11-26 11:54:02] SEM: Icarus USB open failed '/tmp/cgminer-usb-1-58' err (24) Too many open files

It revives the zombies until it runs out of file descriptors on unix.  Maybe some similar resource exhaustion is happening on Windows?

Interesting thought. It's easy enough to raise the number of file descriptors allowed in unix, but the default on windows should be much higher. Either way we should be removing the semaphores when the devices get zombied so that's at least one fix worth adding, thanks.

EDIT: Checked the code and the semaphores are being removed so that's not it.

[stridergt]

I am using minepeon (cgminer3.6.4) with a Jalapeno and observing that DAcc (Difficulty Accepted) is 60-85% when mining with the eligius pool and 100-105% when mining with BTCguild. (both pools had min difficulty set to auto, but even when I changed BTCguild to 8+GH/s, the difference in percentage roughly stayed the same)
Can someone elaborate a bit on the Dacc calculation and the difference I am observing between the two pools, does it affect my share contribution accordingly???
I checked github, but I was a bit lost. I also asked at the minepeon forum but the dev just parsed the DAcc value and could not elaborate on the calculation method.

Thank you in advance

Have I asked in the wrong thread? :-)
Please advise if so...