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

[ewibit]

ZOMBIES not restarted @Linux cgminer 3.8

Code:

 AMU 10:                | 293.4M/323.9Mh/s | A:  5865 R:   45 HW: 459 WU:  4.3/m
 AMU  2:                | ZOMBIE/114.7Mh/s | A:  2317 R:   16 HW: 160 WU:  1.6/m
 AMU  3:                | ZOMBIE/115.1Mh/s | A:  2121 R:   32 HW: 209 WU:  1.5/m
 AMU  4:                | ZOMBIE/158.2Mh/s | A:  3162 R:   12 HW: 245 WU:  2.2/m
 AMU  6:                | ZOMBIE/66.72Mh/s | A:  1325 R:    8 HW: 112 WU:  0.9/m

any way that they restart automatic?
TIA

[Aurum]

I find I have to exit and restart my BFL Singles using 3.8.1 at least once a day or they sllooowwww down. I don't recall that happening with 3.7.2, I'll go back and try 3.7.2 again.

[-ck]

Windows users with issues on 3.8.1 can just use 3.7.2. For most drivers it is trivially different except for the one change that might be the cause of your problems.

[os2sam]

Ok, the max number of USB miners I can get to work on Win7 is 60.  The max I can get on Win Vista is 50.  I wish I knew why that might be?

[ChipGeek]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

[chadtn]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

I haven't had any problems with raspbian and 3.8.1 on my end so far.  I've got four instances of cgminer up on the same Rpi with each built for different hardware.  After I did an update & upgrade last week my Rpi started crashing when ever I tried mining on it.  The fix was to turn on some kind of memory debugging feature.

Chad

[QiVX]

I don't know if it's me or not.
Unzipped latest version of cgminer, and tried running cgminer.exe with --scrypt and it comes up with unrecognized parameter ?

Went back to 3.7.2 and all is fine. Can't seem to mine LTC with 3.8 c:

[jedimstr]

I don't know if it's me or not.
Unzipped latest version of cgminer, and tried running cgminer.exe with --scrypt and it comes up with unrecognized parameter ?

Went back to 3.7.2 and all is fine. Can't seem to mine LTC with 3.8 c:

I think you missed this a few pages back... https://bitcointalk.org/index.php?topic=28402.msg3538435#msg3538435

We discuss it further here:
https://forum.litecoin.net/index.php/topic,6925.0.html

Others are going to pick up the pieces and continue development here: https://forum.litecoin.net/index.php/topic,6994.0.html

[ChipGeek]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

I haven't had any problems with raspbian and 3.8.1 on my end so far.  I've got four instances of cgminer up on the same Rpi with each built for different hardware.  After I did an update & upgrade last week my Rpi started crashing when ever I tried mining on it.  The fix was to turn on some kind of memory debugging feature.

Chad

Hmmm...  Thanks for the info.  I did to this and perhaps that's the culprit? 

Code:

sudo apt-get update

What is the "memory debugging feature" that you turned on?

[chadtn]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

I haven't had any problems with raspbian and 3.8.1 on my end so far.  I've got four instances of cgminer up on the same Rpi with each built for different hardware.  After I did an update & upgrade last week my Rpi started crashing when ever I tried mining on it.  The fix was to turn on some kind of memory debugging feature.

Chad

Hmmm...  Thanks for the info.  I did to this and perhaps that's the culprit? 

Code:

sudo apt-get update

What is the "memory debugging feature" that you turned on?

Here is a link to instructions.  Scroll down to the section that says Rpi freezing up.

http://projectklondike.org/how-to-run

Chad

[Ghost of USD]

Has anyone tested out the 20131112-unstable avalon firmware?

[aneutronic]

Has anyone tested out the 20131112-unstable avalon firmware?

It's unstable on my b3. The latest stable version for mine is 3.6.6, it runs strong but requires daily restarts due to filling up the very small ram on the tplink.

[ChipGeek]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

Here is a link to instructions.  Scroll down to the section that says Rpi freezing up.
http://projectklondike.org/how-to-run
Chad

Thanks but that is not the problem I'm seeing.  My RPi does not freeze or lock up.  Instead it appears as if the 'q' key was pressed and cgminer quits for no apparent reason.  It happened again last night.  I will revert to an older version.

BTW - when getting source from github, now do I request an older version (such as 3.7.2)? 
I can't just go back to the ancient version I was using (3.4.2).

[-ck]

I'm seeing a problem with 3.8.1 on an RPi running Rasbian.  Twice in the last 24 hours cgminer has stopped running.  It appears as if the "q" key was pressed even though I'm sure it was not.  This hardware has run solid for weeks before I upgraded to 3.8.1. 

Here is a link to instructions.  Scroll down to the section that says Rpi freezing up.
http://projectklondike.org/how-to-run
Chad

Thanks but that is not the problem I'm seeing.  My RPi does not freeze or lock up.  Instead it appears as if the 'q' key was pressed and cgminer quits for no apparent reason.  It happened again last night.  I will revert to an older version.

BTW - when getting source from github, now do I request an older version (such as 3.7.2)? 
I can't just go back to the ancient version I was using (3.4.2).

Use a tag
git checkout v3.7.2

or whatever

[-ck]

Windows users with random communication problems/zombies, here's a new binary to test please (multi AMU users, I'm looking at you).

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

[ewibit]

Windows users with random communication problems/zombies, here's a new binary to test please (multi AMU users, I'm looking at you).

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

is not only Windows
Ubuntu 13.10:

Code:

AMU  0:                | ZOMBIE/182.3Mh/s | A:  1767 R:  12 HW: 139 WU:   2.4/m
 AMU  1:                | ZOMBIE/177.4Mh/s | A:  3740 R:   4 HW: 126 WU:   2.4/m
 AMU  2:                | ZOMBIE/182.5Mh/s | A:  1857 R:  13 HW: 139 WU:   2.3/m
 AMU  3:                | ZOMBIE/182.5Mh/s | A:  3919 R:  12 HW: 139 WU:   2.4/m
 AMU  4:                | ZOMBIE/155.8Mh/s | A:  1460 R:  12 HW:  93 WU:   2.1/m
 AMU  5:                | ZOMBIE/182.4Mh/s | A:  1722 R:   0 HW: 136 WU:   2.5/m
 AMU  6:                | ZOMBIE/182.0Mh/s | A:  3710 R:  16 HW: 128 WU:   2.4/m
 AMU  7:                | ZOMBIE/156.1Mh/s | A:  1425 R:  12 HW: 114 WU:   2.1/m
 AMU  8:                | ZOMBIE/182.2Mh/s | A:  1829 R:  16 HW: 144 WU:   2.5/m
 AMU  9:                | ZOMBIE/182.3Mh/s | A:  1772 R:  16 HW: 136 WU:   2.4/m
 BAL  0:  max 58C 3.27V | ZOMBIE/16.38Gh/s | A:195597 R:5755 HW:1076 WU: 227.4/m

cgminer 3.8

[-ck]

Windows users with random communication problems/zombies, here's a new binary to test please (multi AMU users, I'm looking at you).

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

is not only Windows
Ubuntu 13.10:

Code:

AMU  0:                | ZOMBIE/182.3Mh/s | A:  1767 R:  12 HW: 139 WU:   2.4/m
 AMU  1:                | ZOMBIE/177.4Mh/s | A:  3740 R:   4 HW: 126 WU:   2.4/m
 AMU  2:                | ZOMBIE/182.5Mh/s | A:  1857 R:  13 HW: 139 WU:   2.3/m
 AMU  3:                | ZOMBIE/182.5Mh/s | A:  3919 R:  12 HW: 139 WU:   2.4/m
 AMU  4:                | ZOMBIE/155.8Mh/s | A:  1460 R:  12 HW:  93 WU:   2.1/m
 AMU  5:                | ZOMBIE/182.4Mh/s | A:  1722 R:   0 HW: 136 WU:   2.5/m
 AMU  6:                | ZOMBIE/182.0Mh/s | A:  3710 R:  16 HW: 128 WU:   2.4/m
 AMU  7:                | ZOMBIE/156.1Mh/s | A:  1425 R:  12 HW: 114 WU:   2.1/m
 AMU  8:                | ZOMBIE/182.2Mh/s | A:  1829 R:  16 HW: 144 WU:   2.5/m
 AMU  9:                | ZOMBIE/182.3Mh/s | A:  1772 R:  16 HW: 136 WU:   2.4/m
 BAL  0:  max 58C 3.27V | ZOMBIE/16.38Gh/s | A:195597 R:5755 HW:1076 WU: 227.4/m

cgminer 3.8

That windows binary is truly a windows only thing that I implemented. Your zombies I'm gonna blame on your hardware

* ckolivas runs away screaming

[os2sam]

(multi AMU users, I'm looking at you).

Don't look at me.  3.8.1 has been rock solid for me on Win7 and even Vista, can't believe that crap OS is working well.

[-ck]

Windows users with random communication problems/zombies, here's a new binary to test please (multi AMU users, I'm looking at you).

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

And here's an extra one to test afterwards.

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

[aigeezer]

Windows users with random communication problems/zombies, here's a new binary to test please (multi AMU users, I'm looking at you).

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

And here's an extra one to test afterwards.

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

The first one is doing well for me after about 4.5 19.75 hours. Don't need the lulz yet, I guess.  

Edit: updated elapsed time of run.

Edit: finally got a zombie (AMU3) after about 24.75 hours. I'll try "lulz" next, for the lulz.

Edit: "lulz" is working perfectly, 19 hours into its run.

Edit: Oops - AMU10 went zombie, 22 hours in.