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

You're welcome. Thanks for the feedback 

2.9.3 seems too run great for me thanks allot

Noted.

Neither the balance nor load balance strategies seem to work when your mining on a stratum server as your primary.  I've noticed this on all of the stratum enabled CGMiner's so far.

Sam

cut/paste ...

2.9.3
An Xubuntu 11.04 x86_64 executable is in my github downloads called cgminer-2.9.3a
https://github.com/kanoi/cgminer/downloads
(it also works on Fedora 16 and 17)

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

No problems so far on my '2xGPU' or 'BFL+ICA' (20 minutes + 3 LP's so far) GPU's on solo and BFL+ICA (1.6GH/s) on EMC with GBT
(MMQ is doing new code testing)

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./autogen.sh --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt
make clean
make

(and yes I made a 2.9.2a but deleted it and the post)

New versions: ->2.9.3, 11th November 2012

The GBT rollout wasn't that painful, so hopefully with this release cleaning up a few issues I can call this version the current stable release. I note more and more pools are moving to stratum instead anyway, which is in my opinion the better choice for pooled mining.


Human readable changelog

If a GBT pool was not the primary, then shares leaked to it or switching to the GBT pool would easily generate stale work. Now cgminer gets a new block template once per minute even from the backup pools. This is of course going to waste more bandwidth but is the only way to guarantee that any GBT work generated is not stale.
Cgminer will now detect backup pools failing even when not mining on them.
Sometimes cgminer would show the current block as just all zeroes. This bug has been worked around.
When mining on a server without longpoll, such as solo mining, if a stratum pool is available, its block change information will help the solo now.
Hopefully the URL stored for stratum pools when saving a configuration file works now.
The pools that had longpoll failing (like p2pool) should be fixed again.
Solo mining will now show the best share diff as well, even if they're all below target.


Full changelog

- Make header larger on gen stratum work to accomodate \0 at the end.
- Use stratum block change from backup pools as an alternative to longpoll for
pools that don't support LP.
- Check share target diff for best_share to be calculated when solo mining.
- Round some more static string arrays to 4 byte boundaries.
- There is no need for the static arrays to be larger than required, so long as
they're 4 byte aligned to appease ARM.
- Store the full stratum url information in rpc_url for correct configuration
file saving.
- Put in a hack to prevent dud work from sneaking into test_work_current being
seen as a new block.
- Reset the work->longpoll flag where it will affect stratum work items as well.
- Check for both coinbase/append and submit/coinbase support before using GBT
protocol.
- First pass through testing for GBT should not set probed to true since we are
about to probe again.
- Hash1 is only used by the deprecated cpu mining code and never changes so
remove it from the work struct and bypass needing to process the value for all
other mining.
- Get a work item once per minute for all getwork and GBT pools to test they're
still alive and to maintain a current GBT template.
- Get a fresh block template with GBT pools on switching to them.

Should be
"log" : "5",

It didn't really get trumped. No one has any idea. Usually if nothing is being produced or lots of HW errors despite a high hashrate, the intensity is too high.

Yes you can. The instructions and debug versions required are here:
http://ck.kolivas.org/apps/cgminer/debug/

Same goes for any windows related crashes.

--log|-l       Interval in seconds between log output (default: 3)

That change was after 2.9.1 in git only at the moment

Upgraded to 2.8.7, lets see how well it goes

2.9.1 is working fine here as long as the stratum pool I'm on is stable.  Otherwise it crashes.  2.8.7 does too.  Can you see if your instability issues are in 2.8.7?

M

Con,

2.9.1 is extremely unstable for me on Win7 64bit... I went back to 2.8.5.

Can I get you extra debugging info?

If you mean the Log interval then have a Look at the git in the section commits.

Somewhere between 2.8.5 and 2.9.1 the mhs 5s fields changed from 5 to 3. What is the setting to change this back to 5s?

Thanks,
gigavps

I'm on 2.8.7, and it crashed when I unplugged my wifi adapter. I didn't think anything of it, but it sounds similar.

cgminer 2.9.1 and 2.8.7 crash hard when mining on stratum pool and get disconnected.  I've seen it happen multiple times now.

windows 7 x64.

next time it happens I'll see if I can get some details from windows.

M

Leave the striked out bit out of the conf file. It's a bug in the configuration reading code.

Currently on 2.9.1 with all the same stats as in my previous post.  There has been several times where my GPU winds down(hash rate abruptly drops) after a block has been found, and then Cgminer crashes.  Fortunately, I was able to watch the crash occur, and there was nothing abnormal being displayed on the program  the moment before the crash happens.  I'm currently on a mining pool that uses GBT protocol.  Thanks, I thought I'd report this abnormality.

Another thing...
The Stratum pool isn't be read correctly from the conf file.
I added it via the API, saved config and it correctly shows in conf file:

   {
      "url" : "stratum+tcp://stratum.ozco.in:3333",
      "user" : "xxxxx",
      "pass" : "xxxxx"
   }

But then when cgminer starts, it shows via the API as a disabled pool, without the 'stratum+tcp://' prefix or port suffix, just 'stratum.ozco.in'.