and still no support for 6gb cards under win10 for cucaroo
:/
:/
that is not a fault with the miner devs.. that is something you should discuss with the coin devs
somehow bminer and nebutech had no problem implementing 5gb solvers
Topic: GMiner v3.24 Ergo+KASPA+ZIL/KAWPOW/Equihash/Cortex - page 88. (Read 307024 times)
that is not a fault with the miner devs.. that is something you should discuss with the coin devs
somehow bminer and nebutech had no problem implementing 5gb solvers
I’m actually still waiting for a GRIN windows wallet so I don’t lose what I have mined already since they expire after 60 days of no withdrawal. Anyone have an idea if that is something in thr works? Thank you!!
https://www.grin-forum.org/t/yeastplume-progress-update-thread-mar-19-to-sep-19/4303
Sometimes i have strange problem with cucko 29 and 31, miner starts, but doing nothing, log does not show anything (not showing my real btc address). Other algos does not have this problem, always starts mining. Bminer works fine always with all algos.
have had same thing
Sometimes i have strange problem with cucko 29 and 31, miner starts, but doing nothing, log does not show anything (not showing my real btc address). Other algos does not have this problem, always starts mining. Bminer works fine always with all algos.
C:\gminer>miner.exe --algo grin29 --pers auto --server grincuckaroo29.eu.nicehash.com --port 3371 --user btc.address.worker --pass x
+----------------------------------------------------------------+
| GMiner v1.36 |
+----------------------------------------------------------------+
Algorithm: Cuckaroo 29 "Grin"
Stratum server:
host: stratum://grincuckaroo29.eu.nicehash.com:3371
user: btc.address.worker
password: x
Power calculator: on
Color output: on
Watchdog: on
API: off
Log to file: off
Selected devices: GPU0 GPU1 GPU2
Intensity: 100 100 100
Temperature limits: 90C 90C 90C
------------------------------------------------------------------
C:\gminer>miner.exe --algo grin29 --pers auto --server grincuckaroo29.eu.nicehash.com --port 3371 --user btc.address.worker --pass x
+----------------------------------------------------------------+
| GMiner v1.36 |
+----------------------------------------------------------------+
Algorithm: Cuckaroo 29 "Grin"
Stratum server:
host: stratum://grincuckaroo29.eu.nicehash.com:3371
user: btc.address.worker
password: x
Power calculator: on
Color output: on
Watchdog: on
API: off
Log to file: off
Selected devices: GPU0 GPU1 GPU2
Intensity: 100 100 100
Temperature limits: 90C 90C 90C
------------------------------------------------------------------
I’m actually still waiting for a GRIN windows wallet so I don’t lose what I have mined already since they expire after 60 days of no withdrawal. Anyone have an idea if that is something in thr works? Thank you!!
Any plans for implement Grin31 Cuckatoo for 16 GB AMD cards like Radeon VII and Sapphire RX 580 16 GB? I think atleast the first will do quite nice at this algorithm..
and still no support for 6gb cards under win10 for cucaroo
:/
:/
Actually I'll let it run for a few hours before making a negative comment
Update: Hashrate is good
So, what intensity do you recommend for gtx 1080 ti on C29?
I recommend intensity 100, it's used by default. GMiner v1.36 available for download
v1.36
+ significantly decreased CPU usage for cuckoo cycle algorithms for Nvidia GPUs (up to 40%)
+ added adaptive CPU usage adjustment for cuckoo cycle algorithms (increase hashrate on weak CPUs). miner need about few minutes to adapt CPU usage on weak CPU.
+ added option to control GPU intensity (--intensity, 1-100)
Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta
Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases
So, what intensity do you recommend for gtx 1080 ti on C29? v1.36
+ significantly decreased CPU usage for cuckoo cycle algorithms for Nvidia GPUs (up to 40%)
+ added adaptive CPU usage adjustment for cuckoo cycle algorithms (increase hashrate on weak CPUs). miner need about few minutes to adapt CPU usage on weak CPU.
+ added option to control GPU intensity (--intensity, 1-100)
Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta
Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases
GMiner v1.36 available for download
v1.36
+ significantly decreased CPU usage for cuckoo cycle algorithms for Nvidia GPUs (up to 40%)
+ added adaptive CPU usage adjustment for cuckoo cycle algorithms (increase hashrate on weak CPUs). miner need about few minutes to adapt CPU usage on weak CPU.
+ added option to control GPU intensity (--intensity, 1-100)
Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta
Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases
v1.36
+ significantly decreased CPU usage for cuckoo cycle algorithms for Nvidia GPUs (up to 40%)
+ added adaptive CPU usage adjustment for cuckoo cycle algorithms (increase hashrate on weak CPUs). miner need about few minutes to adapt CPU usage on weak CPU.
+ added option to control GPU intensity (--intensity, 1-100)
Telegram group: https://t.me/gminer_equihash
Telegram beta test group: https://t.me/gminer_beta
Download links:
GitHub: https://github.com/develsoftware/GMinerRelease/releases
Guys, last 1-2 week my result does not coincide with calculate (Beam), 540m/h ~ 20 coins, but i get only ~17, check every day calculate - my result, different ~2-3 coins, maybe i not lonely with it problem? if you have all okey, pls write too, need any oppinion)) 
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
change pool.
what pool you use? or it just advice)
Guys, last 1-2 week my result does not coincide with calculate (Beam), 540m/h ~ 20 coins, but i get only ~17, check every day calculate - my result, different ~2-3 coins, maybe i not lonely with it problem? if you have all okey, pls write too, need any oppinion))
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
change pool.
Guys, last 1-2 week my result does not coincide with calculate (Beam), 540m/h ~ 20 coins, but i get only ~17, check every day calculate - my result, different ~2-3 coins, maybe i not lonely with it problem? if you have all okey, pls write too, need any oppinion))
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
PS, 1.35 miner. 1080ti rigs, leafpool(beam)
I've updated from 417.01 to latest 419.35 and noticed h\r drop in G29, at least on miner's side. Drop is really minor, but still its there...
in 1.35, miner stops reporting hashrate to awesomeminer periodically, triggering an offline notification (maybe when mining dev fee?)
miner miner dev fee continuously without interruption, 2% of iterations go to devfee mining
in 1.35, miner stops reporting hashrate to awesomeminer periodically, triggering an offline notification (maybe when mining dev fee?)
Hello,I'm Minerbabe's staff,Minerbabe is a professional GPU mining OS，And we also have a lot users all over the world.Gminer is an excellent product, our system supports it.I have some other cooperation to communicate with you,I would like you to add my telegram:https://t.me/Minerbabeyan.Looking forward to communicating with you.
Please visit our website: https://en.minerbabe.com/pc.html#/ for product experience.
Please visit our website: https://en.minerbabe.com/pc.html#/ for product experience.
70% power limit, 90 core and -502 mem; averaging 187watt per gpu;
GPU0: 30.5 Sol/s
GPU1: 30.6 Sol/s
GPU2: 31.1 Sol/s
GPU3: 29.9 Sol/s
GPU4: 29.4 Sol/s
GPU5: 29.8 Sol/s
GPU0: 30.5 Sol/s
GPU1: 30.6 Sol/s
GPU2: 31.1 Sol/s
GPU3: 29.9 Sol/s
GPU4: 29.4 Sol/s
GPU5: 29.8 Sol/s
Why would you clock down memory? It gives nice boost to h\r. I kept my 1080ti's at stock 5500mhz, but OC'ed 1080 from 5.0 to 5.5Ghz and it gave each card ~0.5sol\s according to the miner. My TI's averaging 185wt as well but produce ~31-32sol\s
I get a "connection error: end of file" anyone know what that is?
What's coin do you mine? Beam? Most of beam pools uses SSL connection, to enable it add "--ssl 1" to command line arguments. Jump to: