lolMiner 1.64: Fastest Kaspa miner in market

[UnclWish]

Will you add asm version for windows?

[1685607412]

1685607412

[1685607412]

1685607412

[1685607412]

1685607412

[godzila2018]

hey.
what happened to the github links?

https://github.com/Lolliedieb/lolMiner-releases/releases/tag/0.71
?!?!

[SilverDesert]

Can lolMiner mine with NiceHash stratum servers?

[UnclWish]

Can lolMiner mine with NiceHash stratum servers?

Yes, I mined beam on nicehash via this miner.

[SilverDesert]

Thanks
Can you please show me how it done? I tried but it doesn't connect to the stratum servers.

[UnclWish]

Thanks
Can you please show me how it done? I tried but it doesn't connect to the stratum servers.

Add --tls 0 to command line.

[SilverDesert]

Thanks

[UnclWish]

Any news about asm kernels implementation in Windows version?

[bolt1909@gmail.com]

Any news about asm kernels implementation in Windows version?

Mar 1st 2020....

[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

[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.

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