Did anybody talk to cklovias before he left, and might now what time frame he was expecting to be gone?
Hope things are going well for him, at least as much as possible with whatever emergency he is dealing with.
Anybody else still trying to use dynamic intensity figure out what is triggering it to turn to negative intensity after running for a while? When I see it happen I seem to be able to fix it by manually using the keyboard controls to set intensity to a fixed number and back to dynamic. When I do that it seems to stay running properly thereafter, but when I renable dynamic I see this in the output:
[2012-09-16 13:51:11] Thread 1 being disabled
[2012-09-16 13:51:11] Thread 1 being re-enabled
[2012-09-16 13:51:12] Thread 1 being disabled
[2012-09-16 13:51:12] Thread 1 being re-enabled
[2012-09-16 13:51:13] Thread 1 being disabled
Kind of weird it shuts down three times, plus I only seem to see this after re-enabling dynamic mode after it drops to negative. Can anyone else seeing this confirm?
I had the same issue in the past, I was waiting for Con to get back to discuss it further. But what I did find in my case was this only happened when I had either one of my two cards set to dynamic, and the other one set to a fixed intensity with more then one thread. I found if I just set CGminer to only run 1 thread per GPU that I didn't have this problem. Unfortunately I haven't been able to capture a log of when it would go into maximum negative mode because it seems to happen at random. I know that there is something triggering it, but I haven't been able to make a connection to anything else that I'm running or doing at the time.
The only other time I have seen it go into negative mode is when I have something else, like ripping a Blu-Ray, using up 100% of the CPU. This is not a problem with CGminer, it's just a limitation on how much your CPU can deal with at once.
So first off, make sure you aren't using up 100% of your CPU for something. If that doesn't work, try setting CGminer to only run 1 thread per GPU. If neither of those work for you, either you have a different problem then I have/had, or you have the same issue I do, and what I used to "fix" it, wasn't really what fixed it.
Regardless, please report back if you got this issue solved, and what you did if so. Any more information you can add will help track down the issue faster.