Hi Gents

Just want to report a possible bug here of some kind.

Here is what I am running.

Windows 7 64x
Cgminer 2.0
AMD 11.8 Drivers

(I have been running cgminer since 1.5.something and I am a HUGE fan)
 
CGMINER 2.0 Has Same Great Mining performance as 1.6.2 if I clock the cards with my own util (Saphire Trixx or MSI Afterburner)

But if I use CGMiner to clock my cards, I am getting significantly less performance
like 20 Mhash per card difference (total of 3 cards in machine)

I am 100% positive I am using the correct syntax to clock the cards at command line
and its the same if I go into the program and use CGMiner to clock them manually

it does not matter if I have auto-tune features on or off, I know the developer is a linux guy, but has any one run into this issue yet? I would love to be able to use cgminer to clock my cards and start mining with a nice batch file (more time for madden 2012)
Any Ideas?

You have the option to bypass the registration and go straight to the download.
Sam

Ooopss! Thanks a lot!

It's while the GPU code is executing that the CPU usage is high due to the driver consuming useless cycles. Sleeping when it comes back to the CPU will do nothing for that.

I'm using WinXP with 11.6 and am using it to overclock a Radeon 5770 and 5830 to 950Mhz and underclock the memory to 300MHz and I verified that the settings took with GPU Shark.  I could not do that with the ATI CCC.  And my hash rate has improved by 60 to 70Mhs for the pair of GPU's.
Sam

When I build 2.0.0 (with the original or newer -1 source), it works fine as long as I don't add the ADL header files to the ADL_SDK folder.  When I do that, I get this at the end of the make step:This is running Fedora 15 with GLIBC 2.14-4.  I'm guessing that is the problem, and I'm guessing it is due to the AMD header files and outside of ck's control, but wanted to report it just in case.  I may look for some repo with a newer GLIBC at some point if I can find time, but in the meantime, FYI:  It would appear that you have to have a pretty recent version of GLIBC to compile the gpu monitoring support.

EDIT:  I actually resolved this issue by defining LDFLAGS to point at ..../ati-stream-sdk-v2.1-lnx64/lib/x86_64/

I guess that means my guess was wrong.

For further clarification:  To get this running on Fedora 15 x86_64, I am running ./configure, gathering the CFLAGS and LDFLAGS settings from Makefile, and re-running ./configure with CFLAGS using those settings plus a -I..../ati-stream-sdk-v2.1-lnx64/..../includes/ setting and LDFLAGS using those settings plus a -L..../ati-stream-sdk-v2.1-lnx64/lib/x86_64/ (where the .... sections indicate paths that may vary per machine that I don't remember and can't see at this very moment).  Finally, because Fedora 15's JSON library is too old, I am editing the Makefile to use the source's included JSON instead of my installed JSON (I haven't tried setting JSON_INCLUDES for .lconfigure yet).

The new GPU features are awesome! A few suggestions/requests:


1) Dual GPU cards don't get adjusted/disabled correctly. For example, a 5970 will only disable the one GPU that has the temp sensor:


2) It'd be awesome if cgminer would record the current clocks on startup, and restore them on exit if the auto tuning changed them at all.

3) Pressing "G" when you have more than a couple of cards makes it impossible to read the output, because the window the output is displayed to is too small unless you have a HUGE screen.

4) I'd love a way to specify different temperature thresholds per GPU on the command line. If I have different model cards in there, they have different points where they're happy. 5770s get crashy above 90-95, where 5970 and 6990 cards idle near there at times.

5) My ideal dream would be a way of somehow saying "Any 5970 cards you see, set the temperature thresholds to X/Y, the voltage to Z, etc. Any 5770 cards, the temperature threshold is..." so that I don't have to look up which cards are in which system, just to pass that along to cgminer.

6) Temperatures >100C should be allowed, no matter how bad of an idea that sounds. We have some cards that go up to 105-107C without issue.

7) Specifying an overclock/underclock range that cgminer is allowed to adjust the clock in would be handy.

One step further, having it attempt to determine (maybe even saved into a local file) how high the clock was able to go without problems, and self-tuning the max clock rate while under the threshold temperature.

This should probably identify which GPU it's talking about, and maybe have some kind of throttling added to it, if a card's temperature is wiggling around the threshold.

Are you having trouble in that department, or did you just miss this?