Bitcoin Forum
November 18, 2017, 09:09:26 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 ... 284 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4  (Read 322252 times)
citronick
Hero Member
*****
Offline Offline

Activity: 798


winter*juvia


View Profile
July 06, 2017, 03:34:34 PM
 #1581

Working on a video to get this set up with 6 1070 Asus Dual OC and the Z270 prime motherboard, hope it will help new users.

I did have one question, would it be possible to add DBIX in the next update? Also, I am running 12 1070's, and have been mining ZCash since, it seems like that was optimized with this miner and gtx cards in general. (maybe I am wrong?) What are people mining with their 1070's? is Zcash still the best or does mining NICE with the profit switcher make more sense?

imho

1060, 1070 = ETH

1080ti = ZEC

Citronick's Beer & Chicken Wings Fund : 32oo5tk1RfTbndrUjWvHJ9yT3bb2EyQYkq
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
Coinlancer is Disrupting the Freelance marketplace!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
1510996166
Hero Member
*
Offline Offline

Posts: 1510996166

View Profile Personal Message (Offline)

Ignore
1510996166
Reply with quote  #2

1510996166
Report to moderator
achalmersman
Newbie
*
Offline Offline

Activity: 16


View Profile
July 06, 2017, 04:33:42 PM
 #1582

Is anybody else experiencing nvOC hang / lockup to the point of needing a hard powerdown when Genoil crashes?  I can log in but when I try to close the miner and shutdown the OS becomes locked up. I am wondering if it is hardware related?  I am only using 4GB of ddr4 is that enough???  I believe I will be going back to Claymore.  I can't seem to get Genoil stable even dialed 300mc back from Claymore.  I will reimage a USB stick and go back to Claymore to see if stability comes back. 
cvitanihc0011
Jr. Member
*
Offline Offline

Activity: 35


View Profile
July 06, 2017, 04:47:43 PM
 #1583

Working on a video to get this set up with 6 1070 Asus Dual OC and the Z270 prime motherboard, hope it will help new users.

I did have one question, would it be possible to add DBIX in the next update? Also, I am running 12 1070's, and have been mining ZCash since, it seems like that was optimized with this miner and gtx cards in general. (maybe I am wrong?) What are people mining with their 1070's? is Zcash still the best or does mining NICE with the profit switcher make more sense?

DBIX - runs fine on Win on Claymore...I just edited address .. pool and some paramers .
For nvOC I've done the same thing but I get :
Quote
ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Pool link  : http://dbix.pool.sexy/#/help
Every rig is so stable ... too bad I suck at linux ! Time to learn
Grat job man !  Grin
fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 06:50:26 PM
 #1584


OverEasy has been testing MUSIC with genoil.

If you swap out the MUSIC block in oneBash with:

Code:
if [ $COIN == "MUSIC" ]
then

if [ $GENOILorCLAYMORE == "GENOIL" ]
then
HCD='/home/m1/eth/Genoil-U/ethminer'

MUSICADDR="$MUSIC_ADDRESS"
until $HCD --farm-recheck 200 -SP 1 -S $MUSIC_POOL -O $MUSICADDR:x -U
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done
fi

if [ $GENOILorCLAYMORE == "CLAYMORE" ]
then
if [ $CLAYMORE_VERSION == "9_5" ]
then
HCD='/home/m1/eth/9_5/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "9_4" ]
then
HCD='/home/m1/eth/9_4/ethdcrminer64'
fi

if [ $CLAYMORE_VERSION == "8_0" ]
then
HCD='/home/m1/eth/8_0/ethdcrminer64'
fi

MUSICADDR="$MUSIC_ADDRESS/$MUSIC_WORKER"
until $HCD -epool $MUSIC_POOL -ewal $MUSICADDR -epsw x -mode 1 -allpools 1 -dbg -1 $MUSIC_EXTENTION_ARGUMENTS
   do
   echo "FAILURE; reinit in 5" >&2
   sleep 5
done
fi
fi

You should be able to mine MUSIC with Genoil.

I will add this change to the next oneBash.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:00:27 PM
 #1585

Heya man, awesome project but have two problems.

1) Have 6 rigs with 5 GPU on each ASUS 1060, and they work well with v0017.

Trying to make another rig with 3x ASUS 1070 dual OC but getting the following error in dmesg, it randomly sees and unsees a GPU - sometimes two GPU after reboot. If I start mining, the load jumps to 10-15 / 5sec and the system goes to unresponsive state. Tried replacing risers, no luck.

Rig with 3x 1070 is running exactly same hardware specs as any other 1060 that works great.
- Gigabyte Z270X Gaming K3
- 4GB RAM
- G4400 CPU

Code:
[   11.554804] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554855] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554883] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554907] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554932] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554955] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   11.554979] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901585] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901630] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901656] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901681] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901705] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901728] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   12.901751] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   81.820739] NVRM: RmInitAdapter failed! (0x24:0x65:1060)
[   81.825027] NVRM: rm_init_adapter failed for device bearing minor number 2
[   98.031090] alx 0000:06:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [1c:1b:0d:91:b4:91]
[   98.036072] alx 0000:06:00.0 enp6s0: renamed from eth0
[   98.055932] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[   98.056746] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[   98.057522] alx 0000:06:00.0 enp6s0: NIC Up: 100 Mbps Full
[   98.057743] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
[   99.017089] nvidia-modeset: Allocated GPU:0 (GPU-dc2aec1a-94de-a009-4336-d4a879e5da36) @ PCI:0000:01:00.0
[   99.747611] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747654] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747681] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747705] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747729] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747752] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.747776] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.374992] nvidia-modeset: Allocated GPU:1 (GPU-6d1a8ede-d79a-6ad6-a2a5-f1d449b6b5dd) @ PCI:0000:07:00.0
[  100.554810] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554854] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554881] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554905] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554929] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554952] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.554976] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  100.959944] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  100.959980] NVRM: rm_init_adapter failed for device bearing minor number 2
[  102.860179] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  102.860181] Bluetooth: BNEP filters: protocol multicast
[  102.860184] Bluetooth: BNEP socket layer initialized
[  109.907211] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908095] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908142] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908170] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.908194] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.909014] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  109.909053] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  110.326085] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  110.326118] NVRM: rm_init_adapter failed for device bearing minor number 2
[  180.997458] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997504] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997531] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997556] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997579] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997603] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  180.997627] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.400594] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  181.400629] NVRM: rm_init_adapter failed for device bearing minor number 2
[  181.413439] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413485] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413513] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413538] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413562] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413586] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.413609] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  181.816764] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  181.817572] NVRM: rm_init_adapter failed for device bearing minor number 2
[  182.084881] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084928] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084956] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.084981] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085004] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085028] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.085051] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.505188] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  182.505231] NVRM: rm_init_adapter failed for device bearing minor number 2
[  182.713761] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713807] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713835] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713860] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713884] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713908] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  182.713932] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  183.124177] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  183.124217] NVRM: rm_init_adapter failed for device bearing minor number 2
[  184.089772] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089820] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089848] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089873] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089898] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089922] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.089946] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.527141] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  184.527174] NVRM: rm_init_adapter failed for device bearing minor number 2
[  184.888148] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888196] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888223] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888248] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888272] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888295] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  184.888319] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.303152] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  185.303187] NVRM: rm_init_adapter failed for device bearing minor number 2
[  185.776271] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776316] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776343] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776368] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776392] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776416] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  185.776440] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.190421] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  186.193080] NVRM: rm_init_adapter failed for device bearing minor number 2
[  186.363417] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363462] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363488] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363513] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363536] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363559] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.363583] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.766576] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  186.766616] NVRM: rm_init_adapter failed for device bearing minor number 2
[  186.880321] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880366] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880393] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880418] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880441] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880465] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  186.880488] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.288080] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  187.288120] NVRM: rm_init_adapter failed for device bearing minor number 2
[  187.390639] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390683] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390710] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390734] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390757] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390781] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.390804] ACPI Warning: \_SB_.PCI0.RP07.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[  187.794130] NVRM: RmInitAdapter failed! (0x25:0x40:1075)
[  187.794240] NVRM: rm_init_adapter failed for device bearing minor number 2
root@rig7:/home/m1# dmesg | less
root@rig7:/home/m1# uname -a
Linux rig7 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
root@rig7:/home/m1# nvidia-smi
Wed Jul  5 17:19:42 2017      
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13                 Driver Version: 378.13                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 0000:01:00.0      On |                  N/A |
|  0%   48C    P8     7W / 151W |    142MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 0000:07:00.0     Off |                  N/A |
|  0%   44C    P8     7W / 151W |      1MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                              
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1232    G   /usr/lib/xorg/Xorg                             117MiB |
|    0      1704    G   compiz                                          22MiB |
+-----------------------------------------------------------------------------+

Code:
root@rig7:/home/m1# nvidia-smi
Wed Jul  5 17:55:47 2017      
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 378.13                 Driver Version: 378.13                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 0000:01:00.0      On |                  N/A |
| 32%   49C    P2    35W / 151W |    219MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 0000:07:00.0     Off |                  N/A |
|ERR!   49C    P8    N/A /  N/A |    106MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
                                                                              
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1232    G   /usr/lib/xorg/Xorg                             105MiB |
|    0      1704    G   compiz                                           6MiB |
|    0      3166    C   /home/m1/SPccminer/ccminer                      95MiB |
|    1      3166    C   /home/m1/SPccminer/ccminer                      95MiB |
+-----------------------------------------------------------------------------+
WARNING: infoROM is corrupted at gpu 0000:07:00.0


2) Another problem is that on none of my rigs can't run custom fan speed and get the following error:

Code:
ERROR: Error assigning value 75 to attribute 'GPUTargetFanSpeed' (rig1:0[fan:0]) as specified in assignment '[fan:0]/GPUTargetFanSpeed=75' (Unknown Error).

Tried making changes in /etc/X11/xorg.conf but no luck, the devices (GPUs) are already there.
Thanks

This line means there is a problem with the bios (rom) on one of the GPUs:
Code:
WARNING: infoROM is corrupted at gpu 0000:07:00.0

I would return this GPU or RMA it.

You could try re flashing its rom with NVFlash; but if this doesn't work it will most likely void your warranty; so if the GPUs are new I would go the other route.

For fan speed, try setting:

Code:
SLOW_USB_KEY_MODE="YES"

let me know if that works.

Also what kind of USB / SSD are you using?

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:02:51 PM
 #1586

What with drivers under nvOC? Do we should use latest (newest) drivers? there is no problem in nvOC update, change, remove drivers? (in windows sometimes it is pain Sad )

BR and good job

v0017 uses the second to newest driver currently:

to Update the driver:

Click Ubuntu button on top left and type:

Code:
u

Click on software updater

Install updates

Click Ubuntu button on top left and type:

Code:
ad

Click on additional drivers

Select 381.22 driver

Click apply changes

Enter password and wait for it to finish applying changes

Reboot





Any hash difference on the new drivers ?

I haven't noticed a hash difference; but they do seem more stable with 1080tis.  Might be able to OC more with stability; haven't done enough testing yet.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:06:48 PM
 #1587

I still get an error when trying to mine lbry with a maxwell card (980ti). Is this something that will be supported in the future?

I would have to recompile ccminer for maxwell; specifically 980ti.

If I make a maxwell build later, I will compile each ccminer fork for maxwell with 980ti / 970s optimizations. 

Making a Maxwell build is at the bottom of my list; as there are already other mining OSes that support Maxwell well.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:28:40 PM
 #1588

Is anybody else experiencing nvOC hang / lockup to the point of needing a hard powerdown when Genoil crashes?  I can log in but when I try to close the miner and shutdown the OS becomes locked up. I am wondering if it is hardware related?  I am only using 4GB of ddr4 is that enough???  I believe I will be going back to Claymore.  I can't seem to get Genoil stable even dialed 300mc back from Claymore.  I will reimage a USB stick and go back to Claymore to see if stability comes back. 

Having more ram would probably help; I use 8gb on most of my rigs and I have achieved multi day stability with the ones that are using genoil by previously lowing the clocks / adjusting the powerlimits whenever a soft crash occurred.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:41:45 PM
 #1589

Working on a video to get this set up with 6 1070 Asus Dual OC and the Z270 prime motherboard, hope it will help new users.

I did have one question, would it be possible to add DBIX in the next update? Also, I am running 12 1070's, and have been mining ZCash since, it seems like that was optimized with this miner and gtx cards in general. (maybe I am wrong?) What are people mining with their 1070's? is Zcash still the best or does mining NICE with the profit switcher make more sense?

imho

1060, 1070 = ETH

1080ti = ZEC

IMO if you are coin dumping:

SALFTER_NICEHASH_PROFIT_SWITCHER is probably the best choice.

If you don't need to exchange mined coins right away and are willing to wait for OPT times: then I would select a set of Coins that you think will increase in value overtime.

Mine whichever one currently has the lowest difficulty.  I will probably implement this using SALFTERs implementation as a basis later.  IMO this is the OPT strategy long term.  Of course its success is highly dependent upon picking the right set of coins.   Wink


fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:44:52 PM
 #1590

Working on a video to get this set up with 6 1070 Asus Dual OC and the Z270 prime motherboard, hope it will help new users.

I did have one question, would it be possible to add DBIX in the next update? Also, I am running 12 1070's, and have been mining ZCash since, it seems like that was optimized with this miner and gtx cards in general. (maybe I am wrong?) What are people mining with their 1070's? is Zcash still the best or does mining NICE with the profit switcher make more sense?

DBIX - runs fine on Win on Claymore...I just edited address .. pool and some paramers .
For nvOC I've done the same thing but I get :
Quote
ETH: Authorization failed
: {"id":2,"jsonrpc":"2.0","result":null,"error":{"code":-1,"message":"Invalidlogin"}}
Stratum - reading socket failed, disconnect
ETH: Job timeout, disconnect, retry in 20 sec...

Pool link  : http://dbix.pool.sexy/#/help
Every rig is so stable ... too bad I suck at linux ! Time to learn
Grat job man !  Grin

I have added this to the list.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:46:50 PM
 #1591

Hi, newbie miner here!

Just wanted to register and say THANK YOU so much for making this, works brilliant on my PC (dual 980 ti's), and I love that I can run this from a USB drive.
Currently mining ETH with my 980ti's, and XMR with my CPU.
Not really skilled in Linux but my performance was so low in Win10, and this guide was pretty easy to follow , and performance is great IMO.
Any chance for Litecoin support?

Keep up the good work!

Glad you like nvOC.  Smiley

LTC went ASIC a long time ago: 2013.  Look at Bitmain L3 / L3+ for mining LTC.


fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 07:50:43 PM
 #1592

So new build, similar problem to the first rig I built myself. Getting the never ending "bootloop" when I fire up my mobo with everything plugged in. I know everyone says to unplug everything and try it one part at a time, which i will indeed do, but I was wondering if anyone else had this issue and found a more uniform way to fix it? Last time it was because my RAM was loose. This time my connections are all secure.

Background: building a trio rig with 2 1080ti and a 1080 mini using a 270 mobo with 850w psu. First mobo I used for this build didn't work at all. This one fires up but then goes into the endless loop. I have tried a different psu and a different RAM as well as different GPU. Leaning towards it being a faulty cpu but curious to see if anyone else has any other suggestions before I dismantle everything.

CPUs are almost never bad; sometimes you can have a bent mobo pin that causes CPU related problems.  However, I don't think that is the case here.

Maybe this will work:

Ensure the monitor is connected to the primary GPU ( the one in the 16x slot closest to the CPU )

Disconnect the USB or SSD/HHD from the rig.

Fully power off everything: including the PSU.

Press the power button several times to clear any remaining power in the mobo.

Turn the PSU powerswitch back to | "on".

power on (without the USB attached)

See if the bios posts; if you get nothing in 20 seconds; press ctrl + alt + del repeatedly until the system reboots.

Wait and see if the bios posts.

If the bios posts attach the USB key and press ctrl + alt + delete.

Let me know if this works.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 08:00:38 PM
 #1593

I have been GPU mining for over a year now (mostly ETH on AMD rigs) using Ethos. In my experience, 70=80% of the hardware problems I have had have been related to poor quality risers. It's hard to find a source of decent quality ones - they are all made in China and it seems with little or no quality control. They are a very cheap high volume item so this means unfortunately for us it's just luck if  you get good ones.
I have a friend who ordered a bag of 10 and 7 of them were faulty right away, then an eighth failed after 24 hours.

So if you find a reliable source  - buy twice as many as you think you will need!

I have a stash of extra risers; I agree with newmz: its a good idea to keep extras on hand.

this is  a better way  go riser free
2x 1080 ti's 1x 1070 itx
1750 sols  for zec uses 500- 550 watt


mobos slots are better then risers.
a cpu- ram-- mobo-- psu -- usb stick combo for 3 cards is about
120 +  50 +  114 +  130  +    16 =  430  high end 

50  + 25  + 114  +   100  +   11  = 300  low end

so low end   600  all under long warranty  for six cards two 3 card rigs.

six card   rig

50 + 25 + 114 + 400 +  11 + 60  = 660   if you go with evga  1600

______________260 ------------ = 520 if you use 2 rosewill quark 850 watts    and the risers are not under warranty.

-------------------150 ------------ = 410 if you use  a server pico setup 

So 410   vs 600 on smaller farms  is not much  for 2 complete 3 card  vs 1 six complete.

All my three card can go to 4 card with 1 riser
many of my three card can go to 5 cards with 2 risers.

the one below does 5 with zero problems



This works for small setups; but there is no avoiding risers for medium or large scale farms targeting OPT $/hash.



TheCoinMine
Jr. Member
*
Offline Offline

Activity: 40


View Profile
July 06, 2017, 08:01:41 PM
 #1594

So new build, similar problem to the first rig I built myself. Getting the never ending "bootloop" when I fire up my mobo with everything plugged in. I know everyone says to unplug everything and try it one part at a time, which i will indeed do, but I was wondering if anyone else had this issue and found a more uniform way to fix it? Last time it was because my RAM was loose. This time my connections are all secure.

Background: building a trio rig with 2 1080ti and a 1080 mini using a 270 mobo with 850w psu. First mobo I used for this build didn't work at all. This one fires up but then goes into the endless loop. I have tried a different psu and a different RAM as well as different GPU. Leaning towards it being a faulty cpu but curious to see if anyone else has any other suggestions before I dismantle everything.

CPUs are almost never bad; sometimes you can have a bent mobo pin that causes CPU related problems.  However, I don't think that is the case here.

Maybe this will work:

Ensure the monitor is connected to the primary GPU ( the one in the 16x slot closest to the CPU )

Disconnect the USB or SSD/HHD from the rig.

Fully power off everything: including the PSU.

Press the power button several times to clear any remaining power in the mobo.

Turn the PSU powerswitch back to | "on".

power on (without the USB attached)

See if the bios posts; if you get nothing in 20 seconds; press ctrl + alt + del repeatedly until the system reboots.

Wait and see if the bios posts.

If the bios posts attach the USB key and press ctrl + alt + delete.

Let me know if this works.


Thanks a ton, will give it a shot. And if this doesn't work? Just break everything?
fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 08:04:51 PM
 #1595

Hey everyone, new here and new to mining too!! and really enjoying the experience. My roommate taught me into mining and we started upgrading my gaming rig to mining too (running claymore on windows 7 with 1x Asus Rog Strix 1080 OC and 2x Asus Rog Strix 1070 OC) but now we're going to build each a rig of our own and we bought the same components. (excepted of 1 gpu)

Here is what our build are going to be ;

Motherboard : AsRock H81 PRO BTC R2.0
Processor : Intel Celeron G1840 Haswell Dual Core 2.8ghz LGA 1150
GPU 3x Asus ROG Strix GeForce GTX 1070 8Gb Gaming OC 1632MHz base/1860MHz 
Ram : G.Skill 4Gb (2x2Gb) DDR3 PC3-12800 1600Mhz NQ series Dual Channel
Psu : EVGA SuperNova 1000w P2 (Platinum) ECO
Drive : KingSpec 32GB Sata II 2.0 SSD
Risers : USB PCie 1x-16x

So basiclly this is the rig except one of them will have 2x 1070 rog strix oc and have 1x Asus Gtx 1070 Dual OC.

I also would like to specify that we would like to upgrade to 6 Gpu per rig..

I read thorough the first post and I was wondering if there is a step by step tutorial for setting up everything or we just go by our knowledge. My friend is familiar with linux but I'm not and I think learning is the best way to live so I'm ready to step in and I really want to get involved into this community!

And also if you have any recommendation towards our builds!

Thanks!

I recommend using 8gb of ram, and ensuring the risers you get are the new pcie 6 pin powered type.  I think some members are working on build guides.  Phil has made some guides that are linked on the OP.


fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 06, 2017, 08:06:41 PM
 #1596

So new build, similar problem to the first rig I built myself. Getting the never ending "bootloop" when I fire up my mobo with everything plugged in. I know everyone says to unplug everything and try it one part at a time, which i will indeed do, but I was wondering if anyone else had this issue and found a more uniform way to fix it? Last time it was because my RAM was loose. This time my connections are all secure.

Background: building a trio rig with 2 1080ti and a 1080 mini using a 270 mobo with 850w psu. First mobo I used for this build didn't work at all. This one fires up but then goes into the endless loop. I have tried a different psu and a different RAM as well as different GPU. Leaning towards it being a faulty cpu but curious to see if anyone else has any other suggestions before I dismantle everything.

CPUs are almost never bad; sometimes you can have a bent mobo pin that causes CPU related problems.  However, I don't think that is the case here.

Maybe this will work:

Ensure the monitor is connected to the primary GPU ( the one in the 16x slot closest to the CPU )

Disconnect the USB or SSD/HHD from the rig.

Fully power off everything: including the PSU.

Press the power button several times to clear any remaining power in the mobo.

Turn the PSU powerswitch back to | "on".

power on (without the USB attached)

See if the bios posts; if you get nothing in 20 seconds; press ctrl + alt + del repeatedly until the system reboots.

Wait and see if the bios posts.

If the bios posts attach the USB key and press ctrl + alt + delete.

Let me know if this works.


Thanks a ton, will give it a shot. And if this doesn't work? Just break everything?

If this doesn't work I would try reimaging the USB key. (first ensure your downloaded zip produces the correct hash)

What kind of USB key are you using btw?

salfter
Hero Member
*****
Offline Offline

Activity: 627


My PGP Key: 92C7689C


View Profile WWW
July 06, 2017, 09:06:11 PM
 #1597

Any idea why when i try to SSH into nvOC as root with miner1 as my password i get "Permission denied" but as m1 it works?

EDIT: nevermind figured it out, my linux knowledge is very limited so i wasn't aware i can jump into root with "sudo su", anyhow after that "sudo echo b > /proc/sysrq-trigger" did manage to restart the rig.

Password-based root login is disabled for security reasons.  You can either log in as a normal user and use sudo to get root (as you did) or use public-key authentication to log into root directly.

My Bitgem Pool - PPLNS, Stratum | BTG Explorer
Tipjars: BTC 1TipsGocnz2N5qgAm9f7JLrsMqkb3oXe2 LTC LTipsVC7XaFy9M6Zaf1aGGe8w8xVUeWFvR BTG gTipsVB9qmyYHuqMMKTuCYMHpfkUFBXKrZ | My Bitcoin Note Generator
DJ ACK
Newbie
*
Offline Offline

Activity: 11


View Profile
July 06, 2017, 10:02:45 PM
 #1598

Good day!  Does anyone know of a good way to identify which PCI Lane is assigned to each physical PCI slot.  Scanning system logs, System Info, etc. it is easy to correlate which PCI lane, GPU #, GPU serial number, etc. fell off the bus.  But is there a way to correlate PCI Lane to actual PCI slot?  Short of me logging the GPU serial number as I add each card to the board, It would be nice if there was a one stop shop to display GPU PCI slot information.  

I don't believe that they are assigned sequentially during system boot up because I have seen lane assignments go from 1, 2, 5, 6, 7, 8.   It would really help in troubleshooting riser problems if physical slot assignment was easily found.  

I have learned over the years that riser board version type really does not matter (even though I have seen several posts that claim v6 is better, v7 is better, C vs. S, etc.).   It all depends on where each lot is manufactured and if they had any kind of quality assurance check prior to shipment.  Heck I have an allotment of v1s from the BTC mining days that still work great.  Some riser boards work fine if the card is not overclocked too high.  But it is never the same across the board.    

Whether the risers are purchased from eBay, Newegg, Amazon, Craig's List, etc., it all seems to be a crap shoot.  And returning products across the ocean is real pain in the a$$.  My recommendation is find one vendor that has not failed you and stick with them (regardless of the wait time)...and order EXTRAS!  Does anyone know of a US, UK or Asia based reliable vendor?      

Just some food for thought from an extremely happy nvOC user.
dspx
Newbie
*
Offline Offline

Activity: 1


View Profile
July 06, 2017, 10:26:09 PM
 #1599

Good day!  Does anyone know of a good way to identify which PCI Lane is assigned to each physical PCI slot.  Scanning system logs, System Info, etc. it is easy to correlate which PCI lane, GPU #, GPU serial number, etc. fell off the bus.  But is there a way to correlate PCI Lane to actual PCI slot?  Short of me logging the GPU serial number as I add each card to the board, It would be nice if there was a one stop shop to display GPU PCI slot information.  

I don't believe that they are assigned sequentially during system boot up because I have seen lane assignments go from 1, 2, 5, 6, 7, 8.   It would really help in troubleshooting riser problems if physical slot assignment was easily found.  

I have learned over the years that riser board version type really does not matter (even though I have seen several posts that claim v6 is better, v7 is better, C vs. S, etc.).   It all depends on where each lot is manufactured and if they had any kind of quality assurance check prior to shipment.  Heck I have an allotment of v1s from the BTC mining days that still work great.  Some riser boards work fine if the card is not overclocked too high.  But it is never the same across the board.    

Whether the risers are purchased from eBay, Newegg, Amazon, Craig's List, etc., it all seems to be a crap shoot.  And returning products across the ocean is real pain in the a$$.  My recommendation is find one vendor that has not failed you and stick with them (regardless of the wait time)...and order EXTRAS!  Does anyone know of a US, UK or Asia based reliable vendor?      

Just some food for thought from an extremely happy nvOC user.


I identified them by setting all fans to 0 and popping them up to 100 one at a time.
weareken
Newbie
*
Offline Offline

Activity: 27


View Profile
July 07, 2017, 02:15:53 AM
 #1600

Is anybody else experiencing nvOC hang / lockup to the point of needing a hard powerdown when Genoil crashes?  I can log in but when I try to close the miner and shutdown the OS becomes locked up. I am wondering if it is hardware related?  I am only using 4GB of ddr4 is that enough???  I believe I will be going back to Claymore.  I can't seem to get Genoil stable even dialed 300mc back from Claymore.  I will reimage a USB stick and go back to Claymore to see if stability comes back. 

Having more ram would probably help; I use 8gb on most of my rigs and I have achieved multi day stability with the ones that are using genoil by previously lowing the clocks / adjusting the powerlimits whenever a soft crash occurred.

On a 4 x 1060 rig I use 1.1GB of RAM.  On a 6 x 1060 rig I use 1.3GB of RAM.  Unless there are spikes of memory usage or a memory leak somewhere, I don't see why 4GB would be more than enough.  It certainly shouldn't have any effect on Genoil stability.  Genoil seems to give comparable/better hash rates even with lower clocks and power limits than Claymore requires.  I've found that dropping the clocks has definitely increased stability without reducing hash rate.
Pages: « 1 ... 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 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 ... 284 »
  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!