GMiner v3.44 Dero/Karlsen/Radiant/Ergo+IronFish+ZIL/KAWPOW/Equihash/Cortex

[Dr_Victor]

How to use OC1 kernels  on command line ?  what is parameters ?

THE SYNTAX IS STRICT--

For a simple command line flag, it took a while to figure out.  If you have one (1) card try:

        "miner -a algorithm --OC 1"

If you have four (4) cards try:

        "miner -a algorithm --OC 1 1 1 1"

The flag is space-delineated, do not use commas.  If you have a weak card that will not work with an overclock (OC) kernel, use "0" instead of "1".  A setting of "0" is the same as default, or no setting at all.  If you have improper syntax, the miner may not launch.

I do not believe that setting "--OC 1" for a multi-card rig will work properly, each separate card must have a corresponding "0" (no overclock), or "1" (overclock).

My 3GB 1060 cards and my 1070ti cards see a slight improvement at best.  If I am wrong, please correct me if you know better.       --scryptr

I am using '--oc1'  for 7-card rig.

[1715158732]

1715158732

[1715158732]

1715158732

[1715158732]

1715158732

[scryptr]

How to use OC1 kernels  on command line ?  what is parameters ?

THE SYNTAX IS STRICT--

For a simple command line flag, it took a while to figure out.  If you have one (1) card try:

        "miner -a algorithm --OC 1"

If you have four (4) cards try:

        "miner -a algorithm --OC 1 1 1 1"

The flag is space-delineated, do not use commas.  If you have a weak card that will not work with an overclock (OC) kernel, use "0" instead of "1".  A setting of "0" is the same as default, or no setting at all.  If you have improper syntax, the miner may not launch.

I do not believe that setting "--OC 1" for a multi-card rig will work properly, each separate card must have a corresponding "0" (no overclock), or "1" (overclock).

My 3GB 1060 cards and my 1070ti cards see a slight improvement at best.  If I am wrong, please correct me if you know better.       --scryptr

I am using '--oc1'  for 7-card rig.

DOES THE MINER EVEN LAUNCH? --

The flag is "--OC", followed by a space, as in "--OC 1".  If you actually typed "--oc1", the flag that you presented may be completely ignored, at best.  The string"--oc1" is not a correct flag.

Do you notice any improvement in hash rate?  What I do notice is that upon initial launch, there is no report to the console that the overclock kernel is being activated by the miner program.  If there is any improvement in Equihash, it is small.       --scryptr

[fapar]

Prompt cards RX480/580 the following parameters: -- oc/oc1 is supporting? Where can I read about this setting and which graphics cards are supported?
On my Giga 580 MI get average 16.3-16.5 Sol/s.

[2h4u]

I am using '--oc1'  for 7-card rig.

'--oc1' for miniz, not gminer.

[Zminer777]

'--oc1' for miniz, not gminer.

Are you sure? '--oc1' enable OC1 kernels for all devices if available (for GMiner)

[Dr_Victor]

How to use OC1 kernels  on command line ?  what is parameters ?

THE SYNTAX IS STRICT--

For a simple command line flag, it took a while to figure out.  If you have one (1) card try:

        "miner -a algorithm --OC 1"

If you have four (4) cards try:

        "miner -a algorithm --OC 1 1 1 1"

The flag is space-delineated, do not use commas.  If you have a weak card that will not work with an overclock (OC) kernel, use "0" instead of "1".  A setting of "0" is the same as default, or no setting at all.  If you have improper syntax, the miner may not launch.

I do not believe that setting "--OC 1" for a multi-card rig will work properly, each separate card must have a corresponding "0" (no overclock), or "1" (overclock).

My 3GB 1060 cards and my 1070ti cards see a slight improvement at best.  If I am wrong, please correct me if you know better.       --scryptr

I am using '--oc1'  for 7-card rig.

DOES THE MINER EVEN LAUNCH? --

The flag is "--OC", followed by a space, as in "--OC 1".  If you actually typed "--oc1", the flag that you presented may be completely ignored, at best.  The string"--oc1" is not a correct flag.

Do you notice any improvement in hash rate?  What I do notice is that upon initial launch, there is no report to the console that the overclock kernel is being activated by the miner program.  If there is any improvement in Equihash, it is small.       --scryptr

Guys, you are awesome! I had said that '--oc1' working for 7-cards rig. Why are you still speculating?

[scryptr]

TOO OFTEN, PROGRAMMERS ARE POOR AT DOCUMENTATION--

The flag "--OC" was announced with little explanation.  After several attempts, some with the miner not launching at all, I thought I had it figured out.

The miner does not print to the console when an overclock "OC" kernel is in effect.  Whatever improvement to the hash rate that results from the kernel seems minimal at best.

I think the whole thing still needs work.       --scryptr

[abudfv2008]

GMiner v1.60 available for download

v1.60
+ support AMD cards for ZelCash
+ improved performance for Equihash 144.5/192.7 on RTX SUPER cards
+ support OC parameter in config files
+ added OC1 kernel for BeamHashII for GTX 1070

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/1.60

How to set OC paremeter in config files? Maybe "sample-config" needs to be updated?

[Zminer777]

The miner does not print to the console when an overclock "OC" kernel is in effect.  Whatever improvement to the hash rate that results from the kernel seems minimal at best.

Miner print when selected OC kernel: "Selected OC1 solver"
When there is no OC1 kernel for card and algorithm then miner print "Selected Normal solver"

How to set OC paremeter in config files? Maybe "sample-config" needs to be updated?

Will do it in next update, example:
oc=0 1 1 0 1 1

[scryptr]

How to choose oc for each card? can an example. thx

Suppose you have 4 GPUs.

Code:

--OC 0 1 1 0

Set OC0 (default) mode for GPU0, GPU3
Set OC1 mode for GPU1, GPU2
Miner report about this to console.

HERE IS WHERE I READ MY SYNTAX--

There appear to be two kernels, "OC0" (default), and "OC1" (overclock).  This appears to be the names for the kernels.

However, the command-line syntax stated above is as I replied a few posts earlier, a space-delineated series of "1" or "0".

I just re-launched one of my rigs with the command line "miner -a 125_4 --OC1".  It launched with no problem.  There was no notice printed to the console as to the activation of an overclock kernel as the miner was launched.  The hash rate is not different by any significant margin.  The miner is steady with no rejects.

If there is an improvement for kernel "OC1", it is small.       --scryptr

P.S.  Just read your post above.  Perhaps there is no kernel for my 1060 3GB.       --scryptr

[Zminer777]

HERE IS WHERE I READ MY SYNTAX--

There appear to be two kernels, "OC0" (default), and "OC1" (overclock).  This appears to be the names for the kernels.

However, the command-line syntax stated above is as I replied a few posts earlier, a space-delineated series of "1" or "0".

I just re-launched one of my rigs with the command line "miner -a 125_4 --OC1".  It launched with no problem.  There was no notice printed to the console as to the activation of an overclock kernel as the miner was launched.  The hash rate is no different by any significant margin.  The miner is steady with no rejects.

If there is an improvement for kernel "OC1", it is small.       --scryptr

P.S.  Just read your post above.  Perhaps there is no kernel for my 1060 3GB.       --scryptr

Take look to sample screenshot: https://imgur.com/nHI75Om
Currently only GTX1070 and GTX1080TI has OC1 kernel on BeamHashII algorithm

[scryptr]

HERE IS WHERE I READ MY SYNTAX--

There appear to be two kernels, "OC0" (default), and "OC1" (overclock).  This appears to be the names for the kernels.

However, the command-line syntax stated above is as I replied a few posts earlier, a space-delineated series of "1" or "0".

I just re-launched one of my rigs with the command line "miner -a 125_4 --OC1".  It launched with no problem.  There was no notice printed to the console as to the activation of an overclock kernel as the miner was launched.  The hash rate is no different by any significant margin.  The miner is steady with no rejects.

If there is an improvement for kernel "OC1", it is small.       --scryptr

P.S.  Just read your post above.  Perhaps there is no kernel for my 1060 3GB.       --scryptr

Take look to sample screenshot: https://imgur.com/nHI75Om
Currently only GTX1070 and GTX1080TI has OC1 kernel on BeamHashII algorithm

YOUR COMMAND LINE SYNTAX EXAMPLES CONFLICT--

And, are the overclock kernels only for BeamHashII?  Thank you for the screen capture, it shows a report to the console. But your command line examples show, at different times, an equal sign, no equal sign, "--OC1", "--OC 1", "--oc1".   Sorry, there is confusion.

Thanks for Gminer, I use it.       --scryptr

[rampaige]

Hi,
What is the command of these parameters?

retry counts
retry delay
job timeout

Awesomeminer would close the Gminer in case of a connection error even if it was for 30 minutes or less!

[2h4u]

But your command line examples show, at different times, an equal sign, no equal sign, "--OC1", "--OC 1", "--oc1".   Sorry, there is confusion.

I second that. It's a HUGE confusion. I see author's train of thought there, but it's overconsistent.

[Mr Duong]

in configfile
miner --algo 150_5 --OC 111111(Total card) --server beam-asia.leafpool.com --port 3333 --ssl 1.....

[chuck732]

For Overclocking GTX 1060's 6gb and GTX 1070's. What do you you overclock the Core or the Memory?

[Zminer777]

GMiner v1.61 available for download

v1.61
+ improved compatibility with large rigs (>= 13 GPUs)
+ improved launch time of miner

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/1.61

[crypt_fr]

Gminer does a good job on GTX 1660 / 1660 Ti for Equihash 192,7 mining, however performance on RTX 2060 Super is really bad.

Getting around 35-36 sols/s on MSI RTX 2060 Super Ventus OC with Gminer 1.52 to 1.61, while miniZ does 40-41 sols on average (using solver mode=6 by default).

Can you fix this?

Running on Windows 10 btw.

[DanGB]

The miner does not print to the console when an overclock "OC" kernel is in effect.  Whatever improvement to the hash rate that results from the kernel seems minimal at best.

Miner print when selected OC kernel: "Selected OC1 solver"
When there is no OC1 kernel for card and algorithm then miner print "Selected Normal solver"

How to set OC paremeter in config files? Maybe "sample-config" needs to be updated?

Will do it in next update, example:
oc=0 1 1 0 1 1

I am running v1.60.  This is the syntax I tried but it will not work for me.  I have a PNY xlr8 1070 card in a rig with 3 1070ti cards.  I run two miner instances, one with "devices=0" to run the 1070 buy itself and the other with "devices=1 2 3" for the 1070ti cards.  For my 1070 config file, I added OC=1, but it still uses the normal solver.

Additional question...  I have another computer with two 1070 cards that I run in different miner instances because I am running one for me and one for my brother.  So in one config file, I have devices=0 and the other config file I have devices=1.  Does the "OC=" line reference the GPU in the devices= line or reference the GPU in the system?  In other words, for the config file that has devices=1, would OC=1 reference the GPU in the devices line (GPU1) or would it reference GPU0 on the system?

Thanks

[Asusrogmining]

GMiner v1.61 available for download

v1.61
+ improved compatibility with large rigs (>= 13 GPUs)
+ improved launch time of miner

Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta

Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases/tag/1.61

Hi,
What is the command of these parameters?

retry counts
retry delay
job timeout

In the case of a connection error, Gminer closes itself after some tries for the re-connection. Almost all well-know miners have these parameters. By increasing the number of retries and also increasing the timeout, the miner remains open if a connection error occurs. Please take a look at Claymore:

https://bitcointalk.org/index.php?topic=1433925.0