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

Hi @doktor83, when miner auto restart/reconnect for cpu algos will be fixed?
https://i.imgur.com/Tt87p2T.png

Also EPIC cpu dual minig is glitching.

gtx 1070 stopped working completely with 2.2.4 - crashing on init, lowering intensity does not help, back to 2.2.3. --dynex-cpu-pow 0 stil not working with rx 5700, even with lower intensity.

Still can't get core clock offsett and memory clock offset to work. I tried with --gpu-coffset, --gpu-coffset0,  --gpu-moffset and --gpu-moffset0 , but the clocks always fail
https://i.postimg.cc/wB69NBGK/Untitled.png

Dok please, add support for R9380-280x Dynex

V2.2.4
+ Improved mining performance on algorithm 'dynex' for AMD/NVIDIA/INTEL
+ More chips can now fit in VRAM on algorithm 'dynex'
+ Lowered devfee for algorithm 'dynex' to 2.5%
+ Small hashrate improvements on algorithm 'blake3_alephium' & lower power consumption
+ Small hashrate improvements on algorithm 'blake3_ironfish' & lower power consumption
+ Fixed --gpu-coffset and --gpu-moffset parameters on Windows
+ Minor bug fixes

I waiting gfx900 Kawpow support
may be between 2,5 Mh - 3 Mh

2.2.2 and 2.2.3 is crashing on gpu initializing after adding --dynex-cpu-pow 0. If i remove it, srbminer starts fine.
RX 5700 XT, win 10 with latest driver.

Absolute impressive for this old boy  
how are your oc settings? Did your read the watts from the wall? And is this with POUW on CPU or GPU? I must start playing again with the old boys 

RX570 mines DNX coin


https://t.me/Info4atlanin/8864

V2.2.3
+ Improved mining performance on algorithm 'dynex' for AMD/NVIDIA
+ Added fan control for NVIDIA GPU'S : --gpu-fan0, --gpu-fan1, --zil-fan parameters
+ Added support for gfx900 on ROCM drivers for algorithm 'dynex'
+ Minor bug fixes

To answer your question about MSR tweaks read about it on XMRig as they explain it very well, secondly MSR tweaks can only be done as root and is for CPU's only.
So SRBMiner-MULTI and XMRig have to be running as root to make use of MSR, and bytheway you forgot to mention whicj linux distro you are using.

As for the dev fee pool issue it's probably on your end only as otherwise there would be way more people complaining about it.

"Couldn't connect to the dev fee pool, miner is PAUSING" like seriously bro??? So if your pool is down then the miner just stops mining ? Also thanks for replying to my previous question, NOT!

V2.2.2
+ Moved CPU part of the POUW work for algorithm 'dynex' on NVIDIA GPU's to the GPU*
+ Better utilization of CPU's that have more threads than running GPU's for algorithm 'dynex'
+ Parameter '--dynex-cpu-pow' now expects GPU id's of devices on which you want to use the old CPU POW method
+ Increased value of auto intensity a little bit under Linux OS for algorithm 'dynex'*
+ Minor bug fixes

***
Good news for NVIDIA GPU'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
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 use the --dynex-cpu-pow parameter,
list all the GPU id's and the additional work will again be calculated on the CPU side.


***
Info:
Auto intensity (when you don't set --gpu-intensity parameter manually) can set a too high value now, mainly because
on some systems video driver reports more free memory for the GPU than there really is.
Also devices that have a display (monitor) attached will probably need to manually lower intensity.

In this case a few things can happen :

- gpu works but hashrate is lower than expected (previous version)
- gpu errors and won't start working
- gpu crashes

You should manually set the gpu intensity in these cases with --gpu-intensity parameter.
The initial (auto set) value can be seen on miner start.
Decrease that value and do some tests.

Hi, @doktor83, how about cn_gpu/cn_xvh/cn_upx for nvidia?

--gpu-intensity 480 - does not work, "no jobs for mallob/s: error" and the miner closes ..... how to spell it correctly? tried and 360, and other - Does not help

@doktor83, on Radiant I have very high CPU usage on older motherboards and that way the hashrate drops a lot, is there any way to improve it? On new modern CPUs there is no problem of course and your miner is giving the highest Radiant hashrate.

Mallob errors are not miner related, but dynex mallob related.
There are numerous reasons best is to seek help on Dynex discord.

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.

Same problem, can't start the miner.

"mallob registration error" , no mining DNX ! what to do?