[Forager] v20.04 - Profit switching miner (AMD/NVIDIA/CPU) Windows/Linux!

[MaxMidnite]

When is the next version due?

[4ward]

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 ))

[alucard20724]

new HMQ1725  software for AMD works for vega

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

[duboisi]

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

[Dr_Victor]

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

[duboisi]

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.

[alucard20724]

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.

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 <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> --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://<POOL> -u <WALLET_ADDRESS>

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

[4ward]

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.

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 <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> --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://<POOL> -u <WALLET_ADDRESS>

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

[duboisi]

Thanks very much.

[wip]

Any plans on this miner to be included: https://bitcointalk.org/index.php?topic=5027811.0

TeamRed for Lyra2z & phi2.

Thanks in advance.

[4ward]

Any plans on this miner to be included: https://bitcointalk.org/index.php?topic=5027811.0

TeamRed for Lyra2z & phi2.

Thanks in advance.

not until they have a windows version

[4ward]

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

[alucard20724]

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.

[alucard20724]

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?

[4ward]

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?

i'll fix it

[4ward]

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?

i'll fix it

Fixed in master branch (along with update to 0.11.7)

[alucard20724]

T-Rex 0.6.10
CryptoDredge 0.9.2
z-Enemy 1.21a
Bminer 10.4

and FancyIX-b5c (adds allium)

have all been released in the last couple of days

[thinkahead]

May I ask a question?

how do your soft use the infos from Whattomine?
Just for benchmark, and your software will work out a param list to running,
or will switch from coinA to coinB automatically according to the infos?

thanks.

[4ward]

May I ask a question?

how do your soft use the infos from Whattomine?
Just for benchmark, and your software will work out a param list to running,
or will switch from coinA to coinB automatically according to the infos?

thanks.

will switch from coinA to coinB automatically according to the infos

[4ward]

T-Rex 0.6.10
CryptoDredge 0.9.2
z-Enemy 1.21a
Bminer 10.4

and FancyIX-b5c (adds allium)

have all been released in the last couple of days

updates in master branch