damNmad
Full Member
 Offline
Activity: 378
Merit: 104
nvOC forever
|
 |
February 27, 2018, 05:18:19 PM |
|
Hi guys,
as a newbie to linux i have to thank all developers for their work. Thank you guys and please don´t stop, if you did, you would leave people like me hanging in the cold.
A problem i encountered with the new community release version 2.0 is the following.
If i try to connect any of my rigs (doesn´t matter whether nvidia or amd cards) to any etn pool (doesn´t matter as well which pool it is) nvOC uses KTccminer as the miner but once i connect the pool always sets the difficulty at 19, exactly at 19 and this repeats no matter what rig i connect to what etn pool. I had all rigs running under 19. 1.4 and everything was good, now i can´t connect to any of the etn pools.
Any suggestions?
It uses 'KTccminer-cryptonight' Can you paste result of this command (type in guake) ps aux | grep miner Paste the result over here. Can you also paste the ETN coin details you have in 1bash? Thanks for trying to help this is the result of your command m1@m1-desktop:~$ ps aux | grep miner m1 10259 288 0.6 564212 49368 pts/17 Sl+ 22:37 2:15 /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://pool.etnminers.com:3333 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ.1600.19_2_ASGT405XE3 -p x -t 3 m1 10553 0.0 0.0 27188 2896 ? Ss 22:37 0:00 SCREEN -dmSL miner /home/m1/KTccminer-cryptonight/ccminer -o stratum+tcp://pool.etnminers.com:7777 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ.19_2_ASGT405XE3 -p x m1 10554 12.5 5.1 64984620 414744 pts/24 Ssl+ 22:37 0:04 /home/m1/KTccminer-cryptonight/ccminer -o stratum+tcp://pool.etnminers.com:7777 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ.19_2_ASGT405XE3 -p x m1 10702 0.0 0.0 14224 944 pts/16 R+ 22:38 0:00 grep --color=auto miner I also tried to connect to etn.easyhash.io:3631 with the same result, diff gets set at exactly 19 and stays there. I can however set the diff manually by adding it to my etn address as "...address.20000" This works but then the diff stays at that at all times. Once again everything worked fine in 19_1.4 As for the details of my 1bash settings for the etn coin. I have my etn address in there as shown above as well as the port. I use port 3333 for the cpu threads and 7777 for the gpu´s in the rig i am using right now to get back online. There are 4 1050 ti`s in there. When i look at at the outcome above it adds the diff 1600 for the cpu thread (which i set manually by adding it to 1bash) and it puts my custom worker name right behind the etn address. Seeing this now i just converted back to HOST instead of CUSTOM worker name but that doesn´t help a lot. In that case the diff gets set to 100, stays there and the miner never starts mining. The cpu works but only because i set it manually to a 1600 diff. KTccminer-cryptonight never starts mining even though it shows accepted shares. Unfortunately i don´t know enough about Linux to get anywhere close to resolving this. Sorry, it took a while to respond. Ok, i think i've found the issue. a) Your cpu miner command :/home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://pool.etnminers.com:3333 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ.1600.19_2_ASGT405XE3 -p x -t 3 What pool expecting to see is : It's not expecting to see worker name attached to ADDY. /home/m1/cpuOPT/cpuminer -a cryptonight -o stratum+tcp://pool.etnminers.com:3333 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ -p x -t 3 Search for this code in 3main; if [ $plusCPU == "YES" ] && [ $AUTO_START_MINER == "YES" ]
then
HCD='/home/m1/cpuOPT/cpuminer'
XMRADDR="$XMR_ADDRESS.$XMR_WORKER" Change XMRADDR="$XMR_ADDRESS.$XMR_WORKER" to this XMRADDR="$XMR_ADDRESS b) Your ccminer command
/home/m1/KTccminer-cryptonight/ccminer -o stratum+tcp://pool.etnminers.com:7777 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ.19_2_ASGT405XE3 -p x What pool is expecting to see is : It's not expecting to see worker name attached to ADDY. /home/m1/KTccminer-cryptonight/ -o stratum+tcp://pool.etnminers.com:7777 -u etnkEv3h8DxMLSWMBYTmMLfKNgnaQf6k7hGbkEbK6hbeGku69dh8Lm7iihpV4dg3BRXcJFAKfGUaNac isz4bmS6E8HRgEA2cJZ -p x Go to 0miner, search for these lines if [ $COIN == "ETN" ]
then
HCD='/home/m1/KTccminer-cryptonight/ccminer'
ADDR="$ETN_ADDRESS.$ETN_WORKER"
Change this ADDR="$ETN_ADDRESS.$ETN_WORKER" to this ADDR="$ETN_ADDRESS" This should work. Difficulty will vary based on the port you select (most of the stratum pools automatically adjust the difficulty - my suggestion, leave your current port as is), please check the below link for more information : https://etnminers.com/#getting_started |
|
|
|
|
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list. |
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
February 27, 2018, 06:49:11 PM
Last edit: February 27, 2018, 08:31:41 PM by papampi |
|
Hello,
When we get a watchdog alert, is there an easy way to determine which GPU created the error? It looks to me that in the example below, the all 10 GPUs are failing at the same time which is not possible.
Do you have any peace of advice?
See for NVRM errors in /var/log/kern.log Hi LukePicci, If I check kern.log approximately at the time of the watchdog error above (Tue Feb 27 09:35:24 CET 2018) I get: Feb 27 09:35:03 m1-desktop kernel: [72498.782215] NVRM: Xid (PCI:0000:02:00): 31, Ch 0000001b, engmask 00000101, intr 10000000
Feb 27 09:46:34 m1-desktop kernel: [73190.045754] NVRM: Xid (PCI:0000:0f:00): 31, Ch 0000001b, engmask 00000101, intr 10000000 Does that mean that the GPU that gave the error is on PCI slot 02 (or whatever is mapped to PCI slot 02)? Run and find that pci slot GPU number, then you can either run : or max the fan speed of that GPU from nvidia-settings or disable that GPU from miner. But usually that cuda memory illegal access is because of high memory overclock. Lower memory clock, then start raising in small steps. |
|
|
|
_S_C_
Newbie
Offline
Activity: 11
Merit: 0
|
|
February 27, 2018, 10:08:36 PM |
|
Hi all, Trying to switch to nvOC v0019-2.0 but I have some errors and I'm unable to run a miner. Here is my log. In advance thanks for your help. (MSI Z270-A PRO / Intel P 4400 / ram 8GB / SSD 60 GB / 6 MSI GTX 1080 TI) nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:47:09 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... Off | 00000000:01:00.0 On | N/A |
| 0% 29C P0 59W / 280W | 118MiB / 11172MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... Off | 00000000:03:00.0 Off | N/A |
| 0% 34C P8 11W / 280W | 9MiB / 11172MiB | 8% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... Off | 00000000:06:00.0 Off | N/A |
| 0% 33C P8 13W / 280W | 9MiB / 11172MiB | 5% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... Off | 00000000:07:00.0 Off | N/A |
| 0% 37C P8 15W / 280W | 9MiB / 11172MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... Off | 00000000:08:00.0 Off | N/A |
| 0% 35C P8 16W / 280W | 9MiB / 11172MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... Off | 00000000:09:00.0 Off | N/A |
| 0% 39C P8 14W / 280W | 9MiB / 11172MiB | 5% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 87MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: MINER WATCHDOG
process in guake terminal Tab (f12), ~/nvOC wdog-log
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected
/home/m1/2unix: line 55: 1998 Terminated bash '/home/m1/3main'
nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:47:25 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... On | 00000000:01:00.0 On | N/A |
| 50% 30C P2 55W / 150W | 124MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... On | 00000000:03:00.0 Off | N/A |
| 0% 34C P8 10W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... On | 00000000:06:00.0 Off | N/A |
| 0% 33C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... On | 00000000:07:00.0 Off | N/A |
| 0% 37C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... On | 00000000:08:00.0 Off | N/A |
| 0% 35C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... On | 00000000:09:00.0 Off | N/A |
| 0% 39C P8 12W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 93MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 150.00 W.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected
nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:48:47 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... On | 00000000:01:00.0 On | N/A |
| 50% 25C P8 16W / 150W | 124MiB / 11172MiB | 6% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... On | 00000000:03:00.0 Off | N/A |
| 0% 34C P8 10W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... On | 00000000:06:00.0 Off | N/A |
| 0% 32C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... On | 00000000:07:00.0 Off | N/A |
| 0% 36C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... On | 00000000:08:00.0 Off | N/A |
| 0% 34C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... On | 00000000:09:00.0 Off | N/A |
| 0% 38C P8 12W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 93MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 150.00 W.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected
/home/m1/2unix: line 55: 3071 Terminated bash '/home/m1/3main'
nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:50:09 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... On | 00000000:01:00.0 On | N/A |
| 50% 24C P8 12W / 150W | 118MiB / 11172MiB | 6% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... On | 00000000:03:00.0 Off | N/A |
| 0% 34C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... On | 00000000:06:00.0 Off | N/A |
| 0% 32C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... On | 00000000:07:00.0 Off | N/A |
| 0% 36C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... On | 00000000:08:00.0 Off | N/A |
| 0% 34C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... On | 00000000:09:00.0 Off | N/A |
| 0% 38C P8 12W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 87MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 150.00 W.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected
/home/m1/2unix: line 55: 3652 Terminated bash '/home/m1/3main'
nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:51:30 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... On | 00000000:01:00.0 On | N/A |
| 50% 23C P8 13W / 150W | 124MiB / 11172MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... On | 00000000:03:00.0 Off | N/A |
| 0% 33C P8 10W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... On | 00000000:06:00.0 Off | N/A |
| 0% 32C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... On | 00000000:07:00.0 Off | N/A |
| 0% 35C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... On | 00000000:08:00.0 Off | N/A |
| 0% 34C P8 11W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... On | 00000000:09:00.0 Off | N/A |
| 0% 38C P8 12W / 150W | 9MiB / 11172MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 93MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 150.00 W.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 150.00 W.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected |
|
|
|
|
WaveFront
Member
Offline
Activity: 126
Merit: 10
|
|
February 27, 2018, 10:36:01 PM |
|
Hello,
When we get a watchdog alert, is there an easy way to determine which GPU created the error? It looks to me that in the example below, the all 10 GPUs are failing at the same time which is not possible.
Do you have any peace of advice?
See for NVRM errors in /var/log/kern.log Hi LukePicci, If I check kern.log approximately at the time of the watchdog error above (Tue Feb 27 09:35:24 CET 2018) I get: Feb 27 09:35:03 m1-desktop kernel: [72498.782215] NVRM: Xid (PCI:0000:02:00): 31, Ch 0000001b, engmask 00000101, intr 10000000
Feb 27 09:46:34 m1-desktop kernel: [73190.045754] NVRM: Xid (PCI:0000:0f:00): 31, Ch 0000001b, engmask 00000101, intr 10000000 Does that mean that the GPU that gave the error is on PCI slot 02 (or whatever is mapped to PCI slot 02)? Run and find that pci slot GPU number, then you can either run : or max the fan speed of that GPU from nvidia-settings or disable that GPU from miner. But usually that cuda memory illegal access is because of high memory overclock. Lower memory clock, then start raising in small steps. Hi Papampi, I am tuning one rig. Since most cards are of different models, I cannot use the same overclock rate for all cards. This is great. That way I can identify the cards that are crashing and change the rates. |
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
February 27, 2018, 11:30:50 PM |
|
Hi all, Trying to switch to nvOC v0019-2.0 but I have some errors and I'm unable to run a miner. Here is my log. In advance thanks for your help. (MSI Z270-A PRO / Intel P 4400 / ram 8GB / SSD 60 GB / 6 MSI GTX 1080 TI) nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
rig IP: 192.168.0.135
rig MAC:
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1b06 (rev a1)
Tue Feb 27 22:47:09 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.34 Driver Version: 387.34 |
|-------------------------------+----------------------+----------------------+
| 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 108... Off | 00000000:01:00.0 On | N/A |
| 0% 29C P0 59W / 280W | 118MiB / 11172MiB | 1% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... Off | 00000000:03:00.0 Off | N/A |
| 0% 34C P8 11W / 280W | 9MiB / 11172MiB | 8% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... Off | 00000000:06:00.0 Off | N/A |
| 0% 33C P8 13W / 280W | 9MiB / 11172MiB | 5% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... Off | 00000000:07:00.0 Off | N/A |
| 0% 37C P8 15W / 280W | 9MiB / 11172MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 108... Off | 00000000:08:00.0 Off | N/A |
| 0% 35C P8 16W / 280W | 9MiB / 11172MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 108... Off | 00000000:09:00.0 Off | N/A |
| 0% 39C P8 14W / 280W | 9MiB / 11172MiB | 5% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 978 G /usr/lib/xorg/Xorg 87MiB |
| 0 1785 G compiz 28MiB |
| 1 978 G /usr/lib/xorg/Xorg 6MiB |
| 2 978 G /usr/lib/xorg/Xorg 6MiB |
| 3 978 G /usr/lib/xorg/Xorg 6MiB |
| 4 978 G /usr/lib/xorg/Xorg 6MiB |
| 5 978 G /usr/lib/xorg/Xorg 6MiB |
+-----------------------------------------------------------------------------+
/home/m1/3main: line 202: [: ==: unary operator expected
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:0]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:1]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:2]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:3]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:4]) assigned value 0.
Attribute 'GPULogoBrightness' (m1-desktop:0[gpu:5]) assigned value 0.
Power limit for GPU 00000000:01:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:03:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:06:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:07:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:08:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:09:00.0 was set to 150.00 W from 280.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
All done.
/home/m1/3main: line 222: [: ==: unary operator expected
LAUNCHING: MINER TEMPCONTROL
process in guake terminal Tab (f12), ~/nvOC temp-log
/home/m1/3main: line 843: [: ==: unary operator expected
/home/m1/3main: line 885: [: ==: unary operator expected
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 120.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 1200.
ERROR: Error parsing assignment '[gpu:1]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:1]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:2]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:3]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:4]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUGraphicsClockOffset[3]=' (No attribute value specified).
ERROR: Error parsing assignment '[gpu:5]/GPUMemoryTransferRateOffset[3]=' (No attribute value specified).
Auto Start Miner Set to YES
LAUNCHING: MINER WATCHDOG
process in guake terminal Tab (f12), ~/nvOC wdog-log
LAUNCHING: WTM AUTO SWITCH
LAUNCHING: MINER
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
/home/m1/0miner: line 67: [: ==: unary operator expected
/home/m1/0miner: line 72: [: ==: unary operator expected
/home/m1/0miner: line 79: [: ==: unary operator expected
/home/m1/0miner: line 85: [: ==: unary operator expected
/home/m1/2unix: line 55: 1998 Terminated bash '/home/m1/3main'
nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
Have you made any edits to 1bash file? Seems it's not happy with the format of it. I would be better if you paste your 1bash here. |
|
|
|
|
leenoox
|
|
February 28, 2018, 04:02:13 AM |
|
Hi all, Trying to switch to nvOC v0019-2.0 but I have some errors and I'm unable to run a miner. Here is my log. In advance thanks for your help. (MSI Z270-A PRO / Intel P 4400 / ram 8GB / SSD 60 GB / 6 MSI GTX 1080 TI) nvOC v0019-2.0 - Community Release
/home/m1/1bash: line 1041: unexpected EOF while looking for matching `"'
/home/m1/1bash: line 1047: syntax error: unexpected end of file
nvOC v0019-2.0 - Community Release
Have you made any edits to 1bash file? Seems it's not happy with the format of it. I would be better if you paste your 1bash here. It seems your 0miner, 1bash and 3main are somehow corrupted. Try to reimage. P.S. Please enclose long post within CODE formatting. Click on the # icon to post long code. |
|
|
|
papampi
Full Member
Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
February 28, 2018, 08:11:25 AM |
|
Hello,
When we get a watchdog alert, is there an easy way to determine which GPU created the error? It looks to me that in the example below, the all 10 GPUs are failing at the same time which is not possible.
Do you have any peace of advice?
See for NVRM errors in /var/log/kern.log Hi LukePicci, If I check kern.log approximately at the time of the watchdog error above (Tue Feb 27 09:35:24 CET 2018) I get: Feb 27 09:35:03 m1-desktop kernel: [72498.782215] NVRM: Xid (PCI:0000:02:00): 31, Ch 0000001b, engmask 00000101, intr 10000000
Feb 27 09:46:34 m1-desktop kernel: [73190.045754] NVRM: Xid (PCI:0000:0f:00): 31, Ch 0000001b, engmask 00000101, intr 10000000 Does that mean that the GPU that gave the error is on PCI slot 02 (or whatever is mapped to PCI slot 02)? Run and find that pci slot GPU number, then you can either run : or max the fan speed of that GPU from nvidia-settings or disable that GPU from miner. But usually that cuda memory illegal access is because of high memory overclock. Lower memory clock, then start raising in small steps. Hi Papampi, I am tuning one rig. Since most cards are of different models, I cannot use the same overclock rate for all cards. This is great. That way I can identify the cards that are crashing and change the rates. Usually disabling the gpu from miner and find the cold gpu is the fastest way. If mining with dstm zm miner use this : ZM_OPTS=" -dev 0 1 2 3 5" ## gpu 4 is disabled.
Ethminer use this: ETH_EXTENSION_ARGUMENTS=" --cuda-devices 0 1 2 3 5" |
|
|
|
JustM4rt
Newbie
Offline
Activity: 25
Merit: 0
|
|
February 28, 2018, 02:24:11 PM |
|
Demo video links don't work anymore
|
|
|
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
February 28, 2018, 03:49:34 PM |
|
Demo video links don't work anymore
Hey bruv, They aren't updated because of fullzero's (OP) absence. But other places like https://nvoc-mining-os.com/Discord https://discord.gg/8YDFEvYThis topic are always updated. (video links are also updated too) |
|
|
|
urnzwy
Newbie
Offline
Activity: 44
Merit: 0
|
|
February 28, 2018, 04:27:53 PM |
|
Hey guys,
I am getting a low GPU utilization when mining ETN. Power draw for the cards, 1070's is pretty low, but hashing at 650 h/s each. Been mining ZCL and ZEN, but change to ETN and power drops and keep seeing this for all different cards in the miner watchdog.
Wed Feb 28 09:09:05 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 0 100 100 100 23 100 100 100 38 100
GPU_COUNT: 13
Wed Feb 28 09:09:17 MST 2018 - GPU 8 under threshold found - GPU UTILIZATION: 69
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:18 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU UTILIZATION: 100 56 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:31 MST 2018 - GPU 11 under threshold found - GPU UTILIZATION: 0
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:32 MST 2018 - Low Utilization Detected: 3main will reinit if there are 76 consecutive failures
GPU UTILIZATION: 100 100 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:45 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 64 100 65 100 64 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:57 MST 2018 - GPU 4 under threshold found - GPU UTILIZATION: 71
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:59 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU 0, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 74.95
GPU 1, Target temp: 72, Current: 43, Diff: 29, Fan: 65, Power: 76.51
GPU 2, Target temp: 72, Current: 53, Diff: 19, Fan: 65, Power: 75.22
GPU 3, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 77.88
GPU 4, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 81.13
GPU 5, Target temp: 72, Current: 55, Diff: 17, Fan: 65, Power: 78.15
GPU 6, Target temp: 72, Current: 47, Diff: 25, Fan: 65, Power: 77.07
GPU 7, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 42.85
GPU 8, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 109.02
GPU 9, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 74.60
GPU 10, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 78.14
GPU 11, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 75.64
GPU 12, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 77.70
|
|
|
|
|
|
joshuajones02
|
|
February 28, 2018, 06:52:36 PM |
|
Hey guys trying to help a friend but he hasn’t given me much info and then had to take off to take care of some work stuff, I’ll report back when I get more info but does anyone know what’s causing the issue? He’s saying something is wrong with the 3main or receives an error when the 1bash executes and is starting the mining service. He said the machine was running fine before going to bed and has been for a month or so and he woke up to the issue. I told him to reflash instead of trying to troubleshoot the error. He did and is still receiving the error Photo -  |
|
|
|
|
leenoox
|
|
February 28, 2018, 06:53:50 PM |
|
Hey guys,
I am getting a low GPU utilization when mining ETN. Power draw for the cards, 1070's is pretty low, but hashing at 650 h/s each. Been mining ZCL and ZEN, but change to ETN and power drops and keep seeing this for all different cards in the miner watchdog.
Wed Feb 28 09:09:05 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 0 100 100 100 23 100 100 100 38 100
GPU_COUNT: 13
Wed Feb 28 09:09:17 MST 2018 - GPU 8 under threshold found - GPU UTILIZATION: 69
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:18 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU UTILIZATION: 100 56 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:31 MST 2018 - GPU 11 under threshold found - GPU UTILIZATION: 0
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:32 MST 2018 - Low Utilization Detected: 3main will reinit if there are 76 consecutive failures
GPU UTILIZATION: 100 100 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:45 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 64 100 65 100 64 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:57 MST 2018 - GPU 4 under threshold found - GPU UTILIZATION: 71
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:59 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU 0, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 74.95
GPU 1, Target temp: 72, Current: 43, Diff: 29, Fan: 65, Power: 76.51
GPU 2, Target temp: 72, Current: 53, Diff: 19, Fan: 65, Power: 75.22
GPU 3, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 77.88
GPU 4, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 81.13
GPU 5, Target temp: 72, Current: 55, Diff: 17, Fan: 65, Power: 78.15
GPU 6, Target temp: 72, Current: 47, Diff: 25, Fan: 65, Power: 77.07
GPU 7, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 42.85
GPU 8, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 109.02
GPU 9, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 74.60
GPU 10, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 78.14
GPU 11, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 75.64
GPU 12, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 77.70
Are you using the nvoc 19-2.0 Community Release? There was some implementation to calculate percentage of the actual utilization. If you are running on 19-2.0 and still getting this, it seems some miners on some algos are not fully utilizing the GPU's. Unfortunately there isn't an easy and quick fix for this. We will have to rewrite the watchdog to account for situations like this. Hopefully we will have something to fix this for the next release. |
|
|
|
urnzwy
Newbie
Offline
Activity: 44
Merit: 0
|
|
February 28, 2018, 06:59:12 PM |
|
Hey guys,
I am getting a low GPU utilization when mining ETN. Power draw for the cards, 1070's is pretty low, but hashing at 650 h/s each. Been mining ZCL and ZEN, but change to ETN and power drops and keep seeing this for all different cards in the miner watchdog.
Wed Feb 28 09:09:05 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 0 100 100 100 23 100 100 100 38 100
GPU_COUNT: 13
Wed Feb 28 09:09:17 MST 2018 - GPU 8 under threshold found - GPU UTILIZATION: 69
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:18 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU UTILIZATION: 100 56 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:31 MST 2018 - GPU 11 under threshold found - GPU UTILIZATION: 0
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:32 MST 2018 - Low Utilization Detected: 3main will reinit if there are 76 consecutive failures
GPU UTILIZATION: 100 100 100 100 100 100 100 100 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:45 MST 2018 - No mining issues detected.
GPU UTILIZATION: 100 100 100 64 100 65 100 64 100 100 100 100 100
GPU_COUNT: 13
Wed Feb 28 09:09:57 MST 2018 - GPU 4 under threshold found - GPU UTILIZATION: 71
Connection to google.com 443 port [tcp/https] succeeded!
Connection to google.com 443 port [tcp/https] succeeded!
Wed Feb 28 09:09:59 MST 2018 - Low Utilization Detected: 3main will reinit if there are 77 consecutive failures
GPU 0, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 74.95
GPU 1, Target temp: 72, Current: 43, Diff: 29, Fan: 65, Power: 76.51
GPU 2, Target temp: 72, Current: 53, Diff: 19, Fan: 65, Power: 75.22
GPU 3, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 77.88
GPU 4, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 81.13
GPU 5, Target temp: 72, Current: 55, Diff: 17, Fan: 65, Power: 78.15
GPU 6, Target temp: 72, Current: 47, Diff: 25, Fan: 65, Power: 77.07
GPU 7, Target temp: 72, Current: 50, Diff: 22, Fan: 65, Power: 42.85
GPU 8, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 109.02
GPU 9, Target temp: 72, Current: 52, Diff: 20, Fan: 65, Power: 74.60
GPU 10, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 78.14
GPU 11, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 75.64
GPU 12, Target temp: 72, Current: 51, Diff: 21, Fan: 65, Power: 77.70
Are you using the nvoc 19-2.0 Community Release? There was some implementation to calculate percentage of the actual utilization. If you are running on 19-2.0 and still getting this, it seems some miners on some algos are not fully utilizing the GPU's. Unfortunately there isn't an easy and quick fix for this. We will have to rewrite the watchdog to account for situations like this. Hopefully we will have something to fix this for the next release. Correct, running the Community release. I guess that clears that mystery up. I'll keep an eye out for the next release. Thanks for the info |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
February 28, 2018, 07:16:54 PM |
|
@urnzwy and @leenoox I'm not sure that KTccminer-cryptonight ccminer is the best cryptonight miner we have. I think we could try xmr-stak. xmr-stak GPU has good performance for XMR, but i don't knox if it's permit to mine another coin than XMR and AEON. I recently discovered that psychocrypt and Klaust added AEON and a very usefull assistant for newbies for generates somes config files for both GPU and CPU. This assistant put 3 core if you CPU have 4 Core and it's make the same with compute units from GPU. In addition you can modify all config files after automatic assitant generates them in the same folder. I tried it on Windows but not at least on Linux. Remmember that on Linux, you can set fee to 0%, but you must compile it on you machine, not on windows that is 2% by default and you can't compile it. Unified All-in-one Monero miner
GitHub : https://github.com/fireice-uk/xmr-stakGithub Releases : https://github.com/fireice-uk/xmr-stak/releases psychocrypt released this on 22 Dec 201 Sorry for my bad airport globish. I try without translator but ... |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
February 28, 2018, 09:40:28 PM |
|
I am very upset by this team of Zclassic and his Fork as well as after BITTREX Until this morning and even this afternoon, we did not know if the fork would be supported by most of the most famous exchanges. And frankly TradeSatoshi is not really the best known! Not so muich used as Bittrex is. All the exchanges have done everything to make things go wrong. I understand that they do not like being forced by the Forks, but BIttrex did not care about us. They put their wallets back into service after so long that the ZCL had lost more than 60% of its value! All other exchanges were operational at 18h! 30 min after the fork !  I feel like I'm stolen in a very organized way.  On their sites of BTCP, they said to put the coins in their wallet electrum. And tonight I'm discovered that in fact it was better just to leave everything on BIttrex.....pffff A post of Bittrex at 8:39 this morning! Fucking Bittrex Team suppport grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr REALLY VERY ANGRY! BITTREX THIEF! Suddenly, I have a big doubt to get into the mining of this future BTCP coin and this fork very poorly managed until the last minute. Of course, we still do not know when the BTCP wallet will be available and when we can claim our BTCP. The bad business continues so far ... In addition, Bittrex has already indicated that the holders would receive their 1 ZCL = 1 BTCP but not their 1 BTC = 1 BTCP. The only thing that consoles me a little bit is that I had only 0.5 ZCl but it was still 60 € at 13h today! And if I'm counting the time I spent to mine it, I'm losing, even heavily! And now I hesitate to follow the fork of MoneroV in two weeks because it also feels the fir tree their story! It made me very worry to lose 100% of the value of my XMR mined as just made the ZCL tonight! FUCKING BITTREX FUCKING BTCP Team ! Sorry for all theses insult but i need them to not became mad of this stolen. |
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
March 01, 2018, 04:27:58 PM |
|
@urnzwy and @leenoox I'm not sure that KTccminer-cryptonight ccminer is the best cryptonight miner we have. I think we could try xmr-stak. xmr-stak GPU has good performance for XMR, but i don't knox if it's permit to mine another coin than XMR and AEON. I recently discovered that psychocrypt and Klaust added AEON and a very usefull assistant for newbies for generates somes config files for both GPU and CPU. This assistant put 3 core if you CPU have 4 Core and it's make the same with compute units from GPU. In addition you can modify all config files after automatic assitant generates them in the same folder. I tried it on Windows but not at least on Linux. Remmember that on Linux, you can set fee to 0%, but you must compile it on you machine, not on windows that is 2% by default and you can't compile it. Unified All-in-one Monero miner
GitHub : https://github.com/fireice-uk/xmr-stakGithub Releases : https://github.com/fireice-uk/xmr-stak/releases psychocrypt released this on 22 Dec 201 Sorry for my bad airport globish. I try without translator but ... Not sure whether KTccminer-cryptonight ccminer is the right one either, but, personally, for my RIG, its doing the best job, by giving 555 h/s with my 1060 6GB card. Heard from one of the user (@kung on discord) about another ccminer which can be used to mine AEON or such (cryptonight algo) kind of coins, here is the link: https://github.com/xmrig/xmrig-nvidiaWe must compile & test them individually and see how it goes and pick the best one. I am very upset by this team of Zclassic and his Fork as well as after BITTREX Until this morning and even this afternoon, we did not know if the fork would be supported by most of the most famous exchanges. And frankly TradeSatoshi is not really the best known! Not so muich used as Bittrex is. All the exchanges have done everything to make things go wrong. I understand that they do not like being forced by the Forks, but BIttrex did not care about us. They put their wallets back into service after so long that the ZCL had lost more than 60% of its value! All other exchanges were operational at 18h! 30 min after the fork ! I feel like I'm stolen in a very organized way. On their sites of BTCP, they said to put the coins in their wallet electrum. And tonight I'm discovered that in fact it was better just to leave everything on BIttrex.....pffff A post of Bittrex at 8:39 this morning! Fucking Bittrex Team suppport grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr REALLY VERY ANGRY! BITTREX THIEF! Suddenly, I have a big doubt to get into the mining of this future BTCP coin and this fork very poorly managed until the last minute. Of course, we still do not know when the BTCP wallet will be available and when we can claim our BTCP. The bad business continues so far ... In addition, Bittrex has already indicated that the holders would receive their 1 ZCL = 1 BTCP but not their 1 BTC = 1 BTCP. The only thing that consoles me a little bit is that I had only 0.5 ZCl but it was still 60 € at 13h today! And if I'm counting the time I spent to mine it, I'm losing, even heavily! And now I hesitate to follow the fork of MoneroV in two weeks because it also feels the fir tree their story! It made me very worry to lose 100% of the value of my XMR mined as just made the ZCL tonight! FUCKING BITTREX FUCKING BTCP Team ! Sorry for all theses insult but i need them to not became mad of this stolen. Haha, I'm mad at Bittrex too bruv, I waited to see some official announcement from Bittrex, but NOPE, so I've moved them to Trade Satoshi (can we call it another yobit?). I've managed to move them on 27th evening, wallet was working fine by then! Don't know what happened, they had wallet issues after that, they had almost 90% ZCL circulation (even now). They announced that they are participating out of nowhere, on the fork day, less than 12 hours away from the fork, how dramatic  On the other side of the story, Trade Satoshi couldn't handle the traffic (  ), ZCL trading was down for more than hour (or maybe more). But have to wait and see whether BTCP lives up to the drama and fun |
|
|
|
fullzero (OP)
Legendary
Offline
Activity: 1260
Merit: 1009
|
|
March 01, 2018, 08:36:44 PM
Last edit: March 05, 2018, 02:46:27 AM by fullzero |
|
I will try to catch up this month: Thanks for the community edition: papampi , kk003, Stubo, damNmad, leenoox and meligo  Rebuilding the community edition using the vBASIC image as a starting point might be a good idea. Let me know. vBASIC is linked on the OP. |
|
|
|
|
CryptAtomeTrader44
Full Member
Offline
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
|
|
March 01, 2018, 08:53:11 PM |
|
I will try to catch up this month: Thanks for the community edition: papampi , kk003, damNmad, leenoox and meligo Rebuilding the community edition using the vBASIC image as a starting point might be a good idea. Let me know. vBASIC is linked on the OP. Wow, a talented Legendary speaker has come back! We did not think to see you coming here one day, friend! nvOC has evolved since your disappearance, but there is still need to continue the DEV for heavy functions in the coming months. Happy to see you again, as many who came to ask what you became. Like Vosk or Salfter who pass from time to time. |
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
March 01, 2018, 08:58:27 PM |
|
I will try to catch up this month: Thanks for the community edition: papampi , kk003, damNmad, leenoox and meligo Rebuilding the community edition using the vBASIC image as a starting point might be a good idea. Let me know. vBASIC is linked on the OP. Very happy to see you back, hope all is well with you Welcome back bruv |
|
|
|
|
