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

Dead+Orphan are zero. Only 2 shares after an hour at 370 Mhash/sec, with a 40% reject rate, doesn't look too great.
Well … as it seems to work for others here, I'll check over at the p2pool thread.

That's normal for p2pool. You get a lot of LP's. My cgminer rejected rate is less than 2% though. If yours is higher there may be an issue. Watch your dead and orphan rate also. They will indicate where any issues are.

Hmm. I just fired up a new p2pool job (default settings, pretty much, except for talking to bitcoind of course   ) and then connected cgminer 2.2.1 to it.
Somehow, this doesn't fill me with confidence WRT getting an adequate return from p2pool:

… esp. since many of those Accepts seem to be from another pool I'm load-balancing to.

This is what happens when you try and do things quickly from the office at lunch  

Didn't compile - just did a git pull from p2pool and forgot about building (DUH) the cgminer...

Did you forget autogen?

I'm running c0e8819d and it's running fine, although it did take longer than normal to start.

Not to insult you, but did you recompile?  I just pulled and I am showing 2.2.1.

Just pulled from git and got ...

 
And still shows 2.2.0 to boot...

On the reorder issue - it definitely impacted one of my linux boxen (have two).  On one box it just swapped the two 5970 gpu's = no big deal.  On the second box it was originally:


After 2.2.0 it became:


So it wouldn't run with the old .conf as the voltage and clocks were gpu 3 (what was a 5850) was now getting passed to the 5970.  I have since re-done all my configs and it is working fine (hence trying the new --gpu-reorder command).

Wrong. Proof by counterexample: 2.2.0 did reorder some of my GPUs.
2.2.1 does not do any reordering unless explicitly asked to, you should be ok if you just skip 2.2.0

Con, git c0e8819 been running fine for 6 hours.
PS. Now we're talking:

Just to clarify, on linux, we never saw the GPU reordering, correct?

thanks for this release ckolivas - 1 BTC Donation Sent!

can you explain more about what the problem was with the gpu reordering by default?

you said "The whole GPU-reorder  saga caused massive damage"

which is a vague and frightening statement - and since i am using it on all five of my rigs I would love to hear the official statement of what exact damage we are talking about..

thanks again !!!!

New version: 2.2.1

So I'm really loathe to leaving a version out there that makes people adopt to massive change that may not have been a good idea, only to have to pull it again in the future. Today I had the luxury of my long-lost mining rig returning so I was finally able to actually do some meaningful debugging and testing of the code I was putting into cgminer and came up with the conclusion: 2.2.0 was a stinker. I spent most of today putting out all the spot fires under my feet and to release something a little more respectable as quickly as possible.

Here is 2.2.1, a mostly bugfix release.
Probably the most important fix is the fix for cgminer-generated midstate. This could cause massive rejects and is actually the main reason I put out a new release. This only affected pools that support the new work items which don't send midstate.
Bitforce support wouldn't actually build in 2.2.0 and the binaries I shipped didn't really have it built into it.
The whole GPU-reorder  saga caused massive damage, but we all learnt a lot from that one and there's much more useful verbose information of those issues in cgminer now, and that is useful even when GPU reordering is not enabled. When the number of devices doesn't match, cgminer will still continue to try to perform hardware monitoring.
There's more information now in --ndevs and we can use that to debug for real what SDK people are using
I've improved net-delay to not delay submission of shares since they're sporadic and any delays can be costly, especially for p2pool.
I also implemented something I've been meaning to do for a while: Only use one thread when dynamic mode is enabled on a GPU. It will make for even better interactivity of a desktop despite the miner running. The threads are re-enabled if you switch back to a static intensity.


Full changelog:

Version 2.2.1 - January 30, 2012

NOTE - The GPU Device reordering in 2.2.0 by default was considered a bad idea
so the original GPU ordering is used by default again unless reordering is
explicitly requested.

- Fix bitforce failing to build into cgminer.
- Add missing options to write config function.
- Add a --gpu-reorder option to only reorder devices according to PCI Bus ID
when requested.
- Fix for midstate support being broken on pools that supported no-midstate
work by ensuring numbers are 32 bits in sha2.c
- Set virtual GPUs to work when ADL is disabled or all mining will occur on GPU
0.
- Add information about paused threads in the menu status.
- Disable all but the first thread on GPUs in dynamic mode for better
interactivity.
- Set the latest network access time on share submission for --net-delay even if
we're not delaying that submission for further network access.
- Clear adl on exiting after probing values since it may attempt to overclock.
- As share submission is usually staggered, and delays can be costly, submit
shares without delay even when --net-delay is enabled.
- Display GPU number and device name when ADL is successfully enabled on it.
- Display GPU ordering remapping in verbose mode.
- Don't fail in the case the number of ADL and OpenCL devices do not match, and
do not attempt to reorder devices unless they match. Instead give a warning
about
- Display error codes should ADL not return ADL_OK in the more critical function
calls.
- Fix unused warning.
- Fix compile warnings in api.c
- Add extensive ADL based device info in debug mode.
- Make --ndevs display verbose opencl information as well to make debugging
version information easier.
- Display information about the opencl platform with verbose enabled.
- Explicitly check for nvidia in opencl platform strings as well.

I am sorry to hear that but I understand.

BTW.  I have an interesting error.  Because of BSOD when trying to update my drivers I reinstalled windows.  I installed 11.12 but not SDK.  Then installed SDK 2.5 from driver version 11.7.

2.1.12 works flawlessly.  No reduction in hashrate, and no CPU bug.

2.2.0 bombs out when starting w/ error (and yes I should have quoted it exactly ) about OpenCL compiled 0 byte binary.  It then loads the display w/ all cards listed as "off" and then promptly hard faults (Windows: cgminer.exe has encountered an error and will be closed).

Haven't done any investigating because 2.1.12 works fine and after upgrading my entire Linux farm to BAMT (working flawless w/ cgminer now BTW) and reinstalling windows I am done with upgrades for a few days.

This is tricky. It's very hard rolling back on such a big change. However I do think it was not the best idea to do it by default and the release has only been out one day. I suspect going to 2.2.0 will break far more people's configurations than going from 2.2.0 to 2.2.1, and then using the --gpu-reorder option will fix it (which is what I decided to call it). So, sorry, I've pretty much decided to make it default to off.

I vote that it should reorder by default but allow someone to turn it off if needed, I use Saphire Trixx to overclock my cards (19 of them!) and its nice to see them in the same order.

The git ride is about to get rather bumpy. Please be careful if you're pulling at random intervals.

With such a big update going to 2.2.0 it was inevitable some bugs would creep in. I'm trying to iron them all out and work on a bugfix-only 2.2.1 release as soon as is feasible. Having my mining rig AT LAST back will make it much much easier to test all this shit.

+1 for --dev-reorder. It's really awkward to have (for example) gpumon saying one thing, and cgminer saying it in reverse. Or the other way around.

I know it's a bit late with having made the device reorder part of an official release but I was wondering if people would prefer it to be optional in the next release instead of mandatory? I know some of you have some complex set ups with config files and device specific setting and so on that will be broken on going to 2.2.0, and I'm not against changing it back to the old behaviour and making it optional with something like --dev-reorder .

Sleep tight, but unfortunately you've picked one of the bad commits. That code never worked as they were attempts at doing it that didn't work properly and evolved like this (first unbroken commit was 05970):

commit 83a836765432dbc88b972588fb678aff17979a35
    Linux's ADL uses a busnumber in descending order for devices so enumerate them in the opposite order to windows.

commit 059701272c75bc30236f1c4a3aaf8db5e59bf718
    Carry virtual gpu number across.

commit 3bc0583454b09b5c4dac18450c4766572d69644f
    Iterate and change virtual device order instead of shuffling ram.

commit 371e5f688a2b6e5446e243ac9edcc490c0243a79
    Reorder displayed devices to map to physical locations and initialise according to logical location instead.

commit 5a0b4f62d0966d08bd92142d92d8b97f8e68f1e7
    Map GPU devices to virtual devices in their true physical order based on BusNumber.

Did everything, also freshly installed APP-2.5.

Problem is reliably reproducible with my setup (3*6950).

I bisected and found that the problematic commit is 371e5f68, while all builds with up to 5a0b4f62 work.

Need to go now. If you have some ideas on how I can help identifying the problem, let me know.


Good night.

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

Since this may be a recurring theme, I've uploaded a new bleeding edge binary for both windows and linux into that directory which can work around the problem but will give a warning when it happens. I'll try and keep bleeding edge binaries in there if/when required.

Starting with --verbose with these binaries should give you a lot more information which will help you debug where devices are going as well if you're having a new ordering issue.