Hi, everybody. I have asus prime z270-p and a USB flash drive SANDISK Cruzer Ultra Flair 32 GB.
nvOC does not want to start when I connect the USB 3.0 to the USB connector.
When I connect to usb 2.0 then the nvOC starts.
Please help what to do? usb 2.0 is very slow.
Topic: [OS] nvOC easy-to-use Linux Nvidia Mining - page 27. (Read 418249 times)
Z-enemy or ANXccminer to mine LUX
Add this in 0miner
Code:
if [ $COIN == "LUX" ]
then
ADDR="$LUX_ADDRESS.$LUX_WORKER"
HCD='/home/m1/z-enemy/z-enemy_miner'
screen -dmSL miner $HCD -a phi -o stratum+tcp://$LUX_POOL:$LUX_PORT -u $ADDR -p $MINER_PWD -i $LUX_INTENSITY
fi
then
ADDR="$LUX_ADDRESS.$LUX_WORKER"
HCD='/home/m1/z-enemy/z-enemy_miner'
screen -dmSL miner $HCD -a phi -o stratum+tcp://$LUX_POOL:$LUX_PORT -u $ADDR -p $MINER_PWD -i $LUX_INTENSITY
fi
Z-enemy or ANXccminer to mine LUX
I downloaded and ran the new miner updates for 19-2.0 but I don't understand hot to implement them into 1bash. I get this is a dumb question but I am a noob to GPU mining. Appreciate some hand holding lol
Which miner you want to add?
I downloaded and ran the new miner updates for 19-2.0 but I don't understand hot to implement them into 1bash. I get this is a dumb question but I am a noob to GPU mining. Appreciate some hand holding lol
Well after much frustration with my rigs crashing, I thought I had it figured out but the problem continued.
Originally I had setup SMOS but really didn't care for the simplicity of the interface or should I say lack there of and found nvOC.
As my rigs are remote in another state, it was even more difficult to diagnose.
For ease, I had my brother-in-law load up SMOS on both rigs and they have been running for over 4 days with under-volting (100W 1070 & 1070 Ti / 175W 1080 & 1080 Ti) and overclocking (-50 core 1070/1070 Ti, 200 core 1080 & 1080 Ti with 1100 Mem for the 1070/1070 Ti and 1000 for the 1080 & 1080 Ti). Mining ETH.
Whatever my issue was, it was an issue within nvOC. The question is why and what was causing the crashing issue.
Later this week, I plan on loading up a fresh copy of nvOC and see if the issue continues. Unfortunately I cleared the USB sticks we were using that had the nvOC OS on them. Had I though about it, it would have been good to have them to see if anyone could identify any issues. The only thing I really did was re-compile the miners.
It is difficult to pin-point when the issue really showed up as we were having to re-set the miners at least once a week and then eventually even would crash once daily. Both at the same time even on different algorithms. I tried multiple different mining programs, no over clocks, half overclock, full overclock. Nothing seemed to matter. 18-24 hours the crash was inevitable.
I wish I had more information on this, but wanted to get it into the forum in-case this ever happened to anyone else. I will update once I re-load up nvOC and see what happens.
Originally I had setup SMOS but really didn't care for the simplicity of the interface or should I say lack there of and found nvOC.
As my rigs are remote in another state, it was even more difficult to diagnose.
For ease, I had my brother-in-law load up SMOS on both rigs and they have been running for over 4 days with under-volting (100W 1070 & 1070 Ti / 175W 1080 & 1080 Ti) and overclocking (-50 core 1070/1070 Ti, 200 core 1080 & 1080 Ti with 1100 Mem for the 1070/1070 Ti and 1000 for the 1080 & 1080 Ti). Mining ETH.
Whatever my issue was, it was an issue within nvOC. The question is why and what was causing the crashing issue.
Later this week, I plan on loading up a fresh copy of nvOC and see if the issue continues. Unfortunately I cleared the USB sticks we were using that had the nvOC OS on them. Had I though about it, it would have been good to have them to see if anyone could identify any issues. The only thing I really did was re-compile the miners.
It is difficult to pin-point when the issue really showed up as we were having to re-set the miners at least once a week and then eventually even would crash once daily. Both at the same time even on different algorithms. I tried multiple different mining programs, no over clocks, half overclock, full overclock. Nothing seemed to matter. 18-24 hours the crash was inevitable.
I wish I had more information on this, but wanted to get it into the forum in-case this ever happened to anyone else. I will update once I re-load up nvOC and see what happens.
OK...
So update time. It turns out that the issue all along was a faulty graphics card. In moving to SMOS, I had left the mining screen up on my computer and just happen to walk into an error on GPU 12. The rig crashed, and it took the other rig out as well. We replaced the riser and it crashed again. SO we removed the card completely.
It's been over 4 days running constantly for BOTH rigs and not a single crash or issue..
With this. We are moving back to a fresh copy of nvOC tomorrow as I really do dislike SMOS. But I wanted to update all. So, check your GPU's if you have a crashing issue you can't figure out! We are going to try and replace all other parts and re-insert the card and hope it's not an actual issue with the card. But I have a feeling it is. So it may be going back to TRY and get a replacement. I guess we will see.
Thanks for the feedback. I am glad you finally figured it out. Hopefully it will be smooth sailing for a long time with nvOC and healthy HW.
Well after much frustration with my rigs crashing, I thought I had it figured out but the problem continued.
Originally I had setup SMOS but really didn't care for the simplicity of the interface or should I say lack there of and found nvOC.
As my rigs are remote in another state, it was even more difficult to diagnose.
For ease, I had my brother-in-law load up SMOS on both rigs and they have been running for over 4 days with under-volting (100W 1070 & 1070 Ti / 175W 1080 & 1080 Ti) and overclocking (-50 core 1070/1070 Ti, 200 core 1080 & 1080 Ti with 1100 Mem for the 1070/1070 Ti and 1000 for the 1080 & 1080 Ti). Mining ETH.
Whatever my issue was, it was an issue within nvOC. The question is why and what was causing the crashing issue.
Later this week, I plan on loading up a fresh copy of nvOC and see if the issue continues. Unfortunately I cleared the USB sticks we were using that had the nvOC OS on them. Had I though about it, it would have been good to have them to see if anyone could identify any issues. The only thing I really did was re-compile the miners.
It is difficult to pin-point when the issue really showed up as we were having to re-set the miners at least once a week and then eventually even would crash once daily. Both at the same time even on different algorithms. I tried multiple different mining programs, no over clocks, half overclock, full overclock. Nothing seemed to matter. 18-24 hours the crash was inevitable.
I wish I had more information on this, but wanted to get it into the forum in-case this ever happened to anyone else. I will update once I re-load up nvOC and see what happens.
Originally I had setup SMOS but really didn't care for the simplicity of the interface or should I say lack there of and found nvOC.
As my rigs are remote in another state, it was even more difficult to diagnose.
For ease, I had my brother-in-law load up SMOS on both rigs and they have been running for over 4 days with under-volting (100W 1070 & 1070 Ti / 175W 1080 & 1080 Ti) and overclocking (-50 core 1070/1070 Ti, 200 core 1080 & 1080 Ti with 1100 Mem for the 1070/1070 Ti and 1000 for the 1080 & 1080 Ti). Mining ETH.
Whatever my issue was, it was an issue within nvOC. The question is why and what was causing the crashing issue.
Later this week, I plan on loading up a fresh copy of nvOC and see if the issue continues. Unfortunately I cleared the USB sticks we were using that had the nvOC OS on them. Had I though about it, it would have been good to have them to see if anyone could identify any issues. The only thing I really did was re-compile the miners.
It is difficult to pin-point when the issue really showed up as we were having to re-set the miners at least once a week and then eventually even would crash once daily. Both at the same time even on different algorithms. I tried multiple different mining programs, no over clocks, half overclock, full overclock. Nothing seemed to matter. 18-24 hours the crash was inevitable.
I wish I had more information on this, but wanted to get it into the forum in-case this ever happened to anyone else. I will update once I re-load up nvOC and see what happens.
OK...
So update time. It turns out that the issue all along was a faulty graphics card. In moving to SMOS, I had left the mining screen up on my computer and just happen to walk into an error on GPU 12. The rig crashed, and it took the other rig out as well. We replaced the riser and it crashed again. SO we removed the card completely.
It's been over 4 days running constantly for BOTH rigs and not a single crash or issue..
With this. We are moving back to a fresh copy of nvOC tomorrow as I really do dislike SMOS. But I wanted to update all. So, check your GPU's if you have a crashing issue you can't figure out! We are going to try and replace all other parts and re-insert the card and hope it's not an actual issue with the card. But I have a feeling it is. So it may be going back to TRY and get a replacement. I guess we will see.
Good catch, let us know how it goes
On my test rig with 2x1060 + 1x1070 hash rate is a bit lower than dstm with same OC +PL
dstm:
Code:
2018-05-23 10:35:21 PM| GPU0 64C 45% | 412.9 Sol/s 413.8 Avg 222.2 I/s | 4.18 S/W 98 W | 1.10 100 252
2018-05-23 10:35:21 PM| GPU1 59C 45% | 295.1 Sol/s 290.7 Avg 155.8 I/s | 3.75 S/W 75 W | 0.79 93.3 277
2018-05-23 10:35:21 PM| GPU2 66C 45% | 280.9 Sol/s 281.6 Avg 150.8 I/s | 3.62 S/W 79 W | 0.65 100 253
2018-05-23 10:35:21 PM| ============== | 988.9 Sol/s 986.1 Avg 528.8 I/s | 3.85 S/W 254 W | 2.54 97.9 260
2018-05-23 10:35:21 PM| GPU1 59C 45% | 295.1 Sol/s 290.7 Avg 155.8 I/s | 3.75 S/W 75 W | 0.79 93.3 277
2018-05-23 10:35:21 PM| GPU2 66C 45% | 280.9 Sol/s 281.6 Avg 150.8 I/s | 3.62 S/W 79 W | 0.65 100 253
2018-05-23 10:35:21 PM| ============== | 988.9 Sol/s 986.1 Avg 528.8 I/s | 3.85 S/W 254 W | 2.54 97.9 260
funakoshiMiner:
Code:
[2018-May-23 22:38:47] [GPU-0 (15 sec)] 212 I/s, 409 Sols/s
[2018-May-23 22:38:47] [GPU-1 (15 sec)] 145 I/s, 278 Sols/s
[2018-May-23 22:38:47] [GPU-2 (15 sec)] 142 I/s, 270 Sols/s
[2018-May-23 22:38:47] [TOTAL (15 sec)] 499 I/s, 957 Sols/s, 1 Accepted, 0 Rejected
[2018-May-23 22:38:47] [GPU-1 (15 sec)] 145 I/s, 278 Sols/s
[2018-May-23 22:38:47] [GPU-2 (15 sec)] 142 I/s, 270 Sols/s
[2018-May-23 22:38:47] [TOTAL (15 sec)] 499 I/s, 957 Sols/s, 1 Accepted, 0 Rejected
Thanks, Pap. How many times have the seen the claims of "much faster than others" with these miners only to find otherwise?
Good catch, let us know how it goes
On my test rig with 2x1060 + 1x1070 hash rate is a bit lower than dstm with same OC +PL
dstm:
Code:
2018-05-23 10:35:21 PM| GPU0 64C 45% | 412.9 Sol/s 413.8 Avg 222.2 I/s | 4.18 S/W 98 W | 1.10 100 252
2018-05-23 10:35:21 PM| GPU1 59C 45% | 295.1 Sol/s 290.7 Avg 155.8 I/s | 3.75 S/W 75 W | 0.79 93.3 277
2018-05-23 10:35:21 PM| GPU2 66C 45% | 280.9 Sol/s 281.6 Avg 150.8 I/s | 3.62 S/W 79 W | 0.65 100 253
2018-05-23 10:35:21 PM| ============== | 988.9 Sol/s 986.1 Avg 528.8 I/s | 3.85 S/W 254 W | 2.54 97.9 260
2018-05-23 10:35:21 PM| GPU1 59C 45% | 295.1 Sol/s 290.7 Avg 155.8 I/s | 3.75 S/W 75 W | 0.79 93.3 277
2018-05-23 10:35:21 PM| GPU2 66C 45% | 280.9 Sol/s 281.6 Avg 150.8 I/s | 3.62 S/W 79 W | 0.65 100 253
2018-05-23 10:35:21 PM| ============== | 988.9 Sol/s 986.1 Avg 528.8 I/s | 3.85 S/W 254 W | 2.54 97.9 260
funakoshiMiner:
Code:
[2018-May-23 22:38:47] [GPU-0 (15 sec)] 212 I/s, 409 Sols/s
[2018-May-23 22:38:47] [GPU-1 (15 sec)] 145 I/s, 278 Sols/s
[2018-May-23 22:38:47] [GPU-2 (15 sec)] 142 I/s, 270 Sols/s
[2018-May-23 22:38:47] [TOTAL (15 sec)] 499 I/s, 957 Sols/s, 1 Accepted, 0 Rejected
[2018-May-23 22:38:47] [GPU-1 (15 sec)] 145 I/s, 278 Sols/s
[2018-May-23 22:38:47] [GPU-2 (15 sec)] 142 I/s, 270 Sols/s
[2018-May-23 22:38:47] [TOTAL (15 sec)] 499 I/s, 957 Sols/s, 1 Accepted, 0 Rejected
Good catch, let us know how it goes
Quote from: papampi
19.21 is work in progress and not ready for beta testing yet ...
[/quote
19.21 is work in progress and not ready for beta testing yet ...
[/quote
But it's getting close! Great collaboration and collaborators.
Lots of improvements and a leaner crisper codebase.
Siz
Global+GPU_OFFSET and Algo+GPU_OFFSET are available for next version (Thanks to Lukepicci):
Great, now I just need find time to test it!
--
Tigel
19.21 is work in progress and not ready for beta testing yet ...
Global+GPU_OFFSET and Algo+GPU_OFFSET are available for next version (Thanks to Lukepicci):
Great, now I just need find time to test it!
--
Tigel
nvOC dev team are working hard on next release with so many improvements and new features.
You can have a look at nvOC GitHub
Suggestions for improvement and new features are most welcome
Fist of all, quite impressive, haven't checked for a while as things have been running quite well with 2.0. But:
Algorithm and card specific OC settings maybe? You know, for us who use rigs with mixed cards.
--
Tigel
Global+GPU_OFFSET and Algo+GPU_OFFSET are available for next version (Thanks to Lukepicci):
Code:
POWERLIMIT_MODE="GLOBAL" # GLOBAL, GPU_SPECIFIC, ALGO_SPECIFIC (Pro Settings: GLOBAL_with_GPU_OFFSET, ALGO_SPECIFIC_with_GPU_OFFSET)
OVERCLOCK_MODE="GLOBAL" # NO, GLOBAL, GPU_SPECIFIC, ALGO_SPECIFIC (Pro Settings: GLOBAL_with_GPU_OFFSET, ALGO_SPECIFIC_with_GPU_OFFSET)
# Modes:
# NO disables overclock
# GLOBAL mode means no individual gpu- or algo-specific settings are used
# GPU_SPECIFIC let global setting be overridden by individual gpu-specific setting
# ALGO_SPECIFIC let global setting be dynamically overridden by algo-specific setting
# Pro Settings are not for the faint-hearted. Dont use if you dont know what they are.
OVERCLOCK_MODE="GLOBAL" # NO, GLOBAL, GPU_SPECIFIC, ALGO_SPECIFIC (Pro Settings: GLOBAL_with_GPU_OFFSET, ALGO_SPECIFIC_with_GPU_OFFSET)
# Modes:
# NO disables overclock
# GLOBAL mode means no individual gpu- or algo-specific settings are used
# GPU_SPECIFIC let global setting be overridden by individual gpu-specific setting
# ALGO_SPECIFIC let global setting be dynamically overridden by algo-specific setting
# Pro Settings are not for the faint-hearted. Dont use if you dont know what they are.
nvOC dev team are working hard on next release with so many improvements and new features.
You can have a look at nvOC GitHub
Suggestions for improvement and new features are most welcome
Fist of all, quite impressive, haven't checked for a while as things have been running quite well with 2.0. But:
Algorithm and card specific OC settings maybe? You know, for us who use rigs with mixed cards.
--
Tigel
nvOC dev team are working hard on next release with so many improvements and new features.
You can have a look at nvOC GitHub
Suggestions for improvement and new features are most welcome
hello
I see no activity lately here, did something happen? another thread or project at the end?
thanks
I see no activity lately here, did something happen? another thread or project at the end?
thanks
Just that nvOC working smooth and there are not much users with problems ...
hello
I see no activity lately here, did something happen? another thread or project at the end?
thanks
I see no activity lately here, did something happen? another thread or project at the end?
thanks
I don't know if they are related errors:
I have been messing with it for 2 days, installed the OS again... nothing
I have been messing with it for 2 days, installed the OS again... nothing
Did you try to change drivers? Try from 384.
No i haven't, current drivers are 387.34. So i should go back? All my rigs are 387.34, but this one have different cards in it.
Just download the older drivers and run the install ? or do i have to do something else ? Anyone have upgraded 390.48? https://www.geforce.com/drivers/results/132530
------------------------------------- EDIT
So it was one card that caused the NVML Error "NVML: cannot get fan speed, error 15" i removed it and everything seems fine. I plugged in the culprit card on windows and its fine.... for now. Yes i tried switching risers before that.
So to summarize my ordeal.
• Bad SSD - Slow running miner.
• A card that gave me an NVML error. EVGA 1060 Don't know if it was driver's fault or what.
Jump to: