|
peter_dab
Newbie
Offline
Activity: 1
Merit: 0
|
 |
June 11, 2020, 03:37:57 PM |
|
Hi There,
I'm trying to mine Equihash 150,5 but the miner (2.10) is always restarting stating that "All devfee pools are unavailable". Can you please update (maybe with a new version) your devfee pools so that the miner works again
Thanks in advance.
|
|
|
|
Solovey4ik
Newbie
Offline
Activity: 28
Merit: 0
|
 |
June 11, 2020, 04:38:32 PM |
|
18:40:54 Uptime: 0d 00:02:00 Electricity: 0.030kWh 18:40:55 All devfee mining pools are unavailable 18:40:58 Stopped Mining on GPU0 18:41:00 Stopped Mining on GPU1 18:41:02 Stopped Mining on GPU2 18:41:05 Stopped Mining on GPU3 18:41:08 Stopped Mining on GPU4 18:41:08 Miner terminated, watchdog will restart process after 10 seconds +----------------------------------------------------------------+ | GMiner v2.10 | +----------------------------------------------------------------+ Algorithm: Cuckatoo32 DevFee: 3% Stratum server #1: host: grincuckatoo32.eu.nicehash.com:3383 such an error in two out of three rigs, appears every 2-3 minutes, what's the matter? how did you fix it?
|
|
|
|
Solovey4ik
Newbie
Offline
Activity: 28
Merit: 0
|
 |
June 11, 2020, 04:40:19 PM |
|
Hi There,
I'm trying to mine Equihash 150,5 but the miner (2.10) is always restarting stating that "All devfee pools are unavailable". Can you please update (maybe with a new version) your devfee pools so that the miner works again
Thanks in advance.
same problem here , please let me know how to get it fixed, thanks
|
|
|
|
impynick
Jr. Member
Offline
Activity: 77
Merit: 6
|
 |
June 11, 2020, 05:55:55 PM |
|
Hi There,
I'm trying to mine Equihash 150,5 but the miner (2.10) is always restarting stating that "All devfee pools are unavailable". Can you please update (maybe with a new version) your devfee pools so that the miner works again
Thanks in advance.
same problem here , please let me know how to get it fixed, thanks If Gminer can change the dev fee pool to sunpool.top that would alleviate the issue. Cannot solo 150,3 atm either.
|
|
|
|
|
Newbiteck
Newbie
Offline
Activity: 7
Merit: 0
|
 |
June 12, 2020, 10:18:01 PM |
|
|
|
|
|
TrashSeller
Newbie
Offline
Activity: 22
Merit: 0
|
 |
June 13, 2020, 04:19:20 PM |
|
18:40:54 Uptime: 0d 00:02:00 Electricity: 0.030kWh 18:40:55 All devfee mining pools are unavailable 18:40:58 Stopped Mining on GPU0 18:41:00 Stopped Mining on GPU1 18:41:02 Stopped Mining on GPU2 18:41:05 Stopped Mining on GPU3 18:41:08 Stopped Mining on GPU4 18:41:08 Miner terminated, watchdog will restart process after 10 seconds +----------------------------------------------------------------+ | GMiner v2.10 | +----------------------------------------------------------------+ Algorithm: Cuckatoo32 DevFee: 3% Stratum server #1: host: grincuckatoo32.eu.nicehash.com:3383 such an error in two out of three rigs, appears every 2-3 minutes, what's the matter? how did you fix it? didn’t fix it in any way, it still works with errors
|
|
|
|
ericripi
Newbie
Offline
Activity: 2
Merit: 0
|
 |
June 15, 2020, 04:00:28 AM |
|
hello, can we use GMiner with a personal block header and nonce, such as block header is 32 byte and nonce is 32 byte?
|
|
|
|
BoozyTalking
Newbie
Offline
Activity: 315
Merit: 0
|
 |
June 23, 2020, 07:09:10 AM |
|
please add eth+KDA for AMD cards!
|
|
|
|
xenolink
Newbie
Offline
Activity: 1
Merit: 0
|
 |
June 23, 2020, 09:07:14 PM |
|
Any plan to add support for c31 EpicCash?
I second this, hoping to see C31 support EpicCash mimblewimble fork of Grin as well. Thank you!
|
|
|
|
MrPlus
|
 |
June 26, 2020, 01:10:45 PM |
|
Hi,
Any info on coming Beam fork support (june 28th)
|
|
|
|
|
rgsnedds
Member

Offline
Activity: 952
Merit: 17
raskul
|
 |
June 27, 2020, 11:23:33 AM |
|
|
|
|
|
DanGB
Newbie
Offline
Activity: 25
Merit: 0
|
 |
June 27, 2020, 02:03:11 PM |
|
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
I just tested the newest gminer update. I pointed it to a test pool that is already past block 777777 (so on BeamHashIII) and got 18-19 Sol/s with my 1070ti's (using the same Afterburner settings as with BeamHashII). Now the interesting thing is that I then pointed it to my node (so still BeamHashII) to solo mine and I was getting 18-19 Sol/s on there too. I then ran against my node the previous gminer version that I had been running and it got 40+ Sol/s as I expected (again, no changes in Afterburner settings). Any idea why I am seeing very low hashrate while mining BeamHashII with this latest version?
|
|
|
|
Kringel
Jr. Member
Offline
Activity: 151
Merit: 7
|
 |
June 27, 2020, 06:10:40 PM |
|
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
Now the difference between the C32 hashrate shown by gminer and that one reported by the pool became even bigger; with 1070s it's about 25% (at least on Nicehash servers). Basically, since you started declaring improved C32 hashrate back in April the actual hashrate stays more or less the same, only numbers reported by the miner "improve".
|
|
|
|
joseph32
Member

Offline
Activity: 418
Merit: 21
|
 |
June 27, 2020, 07:07:58 PM |
|
+ improved Cuckatoo32 performance (up to 5%-8% dependent on GPU)
Now the difference between the C32 hashrate shown by gminer and that one reported by the pool became even bigger; with 1070s it's about 25% (at least on Nicehash servers). Basically, since you started declaring improved C32 hashrate back in April the actual hashrate stays more or less the same, only numbers reported by the miner "improve". Same here and also reported weeks ago. Tested 12 hours with a 1080Ti-Rig. Reported hashrate by GMiner = 4.90 G/s. Real hashrate @ Nicehash = 4.52 G/s.
|
|
|
|
jmart123
Newbie
Offline
Activity: 2
Merit: 0
|
 |
June 27, 2020, 07:29:49 PM |
|
Just tested BeamHash as well. Gminer ver 2.05 gets 40 sols and ver 2.11 only gets 17 sols. Test was with a 1070 using same card settings. Tried both beamHashII on regular pool and BeamHashIII on test pool. Hope this gets resolved before the Beam fork.
|
|
|
|
DanGB
Newbie
Offline
Activity: 25
Merit: 0
|
 |
June 27, 2020, 08:20:20 PM |
|
+ support BeamHashIII algorithm for Nvidia GPUs (for auto-switching use algo --beamhash)
I just tested the newest gminer update. I pointed it to a test pool that is already past block 777777 (so on BeamHashIII) and got 18-19 Sol/s with my 1070ti's (using the same Afterburner settings as with BeamHashII). Now the interesting thing is that I then pointed it to my node (so still BeamHashII) to solo mine and I was getting 18-19 Sol/s on there too. I then ran against my node the previous gminer version that I had been running and it got 40+ Sol/s as I expected (again, no changes in Afterburner settings). Any idea why I am seeing very low hashrate while mining BeamHashII with this latest version? We figured out what the issue is. If you test BeamHashIII on a test pool and it is past block 777777, gminer creates a 0k file in the miner folder. With this file there, gminer will continue to run on BeamHashIII even if you go back to a regular mainnet pool that has not yet hit block 777777. To get your hashrate back and to have it actually mine on BeamHashII again, you must delete that 0k file.
|
|
|
|
psiz
Newbie
Offline
Activity: 15
Merit: 0
|
 |
June 28, 2020, 05:09:17 PM |
|
beamhash-3 : nicehash: share rejected share above target
|
|
|
|
|