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

Did you see this?

--intensity|-I Intensity of GPU scanning (d or -10 -> 10, default: d to maintain desktop interactivity)

Ok, thanks. Trying 45 seconds overnight for mincoins...

That's like going back to how we mined bitcoins >2 years ago before pools and longpoll. The answer is set the scantime as low as you can before the hashrate drops. If you're solo mining, something like 5s is usual for sha coins. However it can be slow to return results for scrypt so you'll have to experiment.

Con, can you address the best way to determine settings for scantime & expiry when mining the latest scrypt coins? Do you lower them to try to equal the block frequency? Like chinacoins were every second and mincoins are every minute, so it seems like leaving at default is a bad idea...

thnx

updated to catalyst 13.4 from 13.1 last night. now cgminer (301 and 310) hangs on start. i get as far as this:


and it just sits there indefinitely. tried a few different .conf settings, and get ther same. without a .conf and specifying url and such, it crashes a few seconds after hitting return after entering password.

any ideas?

Question: Is it a good practice to use "--scan-time 1" in cgminer?

I'm trying to solo-mine FTC (scrypt, 2.5 min/block) with GPUs. From what I can found, the usual recommended practice is to add stratum or longpoll pools to the list of pools, so cgminer will know when there is a new block.

However, from my own experiment, I found that existing FTC pools are slow to send out new block notifications. The following is a screenshot of cgminer running on 2 different machines.

https://i.imgur.com/AphbAkv.png

Machine on the left:
pools = [feathercoind, (stratum) feathercoin.is-a-geek.com, (longpoll) featherpool.com]
scan-time = 60

Machine on the right:
pools = [feathercoind]
scan-time = 1

Using "--scan-time 1" with a local feathercoind gives me new blocks detections 0-30 seconds faster than the stratum/longpoll connections (as seen above).

However, the statistics for the machine on the right show 60 new blocks (NB), 177 discarded work items (DW), and 1 rejected block (R). Having "DW > NB" and "R > 0" makes me feel that it might I may be doing something wrong. Naively I think that cgminer discards work only when a new block forces it to do so.

If anyone knows whether it's OK to use "--scan-time 1", and whether it's fine to have "DW > NB" and "R > 0", please let me know. Thanks!

heh, well, i have a remedy for that: http://www.imdb.com/title/tt2237008/?ref_=fn_al_tt_1

Gents,
 mind to decrypt the following please:

http://www.imdb.com/title/tt0118350/?ref_=fn_al_tt_1

Sorry, I couldn't resist... awesome flick.

just what is "intensity"?

Is there any downside to running cgminer as root? I'm getting ready for when my Jalapeno arrives and I can't find the 01-cgminer.rules file anywhere. Ah, I just found it. Still, running as root is much easier.

cgminer 3.1.0, I have found blocks with best share > diff & the pool has confirmed my share. but the counter of found blocks stayed 0. it may introduced in around 2.11.4 with your new block checking logic? (I'm running inside openwrt)

I have a Bitcoin machine running W8 Pro, Radeon 7850 + 7970 and CGminer 2.11.4
I am looking for finer tuning suggestions, and wanted your thoughts as to what you think I may have overlooked or should consider trying. Of the configs I've tried the following seems to run the best, but I'm sure there are more refinements I've not tried, including worksize.

Here is my Config:
"intensity" : "15,15",
"vectors" : "1,1",
"worksize" : "256,64",
"kernel" : "diablo,diablo",
"lookup-gap" : "0,0",
"thread-concurrency" : "0,0",
"shaders" : "0,0",
"gpu-engine" : "800-1100,900-1100",
"gpu-fan" : "0-85,0-85",
"gpu-memclock" : "1180,1190",
"gpu-memdiff" : "0,0",
"gpu-powertune" : "18,18",
"gpu-vddc" : "0.000,0.000",
"temp-cutoff" : "95,95",
"temp-overheat" : "85,85",
"temp-target" : "75,75",
"api-port" : "4028",
"auto-fan" : true,
"expiry" : "155",
"failover-only" : true,
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"per-device-stats" : true,
"queue" : "1",
"scan-time" : "60",
"temp-hysteresis" : "3",
"verbose" : true,
"shares" : "0",
"kernel-path" : "/usr/local/bin"

Is there any reason i can't use a thread concurrency of 1600? My gpu posts 720kh/s with it but all as errors. as soon as i use 8192 it only posts 550ish max. Perhaps this is why ghz card perform so badly?

7970

Hey, sharp eyes! That was the issue with the port 80 pool. It needed to be: mining.eligius.st:80
Thanks for your response nathanrees19!

I have a question and potentially a future feature to implement (maybe !)

I have a scrypt question. I have a rig with very bastardly cards, 6970, 7970, 5970 and 5870. I can get everything working fine -but- ! 7970 works best in scrypt with -g 2, but when I turn it on it makes my ATI driver crash, I reboot, etc, sometimes PC after reboot goes nuts, safe mode, reboot again. If I run -g 1 all works well but 7970 isn't mining as optimal as it should (175KH less than optimal super hashing speed).

I tried the -d option, but cgminer still compiles a scrypt*.bin for the scrypt setting and doesn't run properly. If let's say I run --gpu-fan at like 55, it sets 55 on ALL cards, even if I only tell it to mine from -d 1. I was thinking of running one instance of cgminer on 7970 card with -g 2, then another instance with -g 1, but I don't seem to be able.

Is there anything else I can do ?

Should be in front of that hostname, but the pool is broken anyway. Try another pool.

[2013-05-02 20:07:53] ALL (5s):1.043G (avg):989.3Mh/s | A:125  R:6  HW:0  U:12.6/m  WU:13.6/m
 [2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
 [2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
 [2013-05-02 20:08:05] Setting GPU 0 fan percentage to 47
 [2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
[/quote]
Looks like a pool problem.
[/quote]

Well, to honest this is the first time I've tried port 80 on Eligius. I've been plagued with problems on Eligius pool lately. Had been running pretty solid via :8332, then out of the blue myself and many others ran into problems there with terrible hashrates, stales, unable to retrieve work, and so on. Was just playing with the options of other ports there to see if anything works better. So far I'd say the stratum pool at :3334 seems best but not very good for me. But I digress, not trying to get off topic for this thread, sorry. I was wanting to make sure I wasn't missing something in my config with CGminer.

Here is my call via batch file: cgminer -o http://eligius.st:3334 -u xXXxxXXxxx -p x -I 14,15 --kernel diablo --gpu-memclock 1180,1190 --gpu-engine 800-1100,900-1100 --auto-fan --gpu-map 1:0,0:1 --gpu-powertune 18,18 --expiry 150 --per-device-stats --sharelog %userprofile%\desktop\minedshares.log 2>>%temp%\CGminer.log

And keep in mind the alternate pools are stored in my Config file. I'm open to suggestions for further tweaks as well...

Looks like a pool problem.

Anyone have an idea what this might be indicative of? Suggestions?
This machine is W8 Pro, 7850 + 7970 and CGminer 2.11.4
Pool 0: eligius.st:3334 Pool1: mint.bitminter.com:8332 Pool2: eligius.st:80 Pool3: eligius.st:8337 And I believe confirmed this log was while I was running with Pool Load Balancing Failover only setting, while running on Pool 1. I am wondering if it was just CGMiner trying to re-check the availability/viability of Pool2 and essentially failing, then trying again (see this error multiple times).
 [2013-05-02 20:07:53] ALL (5s):1.043G (avg):989.3Mh/s | A:125  R:6  HW:0  U:12.6/m  WU:13.6/m
 [2013-05-02 20:07:53] GPU1  73.0C 3392RPM | (5s):716.7M (avg):661.3Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
 [2013-05-02 20:07:55] GPU0  73.0C 2047RPM | (5s):330.9M (avg):331.6Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
 [2013-05-02 20:07:57] Setting GPU 0 fan percentage to 48
 [2013-05-02 20:07:57] Setting GPU 1 fan percentage to 74
 [2013-05-02 20:07:58] ALL (5s):1.029G (avg):989.4Mh/s | A:125  R:6  HW:0  U:12.5/m  WU:13.5/m
 [2013-05-02 20:07:58] GPU1  73.0C 3406RPM | (5s):743.5M (avg):660.8Mh/s | A:94 R:6 HW:0 U:9.5/m I:15
 [2013-05-02 20:07:59] Setting GPU 0 fan percentage to 47
 [2013-05-02 20:08:03] ALL (5s):950.3M (avg):987.9Mh/s | A:125  R:6  HW:0  U:12.4/m  WU:13.4/m
 [2013-05-02 20:08:03] Setting GPU 0 fan percentage to 48
 [2013-05-02 20:08:03] Setting GPU 1 fan percentage to 73
 [2013-05-02 20:08:04] GPU1  74.0C 3398RPM | (5s):722.5M (avg):660.4Mh/s | A:94 R:6 HW:0 U:9.3/m I:15
 [2013-05-02 20:08:05] Testing pool http://eligius.st:80
 [2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
 [2013-05-02 20:08:05] GPU0  74.0C 2173RPM | (5s):337.0M (avg):331.1Mh/s | A:31 R:0 HW:0 U:3.1/m I:15
 [2013-05-02 20:08:05] HTTP request failed: necessary data rewind wasn't possible
 [2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
 [2013-05-02 20:08:05] Setting GPU 0 fan percentage to 47
 [2013-05-02 20:08:05] JSON decode failed(1): '[' or '{' expected near '<'
 [2013-05-02 20:08:05] Closing socket for stratum pool 2