Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 14. (Read 42480 times)

Windows/Linux drivers with cuda installed?

Hi, GTX1660 not supported?

V2.1.0
+ Added support for INTEL Alchemist architecture (INTEL ARC 300/500/700)
+ ZIL is now mineable in any single/dual algorithm combination [triple mining]*
+ Added ZIL parameters '--zil-enable', '--zil-pool', '--zil-wallet', '--zil-password', '--zil-esm', '--zil-epoch', '--zil-oc-script'
+ Added ZIL OC parameters '--zil-cclock', '--zil-mclock', '--zil-coffset', '--zil-moffset', '--zil-plimit'
+ Added auto buffer mode for ZIL mining*
+ Added parameters '--disable-gpu-intel', '--gpu-disable-auto-buffer'
+ Added OC parameters '--gpu-cclock1', '--gpu-mclock1', '--gpu-coffset1', '--gpu-moffset1', '--gpu-plimit1'
+ Removed parameters '--gpu-ethash-dag-cache', '--a0-is-zil'
+ Renamed parameters '--a0-start-script' to '--a0-oc-script' , '--a1-start-script' to '--a1-oc-script', '--start-script-delay' to '--oc-delay'
+ Added '--esm 2' which indicates that 'EthereumStratum/1.0.0' + nicehash mode is used for communication with the pool*
+ Allowed separator ',' (comma) which can be used as an alternative for the current '!' separator in all parameters except in '--password'
+ Added custom miner version for Hiveos so you can run 2 SRBMiner instances on the same rig*
+ Minor bug fixes

This is the first release that supports INTEL Alchemist GPU's, so please report any bug/s you find in the discord support channel.

***
Algorithms currently supported on INTEL Alchemist GPU's [more algorithms soon]:

- kaspa
- sha512_256d_radiant
- sha256dt
- blake3_alephium
- heavyhash

No readings from sensors yet (clocks, temp, etc.)



***
ZIL mining parameters

--zil-enable
--zil-pool
--zil-wallet
--zil-password
--zil-esm
--zil-epoch

Every parameter except '--zil-enable' and '--zil-epoch' can have multiple values separated with ! (or now also ,)
You can define multiple ZIL pools, with different wallets for example.

'--zil-epoch' parameter isn't needed now, but it can be used in the future if Zilliqa decides to change the work epoch from 0.


***
GPU OC parameters [NVIDIA ONLY]

First algorithm [A0]:

--gpu-cclock0
--gpu-mclock0
--gpu-coffset0
--gpu-moffset0
--gpu-plimit0
--a0-oc-script

Second algorithm [A1]:

--gpu-cclock1
--gpu-mclock1
--gpu-coffset1
--gpu-moffset1
--gpu-plimit1
--a1-oc-script

ZIL:

--zil-cclock
--zil-mclock
--zil-coffset
--zil-moffset
--zil-plimit
--zil-oc-script

OC parameters are used to set GPU clocks, offsets, etc..
SRBMiner supports algo switching (--multi-algorithm-job-mode 3 and ZIL), so these parameters can be used to change GPU's OC on every algo change!

For example if you mine ETC+ZIL, miner will set OC for ETC on miner start from --gpu-...0 parameters.
When ZIL window opens, miner will apply the OC settings you defined with --zil-.. parameters.
When ZIL window closes, miner will apply OC settings you defined with --gpu-...0 parameters again.

--zil-oc-script :
Path to an executable script (.sh or .bat) which can call external tools to set GPU OC parameters right before switching to ZIL mining.
When ZIL mining period is finished, --a0-oc-script will be called (if user set it) before switching back to main algorithm mining.

--oc-delay can be used to define a delay (in seconds) after the OC settings were applied. Default value is 3 sec.

***
New functionality : auto switch on some algos to '--gpu-buffer-mode 1' on GPU's that probably wont have enough VRAM for ZIL dag and the main algo memory requirements.
Works only if the auto tune parameter is NOT used.
To disable this functionality use : '--gpu-disable-auto-buffer' parameter.
If you did not disable auto buffer mode, but miner crashes on algorithm switching (probably because of the mentioned reason - not enough VRAM), just add manually the --gpu-buffer-mode 1 parameter



***
Examples on how to set up ZIL mining in different combinations:

TIP : if your GPU doesn't have enough memory to hold the buffers of every algorithm you use, try adding '--gpu-buffer-mode 1' parameter

1. Mine ETHW+ZIL on ezil.me :

2. Mine RADIANT+ZIL, RADIANT on rplant.xyz, ZIL on crazypool.org :

3. Mine ERGO+NOVO+ZIL, ERGO on herominers.com, NOVO on mynewmining.com, ZIL on crazypool.org :
4. Mine EPIC+KASPA+ZIL, EPIC on 51pool.online, KASPA on herominers.com, ZIL on crazypool.org :


Now comes the fun part. Adding GPU OC parameters. For simplicity the example will have 2 GPU's (id's 0 and 1) that use different OC settings.

2. Mine RADIANT+ZIL, RADIANT on rplant.xyz, ZIL on crazypool.org :

4. Mine EPIC+KASPA+ZIL, EPIC on 51pool.online, KASPA on herominers.com, ZIL on crazypool.org :


***
--esm values :
0 - getwork/ETHPROXY
1 - EthereumStratum/1.0.0
2 - EthereumStratum/1.0.0 + nicehash mode


***
Custom miner for Hiveos

To use it you need to select “Custom miner” when you create Flight Sheet and paste this into 'Installation url' : https://github.com/doktor83/SRBMiner-Multi/releases/download/2.1.0/srbminer_custom-2.1.0.tar.gz
After that you must set everything manually through the 'Extra config arguments' field by using SRBMiner parameters [ https://github.com/doktor83/SRBMiner-Multi/blob/master/Parameters ]

***
HiveOS update script from v2.0.2 to v2.1.0:

If using a dual algorithm (like etchash/blake3) miner will find the best intensity for the second algorithm based on your current OC settings.
You can define them manually too, but you first need to define which gpu's you wanna use with --gpu-id. so:

Hi.

I've a rig with 7 different GPUs.
I want to dual-mine ETC/ZIL+ALEPHIUM on 6 of them (they are AMDs), with different intensities between etchash & blake3
I'm a bit confused about how to declare that :


doesn't work, all gpus have the same intensities : 23;7.
Is it possible to tune that per GPU?

V2.0.2
+ Improved mining performance on 'sha512_256d_radiant' for AMD RDNA/RDNA2 GPU's and NVIDIA Ampere GPU's
+ Improved mining performance on dual ETCHASH/ETHASH + SHA512_256D_RADIANT for AMD RDNA2 GPU's
+ Added experimental support for NVIDIA architectures older than 'Pascal'
+ Added GPU OC parameters '--gpu-coffset', '--gpu-moffset' [ NVIDIA - LINUX only ]
+ Fixed bug with --gpu-cclock , --gpu-mclock and --gpu-plimit getting applied only in dual mining mode
+ Removed obsolete algorithms: cosa, circash, 0x10, frkhash, balloon_zentoshi
+ Minor bug fixes

***
--gpu-coffset sets the core offset of the GPU [ defined in MHZ ]
--gpu-moffset sets the memory offset of the GPU [ defined in MHZ ]

HiveOS update script from v2.0.1 to v2.0.2:

V2.0.1
+ Added support for NVIDIA 'Hopper' architecture
+ Added NVIDIA support for algorithms : UBQHASH, DYNAMO, BLAKE3_IRONFISH
+ Added GPU OC parameter '--gpu-plimit' [ NVIDIA only ]
+ Re-added kernels for dual ETHASH/ETCHASH/AUTOLYKOS2 + BLAKE3_IRONFISH because of testnet3 [ NVIDIA support added ]
+ Fixed detection of NVIDIA GPU's
+ Fixed compatibility with older NVIDIA drivers
+ Various fixes for mining on nicehash pools / nicehash mode
+ Minor bug fixes

***
--gpu-plimit sets a limit on the maximum power a GPU can use [ defined in W ]

Available parameters for NVIDIA OC:
[separate value with ! for multiple GPU's]

--gpu-cclock (set fixed core clock)
--gpu-mclock (set fixed mem clock)
--gpu-plimit (set power limit)


HiveOS update script from v2.0.0 to v2.0.1:

yeah, at the moment you need at least 526 drivers. im gonna change that in future release/s.

Hello
ver 2.0 1050ti cards on the system
miner says

No worker devices found

V2.0.0
+ Added support for NVIDIA architectures : Pascal, Turing, Ampere, Ada Lovelace
+ Added parameters '--disable-gpu-amd', '--disable-gpu-nvidia'
+ Added GPU OC parameters '--gpu-cclock' and '--gpu-mclock' [NVIDIA Volta and newer]
+ Added GPU efficiency to stats & API
+ Removed kernels for dual ETHASH/ETCHASH/AUTOLYKOS2 + BLAKE3_IRONFISH

This is the first release that supports NVIDA GPU's, so please report any bug/s you find in the discord support channel.

***
Algorithms currently supported on NVIDIA GPU's:

- autolykos2
- etchash
- ethash
- sha512_256d_radiant
- kaspa
- heavyhash
- lyra2v2_webchain
- blake3_alephium
- sha256dt
- kawpow
- evrprogpow
- firopow
- progpow_epic
- progpow_sero
- progpow_zano
- progpow_veil
- progpow_veriblock

Dual mining :

- ethash + kaspa
- ethash + blake3_alephium
- ethash + heavyhash
- ethash + sha512_256d_radiant
- ethash + sha256dt

- etchash + kaspa
- etchash + blake3_alephium
- etchash + heavyhash
- etchash + sha512_256d_radiant
- etchash + sha256dt

- autolykos2 + kaspa
- autolykos2 + blake3_alephium
- autolykos2 + heavyhash
- autolykos2 + sha512_256d_radiant
- autolykos2 + sha256dt


***
Known issues on NVIDIA:
- autotune (--gpu-auto-tune parameter) isn't working for every algorithm

Thanks, I did miss that part.

Read the release notes : https://github.com/doktor83/SRBMiner-Multi/releases/tag/1.1.1

MSR isn't enabled by default? I see a huge performance drop in MinotaurX with this version on a Ryzen 3900x.

Going back to 1.0.7 binary fixes it.

Where can I see the mining test data for the RX 7900 video card?

V1.1.4
+ Added support for gfx1100 (RDNA3 : RX 7900) GPU's
+ Fixed hashrate regression on 'autolykos2' algorithm for Vega/Ellesmere GPU's that was introduced unintentionally in an earlier version
+ Renamed '--adl-disable' parameter to '--gpu-sensors-disable'
+ Minor bug fixes

This was not my question, but ok. You need help, but you don´t accept the help. For me it works like a charm with every pool - so in my opinion the problem sitting in front of the screen. And you write: "we" so your partners also do something wrong.
If you want help, begin to accept other meanings. Start mining with no extra parameters and single mining. When it works - add more parameters you really need.

So for me it works, the developer write it works.

Actually if he was talking about StakeCube coin (don't know he never gives any information except 'not working'), then he was right, it's not working cause they dont use FIROPOW parameters , their period is different. I got that info from zpool admin. So i dont know why they say they use FIROPOW when .. its not.

It cant connect because you are trying to connect to a non existent host:port.
It's pool.xdag.org:13656 or 116.202.3.220:13656 you could at least spend 15 sec and check that on their page : https://xdag.org/setup?pool_id=2

Problem not in extra params, problem is what miner can't connect to pool. And we use different pools.

Tested on serveral GPU´s - mostly polaris pendants from the smallest to the biggest.



Why you don´t set a worker for epic mining? " ;R2700Pro"

this is my commandline for testing xdag

SRBMiner-MULTI.exe --disable-gpu --algorithm xdag --pool xdagmine.com:13654 --wallet ****************** --worker srbminer --cpu-threads 2

why so much extra arguments? You really need them? I don´t think so. Keep the commandline easier. If it works, then you can start to add some extra arguments.