Mallob errors are not miner related, but dynex mallob related.
There are numerous reasons best is to seek help on Dynex discord.
Topic: SRBMiner-MULTI GPU & CPU Miner 0.9.4 - page 13. (Read 42480 times)
I can't mine with versions and the newest V2.2.1 still the same mallob error at zergpool.
And I get invalid share #414.
And please provide parameters for core and memory clock control.
And I get invalid share #414.
And please provide parameters for core and memory clock control.
V2.2.1
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
"mallob registration error" , no mining DNX ! what to do?
Same problem, can't start the miner.
V2.2.1
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
"mallob registration error" , no mining DNX ! what to do?
V2.2.1
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
+ Moved CPU part of the POUW work for algorithm 'dynex' on AMD and INTEL GPU's to the GPU*
+ Added parameter '--dynex-cpu-pow' which uses the old way of 'dynex' hashing
+ Added parameter '--gpu-reset-oc' which resets OC settings to their default values on miner start [NVIDIA]
+ Reduced default value for intensity (number of chips) on algorithm 'dynex'
+ Removed auto-tune for algorithm 'dynex'
+ Bug fixes for algorithm 'dynex'
***
Good news for AMD & INTEL GPU's (and in an upcoming release probably for NVIDIA's) :
A part of POUW work that was done on the CPU's is now done on GPU side.
This unfortunately comes with a penalty : less hashrate [ up to ~10% ]
More memory and additional work is needed on the GPU, which unfortunately decreases the total hashrate.
If you have a good CPU which can run all your cards without issues, then add the --dynex-cpu-pow parameter
and the additional work will again be calculated on the CPU side.
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) got reduced a little bit, mainly because
on some systems video driver reports more free memory for the GPU than there really is, so mining won't start or
it crashes.
You can manually set the gpu intensity (number of chips) with --gpu-intensity parameter which can lead to higher hashrates.
Does anyone know what to set as msr presets/tweaks on linux for randomx? Trying to dual mine randomepic/rx0 but getting hashrate all over the place, and I've tried 50 different combinations of msr mods, my xmrig hashrate is a stable 14kh/s but with srb it sometimes goes to 14kh then settles back at 8-9kh, kind of annoying as it works great out of the box on windows.
On a ryzen 3900x btw.
On a ryzen 3900x btw.
Please add an option to lock the core and the memory clocks.
Greetings, dear ones, for some reason the new version of the miner gives a low hashrate on vega video cards - it is the same as on 480 cards. But the electricity consumption is also low. Is there any way to increase the mining speed for AMD VEGA graphics cards? coin dynex
How much RAM needed for dynex mining?
Dual mining Epic+Dynex not work (RTX3060 12GB):
Dual mining Epic+Dynex not work (RTX3060 12GB):
Code:
[2023-03-09 09:22:38] Update capacity on mallob endpoint
[2023-03-09 09:22:41] A0|GPU0 | [BUS:08] [I: 22]
[2023-03-09 09:22:41] A1|GPU0 | [BUS:08] [I: 688]
[2023-03-09 09:22:45] Update atomic on mallob endpoint
[2023-03-09 09:22:52] Connected to dynexsolve.mine.zergpool.com:4460 [dynex]
[2023-03-09 09:22:52] Difficulty 20000.0000000000 [dynex][1]
[2023-03-09 09:22:52] Job received [689556778] [dynex][1]
[2023-03-09 09:22:55] Working on algorithm 1 jobs
[2023-03-09 09:23:02] Connected to 51pool.online:4416 [progpow_epic]
[2023-03-09 09:23:09] Difficulty 20000.0000000000 [dynex][1]
[2023-03-09 09:23:09] Job received [764251905] [dynex][1]
[2023-03-09 09:23:16] Epoch : 62 [progpow_epic]
[2023-03-09 09:23:18] Difficulty 300000025.0000000000 [progpow_epic][0]
[2023-03-09 09:23:18] Job received [0] block height 1867187 [progpow_epic][0]
[2023-03-09 09:23:23] Working on algorithm 0 jobs
[2023-03-09 09:23:31] Job received [1] block height 1867187 [progpow_epic][0]
[2023-03-09 09:23:33] Couldn't set epoch 62 on GPU0 [progpow_epic]
[2023-03-09 09:23:43] Couldn't set epoch 62 on GPU0 [progpow_epic]
[2023-03-09 09:22:41] A0|GPU0 | [BUS:08] [I: 22]
[2023-03-09 09:22:41] A1|GPU0 | [BUS:08] [I: 688]
[2023-03-09 09:22:45] Update atomic on mallob endpoint
[2023-03-09 09:22:52] Connected to dynexsolve.mine.zergpool.com:4460 [dynex]
[2023-03-09 09:22:52] Difficulty 20000.0000000000 [dynex][1]
[2023-03-09 09:22:52] Job received [689556778] [dynex][1]
[2023-03-09 09:22:55] Working on algorithm 1 jobs
[2023-03-09 09:23:02] Connected to 51pool.online:4416 [progpow_epic]
[2023-03-09 09:23:09] Difficulty 20000.0000000000 [dynex][1]
[2023-03-09 09:23:09] Job received [764251905] [dynex][1]
[2023-03-09 09:23:16] Epoch : 62 [progpow_epic]
[2023-03-09 09:23:18] Difficulty 300000025.0000000000 [progpow_epic][0]
[2023-03-09 09:23:18] Job received [0] block height 1867187 [progpow_epic][0]
[2023-03-09 09:23:23] Working on algorithm 0 jobs
[2023-03-09 09:23:31] Job received [1] block height 1867187 [progpow_epic][0]
[2023-03-09 09:23:33] Couldn't set epoch 62 on GPU0 [progpow_epic]
[2023-03-09 09:23:43] Couldn't set epoch 62 on GPU0 [progpow_epic]
Hi Doktor,
I have a question about the DNX integration.
On two different 4090 rigs (Win 11), I get this error:
Mallob error: [Couldn't resolve host name]
All other rigs on Win 10 are working. Maybe its the Win 11?
I'am using on all rigs dynex.neuropool.net:19331 and --mallob-endpoint mallob.neuropool.net:8081,https://dnx.eu.ekapool.com
Thanks
I have a question about the DNX integration.
On two different 4090 rigs (Win 11), I get this error:
Mallob error: [Couldn't resolve host name]
All other rigs on Win 10 are working. Maybe its the Win 11?
I'am using on all rigs dynex.neuropool.net:19331 and --mallob-endpoint mallob.neuropool.net:8081,https://dnx.eu.ekapool.com
Thanks
V2.2.0
+ Added algorithm 'dynex' (DYNEX coin) for GPU mining, fee 3.0%* [AMD/NVIDIA/INTEL]
+ Added INTEL ARC support for algorithms : autolykos2, etchash, ethash, ubqhash, blake3_ironfish
+ Added INTEL ARC support for dual mining : autolykos2/kaspa, autolykos2/heavyhash, autolykos2/sha512_256d_radiant, autolykos2/sha256dt, autolykos2/blake3_alephium, autolykos2/blake3_ironfish
+ Added dynex specific parameter '--mallob-endpoint'
+ Fixed 'blake3_ironfish' algorithm [also for DUAL modes]
+ Fixed 'sha256dt' algorithm for Nvidia ADA and HOPPER architectures
+ Added parameter '--disable-ptx-check' [nvidia]
+ Fixed bugs with NVIDIA OC parameters
Dynex:
Multiple pools & mallobs can be used.
There is no 'adj' parameter, to manually set the number of chips use '--gpu-intensity' parameter.
Dynex can be 'dual' mined with ZIL :
You can define multiple pools with the same/different wallets, miner will automatically failover when needed:
Windows users [ AMD GPUS ]:
Dynex POUW computations are long, so you should apply TDR fix [can be found in the Help folder], or else driver crashes might occur.
+ Added algorithm 'dynex' (DYNEX coin) for GPU mining, fee 3.0%* [AMD/NVIDIA/INTEL]
+ Added INTEL ARC support for algorithms : autolykos2, etchash, ethash, ubqhash, blake3_ironfish
+ Added INTEL ARC support for dual mining : autolykos2/kaspa, autolykos2/heavyhash, autolykos2/sha512_256d_radiant, autolykos2/sha256dt, autolykos2/blake3_alephium, autolykos2/blake3_ironfish
+ Added dynex specific parameter '--mallob-endpoint'
+ Fixed 'blake3_ironfish' algorithm [also for DUAL modes]
+ Fixed 'sha256dt' algorithm for Nvidia ADA and HOPPER architectures
+ Added parameter '--disable-ptx-check' [nvidia]
+ Fixed bugs with NVIDIA OC parameters
Dynex:
Multiple pools & mallobs can be used.
There is no 'adj' parameter, to manually set the number of chips use '--gpu-intensity' parameter.
Dynex can be 'dual' mined with ZIL :
Code:
--disable-cpu --algorithm dynex --mallob-endpoint mallob.neuropool.net:8081,https://dnx.eu.ekapool.com --pool dynex.neuropool.net:19331,dnx.eu.ekapool.com:19666,dnx.mineradnow.space:18000 --wallet dynex-wallet-here --zil-enable --zil-pool eu.crazypool.org:5005 --zil-wallet zil-wallet-here --zil-esm 2
You can define multiple pools with the same/different wallets, miner will automatically failover when needed:
Code:
--pool dynex.neuropool.net:19331,dnx.eu.ekapool.com:19666,dnx.mineradnow.space:18000 --wallet pool1-wallet,pool2-wallet,pool3-wallet
Windows users [ AMD GPUS ]:
Dynex POUW computations are long, so you should apply TDR fix [can be found in the Help folder], or else driver crashes might occur.
"mallob registration error" , no mining!
Nice, i waited for this update 
This will be a long night of testing
This will be a long night of testing
V2.2.0
+ Added algorithm 'dynex' (DYNEX coin) for GPU mining, fee 3.0%* [AMD/NVIDIA/INTEL]
+ Added INTEL ARC support for algorithms : autolykos2, etchash, ethash, ubqhash, blake3_ironfish
+ Added INTEL ARC support for dual mining : autolykos2/kaspa, autolykos2/heavyhash, autolykos2/sha512_256d_radiant, autolykos2/sha256dt, autolykos2/blake3_alephium, autolykos2/blake3_ironfish
+ Added dynex specific parameter '--mallob-endpoint'
+ Fixed 'blake3_ironfish' algorithm [also for DUAL modes]
+ Fixed 'sha256dt' algorithm for Nvidia ADA and HOPPER architectures
+ Added parameter '--disable-ptx-check' [nvidia]
+ Fixed bugs with NVIDIA OC parameters
Dynex:
Multiple pools & mallobs can be used.
There is no 'adj' parameter, to manually set the number of chips use '--gpu-intensity' parameter.
Dynex can be 'dual' mined with ZIL :
You can define multiple pools with the same/different wallets, miner will automatically failover when needed:
Windows users [ AMD GPUS ]:
Dynex POUW computations are long, so you should apply TDR fix [can be found in the Help folder], or else driver crashes might occur.
+ Added algorithm 'dynex' (DYNEX coin) for GPU mining, fee 3.0%* [AMD/NVIDIA/INTEL]
+ Added INTEL ARC support for algorithms : autolykos2, etchash, ethash, ubqhash, blake3_ironfish
+ Added INTEL ARC support for dual mining : autolykos2/kaspa, autolykos2/heavyhash, autolykos2/sha512_256d_radiant, autolykos2/sha256dt, autolykos2/blake3_alephium, autolykos2/blake3_ironfish
+ Added dynex specific parameter '--mallob-endpoint'
+ Fixed 'blake3_ironfish' algorithm [also for DUAL modes]
+ Fixed 'sha256dt' algorithm for Nvidia ADA and HOPPER architectures
+ Added parameter '--disable-ptx-check' [nvidia]
+ Fixed bugs with NVIDIA OC parameters
Dynex:
Multiple pools & mallobs can be used.
There is no 'adj' parameter, to manually set the number of chips use '--gpu-intensity' parameter.
Dynex can be 'dual' mined with ZIL :
Code:
--disable-cpu --algorithm dynex --mallob-endpoint mallob.neuropool.net:8081,https://dnx.eu.ekapool.com --pool dynex.neuropool.net:19331,dnx.eu.ekapool.com:19666,dnx.mineradnow.space:18000 --wallet dynex-wallet-here --zil-enable --zil-pool eu.crazypool.org:5005 --zil-wallet zil-wallet-here --zil-esm 2
You can define multiple pools with the same/different wallets, miner will automatically failover when needed:
Code:
--pool dynex.neuropool.net:19331,dnx.eu.ekapool.com:19666,dnx.mineradnow.space:18000 --wallet pool1-wallet,pool2-wallet,pool3-wallet
Windows users [ AMD GPUS ]:
Dynex POUW computations are long, so you should apply TDR fix [can be found in the Help folder], or else driver crashes might occur.
It is good to have pufferfish2bmb algo for Pandanite mining. Thank you for your work..
Cause you are using the old blockchain driver which can't allocate big buffers, and the DAG for Firo is 4+GB.
You need to use newer drivers, 19.x or newer
I've ran into this same problem with the latest SRBMiner-MULTI using the 20.4 drivers which is newer than 19.x with FiroPow. It seems to think my max buffer size is still 4GB and I'm not sure what to make of the 3004.80 driver version:
[2023-02-18 07:55:33] Starting init of worker threads
[2023-02-18 07:55:33] GPU DeviceID 0 [BUS:03] driver version: 3004.80
[2023-02-18 07:55:33] GPU DeviceID 0 [BUS:03] reported total memory: 8192 MB
[2023-02-18 07:55:33] GPU DeviceID 0 [BUS:03] reported free memory: 8074 MB
[2023-02-18 07:55:33] GPU DeviceID 0 [BUS:03] max buffer size: 4040 MB
If newer drivers are now required, which ones are good? The latest ones really hate bifurcation and everything freezes up for a minute when trying to enumerate them so hopefully I can use older ones that don't freeze up.
Also, I have this problem when trying to use --password with firopow. It says more passwords than pools given, even if I only just set a password and not try to pass in any parameters.
Thanks for all your help and writing this miner for all these years!
Hal
471.68
Try newer driver maybe. Or you try to mine the wrong algo. Nvidia is not supported for all algos at the moment.
RTX3060 work fine, but with newer driver, will try new driver version.
Even INTEL came but FLUX algorithm did not come.
We wait by digging in Lolminer
We wait by digging in Lolminer
471.68
Try newer driver maybe. Or you try to mine the wrong algo. Nvidia is not supported for all algos at the moment.
471.68
Jump to: