GMiner v1.70 Equihash(BEAM, BTG, YCASH)/CuckooCycle(AE, SWAP, GRIN, BFC)

[jasta more]

devs will your miner be ready for upcoming grin fork from start?

[1571357630]

1571357630

[1571357630]

1571357630

[1571357630]

1571357630

[cryptoyes]

HF is in less than 3 days and there are multiple floonet (testnet) pools available to test the new hashing algo. On Telegram you said a few days ago that you already have the new miner up and running but you refuse to offer a public beta version for others to test. That's shortsighted and everyone loses. Keeping it secret until fork time is bound to lead to a miriad of issues at fork time, issues which could be solved nicely beforehand. Bminer hasn't released any beta either. It shows how immature this space (mining) continues to be ...

[soda37]

I've just tried Gminer today on my test rig and strange enough on one of 1060 6G it says "not enougth VRAM", but only for one of them.

[Dr_Victor]

I've just tried Gminer today on my test rig and strange enough on one of 1060 6G it says "not enougth VRAM", but only for one of them.

Win 10? Does monitor plug to this card?

[soda37]

I've just tried Gminer today on my test rig and strange enough on one of 1060 6G it says "not enough VRAM", but only for one of them.

Win 10? Does monitor plug to this card?

That's right, it was HDMI dongle, but today I upgraded drivers to 431.36 and seems Grin mining works fine, although with Beam I'm still getting "Illegal memory access was encountered". I can't get rid of that HDMI dongle and can't lower intensity like in other miners to alleviate over that problem  

Update: removing HDMI didn't help as well as lowering my OC settings, different cards give "Illegal memory access was encountered" with beam, while Grin works more or less fine.

[jebidia]

Gminer already has several versions that does not work well in my rigti 1080ti and RTX 2080. It starts, detects the cards and randomly or stays stuck there for hours without undermining, or mine well. The only thing is reboot al rig. I am a user of Awesome miner and we recommend not using Gminer to the thousands of users of this program.

It occurs in the cucka and 150.5 and in some more, and it is not the OC, because it reboots and usually works with the same parameters.

Very much 2% Fee for such an unstable miner. I hope they can solve it because in the end the ones that lose the most are them, the less people use Gminer, the less they earn for the FEE. In its place for the Cucka I have to use nbminer that yields less but never fails.

Have you tried versions 1.48+? I hope we have fixed this issue.
Btw nbminer have same comission for grin - 2%, https://github.com/NebuTech/NBMiner

I have these same issues in rig with RTX 2070
Rig after fresh start works well, but randomly - sometimes after 2hours, sometimes half a day suddenly Gminer cannot start and there is only his black empty window, which is blinking cause it start and ends. The only possible thing is reset a whole rig. It not dependis on the version of Gminer (since 1.44 to 1.50) - i have this issue only with RTX. With 1070 and 1080 is it good. RTX cards did this creepy thing with standard settings, slight OC (+50 +300) and with higher OC (+100 +900). Nothing helped.

Same issue here...Switched over to miniz 14o for beam for now...1080ti's work fine...It's definitely with the 2XXX cards...

[coinzzzman]

GRIN coin is updating its POW algorithm at block 262080 in next 48 hours.

Is GMINER coming out with an update before then?

[kbs1]

Hi guys, my windows 10 1903 AMD rig is now showing this weird behavior:

6x RX580 8GB
driver 17.x
all cards set to 'compute' mode
gminer 1.50
attemping to mine grin C29
HDMI dongle connected to one of the GPUs
using only RDP to launch the miner

It 'just works'. For 12 hours. Or for 4 days. Sometimes 3. There are no exact times. When it 'stops working', I just see on the pool the miner disconnected.

I connect via RDP and violla - it starts up instantly! Then I disconnect. Then it dies. In console, there's the following:

21:21:31 Total Speed: 11.01 G/s Fidelity: 0.993 Shares Accepted: 3973 Rejected: 5 Power: 725W 0.02 G/W
21:21:31 Uptime: 0d 18:14:37 Electricity: 13.222kWh $1.98
21:21:34 Connection Error: Write timed out
21:21:50 Connect to eu-west-stratum.grinmint.com:4416 Failed: No such host is known
21:21:52 Stopped Mining on GPU0
21:21:52 Stopped Mining on GPU1
21:21:52 Stopped Mining on GPU2
21:21:52 Stopped Mining on GPU3
21:21:52 Stopped Mining on GPU4
21:21:52 Stopped Mining on GPU5
21:22:06 Connect to eu-west-stratum.grinmint.com:4416 Failed: No such host is known
21:22:06 All user mining pools are unavailable
21:22:09 Miner terminated, watchdog will restart process after 10 seconds <--- miner keeps on restarting every 10 seconds without any further error message. It never starts.

Then I connect to RDP and boom, it instantly starts mining again. I don't have to restart the miner process by hand. Power profile is set to high performance. There are no sleeps, hibernates, power-downs, no "energy saving" features or anything like that.

It's not a connection issue, as I can always connect back to the machine via RDP. So the connection isn't 'asleep'. It's a ethernet connection, not a wifi.

Has anyone ever seen this behavior? It is a first time for me. It might be a bug in GMiner, but it's very very weird that it 'magically' comes back alive INSTANTLY when I connect via RDP when dead. Maybe some windows 'this proccess is using a lot of resources, so I'll pause it' feature? Or something like that? But as I said, I've never encountered anything like that.

Any help is greatly appreciated. Thank you!

[Zminer777]

GMiner v1.51 available for download

v1.51
+ added Cuckarood29 algorithm for Nvidia cards (use --algo grin29 for autoswitch after hardfork)
+ added BeamHashII algorithm for Nvidia cards (use --algo BeamHashII to enable it or use --algo BeamHash for autoswitch after hardfork)
+ added option to print miner version (--version)
+ added option to enable/disable NVML (--nvml 0/1)
+ bug fixes and stability improvements

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/tag/1.51

[Atrixis]

drop hash on p102-100, like another version excludes 1.45 and older

version cuda recommended?

[mmitech]

GMiner v1.51 available for download

v1.51
+ added Cuckarood29 algorithm for Nvidia cards (use --algo grin29 for autoswitch after hardfork)
+ added BeamHashII algorithm for Nvidia cards (use --algo BeamHashII to enable it or use --algo BeamHash for autoswitch after hardfork)
+ added option to print miner version (--version)
+ added option to enable/disable NVML (--nvml 0/1)
+ bug fixes and stability improvements

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/tag/1.51

could you please share BeamHashII hashrate numbers with us?

[artful]

fix please grin29 on gtx 1650 4gb!

12:23:10 Failed to initialize miner on GPU0: GIGABYTE GeForce GTX 1650 4GB: out of memory
12:23:11 No devices for mining

only version 1.38 working on 1650 4Gb, other version - out of memory
Linux x64

nvidia-smi:

Code:

|   0  GeForce GTX 1650    On   | 00000000:01:00.0 Off |                  N/A |
| 70%   38C    P0    17W /  60W |     17MiB /  3910MiB |      8%      Default |

[kbs1]

@Zminer777 OK it seems to be a connection issue afterall. The miner is using a "ethernet over power lines" adapter and while I was on site today, the connection really dropped for like ~5 seconds due to presumably power line noise (miners pull a lot of electricity).

This resulted in the miner stopping (I can see this by looking at the GPU fans, they stop spinning after a while when disconnected from pool).

I connected via RDP and violla - it started mining again.

I think this is a bug in GMiner, when launched via RDP. I think when it releases the GPUs, it's unable to use them again because of windows reasons presumably because "there's nobody at the computer, so why would any program want to use the GPU". When I connect, it starts up instantly. Is there anything we can do about this?

[2h4u]

Mining Grin29 on Nicehash right after the fork. Algo is 'grin29':

Code:

16:54:49 Connected to grincuckaroo29.eu.nicehash.com:3371
16:54:49 New Job: 2328929219742 Difficulty: 4
16:54:49 Authorized on Stratum Server
16:54:49 Started Mining on GPU0: ASUS GeForce GTX 1070 Ti 8GB
16:54:49 Started Mining on GPU1: GIGABYTE P106-100 6GB
16:54:49 Started Mining on GPU2: GIGABYTE P106-100 6GB
16:54:49 Started Mining on GPU3: NVIDIA P106-100 6GB
16:54:49 Started Mining on GPU4: MSI GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU5: GIGABYTE GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU6: GIGABYTE GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU7: MSI GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU8: ASUS GeForce GTX 1050 Ti 4GB
16:54:49 Started Mining on GPU9: ASUS GeForce GTX 1050 Ti 4GB
16:54:53 GPU3 Share Rejected: Share above target.
16:54:54 GPU2 Share Rejected: Share above target.
16:54:56 GPU0 Share Rejected: Share above target.
16:54:56 GPU3 Share Rejected: Share above target.
16:54:57 GPU5 Share Rejected: Share above target.
16:54:59 GPU7 Share Rejected: Share above target.
16:55:01 GPU4 Share Rejected: Share above target.
16:55:05 GPU1 Share Rejected: Share above target.
16:55:06 GPU2 Share Rejected: Share above target.
16:55:07 GPU6 Share Rejected: Share above target.
16:55:08 GPU3 Share Rejected: Share above target.
16:55:08 GPU6 Share Rejected: Share above target.
16:55:13 GPU6 Share Rejected: Share above target.

Fancy that, 'cuckaroo29' still does work good and has no rejects. Whose court the ball in? Is it Nicehash-related or @Zminer777?

[TBOEMC]

Mining Grin29 on Nicehash right after the fork. Algo is 'grin29':

Code:

16:54:49 Connected to grincuckaroo29.eu.nicehash.com:3371
16:54:49 New Job: 2328929219742 Difficulty: 4
16:54:49 Authorized on Stratum Server
16:54:49 Started Mining on GPU0: ASUS GeForce GTX 1070 Ti 8GB
16:54:49 Started Mining on GPU1: GIGABYTE P106-100 6GB
16:54:49 Started Mining on GPU2: GIGABYTE P106-100 6GB
16:54:49 Started Mining on GPU3: NVIDIA P106-100 6GB
16:54:49 Started Mining on GPU4: MSI GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU5: GIGABYTE GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU6: GIGABYTE GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU7: MSI GeForce GTX 1060 6GB
16:54:49 Started Mining on GPU8: ASUS GeForce GTX 1050 Ti 4GB
16:54:49 Started Mining on GPU9: ASUS GeForce GTX 1050 Ti 4GB
16:54:53 GPU3 Share Rejected: Share above target.
16:54:54 GPU2 Share Rejected: Share above target.
16:54:56 GPU0 Share Rejected: Share above target.
16:54:56 GPU3 Share Rejected: Share above target.
16:54:57 GPU5 Share Rejected: Share above target.
16:54:59 GPU7 Share Rejected: Share above target.
16:55:01 GPU4 Share Rejected: Share above target.
16:55:05 GPU1 Share Rejected: Share above target.
16:55:06 GPU2 Share Rejected: Share above target.
16:55:07 GPU6 Share Rejected: Share above target.
16:55:08 GPU3 Share Rejected: Share above target.
16:55:08 GPU6 Share Rejected: Share above target.
16:55:13 GPU6 Share Rejected: Share above target.

Fancy that, 'cuckaroo29' still does work good and has no rejects. Whose court the ball in? Is it Nicehash-related or @Zminer777?

Nicehash supports Grin29D (forked version) only with "new platform" - 1.9.2.9.
There is a chance to put new version of GMiner, as always.

Old platform version 1.9.1.x has only Grin29.

[2h4u]

Mining Grin29 on Nicehash right after the fork. Algo is 'grin29':

Code:

16:54:49 Connected to grincuckaroo29.eu.nicehash.com:3371
16:54:49 New Job: 2328929219742 Difficulty: 4
16:54:49 Authorized on Stratum Server
16:54:53 GPU3 Share Rejected: Share above target.
16:55:13 GPU6 Share Rejected: Share above target.

Fancy that, 'cuckaroo29' still does work good and has no rejects. Whose court the ball in? Is it Nicehash-related or @Zminer777?

Nicehash supports Grin29D (forked version) only with "new platform" - 1.9.2.9.
There is a chance to put new version of GMiner, as always.

Old platform version 1.9.1.x has only Grin29.

Don't know nothing about Nicehash 'platform', is it Windows-something? I running latest gminer 1.51 under Linux, mining directly to NH stratum (an old one tho).

[_javi_]

Gminer 1.51

reporting a bug, maybe...

Fidelity 2 ??
Hashrate in pool is 2x what it used to be. Its fine on the rig.

[Zminer777]

Gminer 1.51

reporting a bug, maybe...

Fidelity 2 ??
Hashrate in pool is 2x what it used to be. Its fine on the rig.

check this https://www.grin-forum.org/t/mid-july-pow-hardfork-cuckaroo29-cuckarood29/5082

Curiously, this results in twice the expected number of cycles.

2 is right fidelity for cuckarood29

[PhAlAnXcOiN]

Trying to get GMiner v1.51 working on linux for mining Grin on cuckatoo31 with my 1080 (non ti) 8gb card. It is not overclocked and wattage is at 175 (using SMOS OS). Upon starting up it gives me:

18:48:12 Error on GPU0: an illegal memory access was encountered
18:48:12 Stopped Mining on GPU0
System watchdog rebooted rig due to some problem. Lower OC and try less undervolting and if that will not help then most probably riser is broken.
18:48:13 Miner terminated, watchdog will restart process after 10 seconds

My miner config is as follows:

-a grin31 -s grin-us.luxor.tech -n 3000 -u myusername.myrigname -p x

I was able to get this card working on cuckatoo31 for Grin with bminer and lolminer but not gminer so far. Would like to just to compare how well it does with my card.

is there anything i'm missing here? Has anyone been successful in getting gminer to work on a 1080? Any tips? I appreciate any help! Thanks!

[madnessteat]

Guys, please tell me I installed the new Beam Wallet 3.0.5654 and gminer 1_5.1. In version 1_4.7 I used the following bat file:

"miner --algo 150_5 --server beam-us.leafpool.com --port 3333 --ssl 1 --user YOUR_ADDRESS.WORKER_NAME"

In order for mining not to stop when changing the algorithm, I need to change: "--algo 150_5" to "--algo BeamHash"?