lolMiner v1.47 keep retuning once every hour

[kaitran1910]

First of all, I'm much appreciated all of your hard works to bring us amazing LHR solver.

One of the issue I've got lately when updating to lolMiner v1.47 is the miner keep re-tuning the LHR once every 1 hour as observed:

Issued observed within lolMiner log: Suddenly received a job with Epoch 0 as below:

Using NiceHash pool stratum+tcp://daggerhashimoto.usa-east.nicehash.com:3353 Currently using HiveOS newest version. Nvidia driver: 470.103.01

Same OC works fine in v1.46a version with driver 470.86 Issue only happened when updating HiveOS alongs with new lolMiner v1.47

[jgonzis]

First of all, I'm much appreciated all of your hard works to bring us amazing LHR solver.

One of the issue I've got lately when updating to lolMiner v1.47 is the miner keep re-tuning the LHR once every 1 hour as observed:

Issued observed within lolMiner log: Suddenly received a job with Epoch 0 as below:

Using NiceHash pool stratum+tcp://daggerhashimoto.usa-east.nicehash.com:3353 Currently using HiveOS newest version. Nvidia driver: 470.103.01

Same OC works fine in v1.46a version with driver 470.86 Issue only happened when updating HiveOS alongs with new lolMiner v1.47

That's completely normal you are doing ZIL and you don't have --enablezilcache that means the DAG Generation creates a LHR Semiock. Try adding that... normally each DAG Change creates always a semilock

[kaitran1910]

Wait but I'm not even mining ZIL ...? I'm dual mining ETH+TON. Will --enablezilcache mean anything in this scenario?

[jgonzis]

Wait but I'm not even mining ZIL ...? I'm dual mining ETH+TON. Will --enablezilcache mean anything in this scenario?

No ... Nicehash will have several switch in case their pick your rig for other user

[kaitran1910]

Much appreciated.

After switching to other pool, the problem has gone.

[jgonzis]

Much appreciated.

After switching to other pool, the problem has gone.

Many thanks for the feedback 😀

Enjoy mining

[Rom66]

I have same issues with nicehash and eth, can i fix autotune, or - - enableethcache ?

[Rom66]

It seem to be ok with - - enablezilcache!

[KevinCRM]

Much appreciated.

After switching to other pool, the problem has gone.

I have the same problem mining ETH+TON, what pool did u change? Eth or Ton pool

[KevinCRM]

It seem to be ok with - - enablezilcache!

Where do u put that? I'm new on HiveOS Would work with ETH+TON mining?

[jgonzis]

Yes for sure 1.47 will work with ETH +TON also... you can follow the guides from the YouTube Channel to configure it

[KevinCRM]

Yes for sure 1.47 will work with ETH +TON also... you can follow the guides from the YouTube Channel to configure it

I mean the --enablezilcache Ihave the same issues about miner restarting every hour with ETH+TON

[kaitran1910]

Yes for sure 1.47 will work with ETH +TON also... you can follow the guides from the YouTube Channel to configure it

I mean the --enablezilcache Ihave the same issues about miner restarting every hour with ETH+TON

For the previous question, I'm changing ETH pool.

If you want to stay on NiceHash, put the --enablezilcache in the Flight Sheet under Extra config arguments section as this example

[ABredhauer]

I have the same issue and have been running with --enablezilcache

I am mining eth/zil using shardpool + ALPH I'm seeing regular drops in hash rate every hour despite having the zil cache option enabled

[jgonzis]

I have the same issue and have been running with --enablezilcache

I am mining eth/zil using shardpool + ALPH I'm seeing regular drops in hash rate every hour despite having the zil cache option enabled

In AMD needs to be improved. In case LHR use 470.103.01 or 510.xx driver

[ABredhauer]

I have the same issue and have been running with --enablezilcache I am mining eth/zil using shardpool + ALPH I'm seeing regular drops in hash rate every hour despite having the zil cache option enabled

In AMD needs to be improved. In case LHR use 470.103.01 or 510.xx driver

This is with a 3060ti running the 510.60.02 driver

[jgonzis]

I have the same issue and have been running with --enablezilcache I am mining eth/zil using shardpool + ALPH I'm seeing regular drops in hash rate every hour despite having the zil cache option enabled

In AMD needs to be improved. In case LHR use 470.103.01 or 510.xx driver

This is with a 3060ti running the 510.60.02 driver

1.48 has improved eth+alph, it is always the same GPU?

[ABredhauer]

I have the same issue and have been running with --enablezilcache I am mining eth/zil using shardpool + ALPH I'm seeing regular drops in hash rate every hour despite having the zil cache option enabled

In AMD needs to be improved. In case LHR use 470.103.01 or 510.xx driver

This is with a 3060ti running the 510.60.02 driver

1.48 has improved eth+alph, it is always the same GPU?

Yeah just the single GPU in this rig at the moment. I’m waiting for hive to release an update that includes 1.48 to test with that version

[kaitran1910]

If you know a bit about Linux command line, you can follow this to manually update the lolMiner to v1.48: https://github.com/Lolliedieb/lolMiner-releases/discussions/1413#discussioncomment-2438121

Please note that the given guide is for updating from v1.46a to v1.47 You need to change the download link and directory accordingly

Here's my short note following that guide to manually update every single time

1. miner stop
2. cd /tmp
3. wget /*download link*/
4. tar -xvf lol<tab>
5. cd /*directory*/
6. cp lolMiner /hive/miners/lolminer/<ver>
7. miner start

Clarification for some placeholder in the code:

1. /*download link*/ : the download link for the version you want to update to. In this v1.48 case on HiveOS, it should be wget https://github.com/Lolliedieb/lolMiner-releases/releases/download/1.48/lolminer-1.48.CustomHiveOS.tar.gz
2. <tab> : here you can hit the Tab button on your keyboard to quickly generate the full file name. In this case, it should be tar -xvf lolminer-1.48.CustomHiveOS.tar.gz
3. /*directory*/ : go to the directory that's just been unzip. In this case, it should be cd lolminer
4. /hive/miners/lolminer/<ver> : depends on each version you currently have. Assuming you are using v1.47, then it should be cp lolMiner /hive/miners/lolminer/1.47

Sorry for the messy explanation. Let me know if you feel unclear 😄

[ABredhauer]

Thanks for the instructions, I've upgraded to 1.48 and will let it run for a few hours and report back

[ABredhauer]

Miner has been running for about 5 and a half hours on 1.48 now. Not seeing any significant difference in behaviour and still getting the hourly drops. The line below is roughly when I upgraded and restarted the miner

I captured 2 section of the logs - first when it switched from Eth to ZIL

And then when it switched back to zil

[jgonzis]

Miner has been running for about 5 and a half hours on 1.48 now. Not seeing any significant difference in behaviour and still getting the hourly drops. The line below is roughly when I upgraded and restarted the miner

I captured 2 section of the logs - first when it switched from Eth to ZIL

And then when it switched back to zil

Right... with nicehash DAG Changes can break that routine...

[ABredhauer]

I'm not using nicehash though? I'm using shardpool proxying ethermine

[jgonzis]

I'm not using nicehash though? I'm using shardpool proxying ethermine

You should have --enablezilcache or you will have cuts

[ABredhauer]

I'm not using nicehash though? I'm using shardpool proxying ethermine

You should have --enablezilcache or you will have cuts

Please scroll up, I already said I'm running with that option enabled

[jgonzis]

I'm not using nicehash though? I'm using shardpool proxying ethermine

You should have --enablezilcache or you will have cuts

Please scroll up, I already said I'm running with that option enabled

Sorry... we will have a look to that double dag...

[ABredhauer]

I'm not using nicehash though? I'm using shardpool proxying ethermine

You should have --enablezilcache or you will have cuts

Please scroll up, I already said I'm running with that option enabled

Sorry... we will have a look to that double dag...

All g, I'm sure you're across a lot of issues. Let me know if there's any logging I can enable to help