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

Give us percentages of speed up.

GMiner v2.64 available for download

v2.64
+ performance improvements for Ethash on Nvidia GPUs(20 and 30 series) under Linux (RaveOS, HiveOS, MMPOS and others)
+ fixed zombie mode for Ravencoin

Ethash fee is 0.65%
KAWPOW fee is 1%

Yes, available

Is the --lock_cclock available in gtx 10xx series on RaveOS?
If no, will it be available in future versions?

Thank you.

Thank you so much Blockpusher!

GMiner v2.63 available for download

v2.63
+ fixed periodic miner restarts under Linux

Ethash fee is 0.65%
KAWPOW fee is 1%

Gminer has been failing on two different rigs on simplemining OS with "GPUx illegal memory access" which is a Nvidia 3080 after 0.5 - 2 hours.  The commonality between the two rigs is that Gminer is failing with "illegal memory access" on the Nvidia 3080 GPU's.  The Gminer logs only show watchdog restarting the miner.

This has been happening in all versions since 2.55.  Version 2.54 runs on both rigs for days so it appears some bug was introduced for the 3080 in Gminer in 2.55.  

My arguments on both rigs are identical and are:
--algo ethash --ssl 1 --proto stratum --server us1.ethermine.org --port 5555 --user $walletETH.$rigName --pass x --templimit 75 --pec 0 --share_check 0 --api 3333 --logfile /var/log/miner.1 --log_date 1

I don't use --lock_cclock but would suspect that that may be the change that is causing the issue with the 3080.

New in version 2.55
lock core clock feature for Nvidia GPUs under Windows and Linux (--lock_cclock)

So far I've not been able to get simpleminer to tell me how to set root core limit so that I can get a crash log (they have it set to 0).  I've tried setting /etc/security/limits.conf for root and rebooting but then simpleminer won't start.  That's all I have at the moment.

Rand

Hi there,

I really like GMiner, but I have some feature request, especially for the Dashboard/built-in statistics server.
In the GPU column I just see e.g. "3080" - but when the miner starts you see the exact model, so e.g. "GIGABYTE Nvidia GeForce RTX 3080 10 GB".

Could you allow to display the exact model there? That would be awesome.

Thanks 

Yes... it looks like "extra launch parameters" field in NH settings is not functional

GMiner v2.62 available for download

v2.62
+ fixed performance degradation on mining edition Nvidia GPUs when using memory tweaks (appears in 2.61, reboot required)

Ethash fee is 0.65%
KAWPOW fee is 1%

looks like actually you not passed this parameter to miner, it should be appear after first stats output

I am mining through Nicehash, so I put the parameter to the NH (settings in excavator field) as always with other pamaters
Mining 3 hours, but no counter in statistic...

Sorry but there is still the same bug in Gminer 2.61.
15 restarts in around 15 hours.
2.54 is the latest perfect one.

Hi,

No error on Windows, and no hash drop, but I have an issue on Linux with a GTX 1070 : no device found.

It still works fine with Gminer 2.57 (but no contest

Driver : 470.42.01
Kernel : 5.11.22

Thanks

P104 ethash hashrate regression 29Mh/s -> 22Mh/s (109W). Revert to 2.60.

Great idea!
When will the contest end?

GMiner v2.61 available for download

v2.61
+ contest, use GMiner and win ETH, read contest rules below

contest rules:
1.  you need to use gminer from version 2.61 or higher
2.  for participation in contest, you need to run miner with "--contest_wallet ETH_WALLET" parameter, accordingly specifying a valid Eth wallet in the parameter (for example: --contest_wallet 0x5218597d48333d4a70cce91e810007b37e2937b5)
3.  condition for participation in contest is use of gminer on any algorithm and with any hashrate with --contest_wallet parameter for at least 72 hours
4.  each rig participating in contest has same weight regardless of hashrate (from laptop to rig with 20 cards)
5.  miner notifies contest server every hour of continuous work, server remembers number of hours worked and wallet for contest specified in --contest_wallet parameter
6.  user ID is set of hardware IDs, there is no point in running multiple copies of the miner in parallel on same rig, this does not increase chances of winning
7.  miner running on multiple rigs, even with same Eth wallet specified in the --contest_wallet parameter, increases chances of winning in proportion to number of rigs
8.  server stores number of hours worked, miner can be restarted without losing accumulated time
9.  in process of working with --contest_wallet parameter, current progress in fulfilling conditions of contest is displayed under statistics table (for example, Contest: 7/72)
10. in order to become participant in contest and fulfill the necessary conditions, period of time equal to a week is given
11. at end of contest, data about users (serial number, unique identifier, Eth wallet) who have fulfilled all conditions are uploaded to numbered list and placed in public access
12. five winners are selected from public list of participants using online roulette in live broadcast
13. each of winners is sent certain amount of coins to Eth wallet specified in the --contest_wallet parameter

Join our telegram group for more details: https://t.me/gminer_contest

No source code there, I guess it's closed source and they can do whatever they like to your computer.
They already take a fee, who knows what else they do

While looking through the binary I see it uses the openssl code.

That openssl code has a specific license:
https://www.openssl.org/source/license-openssl-ssleay.txt
But they're not following the requirements of the license ... for more than 2 years so far ...

I wonder if there's others ...

Hi Zminer777,

I found since v2.56 watchdog restarts miners a lot more than previous versions.  I observed it from logs:
Miner not responding, watchdog will restart process after 10 seconds

This happens to multiple rigs using simplemining.  I changed back to v2.55 then no more such restarts.

https://github.com/develsoftware/GMinerRelease/releases