Bitcoin Forum
November 18, 2024, 12:20:37 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 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 ... 416 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining  (Read 418244 times)
novice2017
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
June 15, 2017, 06:51:51 PM
 #761

Im using an MSI z170 A Gaming pro board. I updated the bios and set the 4g encoding to enable

When i try to boot the nvOC all i get is usb errors.

[  11.819307]  usb 2-6: device not accepting address 2, error -62

there are several lines listing all the usb ports.

at the very bottom of the error message after it lists all my usb ports is (initramfs)

What kind of risers are you using, and how are you powering them?

Hi fullzero,

I only have 2 1070 cards plugged in at the moment so no risers. Cards are in the correct slots according to mother board manual.

What kind of USB key are you using?

Have you tried reimaging the USB?

The usb is a sandisk 32 gb 130mb sec  http://www.bestbuy.com/site/sandisk-ultra-32gb-micro-usb-usb-3-0-flash-drive-black/3530864.p?skuId=3530864
The transfer rate was the same as the one u recommended, i wanted to try your image now not wait on amazon.

I am downloading the image again and i will re-image the USB when i get home. I do not know if something got corrupt or not.



First: did you unzip the image before using it to image the USB?



If you did:

No need to re-download to check the image:

open a cmd prompt:

click the start button and type:  

Code:
cmd

then press enter:

type the following:

Code:
CertUtil -hashfile PATH_TO_IMAGE_ZIP_HERE SHA256

and press enter

if the result is:

Code:
90465b0521590a9e850a84bb1edbc184bac24aba7d309b20adaf106e364b534e

then the ZIP_containing_the_image is good

for example on my windows install:

https://s4.postimg.org/9zva6zj3h/hash.jpg


Note: you can find the file path by right clicking the zip and selecting properties


ill check the hash.

Yes i used winrar and unzipped it to the desktop.

Then used HDDraw to burn to USB. After it was done i opened the image drag and dropped onebash file to look at it.
selected eject and removed it.

then made changes to the BIOs for 4g encoding,  plugged into rig and hit power on.

I just noticed you said you are using the: MSI z170 A Gaming pro

Is this the Motherboard you are using?

https://www.newegg.com/Product/Product.aspx?Item=N82E16813130919

If so;

I haven't tested this motherboard and I don't know what bios settings might be needed.

My guess is: you will need to disable the onboard Audio



I am using MSI Performance Gaming Intel Z170A Gaming Pro (the NON Carbon edition) lGA 1151 DDR4 USB 3.1 ATX Motherboard  

https://www.msi.com/Motherboard/Z170A-GAMING-PRO.html#hero-overview

It is similar to the MSI Gaming M5 you have already tested.

So i updated the bios to get the one that allows 4g decoding. I think it was the same one as the M5

I seen the audio disable on another post so i will also try that later when i get home.

I will try some more testing, i have 2 other boards that are also Z170A Gaming Pro, Ill try one of them also.
ill check boot from USB also to see if thats an option i missed
Dhx
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
June 15, 2017, 06:57:43 PM
 #762

Well that's just great. Just don't get why everything turns on and looks like its working and the display just wont connect.

Did you attempt reseating your RAM?  Not familiar with your motherboard but it should give you an indication if there is a memory issue.  On the ASUS z270 board there is a memok LED/Button for example.  CPU fan will still spin up as you describe but won't POST.
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 07:10:18 PM
 #763

Hello, fullzero!
Thank you for yours work, it's great.
But couldn't you explan me this case.
This is the log of running oneBush on my rig with 10 Nvidia GTX 1060 cards.

Quote
spawn sudo dos2unix /media/m1/1263-A96E/oneBash
[sudo] password for m1: spawn sudo ldconfig /usr/local/cuda/lib64
[sudo] password for m1: spawn sudo nvidia-smi -pl 125
[sudo] password for m1: spawn sudo nvidia-xconfig --cool-bits=24
[sudo] password for m1:
  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:0]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:0]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:1]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:1]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:2]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:2]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:3]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:3]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:4]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:4]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:5]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:5]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:6]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:6]) assigned value 1400.

  Attribute 'GPUGraphicsClockOffset' (N-003:0[gpu:7]) assigned value 100.
  Attribute 'GPUMemoryTransferRateOffset' (N-003:0[gpu:7]) assigned value 1400.










  Attribute 'GPUFanControlState' (N-003:0[gpu:0]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:1]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:2]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:3]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:4]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:5]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:6]) assigned value 0.
  Attribute 'GPUFanControlState' (N-003:0[gpu:7]) assigned value 0.


/home/m1/9.0/ethdcrminer64: /usr/local/cuda/lib64/libOpenCL.so.1: no version information available (required by /home/m1/9.0/ethdcrminer64)

пїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSH»
пїS      Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.0      пїS
пїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSпїSHj

ETH: 1 pool is specified
Main Ethereum pool is eth-eu2.nanopool.org:9999
PASC: 1 pool is specified
Main Pascal pool is pasc-eu2.nanopool.org:15555
AMD OpenCL platform not found

Driver 368.81 is recommended for best performance and compatibility
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools
CUDA initializing...

NVIDIA Cards available: 10
CUDA Driver Version/Runtime Version: 8.0/8.0
GPU #0: GeForce GTX 1060 6GB, 6071 MB available, 10 compute units, capability: 6.1

GPU #1: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #2: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #3: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #4: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #5: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #6: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #7: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #8: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1
GPU #9: GeForce GTX 1060 6GB, 6072 MB available, 10 compute units, capability: 6.1

Total cards: 10
ETH: Stratum - connecting to 'eth-eu2.nanopool.org' <198.251.88.21> port 9999
ETH: Stratum - Connected (eth-eu2.nanopool.org:9999)
DUAL MINING MODE ENABLED: ETHEREUM+PASCAL
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333

 PASC: Stratum - connecting to 'pasc-eu2.nanopool.org' <185.71.66.39> port 15555
 PASC: Stratum - Connected (pasc-eu2.nanopool.org:15555)
ETH: Authorized
Setting DAG epoch #129...
 PASC: Authorized
 PASC: 06/15/17-13:54:05 - New job from pasc-eu2.nanopool.org:15555
Setting DAG epoch #129 for GPU #1
Create GPU buffer for GPU #1
Setting DAG epoch #129 for GPU #8
Create GPU buffer for GPU #8
Setting DAG epoch #129 for GPU #2
Create GPU buffer for GPU #2
Setting DAG epoch #129 for GPU #4
Create GPU buffer for GPU #4
Setting DAG epoch #129 for GPU #3
Create GPU buffer for GPU #3
Setting DAG epoch #129 for GPU #5
Create GPU buffer for GPU #5
Setting DAG epoch #129 for GPU #7
Create GPU buffer for GPU #7
Setting DAG epoch #129 for GPU #9
Create GPU buffer for GPU #9
Setting DAG epoch #129 for GPU #6
Create GPU buffer for GPU #6
Setting DAG epoch #129 for GPU #0
Create GPU buffer for GPU #0
 PASC: 06/15/17-13:54:09 - New job from pasc-eu2.nanopool.org:15555
 PASC: 06/15/17-13:54:13 - New job from pasc-eu2.nanopool.org:15555
GPU 6 DAG creation time - 7137 ms
Setting DAG epoch #129 for GPU #6 done
GPU 7 DAG creation time - 7180 ms
Setting DAG epoch #129 for GPU #7 done
GPU 1 DAG creation time - 7184 ms
Setting DAG epoch #129 for GPU #1 done
GPU 0 DAG creation time - 7208 ms
Setting DAG epoch #129 for GPU #0 done
GPU 5 DAG creation time - 7149 ms
Setting DAG epoch #129 for GPU #5 done
GPU 2 DAG creation time - 7172 ms
Setting DAG epoch #129 for GPU #2 done
GPU 3 DAG creation time - 7160 ms
Setting DAG epoch #129 for GPU #3 done
GPU 4 DAG creation time - 7176 ms
Setting DAG epoch #129 for GPU #4 done
GPU 9 DAG creation time - 8440 ms
Setting DAG epoch #129 for GPU #9 done
GPU 8 DAG creation time - 8473 ms
Setting DAG epoch #129 for GPU #8 done

As you can see - there is not info about applying OC settings for gpu:8 and gpu:9.
In really work GPUs from #0 to #7 show about 21mh/s (eth) but GPUs from #8 to #9 show about 18mh/s.

It's looks like cool-bits is not settings for GPUs from #8 to #9.

In NVIDIA console I see section "Editable performance levels" for GPUs from #0 to #7, but don't for GPUs from #8 to #9.
I trying Supermicro X10SRL-F and ASUS PRIME Z270-P motherboards. But is't the same problem. OC settings not applying for 2 cards of 10.

Why?..

open the guake terminal: f12

and enter the cmd:

Code:
lspci | grep VGA

and post what it outputs

With that information I can ensure the next version of nvOC will fully support OC on all 10x GPUs.

The indexing of the GPUs must be in a way that I did not predict when making v0015.

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)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 07:12:20 PM
 #764

If I have corrupted DAG file, how can I delete it? Can't find it in the normal place.

The DAG is built on the GPUs with Claymore.  

I would reboot if you have a message from Claymore about a corrupted DAG file. ( I am not familiar with such an error message ).

Apparently the DAG file is stored here: ~/.ethash, but I cant seem to 'cd' there to delete it. The message was from dwarfpool, not Claymore.

My first guess is that; you're mining a different Ethash coin than the one expected with dwarfpool: ie ETC on an ETH pool or ETH on a EXP pool. 

If this is correct; it is most likely due to using the wrong port for the coin of your choice.

Everything was working 100% then randomly started giving this problem

I would try another pool and see if it's just dwarfpool.  Nanopool is easy to try without an account.

Nanopool not picking it up either.

On their FAQ:

My hashrate on pool drops to zero and no more shares accepted, although miner is working as usual.
Most probably, DAG files on your miner were corrupted and it computes invalid shares. Try to stop the miner, delete DAG files and start the miner again.
DAG files location: %USERPROFILE%/AppData/Local/Ethash

Something is not right somewhere; pm me your oneBash and I will try to find 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
gustavdp
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
June 15, 2017, 07:13:47 PM
 #765


The indexing of the GPUs must be in a way that I did not predict when making v0015.

What I saw with my 5 card setup on an ASUS 270P was that it only picked up 4 cards when a card was plugged into the slot above the mail PCI Express slot. When I moved the card to another one everything was working 100%

I just reformatted my drive and set up the bash file again. Lets hope it fixes the DAG issue.
yslyung
Legendary
*
Offline Offline

Activity: 1500
Merit: 1002


Mine Mine Mine


View Profile
June 15, 2017, 07:18:42 PM
 #766

i see only 5 out of 6 1080 ti's using nvoc . . .

wrote onebash using hddraw , all works normal, plugged into mobo boots up after abt 4 mins, starts automatically, it sees 5 out of 6 gpus then hangs. tried couple of times even at default or lower clocks on both core & memory.

4 x msi gaming  2 x aorus 1080ti

mobo tb 85

on another rig, running 6 x gaming x ti on win 10 runs fine no problems. same cpu, same ram on the mobo, same psu & risers.

TIA for some tips & help.
voltsifer
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
June 15, 2017, 07:25:09 PM
Last edit: June 15, 2017, 07:36:10 PM by voltsifer
 #767

fullzero, thank you for attention for my case.

lspci | grep VGA for SuperMicro
Code:
root@m1-desktop:/home/m1# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
10:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
14:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

As I understand,
14:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)
is an CPU-based VGA.

lspci | grep VGA for ASUS PRIME Z270-P (the same problem - 2 out of 8 GPU is not overclocking)
Code:
m1@N-005:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
UberDaemon
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
June 15, 2017, 07:27:43 PM
 #768

Is anyone using EVGA 1070 FTW edition GPUs?  Is there no getting around needing TWO pcie connectors per card?  This is aggravating... I wish I'd realized this before I bought them.  Might have to end up returning these to Newegg.

I don't see why these jerks require 2 connectors when my Founders Ed cards work just fine on a single one, and they have the same exact chip inside.  Ugh.
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 08:18:43 PM
 #769

i see only 5 out of 6 1080 ti's using nvoc . . .

wrote onebash using hddraw , all works normal, plugged into mobo boots up after abt 4 mins, starts automatically, it sees 5 out of 6 gpus then hangs. tried couple of times even at default or lower clocks on both core & memory.

4 x msi gaming  2 x aorus 1080ti

mobo tb 85

on another rig, running 6 x gaming x ti on win 10 runs fine no problems. same cpu, same ram on the mobo, same psu & risers.

TIA for some tips & help.

I have several tb85 rigs; all are working with 6x OC without issue.

Since both systems are nearly identical; if you try booting the w10 ssd with the 4 x msi gaming  2 x aorus 1080ti rig it will tell us if the problem is with hardware or software.

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)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 08:20:56 PM
 #770

fullzero, thank you for attention for my case.

lspci | grep VGA for SuperMicro
Code:
root@m1-desktop:/home/m1# lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
06:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
09:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0a:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
10:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
14:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)

As I understand,
14:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30)
is an CPU-based VGA.

lspci | grep VGA for ASUS PRIME Z270-P (the same problem - 2 out of 8 GPU is not overclocking)
Code:
m1@N-005:~$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
07:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
08:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0b:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0c:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c03 (rev a1)

Noted the indexing, first time ive seen 14:00.0.

Are you using a pcie splitter with the ASUS PRIME Z270-P ?

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
voltsifer
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
June 15, 2017, 08:25:28 PM
 #771

Noted the indexing, first time ive seen 14:00.0.

Are you using a pcie splitter with the ASUS PRIME Z270-P ?

ASUS PRIME Z270-P has 6xPCIe slots. So I use 2 x PCIe -> 2 PCIe splitters.

SuperMicro X10SRL-F has 7xPCIe slots. So I use 3 x PCIe -> 2 PCIe splitters.
fullzero (OP)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 08:27:58 PM
 #772

Is anyone using EVGA 1070 FTW edition GPUs?  Is there no getting around needing TWO pcie connectors per card?  This is aggravating... I wish I'd realized this before I bought them.  Might have to end up returning these to Newegg.

I don't see why these jerks require 2 connectors when my Founders Ed cards work just fine on a single one, and they have the same exact chip inside.  Ugh.

You can use a splitter:

https://www.amazon.com/11-inch-PCI-Express-Female-Splitter-Sleeves/dp/B01LVZBJML


or

https://www.amazon.com/Phobya-PCI-E-Splitter-Cable-Sleeving/dp/B00A5TA7NG


or any similar female 8pin pcie to 2x Male 8pin pcie.

Also if your feeling adventurous: I haven't tried this; and it may not work

(so I would test with just one GPU first if you do: also I claim no responsibility for potentially GPU damaging adventurous tests such as this)

attach only one 8pin and most likely it will be fine. 

These cards have a upper powerlimit that will burn a single 8 pin FYI; but if your mining ETH with a lower than TDP powerlimit it should be ok. 

I am assuming that both pcie ports on the card are connected with a single rail in the card. 

If I am incorrect with this assumption, you could damage the card.


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)
Hero Member
*****
Offline Offline

Activity: 882
Merit: 1009



View Profile
June 15, 2017, 08:32:37 PM
 #773

Noted the indexing, first time ive seen 14:00.0.

Are you using a pcie splitter with the ASUS PRIME Z270-P ?

ASUS PRIME Z270-P has 6xPCIe slots. So I use 2 x PCIe -> 2 PCIe splitters.

SuperMicro X10SRL-F has 7xPCIe slots. So I use 3 x PCIe -> 2 PCIe splitters.

I thought so; what ports are the splitters attached to; both on the mobos and on the splitter boards themselves.

I want to try to predict all possible indexes when a splitter is used in any port.

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
voltsifer
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
June 15, 2017, 08:38:39 PM
 #774

ASUS PRIME Z270-P has 6xPCIe slots. So I use 2 x PCIe -> 2 PCIe splitters.

SuperMicro X10SRL-F has 7xPCIe slots. So I use 3 x PCIe -> 2 PCIe splitters.

I thought so; what ports are the splitters attached to; both on the mobos and on the splitter boards themselves.

I want to try to predict all possible indexes when a splitter is used in any port.
I've already tried to change PCIe indexes in /etc/X11/xorg.conf (Section "Device") in accordance with to lspci, but did not see any changes.
Maybe I did something not right...  Huh
ijduncan
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
June 15, 2017, 08:50:55 PM
 #775

So I was trying to run 7 Zotac 1070 Minis with Asus Z270F using Z270A image, the most it could detect is 6 Zotacs. Someone here said that Z270F runs 7 GPUs out of the box, but not in my case. I need to try windows to verify that. Do you have Z270F and planning to post an image? Running 6 Zotacs with TB85 for now, but Minis are so tiny that 8 could fit in Rosewill easily.

Thanks.

I just got one of these mobos in yesterday.  I can get 7x cards to be detected by the system, but there is a conflict with x and the driver.  I can manually OC the first 6 cards, but the 7th has no response to OC commands.  

There is also what appears to be a TPM / Secureboot problem preventing subsequent boots into the same install.  Initially changing the bios setting for enabling above 4gb encoding is required to get 7 cards to work.  There are also some TPM / Secureboot bios changes that are needed, but I still need to isolate which.  I started with the MSI z270-A PRO image.

I will work on this more tonight.



First of all this is an awesome project. Thanks for doing this.  I will mine to your wallets or something to give monetary thanks.

Did you ever get any further on this Z270F mobo.  I can only see 6 cards. I would love to get 9 going.

cheers ever so much.

With v0015 you can use 7x GPUs with that mobo; 9x if you have 2x m2 adapters.

Edit: ensure that you make the bios changes listed for that mobo on the OP.

I followed those instructions and I am using v0015. 

Obviously it works then but I must be missing something.

It might be a hardware problem: what kind of risers are you using, and how are they powered?

What GPUs, and PSU?

7 x https://www.amazon.com/gp/product/B01N3UVJHM/ref=oh_aui_detailpage_o04_s01?ie=UTF8&psc=1
7 x https://www.neweggbusiness.com/product/product.aspx?item=9b-14-487-261
2 x https://www.neweggbusiness.com/product/product.aspx?item=9b-17-438-092
1 x https://www.neweggbusiness.com/product/product.aspx?item=9b-19-117-745
1 x https://www.neweggbusiness.com/product/product.aspx?item=9b-20-156-103

I dont have the m2 adapters yet.

only 6 cards show up in the bios which supports a hardware issue.  I have another mobo which i can test.  I tried a different riser

I have 4GPUs on one PSU and 7 on the other plus Mobo

Sometimes the gpu that isn't working; isn't the one you expect it to be. 

To ensure you know which one isn't working; mine for a little while, at least 10 mins. 

Feel the heatsink of each GPU until you find the one that isn't hot. 

Power down the rig, turn off the PSU.

Either remove that GPU and test it on another motherboard;

or remove all the other GPUs and try booting with just the problem GPU directly in the primary slot in the mobo.

This should tell you if that GPU is INOP or not.

Let me know what the result is. 

Going to sleep now.

Ok some more information.

Def not an issue with GPU.

I have an m2 adapter now and I can get 7 cards going. (6 pci + 1 M2)

The issue is the pcie slots.  If any 6 are occupied then 6 work.  If i try a 7th in any spot it does not show up.  The tool in the bios only shows 6 cards, even when 7 are active with the addition of the m.2. Maybe they never expected 9 cards so its just not showing up in the tool.

I have a second build up to test 8 x 1070 gpus and a couple of 1kw power supplies. I will see if I have a different experience and let you know.

I have had a lot of graphical issues with this build. 

I have a previous build on the Prime z270A with 7 cards and it has no issues. 

Thanks for all your help.  How best to show appreciation?
philipma1957
Legendary
*
Offline Offline

Activity: 4312
Merit: 8871


'The right to privacy matters'


View Profile WWW
June 15, 2017, 09:09:02 PM
 #776

I got this to work but I am mining for op with the stick

fine with sending some hash to him.

I need help to set my settings in.

I use ewbf_ 3.4b to mine at nice hash

Whatcha need help with Phil?

okay I figured out settings and I am at nicehash.

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

noVCphiltest1

have 2 questions now

 1 ) how to I upgrade to ewbf_ 3.4b

 2) looking to set  power lower  I have -pl at 100  so -pl 90 should drop power?


All you have to do is install ewbf to the same location as the one he has now and it'll pick it up and run it
Yes it will drop the power of all cards if you set it for all
What I would do is download it. Extract it to the desktop then copy and paste it into the same folder and name it the same then onebash will run it all the same also make a copy of the original file to be safe

I found the zec folder so I think  I can upgrade from 3.3 to 3.4

 I do not seem to be setting the power limits correctly -pl  100 ,90, 80, 70, 65  and I pull 150 watts per card

Are you going close to the bottom of the bash file to set the power limit?
You don't have to do it in the command line for the zec miner it'll be its own section for power limit settings

Phil,

if you haven't updated EWBF yet see:  https://bitcointalk.org/index.php?topic=1854250.msg19579963#msg19579963

with powerlimits:

if using the same powerlimit for each card set:

Code:
POWERLIMIT="YES"
         

and in this block of code:

Code:
if [ $POWERLIMIT == "YES" ]
then
sleep 6
#change powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6
fi

find the line:
Code:
expect -c 'spawn sudo nvidia-smi -pl 125

and replace 125 with the desired powerlimit in watts


if using the individual powerlimits for each card set:

Code:
INDIVIDUAL_POWERLIMIT="YES"
      

and in this block of code:

Code:
if [ $INDIVIDUAL_POWERLIMIT == "YES" ]
then
sleep 6
#change GPU 0 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 0 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 1 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 1 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 2 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 2 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 3 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 3 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 4 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 4 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 5 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 5 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

#change GPU 6 powerlimit by changing the number after -pl to the desired wattage
expect -c 'spawn sudo nvidia-smi -i 6 -pl 125
expect "*password*:"
send "miner1\r" '
sleep 6

........

change each line:

expect -c 'spawn sudo nvidia-smi -i 0 -pl 125  ( this is for GPU 0 )

expect -c 'spawn sudo nvidia-smi -i 1 -pl 125  ( this is for GPU 1 )

expect -c 'spawn sudo nvidia-smi -i 2 -pl 125

expect -c 'spawn sudo nvidia-smi -i 3 -pl 125

expect -c 'spawn sudo nvidia-smi -i 4 -pl 125

expect -c 'spawn sudo nvidia-smi -i 5 -pl 125  ( this is for GPU 5 )

to the desired powerlimit.

Note: the indexing of the GPUs might be different than you expect.

If you open the guake terminal; press f12

and enter:
Code:
nvidia-smi

It should list your cards in the correct order.



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

▄▄███████▄▄
▄██████████████▄
▄██████████████████▄
▄████▀▀▀▀███▀▀▀▀█████▄
▄█████████████▄█▀████▄
███████████▄███████████
██████████▄█▀███████████
██████████▀████████████
▀█████▄█▀█████████████▀
▀████▄▄▄▄███▄▄▄▄████▀
▀██████████████████▀
▀███████████████▀
▀▀███████▀▀
.
 MΞTAWIN  THE FIRST WEB3 CASINO   
.
.. PLAY NOW ..
jmooney5115
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
June 15, 2017, 09:46:57 PM
 #777

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

That's some good hash power. I see there are many workers in your NiceHash.com link. How many rigs are you running and what cards? I've got a 4 card 1070 rig I'm ordering 2 more GPUs right now.
jmooney5115
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
June 15, 2017, 09:48:12 PM
 #778

Do you suspect this mobo will work? GIGABYTE GA-Z270XP-SLI

It looks like it has all the same chipset/RAM/CPU as the GIGABYTE GA-Z270P-D3 listed in OP. I say it will work but I'm new to this.
UberDaemon
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
June 15, 2017, 09:58:13 PM
 #779

Is anyone using EVGA 1070 FTW edition GPUs?  Is there no getting around needing TWO pcie connectors per card?  This is aggravating... I wish I'd realized this before I bought them.  Might have to end up returning these to Newegg.

I don't see why these jerks require 2 connectors when my Founders Ed cards work just fine on a single one, and they have the same exact chip inside.  Ugh.

You can use a splitter:

https://www.amazon.com/11-inch-PCI-Express-Female-Splitter-Sleeves/dp/B01LVZBJML


or

https://www.amazon.com/Phobya-PCI-E-Splitter-Cable-Sleeving/dp/B00A5TA7NG


or any similar female 8pin pcie to 2x Male 8pin pcie.

Also if your feeling adventurous: I haven't tried this; and it may not work

(so I would test with just one GPU first if you do: also I claim no responsibility for potentially GPU damaging adventurous tests such as this)

attach only one 8pin and most likely it will be fine.  

These cards have a upper powerlimit that will burn a single 8 pin FYI; but if your mining ETH with a lower than TDP powerlimit it should be ok.  

I am assuming that both pcie ports on the card are connected with a single rail in the card.  

If I am incorrect with this assumption, you could damage the card.



Thanks for the response, OP.

I did try using a single 8 pin per EVGA 1070 FTW card, but video BIOS gives the connect PCIE connector then restart error message during POST.  They're pretty insistent about both ports being filled apparently.

I'll go with the splitters.  All of my PCIE cables are either Corsair originals or individually-sleeved cables from Corsair.com, so I think they should be able to handle the load, and I don't see going over 125W per card anyway.  For now I dusted off my Add2PSU and connected a 2nd Corsair PSU (thankfully I over-ordered and have (2) HX1200i and a HX1000i) so that I could get this rig up and running on 4 GPUs.  I've got 2 more GPUs coming tomorrow but will need to order splitters before I can get those online.

Preliminary OCing results are that my cc200/mc1600 settings from the 1070 Founders Ed caused a hard lockup of Ubuntu after about 120s of mining.  I dropped down to the cc100/mc600 settings listed in your OP for 1070 FTW and they've been mining away for about an hour at ~28.3 MH/sec per card.  I'll try pushing that a bit this evening to see if I can get anymore out of them.  After getting the Founders Ed cards up to 31+ I have my expectations set high, LOL.

https://i.imgur.com/vebi74I.png
achalmersman
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
June 15, 2017, 10:13:46 PM
 #780

Hi!  New member / user / and miner.  Thank you for all the work put into this project.  I am trying to use an ASUS Prime Z270-P mobo.  I downloaded the image off the OP and have my miner up and running but my cards are not overclocking or manual fan control.  I get an error for each card regarding fan control (I specified 90%).  Is this mobo not supported or am I doing something wrong?  I specified 600 mem overclock.  I am currently using 2 GTX1070 and 1 GTX 970 in this rig.  All 3 are running at stock speeds like they do in Windows.  Any help is greatly appreciated.  

PS.  I could not find the 2nd and 3rd items mentioned for the BIOS changes you have talked about for the PRIME Z270-A.  Is this the reason?  Any help greatly appreciated.  

Is your monitor connected to the motherboard?

Did you at anytime boot with only one GPU attached?

If either of these is the case: ensure the monitor is attached to the primary GPU ( the one connected to the 16x slot closest to the CPU )

then follow this process:

https://bitcointalk.org/index.php?topic=1854250.msg19449945#msg19449945



Thank you this worked.  The fans are definitely working now and the overclock seems to have stuck but I am not getting the hash rate I would expect for the mem clock speed when compared to same card in Windows 10 using claymore 9.5.  I notice my card is not at full power and is staying in P2 state in the NVIDIA-SMI window.  Is this normal?  Huge thanks for the help!
Pages: « 1 2 3 4 5 6 7 8 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 ... 416 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!