GMiner v3.44 Dero/Karlsen/Radiant/Ergo+IronFish+ZIL/KAWPOW/Equihash/Cortex

[mnanut]

I've stopped using gminer. 

[veritech]

And gminer also work with MRR and nicehash pool if i mine BEAM, only grin29 have a problem

same problem for me. hope this works soon, bminer is so slow!

[melt7777]

Dear gminer developers:

I am very personally disappointed to see this. We like offering choices of miners to our customers and friends but we cannot support stealing, whether the market is doing well or not.

Lolliedieb is a hardworking pioneer and talented coder and overall plus to the miners. And a friend. If it is true what has been shown in this thread, please reconsider stealing and reselling his code. In the meantime we may be removing formal support for gminer.

Thank you all other miners posting here, and for keeping crypto honest and fair and fun!

~ melt
getpimp.org | miner.farm

[cryptoyes]

does lolMiner work on linux for Nvidia for grin29s?

[fistsofgod]

this code dispute has nothing with do with other uses of gminer, which i enjoy and continue to support.

[Lolliedieb]

this code dispute has nothing with do with other uses of gminer, which i enjoy and continue to support.

You are totally right on it.
Purely from performance characteristics its clear that the cuda codes for Beam and likely also for all the other algorithms are own work and original.
The fraud is only on the recently introduced AMD Beam code that seems to be just the lolMiner code with small modification (two kernels renamed and one kernel doing a small extra output that their miner seems to need) but with double fee. Only purpose: pushing me out of the Beam market and getting more of the cake. And this is not fair. As said, I believe the other codes are their own work and on professional basis I must admit I am always impressed by the speed this cuda codes have. But with this AMD code you gone too far.

[UnclWish]

this code dispute has nothing with do with other uses of gminer, which i enjoy and continue to support.

You are totally right on it.
Purely from performance characteristics its clear that the cuda codes for Beam and likely also for all the other algorithms are own work and original.
The fraud is only on the recently introduced AMD Beam code that seems to be just the lolMiner code with small modification (two kernels renamed and one kernel doing a small extra output that their miner seems to need) but with double fee. Only purpose: pushing me out of the Beam market and getting more of the cake. And this is not fair. As said, I believe the other codes are their own work and on professional basis I must admit I am always impressed by the speed this cuda codes have. But with this AMD code you gone too far.

Agreed.
I'm use lolMiner for BEAM on AMD. Lolliedieb, please add support for grin algos in your miner for AMD cards and all AMD miners go to your miner!

[starlilyth]

this code dispute has nothing with do with other uses of gminer, which i enjoy and continue to support.

It begs the question though - how much other code in gminer is simply ripped off from other developers? How much original code is in gminer at all? Thieves are thieves..

[somaton]

But did you ever thought how many miners with integrated dev fee are using some parts of original and free ccminer? It is open source, so anybody can do same things, thats why we have closed source miners.

[columbiamining]

I've also stopped using gminer until Zminer777 addresses these accusations. This is a despicable thing to do to another hard-working developer. And to charge double on top of it all is just disgusting to me. If this is in fact true, and it appears so, Zminer should be ashamed. At least take the time to code your own kernels rather than steal other people's hard work and put your name on it.

[Howardroid]

i got BSOD system service exception windows 10 after 24+ hours mining Grin with Gminer v1.34

[bigjee]

Can someone return the favor and rip this guys code and make the dev fee 0% or 0.5% please.

Thanks.

[alucard20724]

Can someone return the favor and rip this guys code and make the dev fee 0% or 0.5% please.

Thanks.

no, no. no... it has to be double, otherwise it doesn't mean anything.   

[zeebar]

I've also stopped using gminer until Zminer777 addresses these accusations. This is a despicable thing to do to another hard-working developer. And to charge double on top of it all is just disgusting to me. If this is in fact true, and it appears so, Zminer should be ashamed. At least take the time to code your own kernels rather than steal other people's hard work and put your name on it.

.

You guys are such drama queens. He only borrowed a small snippet of code and for AMD beam only. The rest of the miner is fine unless your mining Beam with a AMD card it should be a non issue.

[BigHarryArmsi]

I will continue to run lolMiner on my AMD cards. Sorry to hear of this dustup as I love this Gminer v1.08 on my Nvidia cards running 144_5 because it Rocks!
So I came by to ask if this existing v1.08 Gminer supports RTX cards and the new GTX1660s on 144_5 and if anyone has any hashing numbers? I've never seen a reason to upgrade this miner on 144_5.
I'm really disappointed to hear about this apparent plagiarism if true. It needs to be set right!

[Newbiteck]

Hello,
it's normal with Gminer V1.34 i had a lot of stale share on GRIN29 and GRIN31 i  returned  V1.33 i had 0 stale share

[george2019]

1.34 build has quite good average hashrate increase on f2pool european server:

https://i.imgur.com/jaAP52S.png
https://i.imgur.com/qSyAzBl.png
https://i.imgur.com/hjIyT1d.png

well 1.33 build also had around 28g/sec on miner but hashrate was below 30g/sec in 24 hour period, now rejected shares is 1.5% but hashrate increased around 3-4g.sec in fpool, maybe i even go 33g/sec after 24 hour non stop mining, with bminer 14.0 build i had 31g.sec but cpu usage was higher than gminer 1.34, daily rejected shares was around 1-1.5% with bminer as well, so i will use gminer 1.34 for now, by the way bminer newer builds always had lower hashrates both pool and miner for my 5 gpu build than 14.0 older build, gminer 1.34 is first build that has higher hashrate than 14.0 bminer build for my rig, well with bminer 14.0 i had only 27.2g/sec hashrate, with 15.0.1 only 16.7g/sec, so if gminer 1.34 has more or less same optimizations than bminer with 28g.sec miner hashrate it should achieve around 1g/sec higher hashrate in f2pool, average fidelity increase is the key to achieve higher hashrates as well as some kernel optimizations, as for beam hashrate i have around 126-127 sols on my 5gpu rig using tdp 70% and memory +500 as well as some core oc

[veritech]

still getting write timeout errors , mining to Miningrigrentals stratum which points to nicehash. (direct to nicehash works).
this was the same error we were getting before 1.28 mining straight to nicehash. hope it's fixed soon! thanks

[installer1983]

parametr --devices 1 2  not working on v1.34 fix it please

[Dr_Victor]

still getting write timeout errors , mining to Miningrigrentals stratum which points to nicehash. (direct to nicehash works).
this was the same error we were getting before 1.28 mining straight to nicehash. hope it's fixed soon! thanks

I have  timeout errors too. It needs to be fixed.