lolMiner 1.51: 100% LHR unlock, new dual tuning, 5G zombie mode

[raptorman]

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

[1656504144]

1656504144

[1656504144]

1656504144

[Lolliedieb]

Hi @Lolliedieb

Mining beam with your miner...have few issues with it.

1. Cannot make logfile from win7?... tried everything
2. Talked with pool owner cause he can make server log for my miners and he says there is some duplicate shares of my miners. He sent it to me. Weird thing that when check on miner there is only accepted shares...no stale and no duplicate if those are different?!
3. How to check from miner is there stale shares?
4. When will you make something like triggering with some keyboard letter, for example S, so can check shares, temps, gpu fans etc? I think it is time for making this.
5. You are not on discord anymore?

Cheers

Hi there,

1. Good question ... need to set up a Windows 7 system to check myself, on Win 10 (just checked) it works. What is needed is that there is an empty folder "logs" in the directory of the miner and using parameters --logs 1. I will check back on that.
2. Thats indeed odd - the miner reports about accepted shares only when pool did send an accept message. Can you send me the thing the pool host send you in a private message? (What algorithm is this by the way? Every code is a bit different...)
3. Currently you can not distinguish. For almost every stratum protocol you get back only "accepted" or "rejected", but barely a reason. 0.7 and 0.6 are different here: 0.6 submits every solution found, independently if already a new job did arrive or not, while for most coins except Beam 0.7 does filter out the stale ones. For Beam it is different, because there the stratum specs allow submitting old shares if they belong to same block height, so some pools (sunpool, sparkpool...) credit stale shares, some do not. By the way if someone is interested in statistics: On my Beam fee account (that should be an average of all miners using my miner) we are at 0.04% rejected shares, 1.2% delayed / stale shares and 98,74% valid + in time.
4. I am planning to add more statistics to the long stats as well as the API - the keyboard trigger is an interesting idea, will check how easy that is to do.
5. I am still there - from time to time. But last week was extremely busy working - a bit too much. Need to step a little shorter. But before (next week) will release 0.8 with a solution to the Nicehash problem on 144/5 and one new algorithm

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?

[Frangomel]

Hi @Lolliedieb

Mining beam with your miner...have few issues with it.

1. Cannot make logfile from win7?... tried everything
2. Talked with pool owner cause he can make server log for my miners and he says there is some duplicate shares of my miners. He sent it to me. Weird thing that when check on miner there is only accepted shares...no stale and no duplicate if those are different?!
3. How to check from miner is there stale shares?
4. When will you make something like triggering with some keyboard letter, for example S, so can check shares, temps, gpu fans etc? I think it is time for making this.
5. You are not on discord anymore?

Cheers

Hi there,

1. Good question ... need to set up a Windows 7 system to check myself, on Win 10 (just checked) it works. What is needed is that there is an empty folder "logs" in the directory of the miner and using parameters --logs 1. I will check back on that.
2. Thats indeed odd - the miner reports about accepted shares only when pool did send an accept message. Can you send me the thing the pool host send you in a private message? (What algorithm is this by the way? Every code is a bit different...)
3. Currently you can not distinguish. For almost every stratum protocol you get back only "accepted" or "rejected", but barely a reason. 0.7 and 0.6 are different here: 0.6 submits every solution found, independently if already a new job did arrive or not, while for most coins except Beam 0.7 does filter out the stale ones. For Beam it is different, because there the stratum specs allow submitting old shares if they belong to same block height, so some pools (sunpool, sparkpool...) credit stale shares, some do not. By the way if someone is interested in statistics: On my Beam fee account (that should be an average of all miners using my miner) we are at 0.04% rejected shares, 1.2% delayed / stale shares and 98,74% valid + in time.
4. I am planning to add more statistics to the long stats as well as the API - the keyboard trigger is an interesting idea, will check how easy that is to do.
5. I am still there - from time to time. But last week was extremely busy working - a bit too much. Need to step a little shorter. But before (next week) will release 0.8 with a solution to the Nicehash problem on 144/5 and one new algorithm

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?

Will send pm soon...so check it out...thanks on your answer.

2.it is on equihash 150/beam

[raptorman]

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?
[/quote]

Hello, It stuck with btg (144/5). Not try other algo.

[justoiurii]

Hi @Lolliedieb

Mining beam with your miner...have few issues with it.

1. Cannot make logfile from win7?... tried everything
2. Talked with pool owner cause he can make server log for my miners and he says there is some duplicate shares of my miners. He sent it to me. Weird thing that when check on miner there is only accepted shares...no stale and no duplicate if those are different?!
3. How to check from miner is there stale shares?
4. When will you make something like triggering with some keyboard letter, for example S, so can check shares, temps, gpu fans etc? I think it is time for making this.
5. You are not on discord anymore?

Cheers

Hi there,

1. Good question ... need to set up a Windows 7 system to check myself, on Win 10 (just checked) it works. What is needed is that there is an empty folder "logs" in the directory of the miner and using parameters --logs 1. I will check back on that.


Hello)
Will you fix AUTO192_7 in new ver?
2. Thats indeed odd - the miner reports about accepted shares only when pool did send an accept message. Can you send me the thing the pool host send you in a private message? (What algorithm is this by the way? Every code is a bit different...)
3. Currently you can not distinguish. For almost every stratum protocol you get back only "accepted" or "rejected", but barely a reason. 0.7 and 0.6 are different here: 0.6 submits every solution found, independently if already a new job did arrive or not, while for most coins except Beam 0.7 does filter out the stale ones. For Beam it is different, because there the stratum specs allow submitting old shares if they belong to same block height, so some pools (sunpool, sparkpool...) credit stale shares, some do not. By the way if someone is interested in statistics: On my Beam fee account (that should be an average of all miners using my miner) we are at 0.04% rejected shares, 1.2% delayed / stale shares and 98,74% valid + in time.
4. I am planning to add more statistics to the long stats as well as the API - the keyboard trigger is an interesting idea, will check how easy that is to do.
5. I am still there - from time to time. But last week was extremely busy working - a bit too much. Need to step a little shorter. But before (next week) will release 0.8 with a solution to the Nicehash problem on 144/5 and one new algorithm

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?

Hello) Will you fix AUTO192_7 in new ver?

[Lolliedieb]

Hello) Will you fix AUTO192_7 in new ver?

Yes that will be fixed as well


@Frangomel:

thanks for the log. That are indeed much more then should usually happen. Is it the 3G or the 4G code (or the 4G ASM) and what version of the miner? Will wireshark that version myself on a test sys to see if I see so many duplicates, too.

[justoiurii]

Hello) Will you fix AUTO192_7 in new ver?

Yes that will be fixed as well

Thanks a lot) Would you please share .bat for AUTO192_7 (for example zergpool) for the new ver?

[raptorman]

Hi @Lolliedieb

Mining beam with your miner...have few issues with it.

1. Cannot make logfile from win7?... tried everything
2. Talked with pool owner cause he can make server log for my miners and he says there is some duplicate shares of my miners. He sent it to me. Weird thing that when check on miner there is only accepted shares...no stale and no duplicate if those are different?!
3. How to check from miner is there stale shares?
4. When will you make something like triggering with some keyboard letter, for example S, so can check shares, temps, gpu fans etc? I think it is time for making this.
5. You are not on discord anymore?

Cheers

Hi there,

1. Good question ... need to set up a Windows 7 system to check myself, on Win 10 (just checked) it works. What is needed is that there is an empty folder "logs" in the directory of the miner and using parameters --logs 1. I will check back on that.
2. Thats indeed odd - the miner reports about accepted shares only when pool did send an accept message. Can you send me the thing the pool host send you in a private message? (What algorithm is this by the way? Every code is a bit different...)
3. Currently you can not distinguish. For almost every stratum protocol you get back only "accepted" or "rejected", but barely a reason. 0.7 and 0.6 are different here: 0.6 submits every solution found, independently if already a new job did arrive or not, while for most coins except Beam 0.7 does filter out the stale ones. For Beam it is different, because there the stratum specs allow submitting old shares if they belong to same block height, so some pools (sunpool, sparkpool...) credit stale shares, some do not. By the way if someone is interested in statistics: On my Beam fee account (that should be an average of all miners using my miner) we are at 0.04% rejected shares, 1.2% delayed / stale shares and 98,74% valid + in time.
4. I am planning to add more statistics to the long stats as well as the API - the keyboard trigger is an interesting idea, will check how easy that is to do.
5. I am still there - from time to time. But last week was extremely busy working - a bit too much. Need to step a little shorter. But before (next week) will release 0.8 with a solution to the Nicehash problem on 144/5 and one new algorithm

Hello @Lollidieb,

I'm mining with vega 64 cards, and after some hours one card  stuck to 0 sol/s in a 8 cards rig. What is the problem. Other mining software works fine.

This happened with 0,6 and 0,7 miner too. Tried several amd driver, but same problem.

Please help.

Hello
Can you tell me what algorithm you did use where it gets stucked? Or does this happen for all algos?

Lollidieb, It's stucked with btg (144/5). Not try other algo.

[Frangomel]

Hello) Will you fix AUTO192_7 in new ver?

Yes that will be fixed as well


@Frangomel:

thanks for the log. That are indeed much more then should usually happen. Is it the 3G or the 4G code (or the 4G ASM) and what version of the miner? Will wireshark that version myself on a test sys to see if I see so many duplicates, too.

No problem. There are both 3g and 4g cards so everything involved . No asm just windows mining. Miner is 0.7 one before this newest version.

[restless]

Any solution for
"No OpenCL devices found in your system. " ?
on Nvidia systems (Win10)

[UselessGuru]

Any solution for
"No OpenCL devices found in your system. " ?
on Nvidia systems (Win10)

Did you verify your OpenCL config? Gpu-Z should recognize your card (Checkbox Computing OpenCL should be ticked).
If not try re-installing your GPU drivers (for Nvidia install the full package).

[OJDrinker]

Does anyone have lolminer 0.5? It said 0.7 was faster so I deleted it without checking (like an idiot) and 0.7 is slower for MNX for me. Undelete didn't work, it was already overwritten.

[4ward]

Does anyone have lolminer 0.5? It said 0.7 was faster so I deleted it without checking (like an idiot) and 0.7 is slower for MNX for me. Undelete didn't work, it was already overwritten.

https://github.com/Lolliedieb/lolMiner-releases/releases

[CoreyM]

@lolMiner

Thank you for adding Vidulum support! Those of you who have not checked us out yet take a quick look-see 

website: https://vidulum.app

discord: https://discord.gg/QhV2Wx6

Vidulum App and Blockchain
Vidulum is not just a cryptocurrency, it is a platform that is comprised of the Vidulum Blockchain ($VDL) and Application (https://vidulum.app).  The Vidulum App is our foundation, providing a web-based, multi-asset wallet that rewards users for their participation.

[joeykolb]

WHAT IS THE RIGHT CONFIG? for vidulum
 its done , working on zergpool
..only its disconnecting a lot, and reconnects , saying:Warning: index out of bounds

[Docice]

I don’t understand why to use this miner on red ones, if these algos are for green ones ?! Even 1050ti faster than rx580. My personal opinion is that this miner is for siphoning money for the developer. Unfortunately, this miner has no competition. We would see a different speed, a vivid example of this is the lyra2z algorithm.

[laik2]

I don’t understand why to use this miner on red ones, if these algos are for green ones ?! Even 1050ti faster than rx580. My personal opinion is that this miner is for siphoning money for the developer. Unfortunately, this miner has no competition. We would see a different speed, a vivid example of this is the lyra2z algorithm.

You are driving far away from your competition. I’d advise you to think before post or accuse.

[Kep2077]

Any chance that new release will contain new asm kernels for GPUs like Hawaii ?

[neuromancer4867]

Anyone have this miner running on AION on older AMD cards like R9 290 or Fury? If so, any idea of hash rate?

[Lolliedieb]

Any solution for
"No OpenCL devices found in your system. " ?
on Nvidia systems (Win10)

Well it seems that the Nvidia OpenCL drivers are missing. In the most recent Nvidia drivers it should ship with the driver, before the OpenCL component was part of the Cuda Toolkit. Maybe a quick re-install of driver already fixes this.

Does anyone have lolminer 0.5? It said 0.7 was faster so I deleted it without checking (like an idiot) and 0.7 is slower for MNX for me. Undelete didn't work, it was already overwritten.

Oh, on what card is that? Something that should not have happened - well each card is different, the MNX part could get a big rework any ways ...
Anyways I will have a look if I find the 0.5 to upload it again.

WHAT IS THE RIGHT CONFIG? for vidulum
 its done , working on zergpool
..only its disconnecting a lot, and reconnects , saying:Warning: index out of bounds

--coin VDL is the right config for it
But that reconnects should not be. Out of bounds means somehow the pool sending less parameters then the miner expects. I will have a check if there is something wrong with the stratum.

I don’t understand why to use this miner on red ones, if these algos are for green ones ?! Even 1050ti faster than rx580. My personal opinion is that this miner is for siphoning money for the developer. Unfortunately, this miner has no competition. We would see a different speed, a vivid example of this is the lyra2z algorithm.

You are driving far away from your competition. I’d advise you to think before post or accuse.

Well ... what to say about this. Nothing best.
I have to admit my code may not be fastest, but there are barely opportunities to learn from. But same way: If its slow then I do not earn any thing, because there are better things to mine, so somehow it should be fair?
I can for example say that in October and November with 144/5 and Aion together I made about 350$ - clearly because my Nvidia codes were not so quick as the closed source Cuda miners and on AMD there was no competition but better mining opportunities. So for me the 350 was kind of fair , especially when considering that I do that not full time and its more a hobby. Else I could not justify putting up to 100 hours per month into this. 

Regarding the Speed: I am sure a few more % are possible, but also that its not easy to achieve it - else won't there be others trying to do it - or just do it? Devs follow the path where the money is, you saw that at gminer who gave AMD support for Beam because with that you can earn money - but are they faster? No.

I could explain why AMD does so hard at Equihash coins but that would be too technical right now. Hint: cache line size and the more difficult to make writing coalesced.

Any chance that new release will contain new asm kernels for GPUs like Hawaii ?

I can do more ASM kernels, but at the moment only on ROCm, because that allows inline asm. But not got the impression many were willing to change driver for the higher speed. Unfortunately my attempts to make same work with normal drivers failed so far - and doing that experiments took me weeks of testing :/