[Forager] v18.08.3 - Multi-Pool profit switching miner (AMD/NVIDIA/CPU) - page 7.

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: alucard20724 on September 22, 2018, 01:29:39 AM

Quote from: 4ward on September 20, 2018, 09:52:38 AM

Forager 18.09.1 released
https://github.com/yuzi-co/Forager/releases

- Changelog:
  - CryptoDredge 0.9.1
  - SGMinerKL 1.0.6
  - SuprMiner git11
  - lolMiner 0.43b
  - BMiner 10.3
  - SGMinerFancyIX beta4b
  - zEnemy 1.20
  - T-Rex 6.6
  - Phoenix 3.5d
  - WildRig 0.10.5
  - WildRigMulti 0.11.6
  - JCEMiner 0.32n
  - EthMiner 0.16

WildRigMulti appears to be having problems with configuration within forager... my vega cards don't run wildrigmulti, and my rx570 are only getting kHash instead of Mhash.

ok.. i figured out the vega problem. it's the naming of the kernels. the kernels he has posted are gfx900.bin, but the program identifies the vegas as gfx901... i renamed the gfx900.bin file to gfx901.bin

as for the low hashrate, that is an error on forager's end. forager is recording the hash rate as khash, instead of Mhash. miner says 16000khash, pool says 16Mhash, but forager records as 16.000 khash

UPDATE... it's an API issue. WildRigMulti reports khash instead of mhash. is there a way to adjust for that in forager?

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: 4ward on September 20, 2018, 09:52:38 AM

Forager 18.09.1 released
https://github.com/yuzi-co/Forager/releases

- Changelog:
- CryptoDredge 0.9.1
- SGMinerKL 1.0.6
- SuprMiner git11
- lolMiner 0.43b
- BMiner 10.3
- SGMinerFancyIX beta4b
- zEnemy 1.20
- T-Rex 6.6
- Phoenix 3.5d
- WildRig 0.10.5
- WildRigMulti 0.11.6
- JCEMiner 0.32n
- EthMiner 0.16

WildRigMulti appears to be having problems with configuration within forager... my vega cards don't run wildrigmulti, and my rx570 are only getting kHash instead of Mhash.

4ward

member

Activity: 473

Merit: 18

Forager 18.09.1 released
https://github.com/yuzi-co/Forager/releases

- Changelog:
- CryptoDredge 0.9.1
- SGMinerKL 1.0.6
- SuprMiner git11
- lolMiner 0.43b
- BMiner 10.3
- SGMinerFancyIX beta4b
- zEnemy 1.20
- T-Rex 6.6
- Phoenix 3.5d
- WildRig 0.10.5
- WildRigMulti 0.11.6
- JCEMiner 0.32n
- EthMiner 0.16

4ward

member

Activity: 473

Merit: 18

Quote from: wip on September 18, 2018, 02:17:31 PM

Any plans on this miner to be included: https://bitcointalksearch.org/topic/ann-teamredminer-optimized-winlinux-amd-gpu-miner-for-lyra2z-and-phi2-5027811

TeamRed for Lyra2z & phi2.

Thanks in advance.

not until they have a windows version Wink

wip

newbie

Activity: 8

Merit: 0

Any plans on this miner to be included: https://bitcointalksearch.org/topic/ann-teamredminer-optimized-winlinux-amd-gpu-miner-for-lyra2z-and-phi2-5027811

TeamRed for Lyra2z & phi2.

Thanks in advance.

duboisi

full member

Activity: 202

Merit: 100

Thanks very much.

4ward

member

Activity: 473

Merit: 18

Quote from: alucard20724 on September 12, 2018, 01:35:26 AM

Quote from: duboisi on September 12, 2018, 12:46:14 AM

Would be good if added a parameter to delay launch of new miner.
Was using MinerControl and it has a "delay" parm that I set to 1.5 second.

actually, that doesn't need to be done. cryptodredge talks about this.

Quote from: cryptodredge on August 02, 2018, 10:53:57 PM

Watchdog
If you are using a third-party watchdog, you can disable the built-in watchdog by using --no-watchdog option.
Example:

Code:

CryptoDredge -a  -o stratum+tcp:// -u  --no-watchdog

Lyra2REv2 Issues
In case if you have issues with the current implementation of Lyra2REv2 (lyra2v2), you might want to try lyra2v2-old.
Example:

Code:

CryptoDredge -a lyra2v2-old -o stratum+tcp:// -u

Several Instances After a While
It seems that you are using an own restart mechanism of CryptoDredge (see the Watchdog item).

just needs to add --no-watchdog parameter for cryptodredge

Thanks for the find. Update in master branch

alucard20724

sr. member

Activity: 703

Merit: 272

Quote from: duboisi on September 12, 2018, 12:46:14 AM

Would be good if added a parameter to delay launch of new miner.
Was using MinerControl and it has a "delay" parm that I set to 1.5 second.

actually, that doesn't need to be done. cryptodredge talks about this.

Quote from: cryptodredge on August 02, 2018, 10:53:57 PM

Watchdog
If you are using a third-party watchdog, you can disable the built-in watchdog by using --no-watchdog option.
Example:

Code:

CryptoDredge -a  -o stratum+tcp:// -u  --no-watchdog

Lyra2REv2 Issues
In case if you have issues with the current implementation of Lyra2REv2 (lyra2v2), you might want to try lyra2v2-old.
Example:

Code:

CryptoDredge -a lyra2v2-old -o stratum+tcp:// -u

Several Instances After a While
It seems that you are using an own restart mechanism of CryptoDredge (see the Watchdog item).

just needs to add --no-watchdog parameter for cryptodredge

duboisi

full member

Activity: 202

Merit: 100

Would be good if added a parameter to delay launch of new miner.
Was using MinerControl and it has a "delay" parm that I set to 1.5 second.

Dr_Victor

sr. member

Activity: 954

Merit: 250

I have seen it - two miners at the same time.

duboisi

full member

Activity: 202

Merit: 100

Anyone has problem that CryptoDredge 0.9 running Neoscrypt was not killed off when switch session? It ended up having 2 miner windows running.

alucard20724

sr. member

Activity: 703

Merit: 272

new HMQ1725 software for AMD works for vega

https://bitcointalksearch.org/topic/wildrig-multi-0351-beta-2-multi-algo-miner-for-amd-nvidia-5023676

4ward

member

Activity: 473

Merit: 18

Quote from: MaxMidnite on September 06, 2018, 10:15:00 AM

When is the next version due?

Last version released just 3 days ago...

When I get enough changes for a version release to be reasonable ))

MaxMidnite

newbie

Activity: 143

Merit: 0

When is the next version due?

4ward

member

Activity: 473

Merit: 18

Quote from: twente-mining on September 06, 2018, 04:29:53 AM

Quote from: 4ward on September 05, 2018, 10:12:20 PM

Quote from: twente-mining on September 05, 2018, 03:56:04 PM

benchmarked my rigs, but they really don't like the software it seems.

Keep getting : WARNING : NO Miners above MinProfit

And it stops mining and only giving this warning.....

Which means that's it's not profitable for you to mine. If you want to ignore this, set min profit in config to large negative value

Don't see any line containing min Profit....

Guess we have to change electricity costs then ?

MinProfit_AMD = 0
MinProfit_NVIDIA = 0
MinProfit_CPU = 0

Set to negative

Or change the electricity costs as you mentioned )

twente-mining

member

Activity: 176

Merit: 10

Quote from: 4ward on September 05, 2018, 10:12:20 PM

Quote from: twente-mining on September 05, 2018, 03:56:04 PM

benchmarked my rigs, but they really don't like the software it seems.

Keep getting : WARNING : NO Miners above MinProfit

And it stops mining and only giving this warning.....

Which means that's it's not profitable for you to mine. If you want to ignore this, set min profit in config to large negative value

Don't see any line containing min Profit....

Guess we have to change electricity costs then ?

4ward

member

Activity: 473

Merit: 18

Quote from: twente-mining on September 05, 2018, 03:56:04 PM

benchmarked my rigs, but they really don't like the software it seems.

Keep getting : WARNING : NO Miners above MinProfit

And it stops mining and only giving this warning.....

Which means that's it's not profitable for you to mine. If you want to ignore this, set min profit in config to large negative value

twente-mining

member

Activity: 176

Merit: 10

benchmarked my rigs, but they really don't like the software it seems.

Keep getting : WARNING : NO Miners above MinProfit

And it stops mining and only giving this warning.....

4ward

member

Activity: 473

Merit: 18

0 will benchmark whatever is currently set and that's it. So if you set something in Wattman, it will not change it.

LeeMcTired

newbie

Activity: 27

Merit: 0

So if i change it to 0 will it benchmark at 100% initially and then lower the power limit to find the most profitable power setting afterwards?

Topic: [Forager] v18.08.3 - Multi-Pool profit switching miner (AMD/NVIDIA/CPU) - page 7. (Read 24692 times)