Bitcoin Forum
November 21, 2017, 09:21:42 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 ... 287 »
  Print  
Author Topic: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4  (Read 327277 times)
fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 05, 2017, 04:39:11 AM
 #1541

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?

thanks in advance

look at the syslog:

go to ubuntu button top left and enter:

sy

click on system log

1511299302
Hero Member
*
Offline Offline

Posts: 1511299302

View Profile Personal Message (Offline)

Ignore
1511299302
Reply with quote  #2

1511299302
Report to moderator
1511299302
Hero Member
*
Offline Offline

Posts: 1511299302

View Profile Personal Message (Offline)

Ignore
1511299302
Reply with quote  #2

1511299302
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1511299302
Hero Member
*
Offline Offline

Posts: 1511299302

View Profile Personal Message (Offline)

Ignore
1511299302
Reply with quote  #2

1511299302
Report to moderator
gig410
Newbie
*
Offline Offline

Activity: 14


View Profile
July 05, 2017, 04:41:03 AM
 #1542

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

Activity: 14


View Profile
July 05, 2017, 04:48:29 AM
 #1543

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?

thanks in advance

look at the syslog:

go to ubuntu button top left and enter:

sy

click on system log

when I do that it gives me a stream of those messages in my previous post
fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 05, 2017, 04:59:31 AM
 #1544

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?

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 05, 2017, 05:02:25 AM
 #1545

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


Very nice  Smiley  I will probably add some version of this in a later version.  I will include your donation address and ensure you are credited.


car1999
Full Member
***
Offline Offline

Activity: 168


View Profile
July 05, 2017, 05:25:04 AM
 #1546

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.
gig410
Newbie
*
Offline Offline

Activity: 14


View Profile
July 05, 2017, 05:37:17 AM
 #1547

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

Activity: 14


View Profile
July 05, 2017, 06:10:30 AM
 #1548

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

Activity: 8


View Profile
July 05, 2017, 06:12:18 AM
 #1549

Hi,

Please help!
I have got stuck on this problems  Huh
Мy 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: [<ffffffffc0262880>] _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
salfter
Hero Member
*****
Offline Offline

Activity: 627


My PGP Key: 92C7689C


View Profile WWW
July 05, 2017, 06:15:20 AM
 #1550

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.

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

Activity: 14


View Profile
July 05, 2017, 06:45:03 AM
 #1551

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.
andreih
Newbie
*
Offline Offline

Activity: 7


View Profile
July 05, 2017, 07:32:56 AM
 #1552

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.
bel123
Member
**
Offline Offline

Activity: 77


View Profile
July 05, 2017, 10:30:32 AM
 #1553

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

Activity: 16


View Profile
July 05, 2017, 12:40:47 PM
 #1554

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!
Gaza8143
Newbie
*
Offline Offline

Activity: 17


View Profile
July 05, 2017, 12:46:39 PM
 #1555

Woot woot!

Solved my power issue.  Ok so rewind and I was a rookie and started my rig with 1 card.  Fullzero fixed that issue for me by showing me how to copy my xorg file over.  I think that was also my power issue.

Essentially I re imaged the SSD and now I have power and my cards are doing 28.5 ETH and 500 SC each  Cheesy

For anyone else that started with 1 card and copied xorg over you might want to re image as well.  I was on 25.5 ETH and 550 SC before.

( last time the dual mine switch was on 70 I changed it to 60 )

Thanks everyone for your help Smiley
droghtak
Member
**
Online Online

Activity: 70


View Profile
July 05, 2017, 01:14:53 PM
 #1556

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
newmz
Full Member
***
Offline Offline

Activity: 234


View Profile
July 05, 2017, 03:14:22 PM
 #1557

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

Activity: 518


View Profile
July 05, 2017, 04:38:54 PM
 #1558

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

As I see a super coin as the super highway and alt coins as taxis and trucks needed to move transactions. ~philipma1957
fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 05, 2017, 07:33:59 PM
 #1559

Hi,

Please help!
I have got stuck on this problems  Huh
Мy 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: [<ffffffffc0262880>] _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

I see the 381.22 driver is included via ppa now; so it should be properly supported now.

Let me know if it gives you any issues / what the difference in performance is with your rigs.

fullzero
Legendary
*
Offline Offline

Activity: 1092



View Profile
July 05, 2017, 07:38:09 PM
 #1560

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.

/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)

this is not a problem

If you are connecting a monitor directly to the motherboard (don't do this); only connect a monitor the the primary GPU (the one in the 16x slot closest to the CPU).

If you aren't connecting a monitor directly to the motherboard;  I would try reimaging the USB key.


Pages: « 1 ... 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 [78] 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 ... 287 »
  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!