Pages:
Author

Topic: GMiner v3.24 Ergo+KASPA+ZIL/KAWPOW/Equihash/Cortex - page 92. (Read 306918 times)

jr. member
Activity: 312
Merit: 2
Compare v1.33 and v1.34 on pool side, in v1.34 gps can be slightly less, however fidelity significantly better +5%

Fidelity improved in 1.34 for all cards i have(1070\1080\1080ti), but in 1.33 as you've said already there were no optimizations for 1080 kernels, so I was hoping that there will be some day Roll Eyes
member
Activity: 488
Merit: 37
Optimize kernels for GTX1080 on grin29 please please please))) They didnt get any gain in 1.33+ while GTX1070+ had
Compare v1.33 and v1.34 on pool side, in v1.34 gps can be slightly less, however fidelity significantly better +5%
jr. member
Activity: 312
Merit: 2
Optimize kernels for GTX1080 on grin29 please please please))) They didnt get any gain in 1.33+ while GTX1070+ had
member
Activity: 488
Merit: 37
Zminer777 so now what? Are you just going to ignore the claims that you stole lolminer code?
stole? How lolminer understand it? Stole gminer kernels? GMiner detected hacker injection and feed fake sources to hacker.
We are working on optimization of beam amd kernels, also we are working on cuckoo cycle amd implementation.
Future updates for amd cards will answer on your questions.
jr. member
Activity: 230
Merit: 1
Zminer777 so now what? Are you just going to ignore the claims that you stole lolminer code?
member
Activity: 488
Merit: 37
Hi i think i find something special exception.

If i use gminer in nicehash for grin29 works perfectly, but if i want to use it to miningrigrental for grin29 i receive this error:

+----------------------------------------------------------------+
|                          GMiner v1.33                          |
+----------------------------------------------------------------+
Algorithm:          Cuckaroo 29 "Grin"
Stratum server:    
  host:             stratum://eu-01.miningrigrentals.com:3322
  user:             XXXX.XXXXXX
  password:         XXXX
Power calculator:   on
Color output:       on
Watchdog:           on
API:                http://127.0.0.1:3333
Log to file:        off
Selected devices:   GPU0
Temperature limits: 90C
------------------------------------------------------------------
18:50:03 Connected to eu-01.miningrigrentals.com:3322
18:50:05 Authorized on Stratum Server
18:50:05 New Job: 1766548523417 Difficulty: 1
18:50:05 Started Mining on GPU0: ZOTAC GeForce GTX 1080 Ti 11GB
18:50:17 Connection Error: Write timed out
18:50:22 Connected to eu-01.miningrigrentals.com:3322
18:50:23 Authorized on Stratum Server


my miner settings when i use normal nicehash (and works no problem):
--algo cuckaroo29 --server grincuckaroo29.eu.nicehash.com --port 3371 --user XXXXXXXXXXXXXXXXX.rig12 --pass x --api 3333 --pec 1

my miner settings when i want to use miningrigrental grin29 (Connection Error: Write timed out)
--algo cuckaroo29 --server eu-01.miningrigrentals.com --port 3322 --user xxxx.xxxxx --pass x --api 3333

i try without passowrd also, and with ssl also same.




works just fine with these settings on rentals:

miner.exe --algo grin29 --server eu-01.miningrigrentals.com --port 3322 -- XXX.XXX --pass XXX

Ok i try again Cheesy

1. nichehash mining - works
2. when i use miningrigrental, with normal grin29 mining - works
3. when i use miningrigrental to work with nicehash pool than i receive this : Connection Error: Write timed out
Can you provide instruction how to setup option #3, I need it for testing purpose, you can send login/pass for testing via PM.
jr. member
Activity: 161
Merit: 1

What settings are you using on your 2080ti?  I was using 70 tdp. 120 core but starting having issues.
newbie
Activity: 157
Merit: 0
please add --intensity flag for CPU usage in this algos:
- Cuckaroo29/Cuckatoo31 (Grin) (Nvidia only)
- Cuckoo29 (Aeternity) (Nvidia only)
newbie
Activity: 7
Merit: 0
newbie
Activity: 7
Merit: 0
sr. member
Activity: 954
Merit: 250
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.
newbie
Activity: 16
Merit: 0
parametr --devices 1 2  not working on v1.34 fix it please
newbie
Activity: 20
Merit: 0
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
jr. member
Activity: 83
Merit: 3
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
newbie
Activity: 7
Merit: 0
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
newbie
Activity: 137
Merit: 0
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!
newbie
Activity: 6
Merit: 0
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.
sr. member
Activity: 703
Merit: 272
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.   Roll Eyes
full member
Activity: 434
Merit: 107
Can someone return the favor and rip this guys code and make the dev fee 0% or 0.5% please.

Thanks.
Pages:
Jump to: