|
VoskCoin
|
 |
May 31, 2017, 02:48:56 PM |
|
Yes; there is a link in the OP as well. I was asking him to see if they did not have the capacity needed with some of the images, would you recommend the 32gb sticks to alleviate this issue / have you tested them? I do not mind spending 4 dollars to delete a possible headache xD |
|
|
|
|
fullzero (OP)
|
|
May 31, 2017, 03:12:34 PM
Last edit: May 31, 2017, 03:23:00 PM by fullzero |
|
Yes; there is a link in the OP as well. I was asking him to see if they did not have the capacity needed with some of the images, would you recommend the 32gb sticks to alleviate this issue / have you tested them? I do not mind spending 4 dollars to delete a possible headache xD I am not sure what USB keys bentcrypto is using. It is unfortunate that most companies market USB keys beyond the actual usable capacity. The 16gb Lexar USB keys I recommend have a 16.0 gb capacity, any of the nvOC images will fit on one. The 32gb version is marginally faster. The only other reason I can think of to get the 32gb vs the 16gb (while the 16gb is still $8) is if you really like the color orange. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
|
VoskCoin
|
|
May 31, 2017, 04:04:34 PM |
|
Yes; there is a link in the OP as well. I was asking him to see if they did not have the capacity needed with some of the images, would you recommend the 32gb sticks to alleviate this issue / have you tested them? I do not mind spending 4 dollars to delete a possible headache xD I am not sure what USB keys bentcrypto is using. It is unfortunate that most companies market USB keys beyond the actual usable capacity. The 16gb Lexar USB keys I recommend have a 16.0 gb capacity, any of the nvOC images will fit on one. The 32gb version is marginally faster. The only other reason I can think of to get the 32gb vs the 16gb (while the 16gb is still $8) is if you really like the color orange. Okay that is great news, and I was contemplating the 64gb because I love green haha xD I have 2x 16gb on order |
|
|
|
|
bentcrypto
|
|
May 31, 2017, 04:26:18 PM |
|
No they didn't have the ones that fullzero recommended so I just bought 2 different brands and both are too small, result in errors on hdrawcopy and won't boot nvOC. I'll go and get a 32gb Tomorrow and then have another shot. |
|
|
|
|
Sequoia93
Member
 Offline
Activity: 116
Merit: 10
|
|
May 31, 2017, 05:44:24 PM
Last edit: May 31, 2017, 05:58:13 PM by Sequoia93 |
|
What do you mean by "(only 6x OC)" for the z170/z270 boards? Can this OS support 7 cards with those boards?
and you say usb key only....does that mean an M.2 drive will not work? what size ssd is required?
edit: removed lazy question
|
|
|
|
|
|
Maxximus007
|
|
May 31, 2017, 05:54:39 PM |
|
Just finished my first Nvidia rig with 6 x Gigabyte 1070 and a MSI Z270-A Pro.
nvOC works perfectly, now mining a couple of hours on your addresses.
Currently doing around 2600 Sol/s @ 857 Watt at the wall.
I do have a few questions:
- Is there a way to edit oneBASH remotely, using ssh? Not really happy doing this on the rig itself..
- Is it wise to run apt to upgrade Ubuntu packages?
After testing the rig(s) will be in a remote location, and a monitoring tool with basic reload functions would be nice. I do understand that you have quie a few things on your plate, although I would believe the remote part is of more interest than an AMD version, they do already exist in a few different flavours.
I think installing Minerstat on nvOC is possible, but that would probably undermine the finetuning you've done.
Thanks for making nvOC!
|
|
|
|
|
goen
Member
Offline
Activity: 77
Merit: 10
|
|
May 31, 2017, 05:58:37 PM |
|
same here, i used sandish ultra flair 16gb, error at about 95%,
will try on another stick.
|
|
|
|
|
citronick
Legendary
Offline
Activity: 1834
Merit: 1080
---- winter*juvia -----
|
|
May 31, 2017, 07:31:38 PM |
|
Just finished my first Nvidia rig with 6 x Gigabyte 1070 and a MSI Z270-A Pro.
nvOC works perfectly, now mining a couple of hours on your addresses.
Currently doing around 2600 Sol/s @ 857 Watt at the wall.
I do have a few questions:
- Is there a way to edit oneBASH remotely, using ssh? Not really happy doing this on the rig itself..
- Is it wise to run apt to upgrade Ubuntu packages?
After testing the rig(s) will be in a remote location, and a monitoring tool with basic reload functions would be nice. I do understand that you have quie a few things on your plate, although I would believe the remote part is of more interest than an AMD version, they do already exist in a few different flavours.
I think installing Minerstat on nvOC is possible, but that would probably undermine the finetuning you've done.
Thanks for making nvOC!
My rigs running nvoc are offsite and I have installed Teamviewer to remote control the rig, including finetuning oneBASH file. |
If I provided you good and useful info or just a smile to your day, consider sending me merit points to further validate this Bitcointalk account ~ useful for future account recovery...
|
|
|
|
|
|
fullzero (OP)
|
|
May 31, 2017, 11:13:50 PM
Last edit: June 07, 2017, 04:12:11 PM by fullzero |
|
I just confirmed that the ASUS PRIME Z270-A image works without an m2 adapter as well to OC all 7x GPUs: up to 9x gpu (all OC) with 2x m2 adapters. see: https://bitcointalk.org/index.php?topic=1854250.msg19267100#msg19267100 |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
|
fullzero (OP)
|
|
May 31, 2017, 11:23:35 PM |
|
Just finished my first Nvidia rig with 6 x Gigabyte 1070 and a MSI Z270-A Pro.
nvOC works perfectly, now mining a couple of hours on your addresses.
Currently doing around 2600 Sol/s @ 857 Watt at the wall.
I do have a few questions:
- Is there a way to edit oneBASH remotely, using ssh? Not really happy doing this on the rig itself..
- Is it wise to run apt to upgrade Ubuntu packages?
After testing the rig(s) will be in a remote location, and a monitoring tool with basic reload functions would be nice. I do understand that you have quie a few things on your plate, although I would believe the remote part is of more interest than an AMD version, they do already exist in a few different flavours.
I think installing Minerstat on nvOC is possible, but that would probably undermine the finetuning you've done.
Thanks for making nvOC!
Thanks for hashes  Glad you like nvOC. Using teamviewer is probably the easiest way right now. For ssh and related protocols: I really like this tool: http://mobaxterm.mobatek.net/I am not familiar with minerstat; but nvOC is Ubuntu 16.04 based so you should be able to install/run any linux program. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
|
fullzero (OP)
|
|
May 31, 2017, 11:25:41 PM |
|
No they didn't have the ones that fullzero recommended so I just bought 2 different brands and both are too small, result in errors on hdrawcopy and won't boot nvOC. I'll go and get a 32gb Tomorrow and then have another shot. same here, i used sandish ultra flair 16gb, error at about 95%,
will try on another stick.
I think bentcrypto is probably right about getting a 32gb USB key if you can't find the Lexar 16gb. Most USB keys will be under listed capacity. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
|
fullzero (OP)
|
|
June 01, 2017, 04:01:41 AM |
|
I updated the MSI Z170A GAMING M5 image (in stock, 7x gpu (all OC)) see: https://bitcointalk.org/index.php?topic=1854250.msg19203907#msg19203907now supports OC on all 7x GPUs. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
rabbitr32
Newbie
Offline
Activity: 22
Merit: 0
|
|
June 01, 2017, 04:09:39 AM |
|
going to buy a few of asus prime h270 plus 6x pcie slot + 2 x M.2 and will this mobo work? https://www.asus.com/Motherboards/PRIME-H270-PLUS/there is 2 m.2 slot as well can we run 8 GPU on this? Also i have one rig running nvOC on sandisk ultra usb 3 stick 16gb all seems running well, one issue i have is the boot takes almost 1 min. compare to simplemining its big difference. any idea how can i improve the boot up time? maybe a 32gb faster usb sticks? |
|
|
|
|
|
fullzero (OP)
|
|
June 01, 2017, 04:35:20 AM |
|
going to buy a few of asus prime h270 plus 6x pcie slot + 2 x M.2 and will this mobo work? https://www.asus.com/Motherboards/PRIME-H270-PLUS/there is 2 m.2 slot as well can we run 8 GPU on this? Also i have one rig running nvOC on sandisk ultra usb 3 stick 16gb all seems running well, one issue i have is the boot takes almost 1 min. compare to simplemining its big difference. any idea how can i improve the boot up time? maybe a 32gb faster usb sticks? I won't have more m2 adapters until the weekend. I haven't tested any h270 mobos yet, not sure if they will be able to do 8 GPUs with adapters. If that is your intent: I would make sure you use at least G4560 cpus. I will order one of these tomorrow for testing. Boot time was never something I was considering; I'm not sure why you would need to reboot your rig at all. SmOS boots quickly because it is running in console mode (x is not loaded). If there is enough interest I can make a console image, but when you consider the frequency of needing to boot your rig, I think there are more useful improvements I can make first. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
bobers
Member
Offline
Activity: 73
Merit: 10
|
|
June 01, 2017, 06:20:06 AM |
|
Hi, can anyone help?
I have same 4 ASUS 1060 3GB, all OC, but one works slowly then others.
ETH: 05/31/17-02:41:36 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 78.055 Mh/s, Total Shares: 7, Rejected: 0, Time: 00:06
ETH: GPU0 17.358 Mh/s, GPU1 20.249 Mh/s, GPU2 20.263 Mh/s, GPU3 20.185 Mh/s
GPU0 t=47C fan=75%, GPU1 t=52C fan=75%, GPU2 t=51C fan=75%, GPU3 t=48C fan=75%
What are the complete specifications of your system, to include riser type? Have you tried swapping out the riser on that card? How are you powering your risers? I have old asrock 970 extreme4 with 4 ASUS 1060 3G. USB powered risers Blue 006C. In ZEC mining mode cards work with same hashrate, but ETH |
|
|
|
|
jcovercash
Newbie
Offline
Activity: 10
Merit: 0
|
|
June 01, 2017, 07:22:35 AM |
|
Could the b250 gaming 3 support a 5th card with the m.2 adapter? Or does this chipset not work like that.
|
|
|
|
|
rabbitr32
Newbie
Offline
Activity: 22
Merit: 0
|
|
June 01, 2017, 07:27:04 AM |
|
going to buy a few of asus prime h270 plus 6x pcie slot + 2 x M.2 and will this mobo work? https://www.asus.com/Motherboards/PRIME-H270-PLUS/there is 2 m.2 slot as well can we run 8 GPU on this? Also i have one rig running nvOC on sandisk ultra usb 3 stick 16gb all seems running well, one issue i have is the boot takes almost 1 min. compare to simplemining its big difference. any idea how can i improve the boot up time? maybe a 32gb faster usb sticks? I won't have more m2 adapters until the weekend. I haven't tested any h270 mobos yet, not sure if they will be able to do 8 GPUs with adapters. If that is your intent: I would make sure you use at least G4560 cpus. I will order one of these tomorrow for testing. Boot time was never something I was considering; I'm not sure why you would need to reboot your rig at all. SmOS boots quickly because it is running in console mode (x is not loaded). If there is enough interest I can make a console image, but when you consider the frequency of needing to boot your rig, I think there are more useful improvements I can make first. ok, will get G4560 on the h270 if it works i have many (40 1060 3GB) on its way. regarding reboot im not sure because i saw how SMos works id there is GPU freezes it send force reboot command to reboot the rig. i have experience some GPU freezes the whole ubuntu it did not reboot at all requires a hard reset. not a biggie anyway i have ppl monitoring the farm 15/24 a day. thx for your great effort puttin into all this nvOS. cant wait for ur update on the h270 boards, hopefully 8GPUs is possible. |
|
|
|
|
|
Maxximus007
|
|
June 01, 2017, 08:01:49 AM |
|
Thanks for answering! Installed openssh-server for now. Is running apt a good idea, to upgrade packages?
Will a MSI Z270-A Pro also be able to use the M.2?
Please consider a console version, would be very useful especially offsite. Chances are that a mixed AMD / GeForce image will be easier to create in a console version.
|
|
|
|
|
|
fullzero (OP)
|
|
June 01, 2017, 05:01:54 PM |
|
Hi, can anyone help?
I have same 4 ASUS 1060 3GB, all OC, but one works slowly then others.
ETH: 05/31/17-02:41:36 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 78.055 Mh/s, Total Shares: 7, Rejected: 0, Time: 00:06
ETH: GPU0 17.358 Mh/s, GPU1 20.249 Mh/s, GPU2 20.263 Mh/s, GPU3 20.185 Mh/s
GPU0 t=47C fan=75%, GPU1 t=52C fan=75%, GPU2 t=51C fan=75%, GPU3 t=48C fan=75%
What are the complete specifications of your system, to include riser type? Have you tried swapping out the riser on that card? How are you powering your risers? I have old asrock 970 extreme4 with 4 ASUS 1060 3G. USB powered risers Blue 006C. In ZEC mining mode cards work with same hashrate, but ETH That is strange; although ZEC is core intensive and ETH is memory intensive. It is possible that your GPU0 1060 has a different memory type (micron) which generally has lower performance, while the other cards do. It also could be due to a difference in pci bandwith on the slot that GPU0 is using. Are each of your cards risers power with their own cable from the PSU? If not, and GPU0 is sharing a cable with another GPU this may also be the problem. |
|
|
|
|
|
mnh_license@proton.me https://github.com/hartmanm How difficulty adjustment works: Every 2016 blocks, the Network adjusts the current difficulty to estimated difficulty in an attempt to keep the block generation time at 10 minutes or 600 seconds. Thus the Network re-targets the difficulty at a total difficulty time of: 2016 blocks * 10 minutes per block = 20160 minutes / 60 minutes = 336 hours / 24 hours = 14 days. When the Network hashrate is increasing; a difficulty ( 2016 blocks ) should take less than 14 days. How much less can be estimated by comparing the % Network hashrate growth + what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ) against what the Network hashrate was at the beginning of the difficulty ( 2016 blocks ). This is only an estimate because you cannot account for "luck"; but you can calculate reasonably well using explicitly delimited stochastic ranges. The easy way to think about this is to look at this graph and see how close to 0 the current data points are on its y axis. If the blue line is above 0 the difficulty ( 2016 ) blocks should take less than 14 days; if it is below it should take more. http://bitcoin.sipa.be/growth-10k.png
|
|
|
|
