Dear all who work on this. Thank you so much for everything. The 19-1.4 version was great, but the 2.0 is much better for me so I'm sticking with community builds going forward.
Would love to help, but I'm not the greatest scriptkiddie.
Couple of suggestions for 19-2.1:
1: Can we add GPU support for GPU19 (b250 mining board). I can manually add this myself with simple copy and paste etc, but it would be good to just have that rolled out to all.
2: I see in the community page on nvoc-mining that states, under the updatelog: There are community builds that have numerous bug fixes and 1 community build has an auto overclocker.
Is this just expressing the ability to overclock with the config files or has someone scripted nvidia-smi -q | grep -A 5 "Max Clocks" | grep "Memory" to compile the max settings for each card and then automatically overclock your cards? (I'm using a multi-model rig with different nvidias for benchmarking. 1060 3gb/6gb/1070 etc. Hoping to obtain more soon.) I started working on this, but ultimately I keep getting the failed mir error and lost my attempt when updating to 19-2.
3: Rather than dual mining, can we integrate two separate miners? I scripted the following to allow hynix memory to mine ZEC as they only suffer when mining ETHash.
#!/bin/bash
#Ask for GPUs to use
echo "Enter the GPU numbers separated by spaces (e.g. 0 1 2 3)"
read gpus
ZEC_WORKER="19.4_0"
# replace_with_your_ZEC_address
ZEC_ADDRESS="t1Uzd2zmuJyxYGPfpLs1wZaGqjE33TM72c3"
ZEC_POOL="zec-us-east1.nanopool.org"
ZEC_PORT="6666"
ZECADDR="$ZEC_ADDRESS.$ZEC_WORKER"
#if [ $ZM_or_EWBF == "ZM" ]
HCD='/home/m1/zec/zm/5_2/zm_miner'
screen -dmSL MultiMiner $HCD --server $ZEC_POOL --user $ZECADDR --pass z --port $ZEC_PORT --dev $gpus
echo ""
echo "Starting Ande's MultiMiner on GPU's $gpus"
It's all stolen from the 3main file (now 0miner). I start mining ETH and any card performing under the benchmark of the others gets disabled (number key in claymore), then I run ./multi and enter "3 5 6" and this starts mining just those cards.
That may be specific to my setup and not included, that's no problem, just thinking it might help others.
Something like 1bash addition:
BI-MINING="YES" #YES or NO
#DECLARE COIN
BI_GPU0="ETH"
BI_GPU1="ETH"
BI_GPU2="ETH"
BI_GPU3="ZEC"
BI_GPU4="ETH"
BI_GPU5="ZEC"
BI_GPU6="ZEC"
BI_GPU7="ETH"
BI_GPU8="ETH"
3main addition:
if [ BI-MINING == "YES" ]
for i in $BI_GPU $i
if [ echo $BI_GPU$i == ZEC ]
screen -S miner -X exec $i ##This command doesn't work, it's a failed attempt to enter screen and press the GPU that is needed for equihash.
$i+1 loop until maxed
fi
-------
Not sure what will be of use and what wont, but thanks again, even if these are useless to the community, I'm really glad I found nvOC. Excellent work guys.
#New2Mining
#New2Forum
#NoSignature
#Hashtag
LOL, you've got the term "scriptkiddie" mixed... it refers to hacker-wannabes, the "hackers" that use scripts/programs made by real hackers but have no clue on how and why those scripts work
It has nothing to do with developers that code the scripts
Anyway,
#1. The support for 19 GPU's is already implemented. Numbering starts at GPU0, ends at GPU18, That's a total of 19 GPU's. However, this board had problems with more than 13 GPU's. To get 19 working you need 13 regular + 6 GP106. Asus was promising to fix this with a bios update but to my knowledge it hasn't been fixed yet.
#2. The Comunity Release does not have auto overclock feature. There is another fork that is experimenting with auto overclock but my understanding is that it is hit and miss. It works for some people, it doesn't for other. IMO, the implementation is not mature, not stable and not recommended unless you are willing to risk the lifespan of your GPU's and/Or willing to risk downtime due to freezing.
#3. The multi-miner feature is planned and under development. It probably won't be ready for 19-2.1, hopefully will be implemented in the next release after 2.1.
It requires a complete overhaul of nvoc's operation to make sure it works for all (most) miners while properly overclocking the assigned GPU's to the proper algo chosen. I don't want to rush this feature and release a buggy code... let's make it right.
Thanks for choosing nvoc and for your support and feedback.
