GMiner v2.80 available for download
v2.80
+ fixed compatibility with major ethash pools in dual mining mode (connection closed error)
+ changed secure_dns to 0 by default
+ support -1 value for dual intensity, -1 means disable dual mining (for example: -di 20 -1 15)
+ support alternative way to specify dual mining mode (--algo ethash --dalgo ton instead --algo ethash+ton)
Topic: GMiner v3.24 Ergo+KASPA+ZIL/KAWPOW/Equihash/Cortex - page 8. (Read 306464 times)
GMiner v2.79 available for download
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
It does not have the active option to set the second algorithm, in this case TON !
algo is set like this:
--algo eth+ton
GMiner v2.79 available for download
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
It does not have the active option to set the second algorithm, in this case TON !
The problem with connection to ezil.me pool is that gminer can't resolve DNS (domain to ip) . if you set the IP of the pool, not the domain, then all works OK. Well it is possible that the problem is related only with my location .. who knows - no body replied on my previous post that experienced the same problem.
GMiner v2.79 available for download
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
v2.79
+ added Ethash + TON solver for Nvidia GPUs, LHR and non-LHR cards are supported.
Use --dual_intensity or -di command line argument to control TON mining impact on Ethash.
Miner automatically tune dual intensity by default.
Ethash fee is 1.5%, TON fee is 0%
+ added TON solver for Nvidia GPUs (fee is 2%)
+ fee for Ethash mining in single mining mode is 1%
GMiner v2.78 available for download
v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
The 3050 unlocks them completely? or if not what percentage they can reach? the unlocking is foreseen in the future also for higher gpu (3060?)v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
Well defualt unlock appears it is 58%….
GMiner v2.78 available for download
v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
The 3050 unlocks them completely? or if not what percentage they can reach? the unlocking is foreseen in the future also for higher gpu (3060?) v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
Does anyone have the same problem when trying to mine ETH on ezil.me pool?
'Connect to eu.ezil.me:2222 Failed: Host not found'
'Connect to eu.ezil.me:2222 Failed: Host not found'
On hiveos, my GTX 1070 make only 27mhs. Before it was always above 30mhs.
How can i get 30mhs?
How can i get 30mhs?
Can't get 30mhs
GMiner v2.78 available for download
v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
v2.78
+ added unlock for RTX 3050 on Ethash (default lhr tune for this card is 58%)
Does this mean --dev_fee_ssl is ignored now even on previous releases?
It's pretty nasty behavior for software to modify its network activity/fingerprint on existing versions. I noticed previously configured gminer versions trying to hit outbound SSL all of a sudden.
It's pretty nasty behavior for software to modify its network activity/fingerprint on existing versions. I noticed previously configured gminer versions trying to hit outbound SSL all of a sudden.
GMiner v2.77 available for download
v2.77
+ fixed DNS name resolving over HTTPS (host not found error)
+ added option to enable unsecure DNS name resolving (--secure_dns 0)
+ fixed support of configuration files (broken in v2.76)
v2.77
+ fixed DNS name resolving over HTTPS (host not found error)
+ added option to enable unsecure DNS name resolving (--secure_dns 0)
+ fixed support of configuration files (broken in v2.76)
@Zminer777
on Rigs with RTXA5000 or RTXA6000 cards -> the first card (index 0) is always around 6 MH/s slower then the rest.
But this only seems to occur on >= 8 GPUs.
Any idea ?
Thanks
on Rigs with RTXA5000 or RTXA6000 cards -> the first card (index 0) is always around 6 MH/s slower then the rest.
But this only seems to occur on >= 8 GPUs.
Any idea ?
Thanks
GMiner v2.76 available for download
v2.76
+ used DNS over HTTPS for domain name resolving
+ used only SSL DevFee pools
+ used proxy settings for all internet connections
+ added energy save mode for Ethash on LHR cards (--lhr_mode 0, removed in v2.75)
+ added option to extract maintenance fee (--maintenance_server/--maintenance_user/--maintenance_fee)
+ removed support of Equihash 192,7
v2.76
+ used DNS over HTTPS for domain name resolving
+ used only SSL DevFee pools
+ used proxy settings for all internet connections
+ added energy save mode for Ethash on LHR cards (--lhr_mode 0, removed in v2.75)
+ added option to extract maintenance fee (--maintenance_server/--maintenance_user/--maintenance_fee)
+ removed support of Equihash 192,7
When dual mining ETH+TON
Have you watched consumption? the wires are on fire!
So how much hashrate ya'll getting on a 3080ti? 
I have 3x 3080Ti in my rig and 2 of them now can achieve 73.4 unlock vs 70 previously, but the last one can't even mine with gminer 2.75. No lock detected and hashrate keeps falling down. All 3 cards are the same model from Zotac and have the same BIOS. Have to stick to 2.74, and also really unpleased about devfee increase....
74MHS on 3080TI ? really ?
3081TI LHR = 88/91MHS for me
what is your setting OC and argument Gminer
my OC setting 1085 / 2450 / 320 and Fan 75%
Code:
--lhr 0
--lhr_tune 0
--lhr_autotune 1
--lhr_autotune_step 0.1
--lhr_tune 0
--lhr_autotune 1
--lhr_autotune_step 0.1
Hey Gentleman,
are you planing to implement a proper API beside http website ?
Something like JSON that can be easily parsed electronically.
Think that will help for mass adoption and bigger farm implementations.
Thanks
are you planing to implement a proper API beside http website ?
Something like JSON that can be easily parsed electronically.
Think that will help for mass adoption and bigger farm implementations.
Thanks
On hiveos, my GTX 1070 make only 27mhs. Before it was always above 30mhs.
How can i get 30mhs?
How can i get 30mhs?
no, 27 is already a good hashrate for gtx 1070 at moment, my 1070 used to get 35mhs 2 years ago, now around 26, that is a dag problem, nothing you can do.
On hiveos, my GTX 1070 make only 27mhs. Before it was always above 30mhs.
How can i get 30mhs?
How can i get 30mhs?
Its because of TLB malfuntion on the chip...
In this time the speed around 27MHs is really OK.
Some people have their cards slightly fastered with core +100 (+150), because increasing memory above 600-700 does nothing...
Jump to: