How can I control the speed of the fans directly in the miner?
Currently you can not and I think that will remain so for a while. Why?
Well because there is no way doing that for AMD and Nvidia for all OS (Win 7, Win 10, Linux) the same way.
So the codibg would bind a lot of capacities at my side (I develop this miner alone alongside my dayjob and family) that I rather spend for creating better minibg code. Furthermore it is a matter of resposability. A corrupt kernel code can make a rig hang and can make it require a reboot, but thats it. A bug in overclocking or fan setting routine can physically harm hardware - that I do not like much. Maybe I will do temp reading in future and provide it over the API but I do not think fan or OC setting will come anyhow soon.
Hi. Can i use only 1 or 2 graphic cards of my rig? No matter what i do lolminer is using all of cards and i want to shut down 1 of them. Can i do it?
You are running with config file? Then you can modify the profile of the coin (or default section) by adding
For example to run on first and 3rd GPU but skipping the second. Note if you put this to default section it will be overwritten by a devices entry in the individual profile.
For command line use it should be
doing the same thing.
Benchmark shows this on my 56/64 vega rig for 144.5:
...
Average speed (5s): 62.6 sol/s | 56.0 sol/s | 56.6 sol/s | 61.4 sol/s | 60.4 sol/s | 44.0 sol/s Total: 340.9 sol/s
Average speed (5s): 63.2 sol/s | 58.6 sol/s | 58.6 sol/s | 59.8 sol/s | 59.6 sol/s | 43.2 sol/s Total: 342.9 sol/s
---------------------------------------------
Average speed (60s): 61.8 sol/s | 57.2 sol/s | 56.7 sol/s | 61.5 sol/s | 56.9 sol/s | 46.4 sol/s Total: 340.7 sol/s
I also get invalid share and some warnings/errors:
Hmm something is wrong here. The speed you see is much higher then I would expect for this cards - I rather would think about 30 to 35 to be realistic. No real idea why at the moment but I think something in tge filtering is broken. The miner after last round checks the solutions and filters out incomplere ones. Seems that does not work here and more solutions pass the check then it should. No idea why, but this is not good.
The warning message you got is no problem. This has something to do with a bit fancy pointer magic in GPU code ^^ But I wonder: this messages should not be displayed - you are certainly running 0.42? I think thats an older version.
seems it doesn't work for vegas on linux
Doesn't work at yours? What driver you use for the vegas, the ROCm or the amdgpu-pro?
I have no vega myself, so can not trst directly but with some detail info I think we can debug it
That's a pretty amazingly dramatic performance improvement.
I think there os a bug - your 30 to 33 sols / s is more realistic and in region so I am shure the solutions are all valid. I think in his case something is broken, but will have to see what exactly.
Hope in future versions to put some sol/s on top of cause. New code is already work in progress