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

[mdude77]

Hey guys when i try to run chminer it shuts in a second.

I installed amd sdk but no change.

i have windows 7 64bit home premium
7700hd gzh edition gpu

which step i do wrong i cant get.

i put .bat to cgminer directory and run .bat than msdos openin and shutting in half second...

cgminer no longer supports GPU mining.  I believe 3.7.2 is the last version that supports it.

M

[Gwindor]

Hey guys when i try to run chminer it shuts in a second.

I installed amd sdk but no change.

i have windows 7 64bit home premium
7700hd gzh edition gpu

which step i do wrong i cant get.

i put .bat to cgminer directory and run .bat than msdos openin and shutting in half second...

cgminer no longer supports GPU mining.  I believe 3.7.2 is the last version that supports it.

M

yes i know this and i was trying with that version.

suddenly i tried again and it worked... lol shocked thanks for help anyway.

i have 7700hd any advice for script code?

[padrino]

I am trying to sort through the getwork logic in Anubis, given the fact that with the stratum protocol getwork != number of shares the calculations are off.

Hoping someone can provide some recommendations about how one might go about calculating something meaningful regarding total shares vs. getwork requests to in turn calculate meaningful discards statistics?

[jmc1517]

Here is a sequence of exes to try please. It will emulate a transaction translator for usb1.1 devices.

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

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

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

If any of these prove to work, there is no need to test the ones further down, thanks!

The first one (w1d10) got one zombie during an unattended 12-hour run. It replugged with no problem. I'll try w2d10 now.

"w1d10" has been mining for 3 hours now and no actual zombies yet, but it is behaving rather strangely.  I am regularly getting "rafts" of LEDs coming on - perhaps 15 or more, then another 1,2,3.... 7,8 or so, making 17-25 all on at once, then they all go out and everything looks normal again.  Nothing abnormal in the log file and my hash rate is ok at the pool.  I would say this looks very promising - if it were not for the disconcerting appearance of seeing all those LEDs going on and off...!!

Edit:  Of course it could be my wonderful (not!) broadband playing up - but that typically results in *all* LEDs coming on for 5 seconds or so and then going off en-masse.  What I'm seeing here happens perhaps once every 10, 15 or 30 minutes, and no "pool unavailable" messages.

[blazin8s]

when using gpu-reorder what is the official slot order the program uses?  It appears to be mixed up.

[os2sam]

when using gpu-reorder what is the official slot order the program uses?  It appears to be mixed up.

I'm pretty sure your at the whim of the OS as to how it assigns the order.

[mdude77]

when using gpu-reorder what is the official slot order the program uses?  It appears to be mixed up.

I'm pretty sure your at the whim of the OS as to how it assigns the order.

That and it may/will change from time to time. 

M

[-ck]

Here is a sequence of exes to try please. It will emulate a transaction translator for usb1.1 devices.

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

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

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

If any of these prove to work, there is no need to test the ones further down, thanks!

The first one (w1d10) got one zombie during an unattended 12-hour run. It replugged with no problem. I'll try w2d10 now.

"w1d10" has been mining for 3 hours now and no actual zombies yet, but it is behaving rather strangely.  I am regularly getting "rafts" of LEDs coming on - perhaps 15 or more, then another 1,2,3.... 7,8 or so, making 17-25 all on at once, then they all go out and everything looks normal again.  Nothing abnormal in the log file and my hash rate is ok at the pool.  I would say this looks very promising - if it were not for the disconcerting appearance of seeing all those LEDs going on and off...!!

Edit:  Of course it could be my wonderful (not!) broadband playing up - but that typically results in *all* LEDs coming on for 5 seconds or so and then going off en-masse.  What I'm seeing here happens perhaps once every 10, 15 or 30 minutes, and no "pool unavailable" messages.

Thanks very much for that. I'm pretty sure this is the right track since kano confirms it fixes his 3 AMUs mining on a USB3 hub on his RPi which previously wouldn't work at all unless he daisy chained it via a USB2 one. I don't think the -rw* versions will need to be tested and it will be a matter of whether it's 1d10 or whether I need 2d10 to roll a double 0 ftw.

[aigeezer]

Here is a sequence of exes to try please. It will emulate a transaction translator for usb1.1 devices.

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

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

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

If any of these prove to work, there is no need to test the ones further down, thanks!

The first one (w1d10) got one zombie during an unattended 12-hour run. It replugged with no problem. I'll try w2d10 now.

"w1d10" has been mining for 3 hours now and no actual zombies yet, but it is behaving rather strangely.  I am regularly getting "rafts" of LEDs coming on - perhaps 15 or more, then another 1,2,3.... 7,8 or so, making 17-25 all on at once, then they all go out and everything looks normal again.  Nothing abnormal in the log file and my hash rate is ok at the pool.  I would say this looks very promising - if it were not for the disconcerting appearance of seeing all those LEDs going on and off...!!

Edit:  Of course it could be my wonderful (not!) broadband playing up - but that typically results in *all* LEDs coming on for 5 seconds or so and then going off en-masse.  What I'm seeing here happens perhaps once every 10, 15 or 30 minutes, and no "pool unavailable" messages.

Thanks very much for that. I'm pretty sure this is the right track since kano confirms it fixes his 3 AMUs mining on a USB3 hub on his RPi which previously wouldn't work at all unless he daisy chained it via a USB2 one. I don't think the -rw* versions will need to be tested and it will be a matter of whether it's 1d10 or whether I need 2d10 to roll a double 0 ftw.

My w2d10 test looks good, eight hours in to the run. No reallocations, no zombies, no "light show" so far, although occasional single-LED multi-second displays.

[jmc1517]

Here is a sequence of exes to try please. It will emulate a transaction translator for usb1.1 devices.

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

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

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

If any of these prove to work, there is no need to test the ones further down, thanks!

The first one (w1d10) got one zombie during an unattended 12-hour run. It replugged with no problem. I'll try w2d10 now.

"w1d10" has been mining for 3 hours now and no actual zombies yet, but it is behaving rather strangely.  I am regularly getting "rafts" of LEDs coming on - perhaps 15 or more, then another 1,2,3.... 7,8 or so, making 17-25 all on at once, then they all go out and everything looks normal again.  Nothing abnormal in the log file and my hash rate is ok at the pool.  I would say this looks very promising - if it were not for the disconcerting appearance of seeing all those LEDs going on and off...!!

Edit:  Of course it could be my wonderful (not!) broadband playing up - but that typically results in *all* LEDs coming on for 5 seconds or so and then going off en-masse.  What I'm seeing here happens perhaps once every 10, 15 or 30 minutes, and no "pool unavailable" messages.

Thanks very much for that. I'm pretty sure this is the right track since kano confirms it fixes his 3 AMUs mining on a USB3 hub on his RPi which previously wouldn't work at all unless he daisy chained it via a USB2 one. I don't think the -rw* versions will need to be tested and it will be a matter of whether it's 1d10 or whether I need 2d10 to roll a double 0 ftw.

Finally got an error  - AMIU 27 LED full on but no zombie reported.  The hash rate is sitting at zero. Screenshot in logfile. I enabled debug for a while then tried manual re-plugging. Device appeared as zombie when removed, then when re-plugged it appeared as AMU 34.  2nd screenshot also in file.  Test then ended.  I'll try w2d10 next.
Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-w1d10.txt

Note: Just started w2d10 and it does the same strange thing as w1d10 at startup - all AMU LEDs go off as normal, then they all come back on again.  It takes a second or so for a few to go out, then it works a while with just those few, then the rest go out and mining continues with all devices.

Note 2: I have a zombie AMU 10 already after only a a few minutes...   Manually re-plugged as AMU 34.  Test continuing.

[kano]

I am trying to sort through the getwork logic in Anubis, given the fact that with the stratum protocol getwork != number of shares the calculations are off.
...

The number pretty much means nothing any more.
In stratum, you get work from the pool once every so often (~30s) and can generate enough work in that 30s for 16million TH/s without using a larger than default nonce2 or roll-n-time.
Increasing the size of nonce2 by 32 bits will allow you to generate more than another 9 orders of magnitude larger amount of work ...

Also the numbers were never similar before, unless someone was using the old getwork protocol to a pool that didn't support roll-n-time and was hashing with REALLY slow hardware.

I would suggest you make it display information appropriate for current hardware.

[-ck]

Finally got an error  - AMIU 27 LED full on but no zombie reported.  The hash rate is sitting at zero. Screenshot in logfile. I enabled debug for a while then tried manual re-plugging. Device appeared as zombie when removed, then when re-plugged it appeared as AMU 34.  2nd screenshot also in file.  Test then ended.  I'll try w2d10 next.
Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-w1d10.txt

Note: Just started w2d10 and it does the same strange thing as w1d10 at startup - all AMU LEDs go off as normal, then they all come back on again.  It takes a second or so for a few to go out, then it works a while with just those few, then the rest go out and mining continues with all devices.

Note 2: I have a zombie AMU 10 already after only a a few minutes...   Manually re-plugged as AMU 34.  Test continuing.

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[aigeezer]

Finally got an error  - AMIU 27 LED full on but no zombie reported.  The hash rate is sitting at zero. Screenshot in logfile. I enabled debug for a while then tried manual re-plugging. Device appeared as zombie when removed, then when re-plugged it appeared as AMU 34.  2nd screenshot also in file.  Test then ended.  I'll try w2d10 next.
Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-w1d10.txt

Note: Just started w2d10 and it does the same strange thing as w1d10 at startup - all AMU LEDs go off as normal, then they all come back on again.  It takes a second or so for a few to go out, then it works a while with just those few, then the rest go out and mining continues with all devices.

Note 2: I have a zombie AMU 10 already after only a a few minutes...   Manually re-plugged as AMU 34.  Test continuing.

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Me too or shall I stay with w2d10 which is still clean, 11 hours in?

[-ck]

Finally got an error  - AMIU 27 LED full on but no zombie reported.  The hash rate is sitting at zero. Screenshot in logfile. I enabled debug for a while then tried manual re-plugging. Device appeared as zombie when removed, then when re-plugged it appeared as AMU 34.  2nd screenshot also in file.  Test then ended.  I'll try w2d10 next.
Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-w1d10.txt

Note: Just started w2d10 and it does the same strange thing as w1d10 at startup - all AMU LEDs go off as normal, then they all come back on again.  It takes a second or so for a few to go out, then it works a while with just those few, then the rest go out and mining continues with all devices.

Note 2: I have a zombie AMU 10 already after only a a few minutes...   Manually re-plugged as AMU 34.  Test continuing.

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Me too or shall I stay with w2d10 which is still clean, 11 hours in?

You can stay on w2 thanks.

[-ck]

My site (ck.kolivas.org) will be down for some scheduled maintenance for a few hours shortly.

Here's a windows release candidate for what I'm likely to release as a new version tomorrow in case people want something to play with before it goes down:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-rc.exe

Contains the TT fixes discussed earlier, and auto usb reset of devices that have failed comms.

[jmc1517]

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Started latest trial version of cgminer, renamed as cgminer-2013-12-08.  The AMU LEDs initially all go off, then come back on again and it seems to take ages for all AMU LEDs to go out, then hash rates initially all show 150/ for a while, then 252/ ... afterwards increasing to the normal 335/ - see screenshots in logfile.  I haven't seen this behaviour before!

Test was left running overnight.  When I came back this morning there were 6 zombies and a couple with zero hash rates, please see 2nd screenshot in logfile.  Test stopped

Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-2013-12-08.txt

[-ck]

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Started latest trial version of cgminer, renamed as cgminer-2013-12-08.  The AMU LEDs initially all go off, then come back on again and it seems to take ages for all AMU LEDs to go out, then hash rates initially all show 150/ for a while, then 252/ ... afterwards increasing to the normal 335/ - see screenshots in logfile.  I haven't seen this behaviour before!

Test was left running overnight.  When I came back this morning there were 6 zombies and a couple with zero hash rates, please see 2nd screenshot in logfile.  Test stopped

Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-2013-12-08.txt

Alrighty, try the rc I posted next please then.

[aigeezer]

Finally got an error  - AMIU 27 LED full on but no zombie reported.  The hash rate is sitting at zero. Screenshot in logfile. I enabled debug for a while then tried manual re-plugging. Device appeared as zombie when removed, then when re-plugged it appeared as AMU 34.  2nd screenshot also in file.  Test then ended.  I'll try w2d10 next.
Logfile here:
  https://dl.dropboxusercontent.com/u/44240170/logfile-w1d10.txt

Note: Just started w2d10 and it does the same strange thing as w1d10 at startup - all AMU LEDs go off as normal, then they all come back on again.  It takes a second or so for a few to go out, then it works a while with just those few, then the rest go out and mining continues with all devices.

Note 2: I have a zombie AMU 10 already after only a a few minutes...   Manually re-plugged as AMU 34.  Test continuing.

Try this one instead then please:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Me too or shall I stay with w2d10 which is still clean, 11 hours in?

You can stay on w2 thanks.

Thanks - I got 13 hours on that run, then had an unrelated major system crash. Eventually got things fixed and another 11 hours on w2d10 which performed well throughout. I'll grab the release candidate next if I can, but w2d10 is very well behaved for me.

[koelen3]

Bro, I appreciate your program, but I need your help.
I'm running 2 5970s for scrypt mining on cgminer using xubuntu 13.10
I have amd catalyst 12.8 and AMD APP SDK v2.9

When I run cgminer as
./cgminer --scrypt -o stratum+tcp://mypool:port -u user -p x --shaders 3200 --intensity 13 my screen blacks out
If I use the same command, but replace shaders to 1600 my pc freezes.

So I've trued and find my max thread-concurrency, and it looks like it can't get higher then --thread-concurrency 1024

I've been searching for a week and was able to get my rig to 1500khash/s but wasn't getting any shares.
Could you please try and help me?

[twmz]

I'm running 2 5970s for scrypt mining on cgminer using xubuntu 13.10

cgminer no longer supports scrypt or GPU mining.  Check here for some folks that may be able to help:  https://litecointalk.org/index.php?topic=6925.0