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

Just received 5 new shiney 7970's and was wondering whats the best setup on cgminer for these.  I keep seeing diablominer as the best but I just love cgminer.  Any help is appreciated. 

Good summary D&T

Nobody ever said cgminer WILL change the voltage.  I said cgminer WON'T change voltage (or any other card parameter) unless you tell it to.  Sorry you were confused.

To anyone else wanting to avoid frustration some tips:
1) cgminer doesn't change anything (core clock, mem clock, voltage) unless you specify a value.
2) cgminer displays what the card is running at.  some other utilities show what the card is SET at.  If cgminer conflicts w/ other utilities cgminer is likely right.
3) When setting values cgminer uses AMD ADL library.  It ASKS the card to change the value.  The card is free to ignore it.  Some cards may ignore all requests, some may ignore just ones they consider "invalid".  Some cards may reset to stock after invalid value, some cards may keep last valid setting.
4) Exactly what happens depends on the exact card, the hardware, the vendor, and even the BIOS version (same exact card from same vendor with different BIOS can behave differently)
5) Don't use multiple utilities (TRIXX, atitweak, cgminer, AB, Catalyst) to change values at the same time.  If changing values with another utility don't specify a core, mem, or voltage parameter (as applicable) in cgminer.
6) P4Man encountered a situation where a VRM was damaged by using two utilities which read voltage directly from the hardware at the same time.  Be careful with these non-compliant utilities which read and write directly to the card hardware.

D&T,

I think af and I have been confused about the lack of cgminer to change voltage (underclock) on 7970s.  I skipped the 6xxx series and all my 5xxx series are able to be changed via cgminer.  Jake's post a few back describes the situation well = fscking AMD...

For the last time af.

Nobody said cgminer MUST work.

cgminer doesn't change the voltage UNLESS YOU TELL IT TO.  Period.

If you don't specify gpu-vddc and cgminer REPORTS 1.17V that doesn't mean cgminer CHANGED IT TO 1.17V.  It means CGMINER QUERIED the card and the card indicated it is running at 1.17V.

Very important that you read and comprehend what is being said instead of making assumptions, then getting confused and then blaming your problems on other people.

http://lmgtfy.com/?q=Add+an+exception+to+AVG

For some reason, my AVG tells me that CGMiner is a virus, and I can't use it..
It only happend today, and I've been mining with it for atleast a couple of weeks..

I'm not aware of a single case where cgminer was able to successfully change core voltage on 7xxx cards - those happy days of being able to easily tweak core voltage on any card are gone even though the code to do so still works.

The issue is that any AMD card is free to ignore your vddc change requests which is what the new generations of cards tend to commonly do.
No matter whether the driver returns success or failure, the hardware itself can - and does - merrily ignore your screams of anguish, an issue widely reported with various 6xxx (and now 7xxx) family cards. The 5xxx family of cards were very well-behaved in this respect.

Windows tools like Afterburner modify hardware registers directly, totally bypassing the driver fuckage but they do so using proprietary, non-portable, Windows-only code.
Thank you AMD.

The only surefire way to have your way with the card is by modding the bios but this is not for the faint of heart.
To add insult to injury, the moment you modify your BIOS Windows drivers will always bluescreen on boot to punish you for trying, even though the card may be 100% operational.
Thanks again AMD  

A small status update: the cgminer support for ztex boards now compiles and runs on linux, osx and windows. There are still features missing and the hash rate reporting is pretty broken but the boards hash at their expected speed. Check it out: https://github.com/nelisky/cgminer/tree/ztex

Let me know of any problems / suggestions.

I am having a problem undervolting a 6990.  I use the "--gpu-vddc 1.0" command option but when I use the 'g' key to read back it is always at stock voltage.  What am I doing wrong?

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

Is there a way to run the -na command when using diablo kernel?

Since I've had a few cgminer updates waiting for quite a while, and I've also added another update to the miner.php that some might consider useful, I'll post about it here:

The latest version in my git waiting to be pulled:
https://github.com/kanoi/cgminer/blob/master/miner.h

This adds 3 changes to ckolivas git:
1) Split the devs output tables if there is more than 1 device type
2) A PHP deprecated update for 1)
3) A new option at line 10 "$readonly" that when set to true will force the script to not show any buttons to change cgminer
If it is set to false then it will use the cgminer API command 'privileged' to determine if it should show buttons

Change 3) is useful to force it to read only with true if you want to give public access to the web page but ensure it always is readonly no matter what API access level you set in cgminer

option 3)

Yes, the default config (cgminer.conf) if it's able to find one.

No conf file is specified... will it use one without anything specified?

3 possible Causes:
1) in the "-c conf" file specified and also specified on the command line
2) in the "-c conf" file specified and also in the default conf file
3) specified on the command line and also in the default conf file

Hi folks,

I had a multi-hour Internet outage earlier today, but after replacing the failed component that was the cause the outage my (cgminer 2.3.1-based) rig connected and started hashing for a short while but then crashed with the following error:

I have the system setup to autologin to X and automatically start cgminer, but it was failing with the following error:

It would appear that my fglrx drivers were goofed, as a reboot of the system fixed the problem.

Anyone else ever see something like this?

Funnily enough my 2.3.1-2 doubled up on the poo front. Not using the conf file, and only happened this one time. Haven't re-started it to see if it does it again at all. It's not affecting anything so I've left it.

Thank you, for some reason I was reading the default path in cgminer as /home/ .cgminer/cgminer.conf (with a space before the period, which of course makes no sense) and then also not realizing the -a option to see the dir. Much appreciated.

The default is ~/.cgminer/cgminer.conf
(You must use ls -a to see file/directory names which begin with a ".".)

So to remove:
rm -ri ~/.cgminer