 Show Posts
|
|
Pages: [1] 2 3 »
|
Note: I installed RealVNC for a local remote control in place of Teamviwer that I can not use anymore, but I saw by looking in the menus of the new version of ubuntu that other software have been added, notably SSHVNC (i don't know if this software is user friendly).
There is no any "SSHVNC" there, there is Sharing in the settings, which is disabled by default, and I have a big request to devs, guys please can you make it activated, with disabled "require-encryption" and the default password (miner1 for example) in the next image of nvOC? Cause it's not simple to do that on each rig by SSH, if you do not have a possibility to attach a monitor to it. |
|
|
|
when ubuntu has the most users and many are familiar with it.
agree with you, but for another reason: Lubuntu is just a variant of Ubuntu, it is the same OS, which uses LXDE desktop instead of Uniti Desktop in Ubuntu, and for mining purpose I don't think there will be noticeable difference |
|
|
|
But I'm willing to work with everyone interested in creating a full headless image.
What are the main problems on this way? |
|
|
|
nvOC v0019-2.0 Community Release new shrinked image Mega.nz Download LinkBeta testing... Please test and let me know. Change Log: Image size: 11 GB
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
Ok, i will download it and upload on dl.free.fr. Why don't you use google drive. A lot of users had some problems with Mega in the past. My drive is almost full, Sorry. Problem with Mega was when size is over 5 GB and it triggers the wait, bellow 5 GB should be no problem. So, i see you reduce the image weight by 2 GB ! It's a very good news ! Is it possible to reduce weight again ? it's a big step for nvOC, and a big step for profit switching :-) root partition wont allow to go lower, So I think its the smallest we can get. But will try to cleanup the OS again, see if I can reduse more. I think the only thing left to reduce size and improve stability (maybe?) is abandon Desktop So many users use desktop also use teamviewer, cant do that without making so many angry users  1. I noticed that rigs without Teamviewer are more stable or "responsive" 2. On the farm, where I service 27 rigs, I have 1 cheap PC with Teamviewer and SSH or VNC to the rigs. It is much more convenient than connect by Teamviewer to each Rig. So users just don't know how  |
|
|
|
nvOC v0019-2.0 Community Release new shrinked image Mega.nz Download LinkBeta testing... Please test and let me know. Change Log: Image size: 11 GB
ZIP size: 3.8 GB
Auto Expand to full size on first boot
Fixed copy 1bash from fat partition to SSD/HDD on first boot
SHA256: ACCA9787169E6E722ED74FB02DBE1C44E7760CEB537CB79D4C61C7FFF8AD3057
Ok, i will download it and upload on dl.free.fr. Why don't you use google drive. A lot of users had some problems with Mega in the past. My drive is almost full, Sorry. Problem with Mega was when size is over 5 GB and it triggers the wait, bellow 5 GB should be no problem. So, i see you reduce the image weight by 2 GB ! It's a very good news ! Is it possible to reduce weight again ? it's a big step for nvOC, and a big step for profit switching :-) root partition wont allow to go lower, So I think its the smallest we can get. But will try to cleanup the OS again, see if I can reduse more. I think the only thing left to reduce size and improve stability (maybe?) is abandon Desktop |
|
|
|
Guys, can you make a version of nvOC with Nvidia driver 384.90, because this is the last version of driver to work correctly with power limit for 1050ti?
You can just apply the latest updates yourself. This command should patch your Ubuntu installation: sudo -- sh -c 'apt-get update; apt-get upgrade -y; apt-get dist-upgrade -y; apt-get autoremove -y; apt-get autoclean -y
Edit: If you do this, be sure to shutdown the nvOC processes (watchdog in particular) properly or else you run the risk of having the machine reboot in the middle of applying patches. For nvOC 19-2.0, the command to stop everything is: Thanks. This is fine for upgrading the version but if i understand it right it's look like he want to downgrade. warning, make a backup, if something go wrong you could be unable to boot. ./nvOC stop
sudo apt-get install nvidia-384
Then reboot Oh. My bad. I had assumed upgrade because no driver that I had heard of works properly with the 1050: https://devtalk.nvidia.com/default/topic/1024744/linux/nvidia-387-12-breaks-power-reading-in-nvidia-smi-/post/5213384/#5213384So, for power draw on the 1050, you either get errant numbers with old versions or no numbers with the newer versions. The downgrade to a previous version is done via locally attached display using these instructions from leenoox: The easiest way is LOCAL: 1. I suggest closing all apps, ctrl-c on wdog, temp, miner 2. click on the 4th icon on the left-side panel "Additional Drivers" 3. in the new window click on "Additional Drivers" tab 4. click on the "Using NVIDIA binary driver - version 384.90 from..." 5. click on "Apply Changes" button <this can take a while> 6. enter root password: miner1 6. reboot 1) I know, how to downgrade. Both your suggestions won't work. nvOC with Nvidia driver 384.90 for those who can't downgrade and have 1050Tis 2) Any comparatively new driver up to 384.90 does right numbers, I checked with wattmeter. 3) See images: first screenshot v0019-1.4 updated to v0019-2.0 and driver downgraded to 384.90, the second screenshot as you see PoisonXA edition of nvOC) https://imgur.com/a/UhGtx |
|
|
|
|
Guys, can you make a version of nvOC with Nvidia driver 384.90, because this is the last version of driver to work correctly with power limit for 1050ti?
|
|
|
|
Hello,
I built a very crude SRR circuitry for a Raspberry Pi to remotely reset a rig or switch it on/off (The raspberry Pi basically controls an optocoupler connected to the reset and poweron pins of the mobo).
For the moment the Raspberry Pi just detect if port 22 is open on the rig. If not, it assumes that the rig is not reachable by SSH and reset the rig.
I see that there is an SRR scrips on nvOC, that looks much more sophisticated than what I am doing. Unfortunately there is no mention of the watchdog software to run on the Raspberry Pi.
Anyone can give me a pointer to the software to run on the Raspberry Pi.
Cheers
I have some code to share with you but the site is blocking my input. Trying to contact with an admin about. Thanks :-) Maybe you can post a link outside this forum Ok, have a look at this and see if can help: https://bitcointalk.org/index.php?topic=1854250.msg22615430#msg22615430I don't use Nvoc's temp control. Here the latest version of script (removed reset bit and add var to use/not to use telegram alerts. I did not test the telegram bit so be aware): https://pastebin.com/mcqmt9CFIt is possible to add code to nvoc's temp control (or wdog) and reset/poweroff/on the rig from a raspberry pi. I just look forward to have a well configured rig and make it work stable instead of using wdog. I do not trust wdog not because of the coders/scripts but because of so many gpus and drivers (from time to time they change the output of error codes, etc). Hi kk003, This is awsome!! I will modify the code according the my setup. As far as I can see from a quick look at the the code, the script assumes a rig is frozen if it doesn't respond to pings. Is it correct? In the past I had rigs that were clearly frozen, but were still responding to pings. That is why, instead of pinging I check if the SSH port is open on the rig using netcat: (w5 is a timeout of 5 seconds) Thanks again :-) Since we are on RPi talks ... How many rigs can be monitored and reboot/reset/hard reboot with one RPi? What are the hardwares needed for multiple rig control? I'm not much of a hardware guy but love to make a rig controller with RPi if its not too hard. Hi Papampi, A Raspberry Pi 2B or 3B has up to 26 programmable digital pins (the original Raspberry Pi B has only 17). You could connect each digital output to an optocoupler or a relay and control the power swithch and/or the reset button of the motherboard. Suppose that you want to want to control both switch and reset of each mobo, that would make that you could monitor up to 13 mobo (26 if you just want to control the reset switch). You can also connect digital temperature sensors to the pins (programming them in input mode). You can find pretty inexpensive ready made relay boards with up to 16 relays. In practice the hardware needed for for controlling 12 mobos would be: 1) 16 relay module. There are many on Amazon, for example https://www.amazon.com/SainSmart-101-70-103-16-Channel-Relay-Module/dp/B0057OC66U2) 8 relay module. 3) Usb power supply 4) Optional external HDMI screen, unless you are running the RPi headless through SSH 5) Of course, a raspberry Pi 6) Plenty of cables with female Dupont connectors The standard OS for the Raspberry Pi is Debian (Raspbian), but if you prefer you can have as well Ubuntu or Windows 10 IoT. The advantage of Raspbian is that it comes with all the utilities for controlling directly the GPIO pins, either from Bash or a high level language like C++ or Python. Awesome, Thanks a lot for the info I have 3 RPi 2B that dont use any more because when 3B came out I replaced them for faster kodi So I'm going to get a relay module and start playing with it, for sure I'm going to ask for more help on programming and connecting the relay to the board and ... Thanks a lot mate Keep calm and carry on mining No problems ;-) Just a thing, do not buy the board that I put in the link of my previous message. I justs realised that the inputs are for 5V signals while what you need is a board compatible with 3.3V signals. Look for a board that is specifically designed for the RPi. I have 2 16-Channel Relay Modules with 5v, they work OK. One of them is 5v powered and another 12v powered, and I had to add 12v power supply for the second relay, so now the Rpi3 is powered by the second relay and doesn't need 3) Usb power supply and the first relay is powered by Rpi3. |
|
|
|
Installed nvOC 19-1.4 on my new rig, updated it with nvOC-19-2-update, edited 1bash and ZM miner began restarting almost every minute, while Wdog and Temp were showing that all was OK.
Noticed then that not all files and folders in /home/m1 were owned by m1. Did "sudo chown -R m1 /home/m1" and no ZM restart since. May be it's worth adding this command to the
nvOC-19-2-update, just in case.
You ran the update with sudo ? Yes, without "sudo", forgot to metion, that's what I'm saying, just in case, because many people here don't now the difference between with or without "sudo", and then they run into troubles after update. |
|
|
|
|
Installed nvOC 19-1.4 on my new rig, updated it with nvOC-19-2-update, edited 1bash and ZM miner began restarting almost every minute, while Wdog and Temp were showing that all was OK.
Noticed then that not all files and folders in /home/m1 were owned by m1. Did "sudo chown -R m1 /home/m1" and no ZM restart since. May be it's worth adding this command to the
nvOC-19-2-update, just in case.
|
|
|
|
OK, that's the answer! The bad thing is that it does not only fails to read, but what is more important to set power limit. On older driver it did both correctly, I checked that with wattmeter. |
|
|
|
HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:
GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds
Why power has become "Not Supported"?
Ah. Are you are using the 1050 GPU? For that GPU, Nvidia's linux API does not support reading the power. Hence, reading it returns [Not Supported]. It is the only GPU (so far) that we have seen like that. As far as I know, it has little to no impact on the temp control for 19-2.0 but leenoox can correct me if I am wrong. It is 1050ti. On nvOC-19-1.4 and early versions of nvOC-19-2 it was like this: GPU 0, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70 GPU 1, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70 GPU 2, Target temp: 75, Current: 75, Diff: 0, Fan: 50, Power: 70 GPU 3, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70 GPU 4, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70 GPU 5, Target temp: 75, Current: 66, Diff: 9, Fan: 50, Power: 70 Sun Dec 17 11:52:06 MST 2017 - All good, will check again soon Hmm. Try the this on your rig and see what it returns: nvidia-smi --query-gpu=power.draw --format=csv
It returns the same: m1@m1-desktop:~$ GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported] GPU: command not found m1@m1-desktop:~$ m1@m1-desktop:~$ Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds |
|
|
|
HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:
GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds
Why power has become "Not Supported"?
Ah. Are you are using the 1050 GPU? For that GPU, Nvidia's linux API does not support reading the power. Hence, reading it returns [Not Supported]. It is the only GPU (so far) that we have seen like that. As far as I know, it has little to no impact on the temp control for 19-2.0 but leenoox can correct me if I am wrong. It is 1050ti. On nvOC-19-1.4 and early versions of nvOC-19-2 it was like this: GPU 0, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70 GPU 1, Target temp: 75, Current: 73, Diff: 2, Fan: 50, Power: 70 GPU 2, Target temp: 75, Current: 75, Diff: 0, Fan: 50, Power: 70 GPU 3, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70 GPU 4, Target temp: 75, Current: 68, Diff: 7, Fan: 50, Power: 70 GPU 5, Target temp: 75, Current: 66, Diff: 9, Fan: 50, Power: 70 Sun Dec 17 11:52:06 MST 2017 - All good, will check again soon |
|
|
|
|
HI,
after applying the latest version of nvOC-19-2-update I've got this in the MINER_TEMP_CONTROL:
GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds
Why power has become "Not Supported"?
|
|
|
|
|
After applying nvOC-19-2-update, one of the rigs probably doesn't boot to desktop cause VNC doesn't work, can access it by SSH or nvOC web interface:
nvOC v0019-2.0 - Community Release
Worker : 230
Boot Time: 2017-12-15 21:33:03
System Up Time: up 47 minutes
Miner Up Time: 00:00
Distro: Ubuntu 16.04.3 LTS 4.4.0-97-generic
CPU: Intel(R) Pentium(R) CPU G4600 @ 3.60GHz
Disk / Free Disk: 14G / 4.1G
Memory / Free Memory: 3917 / 3558
Load Average: 0.00 0.00 0.00
Nvidia Driver Version:
Reboot Required: No
Auto Temp Control: Enabled, Not Running
Watch Dog: Enabled, Not Running
Gpu Count:
GPU Target Temp: 65
GPU Minimum Fan Speed: 30
GPU Utilization: NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
Currently Mining: BTG
Auto Switcher: WTM Profit Check Running.
BTC PRICE: 17729 USD
WTM Current Profitabilty: BTG:103 % ETH:100 % ZEN:82 % ZEC:81 % FTC:60 %
WTM Current Revenue: BTG:13.67 ETH:13.24 ZEN:10.81 ZEC:10.69 FTC:7.98
Miner Hash Rate / Output:
GPU Temp, Fan and Power Info:
GPU Temp, Fan and Power Alerts:
Watch Dog Alerts:
How can I fix Nvidia driver?
|
|
|
|
papampi, leenoox did you try update script ( https://github.com/papampi/nvOC_by_fullzero_Community_Release/blob/19.2/nvOC-19-2-update) yourself? I did fresh install of nvOC 19-1.4 and than applied the update script several times during past week, first time when script was about 350 lines and the last yesterday 502 lines. Often it works strange, for example last time ZM and Claymore didn't start after update, when I checked why, I found that the corresponding folders "latest" (in ZM's folder and Claymore's one) were empty, may be some other folders are empty too, cause papampi WTM doesn't work (it does on 1.4), wdog reboots rig when all card are happily mining, temp control doesn't read temps and tries to reboot rig, many things are broken. May be its because of the update script working wrong? May be its time to give updated image for beta testing? |
|
|
|
|
on 1.4 everything worked OK.
after update I have:
1. current version:
##########################################################################
##########################################################################
################# nvOC v0019-2.0 - Community Release #################
############## by papampi, Stubo and leenoox ##############
########## Based on the original nvOC v0019-1.4 by fullzero ##########
##########################################################################
##########################################################################
nvOC_1bash_ver="v0019-2.0.001" # Do not edit this
2. Auto temp is OFF, because it reboots rig immediately
3. Wdog starts, but have to ctrl+c, otherwise it restarts miner and after that restarts rig:
Mon Dec 11 19:35:50 MST 2017 - Watchdog is starting
Mon Dec 11 19:35:52 MST 2017 - Miner is running, waiting 70 seconds before going 'on watch'
GPU UTILIZATION: 100 100 100 100 100 100
GPU_COUNT: 6
Mon Dec 11 19:37:02 MST 2017 - Lost GPU so restarting system. Found GPU's:
pci.bus_id
00000000:01:00.0
00000000:02:00.0
00000000:03:00.0
00000000:04:00.0
00000000:05:00.0
00000000:06:00.0
Mon Dec 11 19:37:02 MST 2017 - reboot in 10 seconds
4. If I ctrl+c wdog, than miner continues working as if nothing happened:
2017-12-11 07:35:51 PM|# zm 0.5.6
2017-12-11 07:35:51 PM|# GPU0 + GeForce GTX 1050 Ti MB: 4037 PCI: 1:0
2017-12-11 07:35:51 PM|# GPU1 + GeForce GTX 1050 Ti MB: 4038 PCI: 2:0
2017-12-11 07:35:51 PM|# GPU2 + GeForce GTX 1050 Ti MB: 4038 PCI: 3:0
2017-12-11 07:35:51 PM|# GPU3 + GeForce GTX 1050 Ti MB: 4038 PCI: 4:0
2017-12-11 07:35:51 PM|# GPU4 + GeForce GTX 1050 Ti MB: 4038 PCI: 5:0
2017-12-11 07:35:51 PM|# GPU5 + GeForce GTX 1050 Ti MB: 4038 PCI: 6:0
2017-12-11 07:35:51 PM|
2017-12-11 07:35:51 PM|# GPU0 connected to: btg.suprnova.cc:8816
2017-12-11 07:35:53 PM|# GPU1 connected to: btg.suprnova.cc:8816
2017-12-11 07:35:55 PM|# GPU2 connected to: btg.suprnova.cc:8816
2017-12-11 07:35:57 PM|# GPU3 connected to: btg.suprnova.cc:8816
2017-12-11 07:35:59 PM|# GPU4 connected to: btg.suprnova.cc:8816
2017-12-11 07:36:01 PM|# GPU5 connected to: btg.suprnova.cc:8816
2017-12-11 07:36:03 PM|# GPU0 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:05 PM|# GPU1 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:07 PM|# GPU2 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:09 PM|# GPU3 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:11 PM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:13 PM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-11 07:36:27 PM|> GPU1 47C Sol/s: 190.3 Sol/W: inf Avg: 190.3 I/s: 103.0 Sh: 2.97 1.00 115 +
2017-12-11 07:36:27 PM|> GPU0 49C Sol/s: 191.6 Sol/W: inf Avg: 191.6 I/s: 100.8 Sh: 5.90 1.00 123 ++
2017-12-11 07:36:28 PM|> GPU2 46C Sol/s: 192.9 Sol/W: inf Avg: 192.9 I/s: 102.0 Sh: 2.99 1.00 112 +
2017-12-11 07:36:30 PM|> GPU3 53C Sol/s: 189.2 Sol/W: inf Avg: 189.2 I/s: 102.6 Sh: 0.00 . .
2017-12-11 07:36:32 PM|> GPU4 52C Sol/s: 188.7 Sol/W: inf Avg: 188.7 I/s: 102.2 Sh: 0.00 . .
2017-12-11 07:36:34 PM|> GPU5 53C Sol/s: 196.6 Sol/W: inf Avg: 196.6 I/s: 102.7 Sh: 0.00 . .
2017-12-11 07:36:34 PM| ========== Sol/s: 1149.5 Sol/W: inf Avg: 1149.5 I/s: 613.3 Sh: 11.86 1.00 116
2017-12-11 07:36:48 PM|> GPU1 52C Sol/s: 184.6 Sol/W: inf Avg: 187.5 I/s: 101.1 Sh: 2.97 1.00 117 +
2017-12-11 07:36:48 PM|> GPU0 54C Sol/s: 186.8 Sol/W: inf Avg: 189.2 I/s: 100.0 Sh: 4.44 1.00 124 +
2017-12-11 07:36:48 PM|> GPU2 52C Sol/s: 182.0 Sol/W: inf Avg: 187.4 I/s: 100.3 Sh: 4.43 1.00 109 ++
2017-12-11 07:36:50 PM|> GPU3 57C Sol/s: 195.3 Sol/W: inf Avg: 192.3 I/s: 100.8 Sh: 0.00 . .
2017-12-11 07:36:52 PM|> GPU4 57C Sol/s: 187.0 Sol/W: inf Avg: 187.8 I/s: 100.6 Sh: 1.47 1.00 109 +
2017-12-11 07:36:54 PM|> GPU5 59C Sol/s: 192.0 Sol/W: inf Avg: 194.3 I/s: 101.0 Sh: 5.92 1.00 125 ++++
2017-12-11 07:36:54 PM| ========== Sol/s: 1127.7 Sol/W: inf Avg: 1138.6 I/s: 603.8 Sh: 19.23 1.00 116
and so on...
|
|
|
|
Strange thing: when i choose in 1bash for example ZEN or ZEC and ALGO_SPECIFIC_OC="YES", after miner restart settings from this algo are applied:
# Skunk
if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" -o $COIN == "ALTCOM" ]
then
ALGORITHM="SKUNK"
POWERLIMIT_WATTS=78
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=1000
fi
Using nvOC v0019-2.0 - Community Release
Thats weird, Are you using latest edits with v0019-2.0.001 1bash from leenoox? v0019-2.0, today will try to update |
|
|
|
Side question, for those who use Teamviewer with no monitor, is there a way to adjust the resolution? I can't even view the entire tab for display options because the resolution is so low. Thanks
Also experiencing this problem when using VNC viewer.  insert in 1bash before TEAMVIEWER="NO" # YES NO this: xrandr --fb 1024x768 (or whatever resolution do you need) works for both Teamviwer and VNC |
|
|
|
|
Strange thing: when i choose in 1bash for example ZEN or ZEC and ALGO_SPECIFIC_OC="YES", after miner restart settings from this algo are applied:
# Skunk
if [ $COIN == "SIGT" -o $COIN == "ZPOOL_SKUNK" -o $COIN == "ALTCOM" ]
then
ALGORITHM="SKUNK"
POWERLIMIT_WATTS=78
__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=1000
fi
Using nvOC v0019-2.0 - Community Release
|
|
|
|
|
