Topic: lolMiner 1.64: Fastest Kaspa miner in market - page 96. (Read 155842 times)

Normal, I thought... RX 580 8Gb do about 13-15 sol.

Hi guys,

Its normal for an vega64 on beam do 26,5 sol?

Only one vega 64 card in a 8cards rig after 5-10 minutes go to 0 s/s hash. The others works fine. I tried increase the virtual memory but same problem. Do you have any idea what can I do? Other software with other algorithm works fine.

0.8.8 already works for 5700, for cuckatoo31, cuckarood29, equihash192, and equihash144.    Doesn't hash from equihash125.

Will lol miner be getting an update to mine with amd rx5700xt

I have 3 7970 with hashing of 63 sol/s is not bad

BEAM on Nicehash gives incorrect shares always...
V2 works fine, but usual BEAM not... Using latest 0.8.8 version of miner.

I suppose I will assemble a couple into a small rig and use it for a heater. And a couple of BEAM, eh?

Thanks

I have a couple of rigs running on ubuntu with 6x R7 370 each. No problems at all with those.
Last few days I been trying to build another rig with HD7970 and R9 280 but those older cards are only hashing 0.2 and 0.4 sol.
I am confused if I need to add the tahiti.bin file somewhere?

Same as per the R7 370, I run ubuntu server 12.04 with fglrx 15.302 drivers. Tried to put the SDK but no changes at all.

I thought I would get more out, anyone knows? Lolliedieb any advice?

Hi folks and thank you in advance for answering my question.

I have some 8gb 480s and a few 8gb 580s doing nothing these days and am wondering what kind of hash rate y'all are getting on lolMiner BeamII. I quit running them because they consume so much power but it will be getting cold up here in the frozen North soon and thinking they will make a great heater while mining some Beam, eh?
Curious about current power consumption, hash rate, OC settings etc, etc. I'm on Win10 with a G3930 CPU.

Thanks again if you have an answer for me.

May be know working proxy software for BEAM mining?
Thanks!

For my problem, what I wrote here before:
There is a version that closing the miner lolminer is due to the temporary unavailability of servers for dev fee. Can lolminer developer do something to solve the problem?

And none of those changes sound useful so yeah, copy/paste shitcoin.

Community driven project lol.

I do not run all miners under one system, you do not understand correctly.
Each miner is a separate rig from a separate motherboard and CPU. Here is what it is:
number 1 rig - 4 video cards 7950,
number 2 and number 3 rig on 3x7950. All use lolminer 0.8.7
line lolMiner.exe --coin BEAM-II --pool beamv2.eu-new.nicehash.com --port 3378 --tls 0 --user ***.

4 rig - consists of 1070 and it uses the Gminer.
line; miner.exe --algo beamhash --server beamv2.eu-new.nicehash.com --port 3378 --user ****.

There is rig number 5, on the video card 470 - there Claymore gives ETH.

 All 5 rigs are all separate systems. This is not one computer.
So sometimes all the miners are closed at the same time, but only for lolminer. Not only the miner stops, but the miner’s window closes as well. This is not when we disconnect the rig from the Internet - then the miner window does not close and the miner writes "reconnect 3 seconds ..".
This happens for lolminer at one time. I don’t know the reason - maybe this is a loss of connection with the pool - but why does the lolminer not wait for the connection but close? On all 3 systems? So far I am solving the problem through the bat file:
@ECHO
COLOR 57
: loop
START NEW_BEAM_NICEHASH
TIMEOUT / t 2400
TASKKILL / f / im lolMiner.exe
Goto loop

For Gminer, who also solves Beam through Nice, this never happens. Why does the lolminer decide to close and how to solve this problem?
I clarify - the lolminer can work and for a long time is normal, but something happens on the pool and the lolminer closes without the ability to continue to work.

About stick your promises at least after i'm pointing this out - my respect and thanks.
About changes. "Missing" and "not needed" different things. To list of changes can adding - removed hww, added gpu mining at ui, added cpu mining for start network, fixed compilation errors, fixed ui bugs, updated core and consensus rules, fixed connecting bugs, updated bp, increased block size, and etc.  We do not following to the direction of development of beam, and talk about new or old version is wrong. In any case Grimm was born and only first release was published. We develop it You can like it or not.  Grimm have own directions. Grimm is community driven project.

Well - if you see it technically it is a code fork of the Beam Bright Boson release (so the new stuff that was added with Clear Cathode is missing). And what is changed from that are

- removed the dev funds
- replaced the pow personalization string
- replaced some wallet images / logo and copyright notices.

I hope you can see that I am not impressed and claim it is mainly a copy.
But ... there is one thing that has weight. I did promise to add it - and I usually stick to my promises. Well do not count on a specific version number, 0.8.7 and 0.8.8 were not planned when I did 0.8.6, but technical problems made me introduce that. But we may see grimm here with one of the next releases.

Grimm not copy of older code base. It's Fork (or for you all alts is just copy?) without founders rewards and without unwanted add-ons. Who decides what's old and what's new? Grimm updated to date. And the development of what is not and will not be in BEAM is underway. We have other directions. If they pay you from the fact that they take away from the miners, then this is a minus for you as the Creator of the good miner for MINERS, Not for the coins you get paid from. You are as centralized as any commercial projects. Grimm - community driven coin. Invite everyone and you on our new Release presentation on the scene at Blockchain Life 2019 And I am happy to meet in person with everyone at our stand G9. It's Gonna be 🔥hot. Grimm will show his TEETH. All in good time.

Just pushed lolMiner 0.8.8
Now the "invalid work group size" problem on Beam should be gone and I added some example bats for those who  do not like the config files.

-------------------


Sry, I do not get what exactly the problem is - if you run them all at the same time they conflict and close?  I have to admit that I did not try that but it may indeed happen when they try to use overlapping GPUs ... not sure.



You are aware that I am advisor for Beam and heavily involved in that - Grimm is nothing but a 1:1 copy of an older Beam code base... maybe I will push an update that will re-enable BeamHash I with Grimm personalization, but that has not much prio atm - first experimenting with ways to make this Beam Hash II faster on AMDs...

I have three miners - lol, Claim and Gminer. Their work on Nice without using the Nicehash shell. And only Lolminer at the same time all three are turned off and closed. I understand that this happens after a disconnect with a pool. How to make sure that this does not happen? Claimor and Gminer have no problems. Claimore on the ETH network and amd 470 video card, but lolminer (HD7950) and Gminer (1070) do the calculations on the Beam network. lolminer 0.8.7

Hi! What about Grimm, man?