Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 167. (Read 5805527 times)

newbie
Activity: 56
Merit: 0
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 :/
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/

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 <[email protected]>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

---

Primary developer/maintainer for cgminer: https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402  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.
newbie
Activity: 35
Merit: 0

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 <[email protected]>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

---

Primary developer/maintainer for cgminer: https://bitcointalksearch.org/topic/official-cgminer-mining-software-thread-for-linuxwinosxmipsarmr-pi-4110-28402  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
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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?
newbie
Activity: 56
Merit: 0

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...
newbie
Activity: 9
Merit: 0
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
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Configured autostart works this way.
Quote
-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.
nov
sr. member
Activity: 433
Merit: 251
Independent crypto developer
Configured autostart works this way.
Thank you for the update.

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

Quote
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?
hero member
Activity: 798
Merit: 1000
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
sr. member
Activity: 339
Merit: 250
The last cgminer version doesn't support scrypt anymore. Is there a fork somewhere adding back the opencl support, and updating the software?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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
member
Activity: 103
Merit: 10
Im using 3.1.3045 from the ubuntu ppa
legendary
Activity: 1540
Merit: 1001
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.

Quote
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
member
Activity: 103
Merit: 10
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.

Quote
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
newbie
Activity: 56
Merit: 0
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...
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Thank you for the update.

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

Quote
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...
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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...
legendary
Activity: 3583
Merit: 1094
Think for yourself
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
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.
Jump to: