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

[alucard20724]

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

.....

can you implement a new Lyra2REv2 miner for AMD?

https://github.com/CryptoGraphics/lyclMiner

thanks

In current state of the miner, there would be lots of changes to Forager code required to fully support it

I have it running locally, but the device configuration is still manual due to miner's requirement of using PCIeBus id

Are you able to at least get the hashrate to display in Forager?  I'm not worried about the manual configuration of the devices.  I would think you would be able to implement it along the lines of how excavator is done.

looks like they're going to try something over at MPM.
https://github.com/MultiPoolMiner/MultiPoolMiner/issues/1894

[4ward]

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

.....

can you implement a new Lyra2REv2 miner for AMD?

https://github.com/CryptoGraphics/lyclMiner

thanks

In current state of the miner, there would be lots of changes to Forager code required to fully support it

I have it running locally, but the device configuration is still manual due to miner's requirement of using PCIeBus id

Are you able to at least get the hashrate to display in Forager?  I'm not worried about the manual configuration of the devices.  I would think you would be able to implement it along the lines of how excavator is done.

looks like they're going to try something over at MPM.
https://github.com/MultiPoolMiner/MultiPoolMiner/issues/1894

Hashrate display works. I pushed a preliminary version, but you will need to set the devices yourself in the pattern file

And to implement PCIBus I need to rewrite lots of stuff in the device detection, but i hope the developer will change the device selection

[4ward]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

[alucard20724]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

Trying it now..  benchmarked fine.  things appear to be working fine

thanks

[alucard20724]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

Trying it now..  benchmarked fine.  things appear to be working fine

thanks

getting an error.  four gpu in system.  but lyclMiner says device1 is wrong. "PCIeBusId" is incorrect inside "Device1" section

here's the error



Here's the config that was made up.





might be related to a problem that was talked about in the discord channel... don't know yet

[4ward]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

Trying it now..  benchmarked fine.  things appear to be working fine

thanks

getting an error.  four gpu in system.  but lyclMiner says device1 is wrong. "PCIeBusId" is incorrect inside "Device1" section

here's the error



Here's the config that was made up.



might be related to a problem that was talked about in the discord channel... don't know yet

Is there a difference between config generated by lyclMiner and the one generated by Forager?
If there is, can you post it? Which one is giving issues?

p.s. which Discord channel?

[alucard20724]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

Trying it now..  benchmarked fine.  things appear to be working fine

thanks

getting an error.  four gpu in system.  but lyclMiner says device1 is wrong. "PCIeBusId" is incorrect inside "Device1" section

here's the error



Here's the config that was made up.



might be related to a problem that was talked about in the discord channel... don't know yet

Is there a difference between config generated by lyclMiner and the one generated by Forager?
If there is, can you post it? Which one is giving issues?

p.s. which Discord channel?

config generated by lyclMiner



one generated by Forager



lycl generated config works fine.     Forager config gives errors.

so it seems that it isn't lyclMiner issue discussed in discord channel.   I'll send you the discord invite later... i found it in one of the forums about vertcoin.   it's in the official vertcoin discord channel

[alucard20724]

Added lyclMiner support in automatic device detection mode (without defined GpuGroups)

Trying it now..  benchmarked fine.  things appear to be working fine

thanks

getting an error.  four gpu in system.  but lyclMiner says device1 is wrong. "PCIeBusId" is incorrect inside "Device1" section

here's the error



Here's the config that was made up.



might be related to a problem that was talked about in the discord channel... don't know yet

Is there a difference between config generated by lyclMiner and the one generated by Forager?
If there is, can you post it? Which one is giving issues?

p.s. which Discord channel?

config generated by lyclMiner



one generated by Forager



lycl generated config works fine.     Forager config gives errors.

so it seems that it isn't lyclMiner issue discussed in discord channel.   I'll send you the discord invite later... i found it in one of the forums about vertcoin.   it's in the official vertcoin discord channel

ok... i'm not seeing the issue on another system that has 4 vega64 cards... i'm only seeing the issue on the system with 4 RX570 cards... might be lyclminer or it might be a system issue.  i'll have to investigate it later.

[4ward]

^ Hoe much hash do yoy get on Vega 64 on lyra2v2 lycl miner ? Can it beat 1080ti ?

from https://www.reddit.com/r/vertcoin/comments/8svyvr/amd_full_release/

AMD VEGA series
VEGA 64 -75mh/s
VEGA 56 -60mh/s
AMD 500 series
RX 580 -42mh/s
RX 570 -36mh/s
RX 560 -16mh/s
RX 550 -8mh/s
AMD 400 series
RX 480 -32mh/s
AMD 300 series
AMD 200 series
R9 280X -23mh/s
R9 270 ~13mh/s
7970- 21mh/s

[alucard20724]

lyclMiner version 0.1.5 released    Amd Lyra2v2 miner.

https://github.com/CryptoGraphics/lyclMiner/releases

[4ward]

lyclMiner version 0.1.5 released    Amd Lyra2v2 miner.

https://github.com/CryptoGraphics/lyclMiner/releases

updated, hopefully detection will work better now

define devices manually in pattern file if it doesnt work

[Sharpeich]

Please add the Wild Keccak algo support

[4ward]

Please add the Wild Keccak algo support

It is supported
Keccak is supported, not Wild Keccak

Edit:
Wild Keccak requires a scratchpad which is coin specific and its complicated to add it to an algo switching miner...

Although I will look into it )

[alucard20724]

lyclMiner version 0.1.5 released    Amd Lyra2v2 miner.

https://github.com/CryptoGraphics/lyclMiner/releases

updated, hopefully detection will work better now

define devices manually in pattern file if it doesnt work

there was an error in the config file when i tried to run and errored out.

If i manually put the devices in the pattern, then it worked

fyi... you didn't create a lyclMiner-0.1.5.json file..

[4ward]

lyclMiner version 0.1.5 released    Amd Lyra2v2 miner.

https://github.com/CryptoGraphics/lyclMiner/releases

updated, hopefully detection will work better now

define devices manually in pattern file if it doesnt work

there was an error in the config file when i tried to run and errored out.

If i manually put the devices in the pattern, then it worked

fyi... you didn't create a lyclMiner-0.1.5.json file..

all created and updated now )

[4ward]

Please add the Wild Keccak algo support

Wild Keccak is now supported (on AMD and CPU), but disabled by default

Due to high initialization time (downloading/updating scratchpad), algo switching to Wild Keccak is counter productive. Only use it if you manually mine this algo

[dudel42]

hi,

Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues.

There are a couple error messages repeated before every new interval:

Code:

Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ...             $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray

Doesn't seem to cause any problems, though.

However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again.

This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months.

[alucard20724]

Is there  a way to disable specific algos for specific pools.

reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.

thanks.

[4ward]

hi,

Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues.

There are a couple error messages repeated before every new interval:

Code:

Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ...             $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray

Doesn't seem to cause any problems, though.

However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again.

This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months.

I'll take a look. I believe the code throwing the error is redundant now
And I hope you can provide something so I can check the issue you are experiencing.
Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work

Is there  a way to disable specific algos for specific pools.

reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.

thanks.

I will add such option, I also noticed this behavior

[4ward]

hi,

Just tried the latest Forager code (cloned from github), as MegaMiner seems abandoned.. there are, however, some issues.

There are a couple error messages repeated before every new interval:

Code:

Cannot index into a null array.
At C:\miner\Forager\Include.ps1:425 char:17
+ ...             $PnpDeviceProperties = ($PnpDevices | Where-Object {$Vend ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray

Doesn't seem to cause any problems, though.

However on two out of three systems I tested, one hard crashes, and one goes into an endless error loop, something like "cannot kill process "IDLE". Unfortunately the error is not written into the log, have to catch and copy it again.

This is all on Nvidia rigs where MegaMiner has been running fine and stable for many months.

I'll take a look. I believe the code throwing the error is redundant now

Fixed in latest commit

And I hope you can provide something so I can check the issue you are experiencing.
Send me the logs, even if they don't show the errors, maybe I'll discover something since I know how it should work

Is there  a way to disable specific algos for specific pools.

reason is that when dual mining with claymore, zpool and ahash will show hi reject rates (50%) for keccak, but nicehash will be ok.

thanks.

I will add such option, I also noticed this behavior

Added now in latest commit