WildRig Multi 0.40.5 multi-algo miner with low dev-fee (AMD/NVIDIA/INTEL)

[andrucrypt]

is it possible to reduce donate to lower than 2% on honeycomb?

try to do it but miner still say that donate is 2%

wildrig.exe --donate-level=1

there is some exception, for wildkeccak and honeycomb donation level is always 2%

[ALEX_RAA]

is it possible to reduce donate to lower than 2% on honeycomb?

try to do it but miner still say that donate is 2%

wildrig.exe --donate-level=1

there is some exception, for wildkeccak and honeycomb donation level is always 2%

ok, may be in future you will describe this in first page of this thread or in help section?

[mollarri]

Uploaded hotfix.

algo xevan rx560 on zergpool work properly

vega56/64 only invalid shares
 

[andrucrypt]

Uploaded hotfix.

algo xevan rx560 on zergpool work properly

vega56/64 only invalid shares
 

hmm, pretty strange bug O_o Will check what hashfunc produces wrong result.

ok, may be in future you will describe this in first page of this thread or in help section?

yeah, will do an update

[andrucrypt]

This is a huge surprise. SHA512 for 128 bytes doesn't work on Vega, while same code compiled for Polaris - works, and same code(less calls) for 64 bytes works too O_O I "like" AMD OpenCL so much )

[andrucrypt]

Uploaded hotfix.

algo xevan rx560 on zergpool work properly

vega56/64 only invalid shares
 

Ok, fixed now, thanks! Will prepare new build soon, with another optimization to x16 family.

[scryptr]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

[andrucrypt]

0.16.2 beta
- fixed xevan on Vega
- another improve to x16-like algorithms for specific hashorder(SIMD at start)

[andrucrypt]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

What pool? Did you try re-download scratchpad? How many cards?

[scryptr]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

What pool? Did you try re-download scratchpad? How many cards?

LUCKYPOOL, NO, 6 CARDS--

The scratchpad has been updating successfully, I did not change it from the pad left by WildRig v10.5.  I could "prime the pump", and restart after a wget download, I suppose.  The cards are running faster on the v16.0 release, near 2.0MH/s per card.

I am running on ethOS, and the rig reports 12MH/s (rounded).    Previously, it was running at 11.4MH/s.  I have the intensity at 22x256, and have tried lowering the intensity with neutral results.  The reject rate is not lessened, but the hashrate is lower.

Any suggestions are welcome, and thanks for adding BoolBerry!       --scryptr

EDIT:  After downloading a fresh scratchpad, and no other changes, the rejects are still present.       --scryptr

[mollarri]

Uploaded hotfix.

algo xevan rx560 on zergpool work properly

vega56/64 only invalid shares
 

Ok, fixed now, thanks! Will prepare new build soon, with another optimization to x16 family.

thanks!

[andrucrypt]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

What pool? Did you try re-download scratchpad? How many cards?

LUCKYPOOL, NO, 6 CARDS--

The scratchpad has been updating successfully, I did not change it from the pad left by WildRig v10.5.  I could "prime the pump", and restart after a wget download, I suppose.  The cards are running faster on the v16.0 release, near 2.0MH/s per card.

I am running on ethOS, and the rig reports 12MH/s (rounded).    Previously, it was running at 11.4MH/s.  I have the intensity at 22x256, and have tried lowering the intensity with neutral results.  The reject rate is not lessened, but the hashrate is lower.

Any suggestions are welcome, and thanks for adding BoolBerry!       --scryptr

EDIT:  After downloading a fresh scratchpad, and no other changes, the rejects are still present.       --scryptr

hmm, what if try --opencl-launch auto? Also how that rejects appear. Between accepted shares, or just starting to be rejected until new job? I was running my small rig(4xRX460) for more than 3 days and no problem %)

[scryptr]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

What pool? Did you try re-download scratchpad? How many cards?

LUCKYPOOL, NO, 6 CARDS--

The scratchpad has been updating successfully, I did not change it from the pad left by WildRig v10.5.  I could "prime the pump", and restart after a wget download, I suppose.  The cards are running faster on the v16.0 release, near 2.0MH/s per card.

I am running on ethOS, and the rig reports 12MH/s (rounded).    Previously, it was running at 11.4MH/s.  I have the intensity at 22x256, and have tried lowering the intensity with neutral results.  The reject rate is not lessened, but the hashrate is lower.

Any suggestions are welcome, and thanks for adding BoolBerry!       --scryptr

EDIT:  After downloading a fresh scratchpad, and no other changes, the rejects are still present.       --scryptr

hmm, what if try --opencl-launch auto? Also how that rejects appear. Between accepted shares, or just starting to be rejected until new job? I was running my small rig(4xRX460) for more than 3 days and no problem %)

LOWERING CLOCKS--

I lowered my clocks to 1100/2000 (core/mem) from 1150/2050.  Default is 1350/2000.  Initially, I now see fewer rejects, but the hash rate is now 11.5MH/s for the rig. and 1.91MH/s for each card.

I need to mow the lawn!  Will check back in a while for a more reliable readout.  Thanks!       --scryptr

[andrucrypt]

HIGH REJECT RATE IN BOOLBERRY--

I am running the new  (v16.0) WildRig-Multi on Linux, and mining BoolBerry.  Up until yesterday, I was using WildRig v10.5.  However, the new version runs about 10% rejects!

Any suggestions?  My cards are RX580, 8GB.       --scryptr

What pool? Did you try re-download scratchpad? How many cards?

LUCKYPOOL, NO, 6 CARDS--

The scratchpad has been updating successfully, I did not change it from the pad left by WildRig v10.5.  I could "prime the pump", and restart after a wget download, I suppose.  The cards are running faster on the v16.0 release, near 2.0MH/s per card.

I am running on ethOS, and the rig reports 12MH/s (rounded).    Previously, it was running at 11.4MH/s.  I have the intensity at 22x256, and have tried lowering the intensity with neutral results.  The reject rate is not lessened, but the hashrate is lower.

Any suggestions are welcome, and thanks for adding BoolBerry!       --scryptr

EDIT:  After downloading a fresh scratchpad, and no other changes, the rejects are still present.       --scryptr

hmm, what if try --opencl-launch auto? Also how that rejects appear. Between accepted shares, or just starting to be rejected until new job? I was running my small rig(4xRX460) for more than 3 days and no problem %)

LOWERING CLOCKS--

I lowered my clocks to 1100/2000 (core/mem) from 1150/2050.  Default is 1350/2000.  Initially, I now see fewer rejects, but the hash rate is now 11.5MH/s for the rig. and 1.91MH/s for each card.

I need to mow the lawn!  Will check back in a while for a more reliable readout.  Thanks!       --scryptr

Try 1150/1750, so memory will be stock. No sense to reduce core(core can provide wrong results as I remember only on Vega).

[scryptr]

<snip --JUST LOOK UP THE PAGE IF YOU NEED TO--snip>

Try 1150/1750, so memory will be stock. No sense to reduce core(core can provide wrong results as I remember only on Vega).

DEFAULT/STOCK IS 1350/2000--

I tried 1150/1750 and the hash rate dropped to 1.6MH/s per GPU, ~10MH/s for the rig.  After changing the configuration to 1150/2000 and rebooting, the rig seemed to behave well.  While I was outside it was mining ok at 1100/2000 clocks, with 345 accepts and 6 rejects at 11.5MH/s for the rig.

Currently, the rig shows 100 accepts with 1 reject at 1150/2000, and the rig is hashing at 11.75MH/s.  It has been mining for about 40 minutes.  Maybe it can be pushed harder somehow, but it seems ok.  The wattage per card is less than 90W in the console report.       --scryptr

[Mashy81]

Any tips on where to start with vegas on honeycomb. I have tried different clocks on memory and core but crash all the time. Might be the auto intensity maybe.

[andrucrypt]

Any tips on where to start with vegas on honeycomb. I have tried different clocks on memory and core but crash all the time. Might be the auto intensity maybe.

This algo needs stable core, so check your voltage. As mentioned in OP I use 1000mV for my Vega 64. Also you can try to decrease the intensity.

[andrucrypt]

<snip --JUST LOOK UP THE PAGE IF YOU NEED TO--snip>

Try 1150/1750, so memory will be stock. No sense to reduce core(core can provide wrong results as I remember only on Vega).

DEFAULT/STOCK IS 1350/2000--

I tried 1150/1750 and the hash rate dropped to 1.6MH/s per GPU, ~10MH/s for the rig.  After changing the configuration to 1150/2000 and rebooting, the rig seemed to behave well.  While I was outside it was mining ok at 1100/2000 clocks, with 345 accepts and 6 rejects at 11.5MH/s for the rig.

Currently, the rig shows 100 accepts with 1 reject at 1150/2000, and the rig is hashing at 11.75MH/s.  It has been mining for about 40 minutes.  Maybe it can be pushed harder somehow, but it seems ok.  The wattage per card is less than 90W in the console report.       --scryptr

Can you press p(this will pause mining) and then r(resume mining) when you get rejects again, and check will it reduce new rejects for next hour? If so, probably I found a problem.

[scryptr]

<snip --JUST LOOK UP THE PAGE IF YOU NEED TO--snip>

Try 1150/1750, so memory will be stock. No sense to reduce core(core can provide wrong results as I remember only on Vega).

DEFAULT/STOCK IS 1350/2000--

I tried 1150/1750 and the hash rate dropped to 1.6MH/s per GPU, ~10MH/s for the rig.  After changing the configuration to 1150/2000 and rebooting, the rig seemed to behave well.  While I was outside it was mining ok at 1100/2000 clocks, with 345 accepts and 6 rejects at 11.5MH/s for the rig.

Currently, the rig shows 100 accepts with 1 reject at 1150/2000, and the rig is hashing at 11.75MH/s.  It has been mining for about 40 minutes.  Maybe it can be pushed harder somehow, but it seems ok.  The wattage per card is less than 90W in the console report.       --scryptr

Can you press p(this will pause mining) and then r(resume mining) when you get rejects again, and check will it reduce new rejects for next hour? If so, probably I found a problem.

I WILL TRY THAT--

Just getting my coffee today, and taking a look at the rig.  Generally, I am seeing more rejects than with WildRig 10.5.  I will download the latest release and work with it rather than my currently installed v16.0 WildRig-Multi.

Bottom line: I get higher hashrates but produce less BoolBerry since using WildRig-Multi.       --scryptr

[Mashy81]

Any tips on where to start with vegas on honeycomb. I have tried different clocks on memory and core but crash all the time. Might be the auto intensity maybe.

This algo needs stable core, so check your voltage. As mentioned in OP I use 1000mV for my Vega 64. Also you can try to decrease the intensity.

Thanks that helps. I lowered intensity so I could get it to run overnight. I will play with voltage now