Author

Topic: [ mining os ] nvoc - page 304. (Read 418549 times)

newbie
Activity: 9
Merit: 0
July 05, 2017, 08:02:10 PM
Hi everyone. I have an Asus Prime Z270-P running great with 2 EVGA 1070's.  I want to run it with 8 cards which I have. Should I reimage the USB stick or will it be fine with installing the cards with risers and just running it again? I'm also assuming I have to run it without a monitor hooked up.
newbie
Activity: 2
Merit: 0
July 05, 2017, 05:49:36 PM
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!
full member
Activity: 169
Merit: 100
July 05, 2017, 05:15:17 PM
What PCIe slots do you have them plugged into?

Tried changing all the slots because there are 3 cards, tried using 123, 456, 124, 235 etc.

Looking at your MB manual I would recommend slotting the GPUs into PCIX16, PCIEX4_1, PCIEX4_2 (from top to bottom slots 2, 4, 6) Also make sure the monitor is plugged into slot 2 or PCIEX16.

If it still isn't working may need to change some settings such as changing it all to Gen 2 or Gen 1 in the BIOS.

newbie
Activity: 45
Merit: 0
July 05, 2017, 05:09:15 PM
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?
newbie
Activity: 25
Merit: 0
July 05, 2017, 05:02:31 PM
What PCIe slots do you have them plugged into?

Tried changing all the slots because there are 3 cards, tried using 123, 456, 124, 235 etc.
full member
Activity: 169
Merit: 100
July 05, 2017, 04:59:39 PM
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 ?
full member
Activity: 169
Merit: 100
July 05, 2017, 04:58:49 PM
newbie
Activity: 25
Merit: 0
July 05, 2017, 04:28:06 PM
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
hero member
Activity: 672
Merit: 500
July 05, 2017, 11:38:54 AM
First of all big thank you to fullzero and everyone contributing to this distro!

I've been struggling with the Genoil crash issue and lack of watchdog implementation for the past few days and I have a bandaid solution that seems to be actually working quite well, perhaps it can help others in the community:

Essentially you need to split the Genoil output to a file, grep it (we only care about 'error' instances only ;  and then this output as input for a monitoring script that kills and restarts the misbehaving process.

So we have 2 scripts launched in screen as daemons "ltail" script and "ett" script

$screen -dmS ltail sh ~/eth/Genoil-U/ltail
and
$screen -dmS ett bash ~/ett

ltail:
--------------------------
#!/bin/bash
echo listening...
cd ~/eth/Genoil-U/
tail -fn0 err.log | \
while read line ; do
        DATE=$(date +%d-%m-%Y" "%H:%M:%S)
        echo "$DATE $line" | grep "error" | tee -a ~/eth/Genoil-U/timestamp.log
        if [ $? = 0 ]
        then
                kill $(ps aux | grep '[e]thminer' | awk '{print $2}')
                sleep 1
                screen -dmS ett bash ~/ett
        fi
done
-------------------------
ett:
-------------------------
#!/bin/bash
cd ~/eth/Genoil-U
./ethminer -U -F eth-us.dwarfpool.com:80/0xBEbd092a03827C37B75cd4ea314b207AA65c348f/208 2>&1 | tee >(grep error --color=never --line-buffered | tee -a err.log)

-------------------------

finally I also send output of ltail to timestamp.log to track how many times Genoil fails per hour - with roughly aiming at 1 crash per hour this gives me about 130MHs out of 5xGTX1060 which is a good 20+ MHs higher then Claymore... most importantly it gives stable hashing despite the OC introduced errors. The recovery is literally seconds.
Oh yeah and I also run
$tail -f ~/eth/Genoil-U/timestamp.log in a screen as well as watch -n 5 'sensors |grep Core' in another screen to fine tune the OC vs crash per hour vs temp
Hope this helps, and I hope the message is not too chaotic.
Cheers!

BTC: 13PnEKpfVzNseWkrm6LoueKcCMPj74zPv7
ETH: 0xBEbd092a03827C37B75cd4ea314b207AA65c348f


i monitored genoil on windows with his zec miner like this https://drive.google.com/open?id=0B0614dRHRS0RYXRnNWtpeWRjbDg'

might give fullzero some ideas on a nice monitoring script

also when is v0018 coming?

was going to image v0017 but if 18 is coming in a the next few days ill wait
sr. member
Activity: 372
Merit: 250
The road of excess leads to the palace of wisdom
July 05, 2017, 10:14:22 AM
m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

no idea what those mean

Those look like the errors I was getting with some crappy PCIe extenders I had recently ordered.  Here's a closeup of the inadequate soldering on the bit that goes in the slot; the other end of the riser is probably similar. Click for the full-res original:



I'll be sending these back.  There were no reviews when I bought them, but since then someone else has left a 1-star review.

I've bought /2uIHOyy]these as replacements, at fullzero's recommendation.

I saw your post about the soldering, I checked mine for the same thing and the solder joints look good. I have another riser set and tried swapping the parts one at a time and still kept getting the same errors. i plugged the riser straight to the psu using one of the molex cables that came with it and no change (actually that's when it no longer booted to the GUI) I used the same riser and mobo with an AMD gpu and ethos and it never reported the error, but simplemining OS did and those serrors started showing. Windows and the nvidia gpus and that same riser didn't have an issue, It's just weird. I truly have no clue as to what is going on.
m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

no idea what those mean

Those look like the errors I was getting with some crappy PCIe extenders I had recently ordered.  Here's a closeup of the inadequate soldering on the bit that goes in the slot; the other end of the riser is probably similar. Click for the full-res original:



I'll be sending these back.  There were no reviews when I bought them, but since then someone else has left a 1-star review.

I've bought these as replacements, at fullzero's recommendation.

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!
member
Activity: 75
Merit: 10
July 05, 2017, 08:14:53 AM
is it possible to mine a different coin with each GPU?
atm one can select a single coin for the full rig, but sometimes you have an heterogeneous rig and would like to mine different currencies with each GPU or even diversify the coins with an homogeneous rig
newbie
Activity: 16
Merit: 0
July 05, 2017, 07:40:47 AM
Some pool, for example nanopool and dwarfpool need e-mail for sending alert with this format: address.worker/email. I would like to ask you to take it to params in the next version. Thank you!
member
Activity: 97
Merit: 10
July 05, 2017, 05:30:32 AM
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
newbie
Activity: 7
Merit: 0
July 05, 2017, 02:32:56 AM
Hi
I need some help to run nvoc. I get this message when mining starts

ERROR: Error assigning value 85 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:3]) as specified in assignment
       '[fan:3]/GPUTargetFanSpeed=85' (Unknown Error).
ERROR: Error assigning value 85 to attribute 'GPUTargetFanSpeed' (m1-desktop:0[fan:4]) as specified in assignment
       '[fan:4]/GPUTargetFanSpeed=85' (Unknown Error).
I'm running on Gigabyte Aorus gaming 7 z270 , 4 Zotac 1070 amp edition and 1 gigabyte 1070 gaming g1.
Cannot OC Gpu 3 and 4 in the Nvidia xServer settings also.
And I found another thing
/home/m1/eth/Genoil-U/ethminer: /usr/local/cuda/lib64/libOpenCL.so.1: no version information available (required by /home/m1/eth/Genoil-U/ethminer)
/home/m1/eth/Genoil-U/ethminer: /usr/local/cuda/lib64/libOpenCL.so.1: no version information available (required by /home/m1/cpp-ethereum/build/libethcore/libethcore.so)
/home/m1/eth/Genoil-U/ethminer: /usr/local/cuda/lib64/libOpenCL.so.1: no version information available (required by /home/m1/cpp-ethereum/build/libethash-cl/libethash-cl.so)
/home/m1/eth/Genoil-U/ethminer: /usr/local/cuda/lib64/libOpenCL.so.1: no version information available (required by /home/m1/cpp-ethereum/build/libethash-cl/libethash-cl.so)
Genoil's ethminer 0.9.41-genoil-1.1.7
is this ok?
Edit:
all I had to do was to modify the xorg.conf with the gpu's BusID that are found in the nvidia x server settings. I've seen a post to change them with the BusIDs found in the nvidia-smi but that did not work at all. Hope this will help.
newbie
Activity: 14
Merit: 0
July 05, 2017, 01:45:03 AM
m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

no idea what those mean

Those look like the errors I was getting with some crappy PCIe extenders I had recently ordered.  Here's a closeup of the inadequate soldering on the bit that goes in the slot; the other end of the riser is probably similar. Click for the full-res original:

https://alfter.us/wp/wp-content/uploads/2017/07/IMG_20170704_225213855-768x1024.jpg

I'll be sending these back.  There were no reviews when I bought them, but since then someone else has left a 1-star review.

I've bought /2uIHOyy]these as replacements, at fullzero's recommendation.

I saw your post about the soldering, I checked mine for the same thing and the solder joints look good. I have another riser set and tried swapping the parts one at a time and still kept getting the same errors. i plugged the riser straight to the psu using one of the molex cables that came with it and no change (actually that's when it no longer booted to the GUI) I used the same riser and mobo with an AMD gpu and ethos and it never reported the error, but simplemining OS did and those serrors started showing. Windows and the nvidia gpus and that same riser didn't have an issue, It's just weird. I truly have no clue as to what is going on.
hero member
Activity: 651
Merit: 501
My PGP Key: 92C7689C
July 05, 2017, 01:15:20 AM
m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

no idea what those mean

Those look like the errors I was getting with some crappy PCIe extenders I had recently ordered.  Here's a closeup of the inadequate soldering on the bit that goes in the slot; the other end of the riser is probably similar. Click for the full-res original:



I'll be sending these back.  There were no reviews when I bought them, but since then someone else has left a 1-star review.

I've bought these as replacements, at fullzero's recommendation.
S9k
newbie
Activity: 26
Merit: 0
July 05, 2017, 01:12:18 AM
Hi,

Please help!
I have got stuck on this problems  Huh
My configuration:

-ASUS PRIME Z270-P - 2 . I tried both, results are similar.
-EVGA GeForce GTX 1080 GAMING ACX 3.0 - 2
-MSI Geforce GTX 1080 Gaming X-  2
-The Gigabyte power supply unit on 1200 watts


Three video cards work perfectly in any any combinations,

m1@m1-desktop:~$ nvidia-smi -L
GPU 0: GeForce GTX 1080 (UUID: GPU-43453088-0fca-9442-106d-7594d157ebf2)
GPU 1: GeForce GTX 1080 (UUID: GPU-d099b67e-f204-66fa-96dc-365a6b559a7e)
GPU 2: GeForce GTX 1080 (UUID: GPU-5aacd4db-f68b-917e-8ac2-84caf68d6cac)
m1@m1-desktop:~$


m1@m1-desktop:~$ lspci |grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)
03:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)
05:00.0 VGA compatible controller: NVIDIA Corporation Device 1b80 (rev a1)
m1@m1-desktop:~$



but if I add the fourth (in this case the ID GPU-5aacd4db-f68b-917e-8ac2-84caf68d6cac ), then the system falls. Here what I see in dmesg


[   98.722227] nvidia-modeset: Allocated GPU:0 (GPU-43453088-0fca-9442-106d-7594d157ebf2) @ PCI:0000:01:00.0
[   98.769072] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769117] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769144] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769169] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769193] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769217] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   98.769241] ACPI Warning: \_SB_.PCI0.RP04.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.359255] nvidia-modeset: Allocated GPU:1 (GPU-5c9c8e29-a088-90a6-2a20-b2b2b971d1fb) @ PCI:0000:05:00.0
[   99.398991] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399035] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399063] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399087] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399112] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399136] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buff er], ACPI requires [Package] (20150930/nsarguments-95)
[   99.399160] ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[   99.984670] nvidia-modeset: Allocated GPU:2 (GPU-5aacd4db-f68b-917e-8ac2-84caf68d6cac) @ PCI:0000:06:00.0
[  100.619118] nvidia-modeset: Allocated GPU:3 (GPU-d099b67e-f204-66fa-96dc-365a6b559a7e) @ PCI:0000:03:00.0
[  100.743159] NVRM: GPU at PCI:0000:01:00: GPU-43453088-0fca-9442-106d-7594d157ebf2
[  100.743162] NVRM: GPU Board Serial Number:
[  100.743164] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 000001e0 00000801 00000004 00000005
[  100.743649] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000080 00000004 00000005 00000004

[  102.432593] r8169 0000:07:00.0 enp7s0: link up
[  102.432600] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
[  103.743306] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[  103.773941] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00000004
[  105.501795] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  105.501798] Bluetooth: BNEP filters: protocol multicast
[  105.501802] Bluetooth: BNEP socket layer initialized
[  105.613048] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00000004
[  105.613106] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00000004
[  105.704570] NVRM: Xid (PCI:0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00000004

[  105.704972] BUG: unable to handle kernel paging request at ffff88167153d830
[  105.704974] IP: [] _nv008171rm+0x620/0x780 [nvidia]
[  105.705052] PGD 220c067 PUD 0
[  105.705053] Oops: 0000 [#1] SMP

Three days I try to solve a problem.
I changed versions of BIOS (0325,0608,0610) and risers, control 4G is included, has updated NVIDIA drivers to 381.22 - nothing helps.
Maybe somebody will have ideas?

My guess is your mobo is trying to / is using SLI.  Are you using an M2 ssd?

There should be some setting in the bios related to SLI; disable it / what slots are you using and are you using risers, if so on which GPUs?

If you are using risers; how are they powered?

Hi,
no, I don't use M2 SSD.
I use risers of the version 006s with the molex socket.

I managed to solve a problem. I modified / etc/default/grub

m1@m1-desktop:/etc/default$ more grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="vga=0 rdblacklist=nouveau nouveau.modeset=0"
GRUB_CMDLINE_LINUX=""

sudo update-grub

also I have created the file  disable-nouveau.conf which contains two lines

m1@m1-desktop:/etc/modprobe.d$ more /etc/modprobe.d/disable-nouveau.conf
blacklist nouveau
options nouveau modeset=0


sudo reboot

Were you connecting the monitor directly to the mobo?

Not sure why else nouveau would be used.



My monitor is connected to GPU0.

m1@m1-desktop:~$ nvidia-smi
Wed Jul  5 02:00:52 2017      
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 381.22                 Driver Version: 381.22                    |
|-------------------------------+----------------------+----------------------+
| 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 1080    Off  | 0000:01:00.0      On |                  N/A |
| 75%   65C    P2   181W / 180W |    319MiB /  8113MiB |     97%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1080    Off  | 0000:03:00.0     Off |                  N/A |
| 75%   60C    P2   180W / 180W |    141MiB /  8114MiB |     96%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 1080    Off  | 0000:05:00.0     Off |                  N/A |
| 75%   72C    P2   165W / 180W |    141MiB /  8114MiB |     96%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 1080    Off  | 0000:06:00.0     Off |                  N/A |
| 75%   71C    P2   166W / 180W |    141MiB /  8114MiB |     98%      Default |
+-------------------------------+----------------------+----------------------+


I remained on version 381.22 drivers, it seems to me they more productive
newbie
Activity: 14
Merit: 0
July 05, 2017, 01:10:30 AM
So my rig crashed again, it was up for about 19 hours with the current settings. The previous it crashed I had not been able to see it crash, I just knew it because the screen was blank and the fans on the gpus went up to 100 percent. This time I was siting in front of it doing something else when the screen went blank and the fans kicked up to 100 percent. My question is if there is some kind of log that could be looked at to see what caused the crash or can one be enabled that only keeps the last one hour of activity?

ssh in and look at the tail end of /var/log/dmesg.  I have some crappy PCIe extenders here that would interrupt the connection between the GPU and the computer as soon as mining software fired up.  The errors show up toward the end of /var/log/dmesg.

There's also /var/log/messages, but that tends to be less useful for hardware errors.

I have a keyboard and monitor connected to the rig for now, I found a file named kern.log that is 1.7 GB in size and kern.log.1 that is about 650 MB. these are the messages

m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

and

m1-desktop kernel: [105577.995353] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.995360] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.995363] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

once in a while I get this

m1-desktop kernel: [105576.736779] pcieport 0000:00:1b.0: can't find device of ID00d8


no idea what those mean


What kind of risers are you using?

Have you checked to ensure they are fully seated in the pcie ports?

just checked if they are seated correctly on the motherboard and on the cards and they are, I did an lspci command and it looks like id a2eb is the first gpu on the rig, it has it's own power cord to the power supply on the card and on the riser. the card does work but it has these errors

looks like I was wrong about a2eb being the first gpu. I removed the gpu completely and I'm still getting these errors as soon as I boot, it won't even go into the GUI any more
newbie
Activity: 14
Merit: 0
July 05, 2017, 12:37:17 AM
So my rig crashed again, it was up for about 19 hours with the current settings. The previous it crashed I had not been able to see it crash, I just knew it because the screen was blank and the fans on the gpus went up to 100 percent. This time I was siting in front of it doing something else when the screen went blank and the fans kicked up to 100 percent. My question is if there is some kind of log that could be looked at to see what caused the crash or can one be enabled that only keeps the last one hour of activity?

ssh in and look at the tail end of /var/log/dmesg.  I have some crappy PCIe extenders here that would interrupt the connection between the GPU and the computer as soon as mining software fired up.  The errors show up toward the end of /var/log/dmesg.

There's also /var/log/messages, but that tends to be less useful for hardware errors.

I have a keyboard and monitor connected to the rig for now, I found a file named kern.log that is 1.7 GB in size and kern.log.1 that is about 650 MB. these are the messages

m1-desktop kernel: [105577.938217] pcieport 0000:00:1b.0:    [ 0] Receiver Error         (First)
m1-desktop kernel: [105577.949736] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.949750] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.949757] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

and

m1-desktop kernel: [105577.995353] pcieport 0000:00:1b.0: AER: Corrected error received: id=00d8
m1-desktop kernel: [105577.995360] pcieport 0000:00:1b.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00d8(Receiver ID)
m1-desktop kernel: [105577.995363] pcieport 0000:00:1b.0:   device [8086:a2eb] error status/mask=00000001/00002000

once in a while I get this

m1-desktop kernel: [105576.736779] pcieport 0000:00:1b.0: can't find device of ID00d8


no idea what those mean


What kind of risers are you using?

Have you checked to ensure they are fully seated in the pcie ports?

just checked if they are seated correctly on the motherboard and on the cards and they are, I did an lspci command and it looks like id a2eb is the first gpu on the rig, it has it's own power cord to the power supply on the card and on the riser. the card does work but it has these errors
full member
Activity: 350
Merit: 100
July 05, 2017, 12:25:04 AM
Also, I couldn't find how I can see the current mining process. I did see the screen -r commands, but that implies killing the current process and restarting it. I'd like to be able to see, from SSH, the current mining process without killing it. Is this possible?

If you want to monitor the mining process via screen you're going to have to kill the initial gnome-terminal.  There's no way around that, as screen can only reconnect to an existing screen session.

This shouldn't be a big deal if you have a stable rig.  You only need to do it once per reboot.  My process is:

1. From my desktop where I monitor my rigs I initiate a constant ping:
Code:
ping -t 10.20.30.40  # substitute your rig's IP, find it in your router, or by running nmap on your LAN subnet, or by running ifconfig from a guake terminal on the rig if you have a monitor connected
2. Boot the rig
3. Wait until I begin to get ping responses from the rig, thus indicating Ubuntu has booted and rig has network connectivity
4. SSH into the rig (user: m1  password: miner1)
5. Initiate a screen session:
Code:
screen -s [name for your rig, make one up or call it "rig"]
6. Start nvidia-smi dmon to watch for mining process to begin (by waiting until this happens you know OC settings, fan speed settings, etc have been applied.  Running those commands from within screen isn't 100% consistent IME as I always see error messages when I tried it that way.  It's best to let those settings commands run from gnome-terminal as Ubuntu first boots IMO).
Code:
nvidia-smi dmon
7. Wait until you see wattage go up and GPU utilization go up to 100% (which indicates that the oneBash script concluded and opened the mining process).  Exit nvidia-smi with CTRL + c
8. Find the PID for gnome-terminal.  
Code:
ps aux | grep gnome-terminal
9. Kill it:
Code:
kill [PID from step 8]
10. Restart mining:
Code:
bash '/media/m1/1263-A96E/oneBash'

It might seem like a lot of steps, but it takes all of 120 seconds and you shouldn't need to do it very often once your rig is dialed in.  You're losing maybe 1 minute's worth of hashes on avg of every week?  Pretty negligible considering the convenience of monitoring from another workstation, and you're not using up system resources by using Teamviewer.  This also lets you go completely headless if you buy a dummy HDMI plug.  I just updated from 16 to 17 and didn't need to haul my extra monitor upstairs to do it.  Easy peasy.
run export DISPLAY=:0 before step 5, if not, setp 10 throws erroe.
Jump to: