papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 07, 2017, 04:28:53 PM |
|
Hi
I'm testing the v19 and I'm completely lost with the XMR mining client
what I have to do if I want to mine XMR with my NVIDIA (not the CPU)
I've set XMR for the coin and I'm seeing a lot of miner process to popup and reboot
thanks
You mine to your wallet? (which pool?)I haven't mined XMR using 1bash yet! (I've mined it using other ways) My guess would be, you may need to disable 'WATCH_DOG'! (because XMR doesn't use memory!!) - hope someone mining XMR will correct me if I'm wrong. (my assumption is WATCH_DOG restarting the miner) Please put any screenshots of errors! ('WATCH_DOG' log probably), can help you further using them. I'm mining toward exchange (bittrex) I've specify add.payID.workername the issue now is the hashrate is too low HASHRATE REPORT | ID | 10s | 60s | 15m | | 0 | 623.2 | 623.2 | (na) | --------------------------- Totals: 623.2 623.2 (na) H/s Highest: 623.3 H/s hHASHRATE REPORT | ID | 10s | 60s | 15m | | 0 | 623.2 | 623.2 | (na) | --------------------------- Totals: 623.2 623.2 (na) H/s Highest: 623.3 H/s I've 7 GPU 1070 and nvidia-smi is showing low GPU utilisation Thu Sep 7 11:45:50 2017 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 384.59 Driver Version: 384.59 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===============================+======================+======================| | 0 GeForce GTX 1070 Off | 00000000:01:00.0 On | N/A | | 37% 60C P2 85W / 125W | 1416MiB / 8113MiB | 100% Default | +-------------------------------+----------------------+----------------------+ | 1 GeForce GTX 1070 Off | 00000000:03:00.0 Off | N/A | | 50% 36C P8 9W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 2 GeForce GTX 1070 Off | 00000000:06:00.0 Off | N/A | | 50% 38C P8 9W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 3 GeForce GTX 1070 Off | 00000000:07:00.0 Off | N/A | | 50% 37C P8 9W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 4 GeForce GTX 1070 Off | 00000000:08:00.0 Off | N/A | | 50% 34C P8 10W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 5 GeForce GTX 1070 Off | 00000000:09:00.0 Off | N/A | | 50% 33C P8 8W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ | 6 GeForce GTX 1070 Off | 00000000:0A:00.0 Off | N/A | | 50% 30C P8 9W / 125W | 19MiB / 8114MiB | 0% Default | +-------------------------------+----------------------+----------------------+ I've switched off Watchdog, it's better has the reboot have stopped It seems GPU 1 to 6 are not mining at all They are all 0% Yes I guess there is an issue with 3main which does not give the right instruction setup is 7 x 1070 ZEC mining and ETH/SC work perfectly Have you set cpu mining to off ?
|
|
|
|
argonaute
Newbie
Offline
Activity: 50
Merit: 0
|
|
September 07, 2017, 04:33:08 PM |
|
Have you set cpu mining to off ?
yep, for sure looks like 3main select only one GPU for a reason I don't know
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 04:54:46 PM |
|
genoil does not report current hashrate to pool. i'm mining etc on nanopool.
is there a way to make it report the hashrate as it would make checking on the rig much easier. with varying hashrates it's difficult to tell whether all gpus are running.
This is something to ask genoil to change; you can use Claymore if you want to ensure default hashrate is reported to your pool.
|
|
|
|
Bibi187
Full Member
Offline
Activity: 420
Merit: 106
https://steemit.com/@bibi187
|
|
September 07, 2017, 04:57:18 PM |
|
Hey guys, i missing something ... I have default file on nvOC, i just modify stresst count on GPU to trigger restart more fast if GPU crash, from 6 cycles verification to 4 cycles. My problem is when i have nvOC launched, if my miner crash, 1bash will launch a dual miner process every time ... So i finish with 2 processing miner running, but i lost some perf. I test it by hand, i close miner process, launch "1bash" and again i get dual process launch EDIT : any fix about this issue ? Tell me more about it; Is it mining same dual coin every time? What is the coin you are actually trying to mine? I actually mining ETH + SC, is simple, on first boot is ok. After if i get a software crash and get reset, i got 2 miner processing working in same time. Same problem, if i stop wdog process, i stop miner process. I do "bash 1bash", screen -ls show me two miner processor running ... in v0019 you should launch 3main , and every time you kill 3main it will launch again. so kill miner by then kill 3main by 3main should be launched again with 1 miner after you killed 3main check if its running again with cannot kill 3main, use pkill -f 3main. Good call, didnt know that Thanks for mentioning. Thanks for your answer That prolly why when i test it i got 2 miner process launched. Any fix about my true issue ? When miner is restart from watchdog i get 2 process launched not one.
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:05:58 PM |
|
Tell me, in this OS there is a possibility to change the core voltage?
You cannot do this in nvOC. If you manually change the coolbits to 33 or some other 30ish number it might work; but most likely it will not.
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:09:01 PM |
|
Thank you, i just tried this. My 1bash setting has -dcri 40 argument, but when i use + and - keys dcri starts changing from 70, so my setting 40 not works. When i manualy lower it to 40 and then restart terminal miner, it again become 70
Where did you set your -dcri 40 at? Did you change any other files besides onebash? If all you changed was onebash, paste your settings here and I'll look over them for you if you'd like. (remove your wallet addresses if your paranoid) Thanks for looking I didn't change anything, only 1bash. USE_ENVIRONMENTAL_VARIBLES="NO" #YES NO
DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT="SLASH" # DOT or SLASH # formerly ETHERMINEdotORG
CLAYMORE_VERSION="9_7" # choose 9_8 or 9_7 or 9_5 or 9_4 or 8_0
ETHMINER_or_GENOIL_or_CLAYMORE="CLAYMORE" # choose ETHMINER or GENOIL or CLAYMORE
ETH_WORKER="$WORKERNAME" ETH_ADDRESS="xxxxxxxxxxxxxxxxxxxxxxxxxxx" ETH_POOL="eth-eu1.nanopool.org:9999" ETH_EXTENTION_ARGUMENTS="-dcri 40" # add any additional claymore arguments desired here Interesting. Have you tried to close and restart the miner after manually adjusting the dcri? Have you also tried to use version 9_8? Yes, i did, dcri become 70 again. At 9.8 i have low ETH hashrate at solo i i swiched back to 9.7 Hey, what coin you are trying to mine?? Or paste the result of this command: You can wipe out your addresses (but no body can do anything by just knowing your wallet addresses ) Im mining DUAL ETH_SC m1 2435 99.7 0.8 416748 34156 pts/18 Sl+ 02:06 22:32 /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://xmr-eu1.nanopool.org:14444 -u 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB.4a0aa02594986680ea5a1216d96f5643b6c19773cfce33e58e2be74336ae5f 5c.053 -p x -t 1 m1 2590 0.0 0.0 27488 2920 ? Ss 02:06 0:00 SCREEN -dmS miner /home/m1/eth/9_7/ethdcrminer64 -epool eth-eu1.nanopool.org:9999 -ewal 0x73736a74f5d80ad6c8c71a4e0651e9dfff789a13/053 -epsw x -allpools 1 -dpool sia-eu1.nanopool.org:7777 -dwal 395a59c4328253491ef79bf01dd637444e79a0d64b92ca56e06087dd8bfc10ef794d1ed1d1a9/053 -dpsw x -dcoin sc -dcri 70 -dbg -1 m1 2591 0.0 0.0 27056 2844 pts/17 S+ 02:06 0:00 screen -r miner m1 2592 3.5 20.1 189844572 803408 pts/21 Ssl+ 02:06 0:48 /home/m1/eth/9_7/ethdcrminer64 -epool eth-eu1.nanopool.org:9999 -ewal 0x73736a74f5d80ad6c8c71a4e0651e9dfff789a13/053 -epsw x -allpools 1 -dpool sia-eu1.nanopool.org:7777 -dwal 395a59c4328253491ef79bf01dd637444e79a0d64b92ca56e06087dd8bfc10ef794d1ed1d1a9/053 -dpsw x -dcoin sc -dcri 70 -dbg -1 m1 4187 0.0 0.0 14224 1060 pts/16 S+ 02:28 0:00 grep --color=auto miner m1@m1-desktop:~$
cpu mining is enabled too disable it How cpu mining can change dcri? The question is how to change dcri argument in 0019. In 1bash dcri setting does not work for me Well, if you are intentionally doing CPU mining (& you are aware of it) that's fine, it doesn't impact the DCRI at all. You can set up or change dcri in 1bash or 3main or even both The thing is, answer is in the result of 'ps aux | grep miner'. Look closely, you can see -dcri 70 in it. So fix goes like this (Trust me, this works) : Go to 3main; search for 'ETC_SC' find this highlighted line; screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 70 -dbg -1 $ETC_EXTENSION_ARGUMENTS Delete that highlighted bit (if you are intending to add it in 1bash 'ETC_EXTENSION_ARGUMENTS'); and it should look like this: screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dbg -1 $ETC_EXTENSION_ARGUMENTS and add that dcri value here ETC_EXTENTION_ARGUMENTS="-dcri 40" or you can even change it from '70' to '40' and don't add any thing under 'ETC_EXTENSION_ARGUMENTS' (it doesn't even matter even if you have same dcri value in 2 places ) screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 40 -dbg -1 $ETC_EXTENSION_ARGUMENTS do the same for 'ETH_SC' by searching 'ETH_SC' in 3main screen -dmS miner $HCD -epool $ETH_POOL -ewal $ETHADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 70 -dbg -1 $ETH_EXTENSION_ARGUMENTS Try this it will definitely work, let me know if you still see any issue of it. Now it works. THANK YOU Glad it worked! You are welcome Thanks for Helping damNmad. I will move the -dcri to be a default EXTENSION_ARGUMENT rather than being hardcoded in 3main in the future to prevent this potential problem in the future; I believe doing so was damNmad's idea.
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:10:05 PM |
|
how do I stop wdog in v0019? selecting no in 1bash doesn`t help.
If you can see it running on Guake? kill it by using CTRL + c You can also use: to kill the mining process, autotemp and watchdog all at once.
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:17:21 PM |
|
Anone managed to start NVOC version 19 with built-in VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs
As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig. I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen? (I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time) Sep 5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes. Sep 5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager... Sep 5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager. Sep 5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file Sep 5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file Sep 5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Sep 5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state. Sep 5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'. Sep 5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Sep 5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager. Sep 5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes... Sep 5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file Sep 5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes. Sep 5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager... Sep 5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager. Sep 5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file Sep 5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file Sep 5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Sep 5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state. Sep 5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'. Sep 5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart. Sep 5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager. Sep 5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes... Sep 5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file Sep 5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file] Sep 5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf Sep 5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes. Sep 5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager... Sep 5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.
i also have following errors in syslog, in clean nvos019 install. I suppose it's kinda tails from previous usage of "SanDisk_Cruzer_Blade", because I've never used such device. Sep 6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out. Sep 6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device. Sep 6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1. Sep 6 02:13:06 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'. Sep 6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'. Sep 6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out. Sep 6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device. Sep 6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB. Sep 6 02:13:06 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'. Sep 6 02:13:06 m1-desktop systemd[1]: Startup finished in 7.010s (kernel) + 1min 30.221s (userspace) = 1min 37.231s. Sep 6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.
Can anybody guess what to do to make this thing work? thanks in advance! ok i'm talking with myself but this becomes useful to solve the problem After a little research i've finally launched mining full headless rig of asus z270-p with 7 gp106-100 onboard. Problem was in xorg configuration, nvidia utility helped to solve it: sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration sudo reboot
Now all works fine including overclocking and powerlimits, just one trouble left - if I connect 8-th GPU, nvOS hangs on boot I included an unverified logic which conditionally reconfigures the xorg.conf in v0019 when: P106_100_FULL_HEADLESS_MODE="YES" perhaps I should have included the forced reconfiguration everytime instead. you can change this portion of 3main to change this manually: find this area in 3main by ctrl + f with gedit or using the vi cmds to search for: P106_100_FULL_HEADLESS_MODE then change this code block: UPDATE="YES"
if [ $P106_100_FULL_HEADLESS_MODE == "YES" ] then if grep -q "XORG_UPDATED" /home/m1/xorg_flag; then sleep 2 UPDATE="NO" fi if [ $UPDATE == "YES" ] then sudo nvidia-xconfig --enable-all-gpus --cool-bits=12 cd /home/m1 echo XORG_UPDATED > '/home/m1/xorg_flag' sleep 4 echo "XORG UPDATED" echo '' echo "Rebooting in 5" echo '' echo "disconnect monitor if connected" sleep 5 sudo reboot fi sleep 4 to: UPDATE="YES"
if [ $UPDATE == "YES" ] then sudo nvidia-xconfig --enable-all-gpus --cool-bits=12 sleep 4 echo "XORG UPDATED" fi sleep 4
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:19:29 PM |
|
Hey guys, i missing something ... I have default file on nvOC, i just modify stresst count on GPU to trigger restart more fast if GPU crash, from 6 cycles verification to 4 cycles. My problem is when i have nvOC launched, if my miner crash, 1bash will launch a dual miner process every time ... So i finish with 2 processing miner running, but i lost some perf. I test it by hand, i close miner process, launch "1bash" and again i get dual process launch EDIT : any fix about this issue ? Tell me more about it; Is it mining same dual coin every time? What is the coin you are actually trying to mine? I actually mining ETH + SC, is simple, on first boot is ok. After if i get a software crash and get reset, i got 2 miner processing working in same time. Same problem, if i stop wdog process, i stop miner process. I do "bash 1bash", screen -ls show me two miner processor running ... in v0019 you should launch 3main , and every time you kill 3main it will launch again. so kill miner by then kill 3main by 3main should be launched again with 1 miner after you killed 3main check if its running again with cannot kill 3main, use pkill -f 3main. Good call, didnt know that Thanks for mentioning. Thanks for your answer That prolly why when i test it i got 2 miner process launched. Any fix about my true issue ? When miner is restart from watchdog i get 2 process launched not one. More aggressive process killing is needed in some of the nvOC logic; I will add these changes.
|
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
September 07, 2017, 05:24:53 PM |
|
Have you set cpu mining to off ?
yep, for sure looks like 3main select only one GPU for a reason I don't know this is due to a problem with the 3main implementation wi$em@n found; but I haven't fixed yet. You can do this manually for now by finding this area in 3main: if [ $COIN == "XMR" ] then HCD='/home/m1/xmr/stakGPU/bin/xmr-stak-nvidia' ADDR="$XMR_ADDRESS.$XMR_WORKER"
cat <<EOF >/home/m1/xmr/stakGPU/bin/config.txt
"gpu_threads_conf" : [ { "index" : 0, "threads" : 32, "blocks" : 18, "bfactor" : 8, "bsleep" : 10, "affine_to_cpu" : false, }, ],
"use_tls" : false, "tls_secure_algo" : true, "tls_fingerprint" : "",
"pool_address" : "$XMR_POOL", "wallet_address" : "$ADDR", "pool_password" : "x",
"call_timeout" : 10, "retry_time" : 10, "giveup_limit" : 0,
"verbose_level" : 4,
"h_print_time" : 60,
"output_file" : "",
"httpd_port" : 0,
"prefer_ipv4" : true EOF
cd /home/m1/xmr/stakGPU/bin
screen -dmS miner $HCD
if [ $LOCALorREMOTE == "LOCAL" ] then screen -r miner fi and adding an additional: gpu_threads_conf" : [ { "index" : 0, "threads" : 32, "blocks" : 18, "bfactor" : 8, "bsleep" : 10, "affine_to_cpu" : false, }, { "index" : 1, "threads" : 32, "blocks" : 18, "bfactor" : 8, "bsleep" : 10, "affine_to_cpu" : false, }, { "index" : 2, "threads" : 32, "blocks" : 18, "bfactor" : 8, "bsleep" : 10, "affine_to_cpu" : false, }, { "index" : 3, "threads" : 32, "blocks" : 18, "bfactor" : 8, "bsleep" : 10, "affine_to_cpu" : false, }, ], index block per GPU to the "gpu_threads_conf" as the above would be for 4x gpus.
|
|
|
|
gdemon
Newbie
Offline
Activity: 4
Merit: 0
|
|
September 07, 2017, 06:00:10 PM |
|
v0019 missing power. / home / m1 / 3main: line 53: nvidia-smi: command not found what to do?
|
|
|
|
elsystem
Newbie
Offline
Activity: 46
Merit: 0
|
|
September 07, 2017, 06:26:15 PM |
|
Is it possible to cpu mine Zcoin and gpu mine simultaneously on nvoc?
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
September 07, 2017, 06:54:00 PM |
|
Thank you, i just tried this. My 1bash setting has -dcri 40 argument, but when i use + and - keys dcri starts changing from 70, so my setting 40 not works. When i manualy lower it to 40 and then restart terminal miner, it again become 70
Where did you set your -dcri 40 at? Did you change any other files besides onebash? If all you changed was onebash, paste your settings here and I'll look over them for you if you'd like. (remove your wallet addresses if your paranoid) Thanks for looking I didn't change anything, only 1bash. USE_ENVIRONMENTAL_VARIBLES="NO" #YES NO
DOT_POOL_FORMAT_or_FORWARD_SLASH_POOL_FORMAT="SLASH" # DOT or SLASH # formerly ETHERMINEdotORG
CLAYMORE_VERSION="9_7" # choose 9_8 or 9_7 or 9_5 or 9_4 or 8_0
ETHMINER_or_GENOIL_or_CLAYMORE="CLAYMORE" # choose ETHMINER or GENOIL or CLAYMORE
ETH_WORKER="$WORKERNAME" ETH_ADDRESS="xxxxxxxxxxxxxxxxxxxxxxxxxxx" ETH_POOL="eth-eu1.nanopool.org:9999" ETH_EXTENTION_ARGUMENTS="-dcri 40" # add any additional claymore arguments desired here Interesting. Have you tried to close and restart the miner after manually adjusting the dcri? Have you also tried to use version 9_8? Yes, i did, dcri become 70 again. At 9.8 i have low ETH hashrate at solo i i swiched back to 9.7 Hey, what coin you are trying to mine?? Or paste the result of this command: You can wipe out your addresses (but no body can do anything by just knowing your wallet addresses ) Im mining DUAL ETH_SC m1 2435 99.7 0.8 416748 34156 pts/18 Sl+ 02:06 22:32 /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://xmr-eu1.nanopool.org:14444 -u 47sghzufGhJJDQEbScMCwVBimTuq6L5JiRixD8VeGbpjCTA12noXmi4ZyBZLc99e66NtnKff34fHsGR oyZk3ES1s1V4QVcB.4a0aa02594986680ea5a1216d96f5643b6c19773cfce33e58e2be74336ae5f 5c.053 -p x -t 1 m1 2590 0.0 0.0 27488 2920 ? Ss 02:06 0:00 SCREEN -dmS miner /home/m1/eth/9_7/ethdcrminer64 -epool eth-eu1.nanopool.org:9999 -ewal 0x73736a74f5d80ad6c8c71a4e0651e9dfff789a13/053 -epsw x -allpools 1 -dpool sia-eu1.nanopool.org:7777 -dwal 395a59c4328253491ef79bf01dd637444e79a0d64b92ca56e06087dd8bfc10ef794d1ed1d1a9/053 -dpsw x -dcoin sc -dcri 70 -dbg -1 m1 2591 0.0 0.0 27056 2844 pts/17 S+ 02:06 0:00 screen -r miner m1 2592 3.5 20.1 189844572 803408 pts/21 Ssl+ 02:06 0:48 /home/m1/eth/9_7/ethdcrminer64 -epool eth-eu1.nanopool.org:9999 -ewal 0x73736a74f5d80ad6c8c71a4e0651e9dfff789a13/053 -epsw x -allpools 1 -dpool sia-eu1.nanopool.org:7777 -dwal 395a59c4328253491ef79bf01dd637444e79a0d64b92ca56e06087dd8bfc10ef794d1ed1d1a9/053 -dpsw x -dcoin sc -dcri 70 -dbg -1 m1 4187 0.0 0.0 14224 1060 pts/16 S+ 02:28 0:00 grep --color=auto miner m1@m1-desktop:~$
cpu mining is enabled too disable it How cpu mining can change dcri? The question is how to change dcri argument in 0019. In 1bash dcri setting does not work for me Well, if you are intentionally doing CPU mining (& you are aware of it) that's fine, it doesn't impact the DCRI at all. You can set up or change dcri in 1bash or 3main or even both The thing is, answer is in the result of 'ps aux | grep miner'. Look closely, you can see -dcri 70 in it. So fix goes like this (Trust me, this works) : Go to 3main; search for 'ETC_SC' find this highlighted line; screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 70 -dbg -1 $ETC_EXTENSION_ARGUMENTS Delete that highlighted bit (if you are intending to add it in 1bash 'ETC_EXTENSION_ARGUMENTS'); and it should look like this: screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dbg -1 $ETC_EXTENSION_ARGUMENTS and add that dcri value here ETC_EXTENTION_ARGUMENTS="-dcri 40" or you can even change it from '70' to '40' and don't add any thing under 'ETC_EXTENSION_ARGUMENTS' (it doesn't even matter even if you have same dcri value in 2 places ) screen -dmS miner $HCD -epool $ETC_POOL -ewal $ETCADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 40 -dbg -1 $ETC_EXTENSION_ARGUMENTS do the same for 'ETH_SC' by searching 'ETH_SC' in 3main screen -dmS miner $HCD -epool $ETH_POOL -ewal $ETHADDR -epsw x -allpools 1 -dpool $SC_POOL -dwal $SCADDR -dpsw x -dcoin sc -dcri 70 -dbg -1 $ETH_EXTENSION_ARGUMENTS Try this it will definitely work, let me know if you still see any issue of it. Now it works. THANK YOU Glad it worked! You are welcome Thanks for Helping damNmad. I will move the -dcri to be a default EXTENSION_ARGUMENT rather than being hardcoded in 3main in the future to prevent this potential problem in the future; I believe doing so was damNmad's idea. Thanks fullzero, yeah having dcri as default EXTENSION_ARGUMENT will be the best way going forward. (will do that in my upcoming 1bash)
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 07, 2017, 07:04:10 PM |
|
It would be nice to implement unified zpool worker name into zpool password in the new 1bash and 3main if use bitcoin for zpool ZPOOLWORKER="$WORKERNAME,c=BTC"
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
September 07, 2017, 07:26:51 PM |
|
It would be nice to implement unified zpool worker name into zpool password in the new 1bash and 3main if use bitcoin for zpool ZPOOLWORKER="$WORKERNAME,c=BTC" Point duly taken papampi Will add it to my upcoming version; You suggested couple of coins after ZPOOL_EQUIHASH and MPH_EQUIHASH? can you please re post them here. From now on, I will make a list and add them simultaneously. Thanks
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 07, 2017, 07:32:01 PM |
|
It would be nice to implement unified zpool worker name into zpool password in the new 1bash and 3main if use bitcoin for zpool ZPOOLWORKER="$WORKERNAME,c=BTC" Point duly taken papampi Will add it to my upcoming version; You suggested couple of coins after ZPOOL_EQUIHASH and MPH_EQUIHASH? can you please re post them here. From now on, I will make a list and add them simultaneously. Thanks Thanks mate No special requests 👍👍 Was gonna tell you that I have plenty free time in coming days and can help adding coins, but u got me first. So let me know what coins are already done and we can add what's left in MPH and Zpool algo- mining
|
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
September 07, 2017, 07:35:32 PM |
|
I think I posted these 3 configs ZPOOL_EQUIHASH ZPOOL_NEOSCRYPT MPH_EQUIHASH
|
|
|
|
Temporel
|
|
September 07, 2017, 07:44:58 PM |
|
Im building another rig next week and I want to try nv OC or SMos, not sure which one Ill try first yet.
Here are the main parts Im waiting for: ASRock H110 Pro BTC+ 12 Asus GTX-1070 16GB RAM m.2 SSD
Anything I should know before I start ?
TYIA
|
|
|
|
leenoox
|
|
September 07, 2017, 08:06:38 PM |
|
Has anyone tried using Firefox in nvOC while mining? It is painfuly slow even on my rigs with i7 cpu's. Same thing happens in v18 and v19. If I kill the mining process Firefox works well. Strange... fullzero, any idea what might cause firefox to crawl like that?
|
|
|
|
dstm
|
|
September 07, 2017, 08:13:31 PM |
|
Has anyone tried using Firefox in nvOC while mining? It is painfuly slow even on my rigs with i7 cpu's. Same thing happens in v18 and v19. If I kill the mining process Firefox works well. Strange... fullzero, any idea what might cause firefox to crawl like that?
It's because your GPU is fully loaded when u start mining, so it needs more time to draw the screen
|
|
|
|
|