Bitcoin Forum
October 14, 2019, 04:36:32 AM *
News: If you like a topic and you see an orange "bump" link, click it. More info.
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4 on: November 13, 2017, 07:19:11 PM
hey, people, please tell me - is it only me who's horrified by necessity of downloading 5+Gb from single server in the end of 2017 year?
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3 on: October 29, 2017, 12:00:42 PM
Hi again, fullzero and all Smiley I've got a question for you. Some of my rigs now have a problem booting from USB stick. I have many different sticks but after a month or two of normal booting some of them started to fail on booting process, I/O errors etc... I understand that this is a quality problem in most cases, but also I think it's the usecase problem. So now I'm thinking of nvOC/rxOC mod that could do network booting to completely exclude this kind of issues while using these distros. The question is - have someone tried to boot nvOC from network? If yes, please share your experience to us!
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3 on: October 26, 2017, 08:36:53 AM

Max GPUs i have in one rig is 13. In case this doesn't help we need to see nvidia-xconfig output and xorg.conf that it makes, so we can try to find what's wrong.

Also you can try to reflash the latest version of nvOC to usb stick, edit 1bash at windows partition (don't forget to enable headless mode) and make the first boot from usb stick without monitor attached. After the first boot in headless mode you need to wait for autoconfiguration and auto reboot. Then use network scanner or see DHCP leases on the server side to find the IP of your rig (in most cases it will be the same as in previous attempts), ssh to it and see if xorg was correctly configured.


Thank you very much for your help!
My rig is now running with all those settings: New USB, Headless, no monitor attached, know IP, have SSH and mining. Here's the weird thing: See below for my current xorg.conf that is running and I'm getting all 19 GPUs mining but only the 1st one is OC'd. What's weird about it is that:

When I run
Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
I get a new xorg.conf that does two things:
Bus IDs lose the "@" symbol, and mining does not work.

Any ideas why some BusIDs use the @ while most I've seen don't, and why this seems to be allowing mining to run?
Also weird is that if you notice, there are only BusIDs for 0-3 (4 and 5 are missing), then it continues from 6-11 and that's it.

What are your thoughts on this?

Current xorg.conf:
Code:
Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "modesetting"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "None"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:2@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:3@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:6@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:7@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:8@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:9@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:10@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:11@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection



current lspci:
Code:
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (
00:02.0 VGA compatible controller: Intel Corporation Device 1902
00:14.0 USB controller: Intel Corporation Device a2af
00:16.0 Communication controller: Intel Corporation Device a2ba
00:1b.0 PCI bridge: Intel Corporation Device a2eb (rev f0)
00:1b.5 PCI bridge: Intel Corporation Device a2ec (rev f0)
00:1b.6 PCI bridge: Intel Corporation Device a2ed (rev f0)
00:1b.7 PCI bridge: Intel Corporation Device a2ee (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a294 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Device a295 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a296 (rev f0)
00:1c.7 PCI bridge: Intel Corporation Device a297 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Device a298 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Device a299 (rev f0)
00:1d.2 PCI bridge: Intel Corporation Device a29a (rev f0)
00:1d.3 PCI bridge: Intel Corporation Device a29b (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a2c8
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connecti
01:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
02:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
03:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
04:00.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:01.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:02.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:03.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:04.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:05.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:06.0 PCI bridge: ASMedia Technology Inc. Device 1187
05:07.0 PCI bridge: ASMedia Technology Inc. Device 1187
06:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
07:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
08:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
09:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0a:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0b:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0c:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0d:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0e:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
0f:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
10:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
11:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
12:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
13:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
14:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)
15:00.0 3D controller: NVIDIA Corporation Device 1c07 (rev a1)



as for BUS IDs naming, I don't have ideas why your rig using @, but if it works - let it be so Smiley The thing with 4-5 pci bus skipped is because other devices are using these buses, it's normal (you can see it with lspci - "04:00.0 PCI bridge: ASMedia Technology Inc. Device 1187" and so on).

What I want to point in your current xorg.conf is that there is no Coolbits option in each Screen section. This option has to be set to overclock GPU, I suppose, so try out what fullzero suggested:
Code:
sudo nvidia-xconfig -a --cool-bits=12 --allow-empty-initial-configuration
sudo reboot

and if it doesn't help, try to add this option to each Screen section in your xorg.conf except the screen section with intel device.
Code:
Option         "Coolbits" "12"

Here's xorg.conf from one of my working rigs, it got 7 GPUs, all P106-100.
Code:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 384.59  (buildmeister@swio-display-x64-rhel04-01)  Thu Jul 20 01:03:28 PDT 2017

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    Screen      1  "Screen1" RightOf "Screen0"
    Screen      2  "Screen2" RightOf "Screen1"
    Screen      3  "Screen3" RightOf "Screen2"
    Screen      4  "Screen4" RightOf "Screen3"
    Screen      5  "Screen5" RightOf "Screen4"
    Screen      6  "Screen6" RightOf "Screen5"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor3"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor4"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor5"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor6"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:4:0:0"
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:5:0:0"
EndSection

Section "Device"
    Identifier     "Device4"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:6:0:0"
EndSection

Section "Device"
    Identifier     "Device5"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:7:0:0"
EndSection

Section "Device"
    Identifier     "Device6"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "P106-100"
    BusID          "PCI:9:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen4"
    Device         "Device4"
    Monitor        "Monitor4"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen5"
    Device         "Device5"
    Monitor        "Monitor5"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen6"
    Device         "Device6"
    Monitor        "Monitor6"
    DefaultDepth    24
    Option         "AllowEmptyInitialConfiguration" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

4  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3 on: October 25, 2017, 12:16:41 PM

Hi! According to the same issue with all my P106-100 rigs, i suppose you need to do this:

1) check that you have set P106_100_FULL_HEADLESS_MODE="YES" in 1bash
2) check that you can control your rig without monitor attached (SSH or Teamviewer enabled)
3) disconnect monitor
4) run the following:
Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
sudo reboot

After the rig reboots, overclocking will work as supposed to. Sometimes i had to do number 4 again after reboot to make it working.


Thanks, trying now. Did you have more than 16 GPUs?
(edit)I tried this and mining would not start. Had to do
Code:
sudo mv /etc/X11/xorg.conf.nvidia.backup /etc/X11/xorg.conf
to return it to being able to mine at all.
I've read that you can add the coolbits part to either screen or device; the code you gave me I think put it in whichever was the wrong one.
Any other ideas?

Max GPUs i have in one rig is 13. In case this doesn't help we need to see nvidia-xconfig output and xorg.conf that it makes, so we can try to find what's wrong.

Also you can try to reflash the latest version of nvOC to usb stick, edit 1bash at windows partition (don't forget to enable headless mode) and make the first boot from usb stick without monitor attached. After the first boot in headless mode you need to wait for autoconfiguration and auto reboot. Then use network scanner or see DHCP leases on the server side to find the IP of your rig (in most cases it will be the same as in previous attempts), ssh to it and see if xorg was correctly configured.
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] rxOC easy-to-use Linux AMD Mining v0012 on: October 25, 2017, 02:24:01 AM
You can try running nvOC and then adding AMD driver for your 380x... but the automated setting of power and OC is effective on NVidia, but not on AMD right now.

(Under Linux. Under Windows, AMD tweaking works better. It's a function of the drivers available, so no good solution for Linux, right now. I think that's part of why rxOC gets less attention - until drivers make tweaking more possible, there's not as much demand for rxOC.)

Thing is I don't know how to add AMD drivers, I tried to follow a video but the terminal in nvOC is Nvidia miner :/ Any ideas?

To open the terminal window after nvOC boots you should press F12.

Try installing drivers for your 380x using this manual http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-PRO-Install.aspx
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3 on: October 25, 2017, 02:09:42 AM
Hey Linux Gurus:

Any idea how to allow a 19x P106-100 rig to OC in nvOC? I can't get my OC settings to apply though mining does work for all 19.

Suggestions appreciated!
PM me if you'd prefer.

-z

Hi! According to the same issue with all my P106-100 rigs, i suppose you need to do this:

1) check that you have set P106_100_FULL_HEADLESS_MODE="YES" in 1bash
2) check that you can control your rig without monitor attached (SSH or Teamviewer enabled)
3) disconnect monitor
4) run the following:
Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
sudo reboot

After the rig reboots, overclocking will work as supposed to. Sometimes i had to do number 4 again after reboot to make it working.
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.3 on: October 24, 2017, 10:36:11 AM
hi, all!

I'm using nvOC for a while and today got some rigs broken, tried to see what's wrong and got this error when launching nvidia-smi: "Failed to initialize NVML: Driver/library version mismatch". This happened to every nvidia rig that I tried to reboot. Never touched the drivers in nvOC distro, so I'm confused how this could happen... Does anyone have ideas? Is there any kind of autoupdater which could change something after reboot? How to disable it and make everything working again?
8  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] rxOC easy-to-use Linux AMD Mining v0012 on: October 16, 2017, 05:15:56 PM
TheNewEthlite, thanks to alko67bi - he gave the idea Smiley
9  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] rxOC easy-to-use Linux AMD Mining v0012 on: October 12, 2017, 02:00:27 PM
First all, Thank you very much for the awesome work you do!!

So,

Tried to put the DAG fix using the following:

#Install new ROCm Kernel:

wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
sudo sh -c 'echo deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main > /etc/apt/sources.list.d/rocm.list'
sudo apt-get update
sudo apt-get install rocm

#edit grub
sudo nano  /etc/default/grub
#2MB fragments for Ellesmere are enabled with a grub option:
GRUB_CMDLINE_LINUX="amdgpu.vm_fragment_size=9"

sudo update-grub
sudo reboot


The problem is the first GPU will now do about half speed while the other GPU's are running properly faster. Tried multiple times, different gpu's, etc, same results.

I know it's being updated in V13, anybody have a clue how to fix this first GPU problem in the meantime? I've just reverted back to untouched V12.

If anyone cares, my 580's run at about 25(no oc), with dag fix 27, but the first gpu will run at 14, would be nice to get them all to 27.

What happens if you run headless?  Is the first GPU still nerfed?

I did the same to apply dagfix, with the same effect on the GPU0, tried to run it headless and yes, it is the same slow without monitor attached. By the way I had the same problem with nvOC headless P106 rigs, and it was easily solved by reconfiguring xorg with nvidia tool when no monitor attached. Maybe reconfiguration is the right way here too, but I don't know how to do it with RX cards.

Issue with slow GPU0 solved by setting it's PCIe slot to Gen2 in BIOS. I had Gen1 for all slots before.
10  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] rxOC easy-to-use Linux AMD Mining v0012 on: October 09, 2017, 08:57:46 PM
First all, Thank you very much for the awesome work you do!!

So,

Tried to put the DAG fix using the following:

#Install new ROCm Kernel:

wget -qO - http://repo.radeon.com/rocm/apt/debian/rocm.gpg.key | sudo apt-key add -
sudo sh -c 'echo deb [arch=amd64] http://repo.radeon.com/rocm/apt/debian/ xenial main > /etc/apt/sources.list.d/rocm.list'
sudo apt-get update
sudo apt-get install rocm

#edit grub
sudo nano  /etc/default/grub
#2MB fragments for Ellesmere are enabled with a grub option:
GRUB_CMDLINE_LINUX="amdgpu.vm_fragment_size=9"

sudo update-grub
sudo reboot


The problem is the first GPU will now do about half speed while the other GPU's are running properly faster. Tried multiple times, different gpu's, etc, same results.

I know it's being updated in V13, anybody have a clue how to fix this first GPU problem in the meantime? I've just reverted back to untouched V12.

If anyone cares, my 580's run at about 25(no oc), with dag fix 27, but the first gpu will run at 14, would be nice to get them all to 27.

What happens if you run headless?  Is the first GPU still nerfed?

I did the same to apply dagfix, with the same effect on the GPU0, tried to run it headless and yes, it is the same slow without monitor attached. By the way I had the same problem with nvOC headless P106 rigs, and it was easily solved by reconfiguring xorg with nvidia tool when no monitor attached. Maybe reconfiguration is the right way here too, but I don't know how to do it with RX cards.
11  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019 on: September 06, 2017, 06:21:44 PM

Now all works fine including overclocking and powerlimits, just one trouble left - if I connect 8-th GPU, nvOS hangs on boot Sad

Allright, i've done with the hanging-on-boot problem on z270-p rig with eight gp106-100 onboard. When I discovered this issue for the first time I have tried to update BIOS right away, done it, and the problem persists. My mistake was that I've tried to update BIOS online from Asus server. Later I've discovered that online update's latest BIOS version is not the same as the latest BIOS version on their website. Only when 0810 version of BIOS was installed, my rig started to boot normaly with 8 GPUs connected.

So I suppose we should add this info about Asus z270-p to FAQ - nvOS works normally with 8 GPU on this motherboard only from BIOS ver.0810.

Also important current info about GP106-100 - in my case full headless rig with monitor never connected requires Xorg reconfigure to start mining:

Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
sudo reboot
12  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019 on: September 06, 2017, 12:43:46 PM

Motherboard H110, 13pc p106, monitor connected on board
I have about the same problem, but for some reason your decision didnít fit. I have one error


i get the same error if i have not enough permissions. Suppose "$sudo" at the beggining of the line in your case is wrong, you need to type just "sudo nvidia-xconfig ..."
13  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019 on: September 06, 2017, 10:47:21 AM
Anone managed to start NVOC version 19 with built-in  VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs

As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig.

I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen?

(I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time)

Code:
Sep  5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.

i also have following errors in syslog, in clean nvos019 install. I suppose it's kinda tails from previous usage of "SanDisk_Cruzer_Blade", because I've never used such device.

Code:
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: Startup finished in 7.010s (kernel) + 1min 30.221s (userspace) = 1min 37.231s.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.

Can anybody guess what to do to make this thing work? Smiley thanks in advance!

ok i'm talking with myself but this becomes useful to solve the problem Smiley
After a little research i've finally launched mining full headless rig of asus z270-p with 7 gp106-100 onboard. Problem was in xorg configuration, nvidia utility helped to solve it:

Code:
sudo nvidia-xconfig -a --cool-bits=28 --allow-empty-initial-configuration
sudo reboot

Now all works fine including overclocking and powerlimits, just one trouble left - if I connect 8-th GPU, nvOS hangs on boot Sad
14  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019 on: September 06, 2017, 06:21:54 AM
Anone managed to start NVOC version 19 with built-in  VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs

As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig.

I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen?

(I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time)

Code:
Sep  5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.

i also have following errors in syslog, in clean nvos019 install. I suppose it's kinda tails from previous usage of "SanDisk_Cruzer_Blade", because I've never used such device.

Code:
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/usb-SanDisk_Cruzer_Blade_4C530001260812105231-0:0-part1.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount: Job mnt-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device: Job dev-disk-by\x2did-usb\x2dSanDisk_Cruzer_Blade_4C530001260812105231\x2d0:0\x2dpart1.device/start failed with result 'timeout'.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start timed out.
Sep  6 02:13:06 m1-desktop systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-55184403759586FB.device.
Sep  6 02:13:06 m1-desktop systemd[1]: Dependency failed for /mnt/55184403759586FB.
Sep  6 02:13:06 m1-desktop systemd[1]: mnt-55184403759586FB.mount: Job mnt-55184403759586FB.mount/start failed with result 'dependency'.
Sep  6 02:13:06 m1-desktop systemd[1]: Startup finished in 7.010s (kernel) + 1min 30.221s (userspace) = 1min 37.231s.
Sep  6 02:13:06 m1-desktop systemd[1]: dev-disk-by\x2duuid-55184403759586FB.device: Job dev-disk-by\x2duuid-55184403759586FB.device/start failed with result 'timeout'.

Can anybody guess what to do to make this thing work? Smiley thanks in advance!
15  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019 on: September 05, 2017, 07:49:59 PM
Anone managed to start NVOC version 19 with built-in  VGA? I heared this version finally have a fix, for using on rigs built on GP106-100 GPUs

As I can see on the first page, it is still advised to start without monitor attached if you have only p106 in your rig.

I have tried to start full headless, with pure p106 mode enabled, but all I get are errors in logs, mining process doesn't start. Does anyone know why this could happen?

(I have asus z270-p with 8 p106-100, screen was attached only to modify bios settings as described for z270-a, usb stick was never attached with monitor at the same time)

Code:
Sep  5 15:13:51 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:51 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:51 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:51 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:51 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:51 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop lightdm[5561]: /etc/modprobe.d is not a file
Sep  5 15:13:52 m1-desktop lightdm[5561]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:52 m1-desktop lightdm[5561]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:52 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:52 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:52 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop gpu-manager[5613]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:54 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:54 m1-desktop systemd[1]: Started Light Display Manager.
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop lightdm[5640]: /etc/modprobe.d is not a file
Sep  5 15:13:54 m1-desktop lightdm[5640]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:54 m1-desktop lightdm[5640]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Unit entered failed state.
Sep  5 15:13:54 m1-desktop systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep  5 15:13:55 m1-desktop systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Sep  5 15:13:55 m1-desktop systemd[1]: Stopped Light Display Manager.
Sep  5 15:13:55 m1-desktop systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: /etc/modprobe.d is not a file
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Sep  5 15:13:56 m1-desktop gpu-manager[5692]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Sep  5 15:13:56 m1-desktop systemd[1]: Started Detect the available GPUs and deal with any system changes.
Sep  5 15:13:56 m1-desktop systemd[1]: Starting Light Display Manager...
Sep  5 15:13:57 m1-desktop systemd[1]: Started Light Display Manager.
Pages: [1]
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!