Bitcoin Forum
July 15, 2020, 12:05:53 AM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 419 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 416834 times)
philipma1957
Legendary
*
Offline Offline

Activity: 2856
Merit: 2444



View Profile
June 25, 2017, 12:06:47 AM
 #1161

okay I am running 3 card rig  I got -pl 105 for all 3 cards to work.

I am pulling about 375 at the k-watt meter for 1275 sols.

I had to set  each gpu individually to    -pl 105

I can't run xmr cpu but not much coin no worries.

my bash had 11 gpus i deleted 6-10  kept 0,1,2,3,4,5

all seems okay


https://www.nicehash.com/index.jsp?p=miners&addr=1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

can be viewed at link above.  last one on the equihash list nvOCphiltest1



Phil,

you can recomplile cpuminer-opt by opening the guake terminal and entering:

Code:
cd cpuOPT

and press enter

then type:

Code:
./build.sh

and press enter

this will recompile for your specific cpu; after it is done, if you change plusCPU to YES in oneBash and enter your XMR info you will mine a little XMR on the side.  

When using a 1080ti I recommend only using 1 thread to ensure the GPU mining is not reduced at all.

okay I did this and I am mining some xmr and of course the 2 1080ti's do zec




I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
AWARD-WINNING
CRYPTO CASINO
ASKGAMBLERS
PLAYERS CHOICE 2019
PROUD
PARTNER OF
1500+
GAMES
2 MIN
CASH-OUTS
24/7
SUPPORT
100s OF
FREE SPINS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
1594771553
Hero Member
*
Offline Offline

Posts: 1594771553

View Profile Personal Message (Offline)

Ignore
1594771553
Reply with quote  #2

1594771553
Report to moderator
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 12:57:09 AM
 #1162

I've tried three different versions of nvOC now and I still just CAN'T GET THE OVERCLOCKS TO WORK!

I've tried individual and whole system and I even see the overclocks apply when onebash starts - but they aren't sticking.

I'm mining eth and in Windows with Afterburner I set all 5 cards (2 1070s and 3 1060s) to core +75 and mem +800 and I get 132mh/s

Using nvOC and trying to set the same overclocks, I get 120mh/s.

It's really frustrating. I just don't understand. Does Claymore set everything to factory clocks when it starts or something?

Anyone else mining ETH and managing to ue overclocking?

Quote from: fullzero
Also linux OC offsets are scaled differently than windows; you will need to use higher offsets to get the same results in linux.

I am mining ETH and am overclocked (~30.9 MH/sec on 1070 Founders Ed cards and ~29.5 MH/sec on a frankenstein rig with 3 different kinds of 1070 cards).

I recommend using v0016 if you aren't already and trying the OC settings:

__CORE_OVERCLOCK=-100
MEMORY_OVERCLOCK=1000

if this is stable I would try:

__CORE_OVERCLOCK=-100
MEMORY_OVERCLOCK=1100

then:

__CORE_OVERCLOCK=-100
MEMORY_OVERCLOCK=1200

... until you get a soft crash in Claymore, then I would backtrack to the previous setting

OK... I have a very weird (at least to me) situation. I'm using v0016 and I followed your suggestion of trying memory overclocks of 1000, 1100 & 1200.

I do see an improvement. previously I saw a hashrate of 120mh/s compared to Win8.1 / MSI Afterburner (core -200 memory +800) getting me around 132mh/s.

Now when I tried your suggestion nvOC is giving me around 127mh/s but the weird thing is - I get this hashrate regardless of whether it's based on memory 1000, or 1100 or 1200. The same improvement. This suggests that your memory overclock is just somehow selecting some arbitrary amount whether I tell it 1000, 1100 or 1200. Not some precise amount which increases as I raise the number. I know the actual memory figure isn't raising it by 800 or 1000 or 1100 or whatever, because the (actual) memory is running in the 5000s.
It would be nice to be able to set a precise number and see a precise gain. It would be especially nice to be able to at least equal (or even improve) what I can achieve in Windows, which seems to be about 132mh/s - not 127mh/s which is what nvOC is reporting. I know it's only 5mh/s but don't we all want the highest hash-rate we can achieve?

I guess I also must consider power consumption. If nvOV is delivering 127mh/s but at much lower power than Windows at 132mh/s of course I will use it.

I just wish it was clear to me what these overclocking setting numbers actuually mean.

When you OC without providing sufficent power; you get what you have experienced: the appearance of the hashrate being constant. 

With some additional amount of power (whatever is needed to fuel the additional OC properly) you will see additional hashrate with higher OC. 

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 01:03:40 AM
 #1163

I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...

To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first.

I would try Maxximus007's suggestion.

Let me know if you keep getting these errors.

It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason.  

Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining.



I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too.

You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing

gp

then click Gparted.  Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size.

click the green checkmark to execute the change, wait for completion and it should be ~17gb larger.

I will do this + add the cmds to enable Claymore to use 16gb VM in the next version.


This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it.

Another  question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining?

I am starting to think a possible hardware failure somewhere with the lack of stability in the rig..

Dual mining is always less stable, especially with OC and powerlimit.  What ram, PSU, and CPU are you using?

Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested:
PSU: Seasonic 1050
CPU: Intel Celeron g3930
RAM: Crucial 4GB.

Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. 

To increase stability you could also try raising your powerlimit slightly and lowering dcri,

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 01:08:17 AM
 #1164

Hey,

Just wondering how many CPU threads you guys are using to mine monero without causing impact to GPU mining operations? Currently have mine set at 2 but was thinking it can probably do 3 using G4560.

Thanks

It depends on what Client you are using to GPU mine.  EWBF is very light on the CPU so you could probably do 3 threads without noticing a difference in the GPU hashrate. 

If you are using Claymore to mine a Ethash COIN; I wouldn't use more than 2: if dual mining with Claymore I wouldn't use more than 1. 

With a weaker CPU I wouldn't cpu mine at all while dual mining with Claymore.

fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 01:18:16 AM
 #1165


okay I am running 3 card rig  I got -pl 105 for all 3 cards to work.

I am pulling about 375 at the k-watt meter for 1275 sols.

I had to set  each gpu individually to    -pl 105

I can't run xmr cpu but not much coin no worries.

my bash had 11 gpus i deleted 6-10  kept 0,1,2,3,4,5

all seems okay


https://www.nicehash.com/index.jsp?p=miners&addr=1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

can be viewed at link above.  last one on the equihash list nvOCphiltest1



Phil,

you can recomplile cpuminer-opt by opening the guake terminal and entering:

Code:
cd cpuOPT

and press enter

then type:

Code:
./build.sh

and press enter

this will recompile for your specific cpu; after it is done, if you change plusCPU to YES in oneBash and enter your XMR info you will mine a little XMR on the side.  

When using a 1080ti I recommend only using 1 thread to ensure the GPU mining is not reduced at all.

okay I did this and I am mining some xmr and of course the 2 1080ti's do zec




Let me know if you think it is slowing down the ZEC hashrate at all; in my tests it appeared to have no impact on simultaneous Equihash mining: but more data makes us better informed.  Smiley


philipma1957
Legendary
*
Offline Offline

Activity: 2856
Merit: 2444



View Profile
June 25, 2017, 01:23:44 AM
 #1166


okay I am running 3 card rig  I got -pl 105 for all 3 cards to work.

I am pulling about 375 at the k-watt meter for 1275 sols.

I had to set  each gpu individually to    -pl 105

I can't run xmr cpu but not much coin no worries.

my bash had 11 gpus i deleted 6-10  kept 0,1,2,3,4,5

all seems okay


https://www.nicehash.com/index.jsp?p=miners&addr=1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

can be viewed at link above.  last one on the equihash list nvOCphiltest1



Phil,

you can recomplile cpuminer-opt by opening the guake terminal and entering:

Code:
cd cpuOPT

and press enter

then type:

Code:
./build.sh

and press enter

this will recompile for your specific cpu; after it is done, if you change plusCPU to YES in oneBash and enter your XMR info you will mine a little XMR on the side.  

When using a 1080ti I recommend only using 1 thread to ensure the GPU mining is not reduced at all.

okay I did this and I am mining some xmr and of course the 2 1080ti's do zec




Let me know if you think it is slowing down the ZEC hashrate at all; in my tests it appeared to have no impact on simultaneous Equihash mining: but more data makes us better informed.  Smiley


  I have a 2 core 4 thread i3-6100t

I just bumped to 2 threads.

I will watch this.
I also plan to use an i7  6700t

and an i5 7500t

I think I will go all linux due to stability .

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
Nexillus
Full Member
***
Offline Offline

Activity: 169
Merit: 100


View Profile
June 25, 2017, 01:49:08 AM
 #1167

I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...

To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first.

I would try Maxximus007's suggestion.

Let me know if you keep getting these errors.

It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason.  

Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining.



I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too.

You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing

gp

then click Gparted.  Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size.

click the green checkmark to execute the change, wait for completion and it should be ~17gb larger.

I will do this + add the cmds to enable Claymore to use 16gb VM in the next version.


This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it.

Another  question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining?

I am starting to think a possible hardware failure somewhere with the lack of stability in the rig..

Dual mining is always less stable, especially with OC and powerlimit.  What ram, PSU, and CPU are you using?

Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested:
PSU: Seasonic 1050
CPU: Intel Celeron g3930
RAM: Crucial 4GB.

Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. 

To increase stability you could also try raising your powerlimit slightly and lowering dcri,


I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM.
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 02:41:12 AM
 #1168

I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...

To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first.

I would try Maxximus007's suggestion.

Let me know if you keep getting these errors.

It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason.  

Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining.



I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too.

You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing

gp

then click Gparted.  Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size.

click the green checkmark to execute the change, wait for completion and it should be ~17gb larger.

I will do this + add the cmds to enable Claymore to use 16gb VM in the next version.


This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it.

Another  question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining?

I am starting to think a possible hardware failure somewhere with the lack of stability in the rig..

Dual mining is always less stable, especially with OC and powerlimit.  What ram, PSU, and CPU are you using?

Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested:
PSU: Seasonic 1050
CPU: Intel Celeron g3930
RAM: Crucial 4GB.

Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. 

To increase stability you could also try raising your powerlimit slightly and lowering dcri,


I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM.

Most likely; but its one of those things that's almost impossible to isolate; so its hard to say what actually makes the difference.


Nexillus
Full Member
***
Offline Offline

Activity: 169
Merit: 100


View Profile
June 25, 2017, 02:46:27 AM
 #1169

I'm really confused now, it just happened on VER15 within 15 minutes... With a different USB drive...

To my knowledge this should not be happening since these are 8GB cards and it will hit 3GB DAG file next year for ETH...
I've had these errors once too, but it was OC. Your temps are nice so that's not the issue. Lower both OC and MC with 100, see if it is stable then. If so, go up with 50, MC first.

I would try Maxximus007's suggestion.

Let me know if you keep getting these errors.

It is also possible that having less free space contributes to these errors with claymore; I think I am going to increase the size of the primary partition to very close to 16gb for the next version for this reason.  

Optimally for claymore you should have up to 16gb of free space and use it as virtual memory, I am considering pushing the size to 32gb and implementing this in an alternative build for better ethash mining.



I changed the OC by mem by 15 and it has been solid for the last 90 minutes. I just think it is very odd since it was on the OC for almost a week. I didn't know you changed the primary partition, I think many of us are using 32GB USB keys too.

You can extend the primary partition on any key, by connecting it to a computer with nvOC that has already booted and clicking the ubuntu launcher at the top left and typing

gp

then click Gparted.  Find the sdb drive select the larger partition; it it is mounted unmount it; then rightclick and select resize and set the max size.

click the green checkmark to execute the change, wait for completion and it should be ~17gb larger.

I will do this + add the cmds to enable Claymore to use 16gb VM in the next version.


This is starting to be very frustrating overall, after 8 hours it just "froze" no crash, no failure just frozen... Had to hard reset it.

Another  question is, what is people's variance on hashrate? I have my go up and down quite often between 177-180. Sometimes goes down to 175. Anyone else have variance with mining? Is this caused by dual mining?

I am starting to think a possible hardware failure somewhere with the lack of stability in the rig..

Dual mining is always less stable, especially with OC and powerlimit.  What ram, PSU, and CPU are you using?

Humm something to consider, when I use to do this dual mining wasn't even an option. Here is the info you requested:
PSU: Seasonic 1050
CPU: Intel Celeron g3930
RAM: Crucial 4GB.

Might be more stable with 16gb of virtual ram; Claymore intermittently uses the CPU intensively and 4GB might not always be enough of a buffer for your cards. 

To increase stability you could also try raising your powerlimit slightly and lowering dcri,


I have raised the powerlimit on all the cards, which I think helped. Do you think adding more RAM would help it? Could get at least another 4GB DIMM.

Most likely; but its one of those things that's almost impossible to isolate; so its hard to say what actually makes the difference.



Well RAM is cheap it wouldn't hurt not including, can never have enough DIMMs sitting around lmao. Just ordered and will have it on Tuesday. Love amazon prime. Thanks fullzero Smiley
Tasbi
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
June 25, 2017, 03:05:27 AM
 #1170

Hello, I´m trying to dual mine ETH-DECRED with pool suprnova.cc, but don´t know how to setup

DCR_WORKER="rig6"
DCR_ADDRESS=""
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252 "

anyone could help me with it?
fullzero
Legendary
*
Offline Offline

Activity: 1246
Merit: 1009



View Profile
June 25, 2017, 03:08:55 AM
 #1171

Hello, I´m trying to dual mine ETH-DECRED with pool suprnova.cc, but don´t know how to setup

DCR_WORKER="rig6"
DCR_ADDRESS=""
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252 "

anyone could help me with it?

for DCR_ADDRESS=""

use your supernova login; so if your login was: Tasbi and your workername was rig6 (note you actually have to make workers at suprnova)

then you would use:

DCR_WORKER="rig6"
DCR_ADDRESS="Tasbi"
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252 "

philipma1957
Legendary
*
Offline Offline

Activity: 2856
Merit: 2444



View Profile
June 25, 2017, 07:50:31 AM
 #1172


okay I am running 3 card rig  I got -pl 105 for all 3 cards to work.

I am pulling about 375 at the k-watt meter for 1275 sols.

I had to set  each gpu individually to    -pl 105

I can't run xmr cpu but not much coin no worries.

my bash had 11 gpus i deleted 6-10  kept 0,1,2,3,4,5

all seems okay


https://www.nicehash.com/index.jsp?p=miners&addr=1JdC6Xg3ajT3rge3FgPNSYYFpmf53Vbtje

can be viewed at link above.  last one on the equihash list nvOCphiltest1



Phil,

you can recomplile cpuminer-opt by opening the guake terminal and entering:

Code:
cd cpuOPT

and press enter

then type:

Code:
./build.sh

and press enter

this will recompile for your specific cpu; after it is done, if you change plusCPU to YES in oneBash and enter your XMR info you will mine a little XMR on the side.  

When using a 1080ti I recommend only using 1 thread to ensure the GPU mining is not reduced at all.

okay I did this and I am mining some xmr and of course the 2 1080ti's do zec




Let me know if you think it is slowing down the ZEC hashrate at all; in my tests it appeared to have no impact on simultaneous Equihash mining: but more data makes us better informed.  Smiley


I now have 2 going. 

a i5 6400t on a biostar z170 2 threads  runs fine.  better cpu so makes sense

 a i3 6100t on a gigabyte b250m     2 threads crash  one thread worked

I see BTC as the super highway and alt coins as taxis and trucks needed to move transactions.
Tasbi
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
June 25, 2017, 08:06:24 AM
 #1173

Hello, I´m trying to dual mine ETH-DECRED with pool suprnova.cc, but don´t know how to setup

DCR_WORKER="rig6"
DCR_ADDRESS=""
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252 "

anyone could help me with it?

for DCR_ADDRESS=""

use your supernova login; so if your login was: Tasbi and your workername was rig6 (note you actually have to make workers at suprnova)

then you would use:

DCR_WORKER="rig6"
DCR_ADDRESS="Tasbi"
DCR_POOL="stratum+tcp://dcr.suprnova.cc:3252 "

Ok thanks for your help, what about the password???
I have very stable rigs with nvoc... I really appreciate your effort and time
ijduncan
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
June 25, 2017, 08:56:35 AM
Last edit: June 25, 2017, 09:31:59 PM by ijduncan
 #1174

I have set up a 9 gpu system with nvOC 16 and here's my experience.

nvOS is stellar. Fullzero has put something really special together here. Hats off to you. I have used windows builds with Claymore as well as other linux os such as PIMP.  This is by far the best experience I have has so far.

nvOS is as easy as setting up in windows but with the advantage of linux as well as being able to control everything including over clocking with a bash script file that's as easy as filling in a form.

Currently this 9 gpu rig is hashing ETH and DCR using the suprvova pools. I have found v16 with claymore 9.5 to be far superior to the previous version and i think it will be our goto for larger deployment for the time being.

Right now it hashes at around 183 Mh/s.  Here's the build:

1x Motherboard Asus z270 K
https://www.amazon.com/gp/product/B01N6E5DGE/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=2c808e893c1258649f2dc669fac68eaa

1x Celeron CPU
https://www.amazon.com/gp/product/B01MYTY55V/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=62eae19da50682d49b19da172923f70d

1x Memory x1
https://www.amazon.com/gp/product/B00MMLUYVU/ref=as_li_ss_tl?ie=UTF8&th=1&linkCode=sl1&linkId=28d39779a7e5f04c0a3194ee0f20b4c9

2x PSU
https://www.amazon.com/dp/B00IKDETOC/ref=as_li_ss_tl?ie=UTF8&linkCode=sl1&linkId=e0bee413cbda09bbca0d433a344de225

1x USB Drive
https://www.amazon.com/gp/product/B00KT7DOSE/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=e9ccce372d51579418f777c9c844d74a

2x m2 pcie adapter
https://www.amazon.com/gp/product/B01ABF9APE/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=441adfeae3389676c409b69f685a53c6

3x pcie riser
https://www.amazon.com/gp/product/B01N3UVJHM/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=92ec3dac391a8212786d89057dff4406

9x GPUs
https://www.amazon.com/gp/product/B01IPVSGEC/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=4cbbd38378ca9a5a74f92155432314bf

1x power switch
https://www.amazon.com/gp/product/B06XPZBM7V/ref=as_li_ss_tl?ie=UTF8&psc=1&linkCode=sl1&linkId=60ed915161819f8f0b0a570310c23b83

1x Wooden frame
https://www.amazon.com/Woodpeckers-Square-Dowel-Rods-Pack/dp/B01C6BMJ7M/ref=as_li_ss_tl?ie=UTF8&qid=1498368074&sr=8-1&keywords=square+wood+dowel&linkCode=sl1&linkId=35a31a17309fd7f18b37fee50ebbb959

around $3300 with tax

Here is a pic.
https://lh3.googleusercontent.com/JEVicIBkHCAEk1SwqyfQZVGtL6LxPPx47qnHLm1rVkMeFE5vlTMFEOdU9pyAV76ziJA1OYdjz07BJmGxtqGHRzjupRIq027ta2Ou6oduYm7bft8VicjmB38vulSdPKGAmLT_KJo=w968-h1290-no

Here are some nvOC wallpapers for your rigs.
https://drive.google.com/drive/folders/0B0lx4O21EyI3eEFHcG8tWEhIU0k?usp=sharing

During setup i encountered numerous errors, all of which were remedied.  I went with 2 psus, not sure if its better in teh long run but splitting 1100 watts over two 850s seem to be decent for efficiency.  I have built 7 of these now and a few with the z270A version using 8 GPUS.  Both are good.  I have created this system as the model for our small mining farm in California, so i will continue to feedback on these builds as I go.

Bios settings were very important.  As was bios version.

Damaged risers and a bum gpu were also headaches during set up so be on the lookout for that.  Once you have the bio settings right and the hardware actually works it really is as simple as flashing the drive, plugging it in and turning it on.  If anyone wants the bios settings PM me but its here in the thread and is mostly about setting all pcie settings to gen2, using bios 0801 and not flashing the newer 0906.  Which was the opposite to PIMP which did not seem to work for me on the older bios.

One last thing, with these gpus I set the OC to

__CORE_OVERCLOCK=150
MEMORY_OVERCLOCK=825

and it seems to be running stable with no ETH rejections and about 1 in 200 DCR rejections. temps at 80 fans at 65% -dcri 50 and pulling about 1050 watts.

I built two of these for a friend and two for my sister.

Both are pointing at nice hash. On is here https://new.nicehash.com/miner/1GCSdasYQ3wWp8zAHHvHyao83aoyA6AFVM - currently its waiting on pcie m2 adapters to get all 9 cards going. They will recoup their investment in 3-4 months and their minds have been opened to the new world of block chains, contracts and decentralized crypto currency.

Thanks fullzero this is a brilliant project.




damNmad
Full Member
***
Offline Offline

Activity: 378
Merit: 104


nvOC forever


View Profile
June 25, 2017, 11:11:21 AM
 #1175

Hello miners...

First things first, I would like to thank 'fullzero' (infact hero Cheesy) for this fantastic job, can't thank him enough.

I've built my first RIG very recently, I would like to find the best OC settings and pool settings to get the best out of it, with the help of miners expertise.

I was getting really good speed on windows but for some reason it doesn't allow me run more than 3 GPU's (it was a trial version), but it was doing 20 MH per card from stock with claymore dual mining.

I had to switch back to Ubuntu but  the trouble is I'm only getting 18 MH on an average per card, I'm using claymore dual (ETC + PASC) with CUDA 8.x nvidia driver - 375.66, pulling 1044 watts from wall.
Temperatures : 65 - 73 C
Fans on Auto : 39 - 43

My config -

ASUS DUAL GTX 1060 - 8 GPU's
ASUS Z270P
8 GB RAM
2 x EVGA G2 750 Watts PSU units
8 x V6 Risers
120 GB SSD

Fellow miners using same cards, please share your Core, memory OC + fan + power settings. I would also like to know how to add multiple pools to the nvOC oneBash file.

Would also welcome suggestions about best combination cryptos for better ROI with my equipment.

Thanks in advance.

Regards,
damNmad


DeepOnion    ▬▬  Anonymous and Untraceable  ▬▬    ENJOY YOUR PRIVACY  •  JOIN DEEPONION
▐▐▐▐▐▐▐▐   ANN  Whitepaper  Facebook  Twitter  Telegram  Discord    ▌▌▌▌▌▌▌▌
Get $ONION  (✔Cryptopia  ✔KuCoin)  |  VoteCentral  Register NOW!  |  Download DeepOnion
Alquemista
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
June 25, 2017, 11:51:06 AM
 #1176

So I had the rig working with one MSI gtx 1080 connected to the x16 slot, when I connect a riser to the x16 slots (any of them) the card fans are working but the card won't be recognised by the operating system, replaced riser and still, doesn't work. The card is working of I put it in the x16 slot.

My mobo is an Asrock H81 pro btc r2.0 PSU is a Corsair Rx 750, in using a powered v3 riser, both molex on mobo are connected to same PSU as the riser and GPUs , on bios I have the pcie card as default, tried gen1 and gen2 everytime clearing CMOS after any plug, no way it is recognised by the pc. Anyone had same issue?
WarwickNZ
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
June 25, 2017, 01:07:54 PM
 #1177

Hey,

Just wondering how many CPU threads you guys are using to mine monero without causing impact to GPU mining operations? Currently have mine set at 2 but was thinking it can probably do 3 using G4560.

Thanks

It depends on what Client you are using to GPU mine.  EWBF is very light on the CPU so you could probably do 3 threads without noticing a difference in the GPU hashrate. 

If you are using Claymore to mine a Ethash COIN; I wouldn't use more than 2: if dual mining with Claymore I wouldn't use more than 1. 

With a weaker CPU I wouldn't cpu mine at all while dual mining with Claymore.

OK thanks for the advice, i'll apply as necessary.

One more thing, is it just me or do the 1070s refuse to draw more than 150W power even when the power limit is increased? Obviously it works upping the powerlimit in windows but it doesnt seem to work for me in linux, only on the reduction.

Cheers
dakky
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
June 25, 2017, 01:17:18 PM
 #1178

Do any of you have idea why 6x Asus 1060 3GB make around 65MH/s on ETH? (65.529 MH/s, 25/0/0 (0.00%): 9.642+9.760+12.370+13.154+8.689+11.911 MH/s)

Gigabyte Z270 Gaming K3, 8GB, Pentium G4400

The same configuration on SMOS makes around 19MH per card.

Thanks
bentcrypto
Full Member
***
Offline Offline

Activity: 186
Merit: 100


View Profile
June 25, 2017, 01:57:47 PM
 #1179

I just got around to test v16.

Same error messages like below.

Getting infinite loop.

LCD connected to mobo graphics (like always in v15 and BIOS set to on board graphics not PCI)

Will test on PCI graphics later thi PM - hopefully no more infinite loops - will post results later.

Much better boot-up speed, this time can use USB3 port fully compatible with build?

I just added 5 more 20A circuits in my warehouse - fun times begins!

I can't seem to get v16 to work on tb-250.

It boots up then terminal pops up and says:

Quote
dos2unix: converting file /media/m1/1263-A96E/onebash to unix format

xorg problem detected

restarting xorg

rebooting in 5

Have tried different USB's and also booting with only one card but still have the same problem.

Anyone know what the problem might be?

Have you waited for the second boot?

If you are using one GPU it is expected that oneBash will need to rebuild the xorg file and reboot before OC will work as intended.

It should work without rebooting on the second boot; unless you have connected the monitor directly to the motherboard (always connect a monitor to the primary GPU).

I have had one member report that their rig is caught in an infinite loop of reboots; so I would like to know if this is happening to you as well.



Full Zero was right. If you change your primary display to PCI and plug your monitor into your primary card it will boot.

The other great thing is my clocks are working with v16...my 1070's have gone from 390MH to 430 MH Cheesy

Thanks full zero!!
Nexillus
Full Member
***
Offline Offline

Activity: 169
Merit: 100


View Profile
June 25, 2017, 03:56:44 PM
 #1180

Thought I would give an update. After adjusting the power settings and doing some specific troubleshooting I have gotten the rig stable for 24 hours.

I took fullzero and Maxximus007 suggestions on the power settings and give it a bit more with more modest OC. It seems to have resolved the issue, as well I have found that one of the cards was not liking bigger OC's while the other 5 worked fine.

This was the outcome.
ETH - Total Speed: 180.068 Mh/s, Total Shares: 2000, Rejected: 0, Time: 15:48
ETH: GPU0 30.198 Mh/s, GPU1 30.240 Mh/s, GPU2 30.186 Mh/s, GPU3 29.500 Mh/s, GPU4 30.086 Mh/s, GPU5 29.857 Mh/s
SC - Total Speed: 1200.451 Mh/s, Total Shares: 429, Rejected: 0
SC: GPU0 201.322 Mh/s, GPU1 201.599 Mh/s, GPU2 201.240 Mh/s, GPU3 196.667 Mh/s, GPU4 200.575 Mh/s, GPU5 199.048 Mh/s
GPU0 t=62C fan=75%, GPU1 t=48C fan=75%, GPU2 t=64C fan=75%, GPU3 t=61C fan=75%, GPU4 t=60C fan=75%, GPU5 t=49C fan=75%

As for the settings, I have the following settings:
5 cards:
Overclock
cc 100
mc 1275
Powerlimit: 125 watts
1 card:
cc -100
mc 1225
Powerlimit: 120 watts
(this card does not like OC had to tweak it some for it to not cause instability within the rig)

Total watts from the wall: 866/867

I am still taking fullzero advice and adding 4 GB more of RAM it will be here in the next few days.

Maxximus007 or fullzero if you have a BTC,ETH address I would like to send you a small thank you for the help on troubleshooting.
Pages: « 1 ... 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 [59] 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 ... 419 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!