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

hm, And if I only use a single pool? Version 2.6.2 would be best for me, or for who use one pool?
Or is it just a side effect, and the end result is the same as the shares was on the previous version. Only DW is too much, because the new methods of work requests?

That's the cost of much smoother getwork behaviour. On the flip side, it will have less chance of dips in the hashrate, leak shares to backup pools, have bursts of work requirements and so on.

after update 2.6.2>2.6.3 , DW numbers greatly increased.
1 rig with 4 phatk kernel have 9-12% DW (before update 5-10%) with int 8, 2 rig witk 3 diablo 1 poclbm kernels have 30-35% DW (before updade 5-10%) with int 9.
1 conf - driver 11.12 ocl 2.5 from 11.11
2 conf - driver 11.12 7970 edition + sdk from 12.4 drivers (SDK 2.6 if not mistaken)
E:   The Efficiency defined as number of shares returned / work item ...... dropped in several times
it's ok?

what OS are you using? if linux, before running cgminer enter:



Have you installed the ADL SDK from AMD? did you copy the appropriate header files into the cgminer ADL directory before compiling?

http://developer.amd.com/sdks/ADLSDK/Pages/default.aspx

@kano
You should mention, that your executable file is compiled in x64_86 enviroment as  ywell.
Took me me somme time to figure, why this is not working on my x86 xubuntu :/
2.6.1 was sucking a lot with my bfl`s anyways.
I`ll give it a try with bfl now.

i`m working on 2.4.3 now - is there a lot of improvements since than (bfl & ztex) ?? answer YES/NO would be nice

can you add a botton to switch Pool for all Miner on miner.php ?

run one single on 2.6.3 for stability test
2.5.0 vs 2.6.3

update
working block on 2.6.3 not equal to 2.5.0

what are debian package configs?

2.6.3 -> https://bitcointalksearch.org/topic/m.1079367
An Xubuntu 11.04 64bit executable in my github downloads called cgminer-2.6.3a
https://github.com/kanoi/cgminer/downloads

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 GPU, BFL or 2xIcarus

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

I have also added a WinXP cgminer-2.6.3a.exe

This ONLY has BFL + ICA (as below) thus it doesn't need a computer with OpenCL on it
CFLAGS="-O2 -W -Wall" ./configure --enable-icarus --enable-bitforce

You will most likely also need the windowsdlls.zip file there in my downloads since my *.dll might be slightly different to ckolivas

I've always had the SDK installed and up through 2.6.2, it was working fine...

With my binaries you need to install opencl, usually from AMD, although the NVIDIA or even the Intel one will suffice. This has ALWAYS been the case.

http://developer.amd.com/sdks/AMDAPPSDK/downloads/Pages/default.aspx

Getting this when I try to start 2.6.3.

New version: 2.6.3 - August 5th 2012

Mostly bugfixes but one significant code rewrite

Human readable changelog
The most significant change in this version is a complete rewrite of the queueing mechanism which gets new work from the pools. The code in that section had gotten out of hand and become a "state machine" that was difficult to model its behaviour and occasionally led to stalls during startup and what-not without work and perhaps queued too much work in general. Now it monitors carefully the amount of queued and available work on a pool-by-pool basis and only queues when needed, but tries hard to make sure it doesn't run empty. You will notice the the TQ value now hovers around zero when all is well, and only jumps up transiently, all going well. Hopefully the efficiency is even higher now too. Detection of pool lag should be more accurate now, and less shares should leak to backup pools now as well.
Autodetect of BFL devices now works on windows too, courtesy of code from jesusminer.
Fixed the inability to disable pools from the menu.
Fixed writing of scrypt parameters to the configuration file.
Can set failover-only mode now from the menu during runtime.
No work is done by backup pools in failover-only mode at startup once again.
The API should be able to bind to the port immediately on linux now instead of having to wait 60 seconds as it used to.
Throttling episodes on bitforce devices will now register as HW errors.

Full changelog

- Count likely throttling episodes on bitforce devices as hardware errors.
- Style cleanups.
- Use FTD2XX.DLL on Windows to autodetect BitFORCE SHA256 devices.
- Make pool_disabled the first in the enums == 0, fixing the pool enabled count
which compares if value is not enabled before enabling it.
- Correct writing of scrypt parameters to config file based on command line
parameters only.
- Use different variables for command line specified lookup gap and thread
concurrency to differentiate user defined versus auto chosen values.
- Queue a request on pool switch in case we have no work from the new pool yet.
- Display failover only mode in pool menu and allow it to be toggled live.
- Reinstate check for system queueing lag when the current pool's queue is maxed
out, there is no staged work, and the work is needed now.
- There is no need for pool active testing to be mandatory any more with queue
request changes.
- Fix harmless warnings.
- Check the current staged and global queued as well before queueing requests.
Discard stales before ageing work in the watchdog thread. Queue requests after
discarding and ageing work in watchdog thread. Display accurate global queued in
curses output. Reuse variable in age_work().
- The queueing mechanism has become a complex state machine that is no longer
predictable. Rewrite it from scratch watching only current queues in flight and
staged work available on a pool by pool basis.
- API remove unused warning in non-GPU compile
- api.c in linux allow to open a closed socket in TIME_WAIT
- Queue an extra request whenever staged work drops below mining thread count in
hash_pop.
- Update debian package configs to v2.6.2

great

Sounds great.
Thanks,
Sam

Looks like a new bug, will fix next version, thanks.

Tried that, per your suggestion, but still no go.

Any other suggestions?
Thanks,
Sam

Switch to another pool, then disable.

I created a little "how to" video for CGMiner

http://www.youtube.com/watch?v=v1TKYpxTmso

Not perfect, but it's a start 

Just upgraded to 2.6.2.

When I try to disable a pool from the menu it says "cannot disable last pool".  All I do is press P and D and get this message, I don't get a chance to select a pool to disable.
Sam