Bitcoin Forum
May 02, 2024, 09:28:16 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 [547] 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 »
10921  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 07, 2011, 12:42:22 AM



Well if you could quickly test this version (drop the .exe in place of your existing one) and tell me if it works, that would be helpful:
http://ck.kolivas.org/apps/cgminer/cgminer.exe

(it's otherwise identical to 2.0)

Sure, I'll do that now.  Just to clarify, I should do this with the "extra" monitors disabled right?
Yes, try it on multiple cards with just the one monitor enabled.

It worked Cheesy    Sees all the cards even without the monitors "active".    Great job!
Great. I've updated the windows zip with the new executable and posted it in the top post since nothing else has changed, but it fixes the most common issue people are running into:

http://ck.kolivas.org/apps/cgminer/cgminer-2.0.0-win32_1.zip
10922  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 07, 2011, 12:06:49 AM



Well if you could quickly test this version (drop the .exe in place of your existing one) and tell me if it works, that would be helpful:
http://ck.kolivas.org/apps/cgminer/cgminer.exe

(it's otherwise identical to 2.0)

Sure, I'll do that now.  Just to clarify, I should do this with the "extra" monitors disabled right?
Yes, try it on multiple cards with just the one monitor enabled.
10923  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 07, 2011, 12:05:54 AM
Wow.  This works fantastic.  Great work, as always.

I love the Temperature display now.  Would it be possible to add an option to display the GPU and fan speed?  That would be nice to see if things are getting throttled down.

I'm rapidly running out of real estate in the status line...
10924  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 11:51:02 PM
The fan speeds and clock speeds seem to be updated too quick, it doesn't sound like it's doing anything at all. Though i have 4 cards in the one box so an adjustment of 5% is probably negligible in terms of audible sound.

Just to confirm, if i want to over clock my core speed to 825, set the fan to never go over 65% and to maintain 90 degrees i would use:
Code:
#!/bin/bash
cd ~/cgminer
DISPLAY=:0 ./cgminer -c p1.json -c p2.json --submit-stale --auto-fan --auto-gpu --gpu-engine 825 --gpu-memclock 300 --temp-overheat 95 --temp-target 90 --gpu-fan 65

Now i assume cgminer would automatically adjust the clock to the maximum possible with a ceiling of 825 while trying to maintain 90 degrees by adjusting the fan speed to a max of 65% (unless it hits the overheat value)?

I would prefer to sacrifice clock speeds to keep fan noise down.

Omitting the --auto-gpu/fan would set cgminer to always run the card at 820mhz and always run the fan at 65% (unless overheating)?

What happens if i use:

Code:
DISPLAY=:0 ./cgminer -c p1.json -c p2.json --submit-stale --auto-fan --auto-gpu  --temp-overheat 95 --temp-target 90

Does cgminer automatically overclock to the maximum possible for me?
You are partially right. The auto-fan ignores the set fan speed (intrinsically this is safer), so if you want a maximum fan speed of 65% you're limited with current options to just setting a static value for fanspeed. However the GPU ceiling you set will be adhered to when clocking up and down to maintain temp up to target. If you do *not* pass any engine speed to cgminer (like your last command line) it will only clock up and down if it already detects an overclock is already present. I'm obsessive about cgminer avoiding doing anything more than you specify is safe or is already running in terms of engine speed.
10925  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 11:41:31 PM
As for it seeing cards, I need all 4 of my cards connected up and the monitors "activated" in the display settings.  Once that's done and cgminer is doing it's thing, you can disable the other two monitors in display settings and it'll be fine until you need to restart cgminer.
That's a very interesting observation. I may be able to code a workaround for that next version.

That'd be awesome if possible.  It's a PITA at the moment, but it's been like that for a fair while (I was using MSI Afterburner prior to this and the same problem existed).

Love the new version by the way, you're a smart cookie Smiley
Smiley

Well if you could quickly test this version (drop the .exe in place of your existing one) and tell me if it works, that would be helpful:
http://ck.kolivas.org/apps/cgminer/cgminer.exe

(it's otherwise identical to 2.0)
10926  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 10:53:07 PM
As for it seeing cards, I need all 4 of my cards connected up and the monitors "activated" in the display settings.  Once that's done and cgminer is doing it's thing, you can disable the other two monitors in display settings and it'll be fine until you need to restart cgminer.
That's a very interesting observation. I may be able to code a workaround for that next version.
10927  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 12:08:48 PM
Unfortunately that does not remotely look like portable code, even to the point of breaking possibly between linux kernel releases if you're really unlucky and card specific.  Undecided Oh and possibly a real bitch to maintain because of that.
10928  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 11:59:13 AM
Can you make it so if the overheattemp >= currenttemp, goto out;

I.e if the temp is high than the set treshhold, stop mining completely and stop the thread?
Anything's possible. I could perhaps make a cutoff temperature over and above the overheat one.
10929  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 10:47:53 AM
What is NFI? How can I make these cgminer stats work with 4 GPUs? I have one dummy plug, should I make more? Wink
http://www.urbandictionary.com/define.php?term=N.F.I

Possibly the dummy plugs will help. Try one and see if that card comes up too. Also see which card it is that happens to be working in the list.
10930  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 10:30:55 AM
You have to make sure the display for all devices is exported on linux for all cards to be seen with "export DISPLAY=:0". NFI what you need to do on windows.
It was suggested on IRC that since we are exporting all the displays like an active one in linux, it may be that the lack of outputs on the displays on windows is why the adl library isn't talking to them. i.e. perhaps it's only the cards connected to monitors or dummy plugs that work.
10931  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 10:27:33 AM
Hey Con,

A truly amazing release !!

A quick 20mn run of the new cgminer with fan/mem/clock control
and everything seems to work peachy.

No more fiddling around with AMDOverDriveCtl, everything is now
controlled from cgminer. This rocks !!!

The only thing I can't now with cgminer do is push vddc beyond 1.05v
on my 5970s (but neither can AMDOverDriveCtl ... for this, the only thing
I've found that works is radeonvolt).

5BTC headed your way right now.
Thanks =) And thanking you muchly for your generous donation. I'm glad people appreciate how much effort this has been.
10932  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 09:49:48 AM
Okay, turned out that I didn't have ADL files in the folder. Con, please fix the readme file in that folder as the adl_structures file isn't checked by the ./configure but doesn't compile on make. Smiley
It checks for only one of the header files. I assumed that the instructions saying to
Quote
Copy all the *.h files in the "include" directory into cgminer's ADL_SDK directory.
were clear enough.
10933  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 08:41:30 AM
You have to make sure the display for all devices is exported on linux for all cards to be seen with "export DISPLAY=:0". NFI what you need to do on windows.
10934  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 07:56:46 AM
wow what an update! gone testing! Smiley

P.S. ckolivas, why do you use --auto-gpu and --gpu-engine 950 together in your example? how is it possible together auto and non-auto gpu? is there a reason? Wink
You need to tell it what speed you actually want auto-gpu to go up to...

I thought I covered all that in the extensive README.  Undecided
10935  Bitcoin / Mining software (miners) / Re: CGMINER CPU/GPU miner, GPU overclock+monitor+fanspeed in C for linux/windows/osx on: September 06, 2011, 04:14:48 AM
MASSIVE UPGRADE VERSION 2.0 - Links in top post

Major feature upgrade - GPU monitoring, (over)clocking and fan control for ATI
GPUs.

Executive summary:
You have to make sure the display for all devices is exported on linux for all cards to be seen with "export DISPLAY=:0". NFI what you need to do on windows.

Add overclocking settings, GPU and fan control for all cards:

cgminer -o http://pool:port -u username -p password -I 9 --auto-fan --auto-gpu --gpu-engine 950 --gpu-memclock 300

Add overclocking settings, GPU and fan control with different engine settings for 4 cards:

cgminer -o http://pool:port -u username -p password -I 9 --auto-fan --auto-gpu --gpu-engine 950,945,930,960 --gpu-memclock 300

---

New command line switches:
--auto-fan          Automatically adjust all GPU fan speeds to maintain a target
temperature
--auto-gpu          Automatically adjust all GPU engine clock speeds to maintain
a target temperature
--gpu-engine <arg>  Set the GPU engine (over)clock in Mhz - one value for all or
separate by commas for per card.
--gpu-fan <arg>     Set the GPU fan percentage - one value for all or separate
by commas for per card.
--gpu-memclock <arg> Set the GPU memory (over)clock in Mhz - one value for all
or separate by commas for per card.
--gpu-powertune <arg> Set the GPU powertune percentage - one value for all or
separate by commas for per card.
--gpu-vddc <arg>    Set the GPU voltage in Volts - one value for all or separate
by commas for per card.
--temp-hysteresis <arg> Set how much the temperature can fluctuate outside
limits when automanaging speeds (default: 3)
--temp-overheat <arg> Set the overheat temperature when automatically managing
fan and GPU speeds (default: 85)
--temp-target <arg> Set the target temperature when automatically managing fan
and GPU speeds (default: 75)

---
OVERCLOCKING WARNING AND INFORMATION

AS WITH ALL OVERCLOCKING TOOLS YOU ARE ENTIRELY RESPONSIBLE FOR ANY HARM YOU
MAY CAUSE TO YOUR HARDWARE. OVERCLOCKING CAN INVALIDATE WARRANTIES, DAMAGE
HARDWARE AND EVEN CAUSE FIRES. THE AUTHOR ASSUMES NO RESPONSIBILITY FOR ANY
DAMAGE YOU MAY CAUSE OR UNPLANNED CHILDREN THAT MAY OCCUR AS A RESULT.

The GPU monitoring, clocking and fanspeed control incorporated into cgminer
comes through use of the ATI Display Library. As such, it only supports ATI
GPUs. Even if ADL support is successfully built into cgminer, unless the card
and driver supports it, no GPU monitoring/settings will be available.

Cgminer supports initial setting of GPU engine clock speed, memory clock
speed, voltage, fanspeed, and the undocumented powertune feature of 69x0+ GPUs.
The setting passed to cgminer is used by all GPUs unless separate values are
specified. All settings can all be changed within the menu on the fly on a
per-GPU basis.

For example:
--gpu-engine 950 --gpu-memclock 825

will try to set all GPU engine clocks to 950 and all memory clocks to 825,
while:
--gpu-engine 950,945,930,960 --gpu-memclock 300

will try to set the engine clock of card 0 to 950, 1 to 945, 2 to 930, 3 to
960 and all memory clocks to 825.

AUTO MODES:
There are two "auto" modes in cgminer, --auto-fan and --auto-gpu. These can
be used independently of each other and are complementary. Both auto modes
are designed to safely change settings while trying to maintain a target
temperature. By default this is set to 75 degrees C but can be changed with:
--temp-target

AUTO FAN:
Fan control in auto fan works off the theory that the minimum possible fan
required to maintain an optimal temperature will use less power, make less
noise, and prolong the life of the fan. In auto-fan mode, the fan speed is
limited to 85% if the temperature is below "overheat" intentionally, as
higher fanspeeds on GPUs do not produce signficantly more cooling, yet
significanly shorten the lifespan of the fans. If temperature reaches the
overheat value, fanspeed will still be increased to 100%. The overheat value
is set to 85 degrees by default and can be changed with:
--temp-overheat

AUTO GPU:
GPU control in auto gpu tries to maintain as high a clock speed as possible
while not reaching overheat temperatures. As a lower clock speed limit,
the auto-gpu mode checks the GPU card's "normal" clock speed and will not go
below this unless you have manually set a lower speed at some time. Also,
unless a higher clock speed was specified at startup, it will not raise the
clockspeed. If the temperature climbs, fanspeed is adjusted and optimised
before GPU engine clockspeed is adjusted. If fan speed control is not available
or already optimal, then GPU clock speed is only decreased if it goes over
the target temperature by the hysteresis amount, which is set to 3 by default
and can be changed with:
--temp-hysteresis
If the temperature drops below the target temperature, and engine clock speed
is not at the highest level set at startup, cgminer will raise the clock speed.
If at any time you manually set an even higher clock speed successfully in
cgminer, it will record this value and use it as its new upper limit (and the
same for low clock speeds and lower limits).

CHANGING SETTINGS:
When setting values, it is important to realise that even though the driver
may report the value was changed successfully, and the new card power profile
information contains the values you set it to, that the card itself may
refuse to use those settings. As the performance profile changes dynamically,
querying the "current" value on the card can be wrong as well. So when changing
values in cgminer, after a pause of 1 second, it will report to you the current
values where you should check that your change has taken. An example is that
6970 reference cards will accept low memory values but refuse to actually run
those lower memory values unless they're within 125 of the engine clock speed.
In that scenario, they usually set their real speed back to their default.

STARTUP / SHUTDOWN:
When cgminer starts up, it tries to read off the current profile information
for clock and fan speeds and stores these values. When quitting cgminer, it
will then try to restore the original values. Changing settings outside of
cgminer while it's running may be reset to the startup cgminer values when
cgminer shuts down because of this.

---
Full changelog:

- Implement ATI ADL support for GPU parameter monitoring now and setting later
(temp, fan, clocks etc.).
- Check for the presence of the ADL header files in ADL_SDK.
- Import adl_functions.h from amd overdrive ctrl.
- Implement a setup function that tries to detect GPUs that support the ADL and
link in the parameters into the gpus struct.
- Put a summary of monitoring information from the GPU menu.
- Implement changing memory speed and voltage on the fly.
- Implement fan speed setting.
- Minor corrections to set fan speed by percentage.
- Make sure to read off the value in RPM only.
- Implement auto fanspeed adjustment to maintain a target temperature and
fanspeed below 85%, with an overheat check that will speed the fan up to 100%.
- Add an --auto-fan command line option to allow all GPUs to have autofan
enabled from startup.
- Add a gpu autotune option which adjusts GPU speed to maintain a target
temperature within the bounds of the default GPU speed and any overclocking set.
- Avoid a dereference if the longpoll thread doesn't exist.
- Clean up by setting performance profiles and fan settings to startup levels on
exit.
- Add a small amount of hysteresis before lowering clock speed.
- Allow target, overheat and hysteresis temperatures to be set from command
line.
- Combine all stats collating into one function to avoid repeating function
calls on each variable.
- Add gpu statistics to debugging output via the watchdog thread.
- Implement menus to change temperature limits.
- Implement setting the GPU engine clock speed of all devices or each device as
a comma separated value.
- Implement setting the GPU memory clock speed of all devices or each device as
a comma separated value.
- Implement setting the GPU voltage of all devices or each device as a comma
separated value.
- Implement setting the GPU fan speed of all devices or each device as a comma
separated value.
- Add support for monitoring powertune setting.
- Implement changing of powertune value from the GPU change settings menu.
- Get the value of powertune in get_stats.
- Implement setting the GPU powertune value of all devices or each device as a
comma separated value.
- Remove the safety checks in speed setting since confirmation is done first in
the menu, then show the new current values after a short pause.
- Force the speed to high on startup and restore it to whatever the setting was
on exit.
- Add temperature to standard output where possible and use more compact output.
- Move and print at the same time in curses to avoid random trampling display
errors.
- Update the status window only from the watchdog thread, do not rewrite the top
status messages and only refresh once all the status window is complete,
clearing the window each time to avoid corruption.
- Set a safe starting fan speed if we're automanaging the speeds.
- Provide locking around all adl calls to prevent races.
- Lower profile settings cannot be higher than higher profile ones so link any
drops in settings.
- Add new needed text files to distribution.
- Queue requests ignoring the number of staged clones since they get discarded
very easily leading to false positives for pool not providing work fast enough.
- Include libgen.h in opt.c to fix win32 compilation warnings.
- Fix compilation warning on win32.
- Add the directory name from the arguments cgminer was called from as well to
allow it running from a relative pathname.
- Add a --disable-adl option to configure and only enable it if opencl support
exists.
- Retry before returning a failure to get upstream work as a failure to avoid
false positives for pool dead.
- Retry also if the decoding of work fails.
- Use the presence of X-Roll-Ntime in the header as a bool for exists unless N
is found in the response.
10936  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx on: September 06, 2011, 12:12:47 AM
No, that will launch multiple instances. Just repeat the parameters with different data:

cgminer.exe -o http://arsbitcoin.com:8344 -u user -p password -o http://mtred.com:8337 -u user -p password -v 2 -w 128

Np btw, and welcome to the cgminer crowd Wink
Awesome, and thanks!   Smiley

guiminer:  ~3.5% stales in about any pool
cgminer:   ~0.3% stales (smaller sample size, of course)
Nice feedback, thanks =)
10937  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx on: September 05, 2011, 09:17:24 AM
Buggy libraries in old distributions.
10938  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx on: September 04, 2011, 10:44:49 AM
Thanks for positive feedback.

Major feature upgrade in the works. Somewhat below the radar and invisible at the moment, but available in the new git branch adl_support till it's complete.
10939  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx on: September 02, 2011, 10:35:51 AM
Yay! It compiles with curl from RHEL5 again! CPU-only RPMs are ready: http://rpm.zaytsev.net/test/cgminer/ . I will edit the RPM post later.
Yes I figured out what I had broken from the old curl at last. Please note that the old curl does not have support for sockoptions that make longpoll reliable. So while it is compiling with older libcurls, it may not be as reliable with longpoll on some servers.
10940  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows/osx on: September 02, 2011, 02:59:17 AM
New version: 1.6.2

Executive summary:
New --failover-only feature for those who complain too much work goes to the backup pool even without the primary pool failing. NOTE that you may get more idle periods with this enabled (which is why it leaked work to the backup pool in the first place).
New scheduling features to specify a start and stop time.
Various fixes and more verbose pebkac warnings.


Full changelog:

- Add --failover-only option to not leak work to backup pools when the primary
pool is lagging.
- Change recommendation to intensity 9 for dedicated miners.
- Fix the bouncing short term value by allowing it to change dynamically when
the latest value is very different from the rolling value, but damp the change
when it gets close.
- Use the curses_lock to protect the curses_active variable and test it under
lock.
- Go back to requesting work 2/3 of the way through the current scantime with
CPU mining as reports of mining threads running out of work have occurred with
only 5 seconds to retrieve work.
- Add start and stop time scheduling for regular time of day running or once off
start/stop options.
- Print summary on quit modes.
- Put some sanity checks on the times that can be input.
- Give a verbose message when no active pools are found and pause before
exiting.
- Add verbose message when a GPU fails to initialise, and disable the correct
GPU.
- Cryptopp asm32 was not correctly updated to the incremental nonce code so the
hash counter was bogus.
- Get rid of poorly executed curl check.
- If curl does not have sockopts, do not try to compile the
json_rpc_call_sockopt_cb function, making it possible to build against older
curl libraries.
- Most people expect /usr/local when an unspecified prefix is used so change to
that.
- Rename localgen occasions to getwork fail occasions since localgen is
unrelated now.


Links in top post.
Pages: « 1 ... 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 [547] 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!