Quote from: 419mining on May 12, 2020, 06:17:18 PM

I know its daunting looking through the 80 pages of posts. Maybe Sidehack/VH can update the first page with all the config settings cgminer now supports?

Adding them to the README.md (github) and the `--help` output would also be really swell.

Quote from: 419mining on May 12, 2020, 06:17:18 PM

you may want to try --gekko-start-freq, I havent gone through the code on github to see if it works for terminus but it would be worth a quick try. like you said, letting it autotune is best, but this is the one your looking for: --gekko-tune-down

https://bitcointalk.org/index.php?topic=5053833.msg50506833#msg50506833

[90-95]% is a healthy range, 95 is default, set to 0 to disable.
   1. Adjusts frequency according to each miner's unique charateristics
   2. To keep a hash performance above 95%.
   3. Based on the idea that (95% of 275MHz) hashes better than (80% of 300MHz)

--gekko-start-freq and --gekko-step-freq are flags I found elsewhere and have been working very well for my 2pacs; sadly, no effect on the compac. Hmm. Maybe that means the r606 patches have made it to master branch. I have been, until today, unaware there even was a feature-branch r606 and these two flags, at least, are working as of my last update and compile cycle.

I'll need to read up on tune-down. I'm not sure it's what I'm looking for. I was thinking something like:

Code:

{
   {
   [pools],
   },
"gekko-newpac-freq" : "",
"gekko-autotune" : "",
[other settings]
}

where N is a setting
  0=disable autotune,
  1=max-hash (per freq setting),
  2=max electrical-efficiency (disregard freq statement, if any);

or something to that effect. Not that this is a big concern, really. I can work out the math from the power tables provided and use frequency values. Of course, it would help if the power table was expanded to include all sane (and some insane) freq values; or a W=vcore*freq formula.