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

Downloaded file is saved in Cache folder. If you or your OS for some reason delete's the Cache folder's contents then it will re-download it again and again.

This Dynex is driving me mad, when mallob file downloads and mining starts and all is working fine untill for some reason
srbminer decides that it is time to pull again same mallob bin file witch is arround 50mb on all rigs simultaneusly.
Then all rigs request same file again 6abfdd7f707d155da0ecef6242593c19.bin, and that apsolutely destroys my 4g internet connection,
so i stopped mining dynex becouse it is only coin that gives me problems.
Is it possible to cash/host mallob file localy so when that moment happends all rigs will pull that file localy.
im currently syncing the dynex node localy in hope that this thing can serve as mallob source, on dynex page i cant find any info how i can host local dynex pool or mallob server, anywhone maybe have solution?

its in the first post..

how to setup dual RTH+radiant FOR windows

doktor83
Vega VII Linux driver --> 22.40.6
Vega VII Windows 10 driver -->
Please!

V2.3.4
+ Added algorithm 'ethashb3' (RETHEREUM coin) support for NVIDIA GPUs
+ Added support for dual mining ETHASHB3/SHA512_256D_RADIANT on NVIDIA and AMD RDNA1/2/3 GPUs
+ Added gfx906 (Vega VII) binaries for algorithm 'dynex' on newer drivers (tested on 22.40.6)
+ Fixed gfx900 mining on algorithm 'dynex' broke in previous version

Thanks for adding 'ethashb3' (RETHEREUM coin). But on Vega 56, only half the hashrate (25 mh).

V2.3.3
+ Added algorithm 'ethashb3' (RETHEREUM coin) for GPU mining, fee 2% [AMD only]*
+ Minor performance improvement on algorithm 'dynex' [Dynexcoin]
+ Bug fixes for algorithm 'dynex'*
+ Minor bug fixes

***
ethashb3:
NVIDIA support will be available in next release

***
dynex:
Upgrading to this release is advised because of better mallob handling and other fixes

Hello,
I have problem with mining DYNEX on Radeon VII. Can not start miner. Miner gives the next error and restarts:
[2023-08-16 16:53:43] Preparing data, please wait..
[2023-08-16 16:53:44] GPU0 allocating memory for 800 chips
[2023-08-16 16:53:44] Initializing GPU0
[2023-08-16 16:53:44] GPU0 couldn't create program for ctx->algorithm
[2023-08-16 16:53:44] GPU1 allocating memory for 800 chips
[2023-08-16 16:53:44] Initializing GPU1
[2023-08-16 16:53:44] GPU1 couldn't create program for ctx->algorithm
[2023-08-16 16:53:44] No worker devices found
[2023-08-16 16:53:44] Releasing GPU resources...

OS-is RAVEOS Miner version is the last one - SRBminer 2.3.2
Tried with over clocks and without them. The same thing happens in both variants.
Please help.
Thank You

Hello doktor83, need your help please!
I'm trying to mine ergo+kaspa with SRBMiner 2.3.2 (never used SRBMiner before), but it stops mining with error message:
"Couldn't connect to a devfee pool for a long time
Please check you firewall/antivirus is not blocking connections
Mining will be paused"
So the miner becomes unusable :-(
My setup: Windows 10 based AMD rigs, Linux iptables-based stateful firewall with NAT on the edge of my network with Internet exit in Germany. All outgoing connections are allowed. I have no antiviruses etc. on my rigs - nothing besides Windows itself, AMD drivers and miners. Also, I turned off Windows firewall completely on that rig and it did not help. I have never had such issues with other miners (xmrig, NBMiner, Teamredminer, lolMiner etc.)
Could you pls advice how to fix this problem?
Thank you!

Is it possible to mine dinex and ziliqa in dual mode on version V2.3.2 on rtx 2070 video cards? In the previous version of the miner, Dinex mining did not work for me.
On AMD video cards, mining goes fine in dual mode. Am I making mistakes in setting up the miner or does your miner not support this mode for rtx 2070 video cards?

V2.3.2
+ Performance improvement on algorithm 'dynex' [Dynexcoin]
+ Added parameter '--gpu-dynex-r' (performance tuning for algorithm 'dynex' - min 1, max 16)
+ Removed auto tuner for algorithm 'dynex' [it was causing data reporting issues]
+ Minor bug fixes

All OC parameters are available on their Github page here below

- https://github.com/doktor83/SRBMiner-Multi/blob/77aafed37a7e9713afc7966b58d2421e90fbcfd4/Parameters#L92

The only problem with OC parameters it only works on Nvidia cards so I think for AMD to overclock these cards you can only use the --gpu-intensity parameter that you can add on the bat file

Check the example parameter from this post below

- https://bitcointalksearch.org/topic/m.54533243

tell me the overclocking parameters in the batch file how to write correctly for AMD cards

nvidia gpu dynex 

if you are using hiveos then you are probably setting up autolykos on gui, then you dont want to define it in parameters too, just alephium :
--algorithm blake3_alephium --pool de.alephium.herominers.com:1199 --wallet alephium-wallet

Hello, i have RX 480 rig, and i am trying to dual mine ergo and alephium, however it keeps crashing and cards dont show up in hive os when i try this. I am able to mine just Alephium with SRBminer, but dual mining gives me a headache.
Is this still the correct extra argument to put in flight sheet?

SRBMiner-MULTI.exe --disable-cpu --algorithm autolykos2 --pool de.ergo.herominers.com:1180 --wallet ergo-wallet --algorithm blake3_alephium --pool de.alephium.herominers.com:1199 --wallet alephium-wallet --gpu-boost 3

or should i change something here?

V2.3.1
+ Updated algorithm 'dynex' to support dynexsolve 2.3.0 (new job types, FP64, etc.)
+ Removed support for INTEL GPU's on algorithm 'dynex'
+ Removed support for NVIDIA GPU's on algorithm 'dynex' [temporary]
+ Fixed dual ERG/ETC/ETH + SHA256DT kernels on some GPU's broken since V2.2.6
+ Minor bug fixes

I can run any 5 device well by using Parameter ''--gpu-id 0!1!2!4!5''.but, it will get some error if I run 6 device,what can i do, thanks.The detail of log are following:


[2023-07-24 02:29:14] Miner version: 2.3.0
[2023-07-24 02:29:14] OS: windows
[2023-07-24 02:29:14] Windows version: 10.0 build 19043
[2023-07-24 02:29:14] Platform 0: Advanced Micro Devices, Inc.
[2023-07-24 02:29:14] Found 1 OpenCL platform/s
[2023-07-24 02:29:14] Default OpenCL platform set to 0
[2023-07-24 02:29:14] Found 6 GPU device/s on platform 0
[2023-07-24 02:29:17] Found mallob configuration file dynex_compute_w340.cnf
[2023-07-24 02:29:19] Connected to mallob endpoint
[2023-07-24 02:29:23] GPU0: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 08]
[2023-07-24 02:29:23] GPU1: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 0b]
[2023-07-24 02:29:23] GPU2: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 0e]
[2023-07-24 02:29:23] GPU3: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 11]
[2023-07-24 02:29:23] GPU4: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 14]
[2023-07-24 02:29:23] GPU5: amd_radeon_rx_6800                    [gfx1030       ][16 GB][CU:   60][BUS: 17]
[2023-07-24 02:29:23] GPU sensors: enabled
[2023-07-24 02:29:23] Algorithm/s: dynex+zil [2.50% fee]+[0.00% fee]
[2023-07-24 02:29:23] Gpu mining: enabled
[2023-07-24 02:29:23] Cpu mining: disabled
[2023-07-24 02:29:23] Watchdog: enabled
[2023-07-24 02:29:23] Gpu tweaking: disabled
[2023-07-24 02:29:23] No DevFee for ZIL mining
[2023-07-24 02:29:29] Updated capacity on mallob endpoint
[2023-07-24 02:29:29] Preparing data [0 chips], please wait..
[2023-07-24 02:29:32] Update atomic on mallob endpoint
[2023-07-24 02:29:32] Starting init of worker threads
[2023-07-24 02:29:33] Initializing GPU0
[2023-07-24 02:29:33] Initializing GPU0
[2023-07-24 02:29:34] Initializing GPU1
[2023-07-24 02:29:35] Initializing GPU1
[2023-07-24 02:29:35] Initializing GPU2
[2023-07-24 02:29:36] Initializing GPU2
[2023-07-24 02:29:36] Initializing GPU3
[2023-07-24 02:29:37] Initializing GPU3
[2023-07-24 02:29:37] Initializing GPU4
[2023-07-24 02:29:38] Initializing GPU4
[2023-07-24 02:29:38] GPU5 couldn't setup ctx->algorithm
[2023-07-24 02:29:38] Error while creating GPU workers..

Request to the developer to add uptime, average hash/watt and hash per pool to the table.