Author

Topic: [ mining os ] nvoc - page 161. (Read 418546 times)

member
Activity: 83
Merit: 10
October 30, 2017, 06:12:46 PM

...

Same PSU too

...

Same bios settings


lol ... going crazy ...



It's also possible that it's dumb luck... you happened to put mostly lower-performing cards in one rig, and mostly better-performing cards in the other.

If that's it, and you swap four of five of the cards, you should start to see things equalize....
newbie
Activity: 36
Merit: 0
October 30, 2017, 05:57:55 PM

Same PSU, too? You can tell if they are using identical power with:

Code:
nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too


Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...



Removed all cards and restart rig with only 1 card direct connect to motherboard no risers,
Same low speed, 18-19 MH/s on eth

do you know what memory types are on the other 1060s?
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
October 30, 2017, 05:57:09 PM

Same PSU, too? You can tell if they are using identical power with:

Code:
nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too


Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...



Removed all cards and restart rig with only 1 card direct connect to motherboard no risers,
Same low speed, 18-19 MH/s on eth
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
October 30, 2017, 05:52:24 PM
Maybe its me but the speeds to download the OS are incredibly slow. I built a torrent and I am seeding it from my server and personal desktop here: https://www.cryptocurrencyfreak.com/2017/10/30/nvoc-mining-os-torrent/

Feel free to help seed!

Is this 1.3 or the name is wrong ?
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
October 30, 2017, 05:41:03 PM

Same PSU, too? You can tell if they are using identical power with:

Code:
nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.

Same PSU too


Are all the BIOS settings the same? Same on the PCI speeds, etc?

Same bios settings


lol ... going crazy ...

newbie
Activity: 35
Merit: 0
October 30, 2017, 05:25:33 PM
To prevent automatic updates in the future:

use your favorite editor, open /etc/apt/apt.conf.d/10periodic and change:

Code:
APT::Periodic::Update-Package-Lists "1";

To:

Code:
APT::Periodic::Update-Package-Lists "0";


and /etc/apt/apt.conf.d/20auto-upgrades
Code:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

to

Code:
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";


D

ps: Seriously, why was this ON?

Very nice suggestion Doodkeen,

This is a community driven project and fullzero is doing the best job ever without asking for a dime (unlike other Linux mining distros)
Some times in the middle of the road we miss some small points that are so obvious to others,

So I'm kindly ask every Linux Guru here to do their best to look for improvements and fixes for nvOC
Feel free to PM me or post in forum any suggestion you have.

Thank you all.


Yep, please feel free and provide the valuable feedback, so that we can make nvOC even better.

Coming to the error, no one expected this sort of failure on this scale!! Hope we identify these sort of issues bit earlier.

I think the problem is while Nvidia driver was updating wdog restarted the rig because of low utilization and that cause a miss configured Nvidia driver,
I think solution is to prevent wdog from restarting the rig if dpkg is running.
Papampi, you are absolutely right  Smiley


I had this happen to 2 of my rigs.  I will change all the update settings for -1.4 except security updates.  My bad.  
fullzero, is there some way that I could completely disable all updates on nvOC:
- disable automatic downloads of updates (drivers, system, nvOC)
- disable automatic installation of updates (drivers, system, nvOC)

I have a rig behind a firewall and absolutely no important data on a nvOC rig, so all I care is about stability.
And stability is more fragile because of USB key usage.
The logging is disabled by default, so there would be no writing to the USB key if I would disable updates.

The nvOC is pretty stable even now, but I think that disabling all updates would help with the stability of the system.

Of course I would also periodically update USB key with the whole image of nvOC, but only every month or so, when you publish the new version of stable nvOC.


I have disabled all updates on -1.4; it does have logs.  I will work on a global long variable implementation ( LOGS="ON"  or OFF ) for the next version
wow, fullzero, you are the best.
Thank you for the time you take, to consider these requests.
member
Activity: 224
Merit: 13
October 30, 2017, 05:24:30 PM
I'm going crazy ...


Today I setup 2 new fully identical rigs.
Both biostar btc-250 pro, core i5 6100, 12xGPU Zotac 1060, same power, ram, ssd, ...

Problem is one of them hashes much less than the other

Any ideas ?


Same PSU, too? You can tell if they are using identical power with:

Code:
nvidia-smi --query-gpu=temperature.gpu,fan.speed,power.draw,power.limit --format=csv

Hope this helps.
member
Activity: 83
Merit: 10
October 30, 2017, 05:18:28 PM
I'm going crazy ...


Today I setup 2 new fully identical rigs.
Both biostar btc-250 pro, core i5 6100, 12xGPU Zotac 1060, same power, ram, ssd, ...

Problem is one of them hashes much less than the other

Equihash

Code:
GPU0: 270 Sol/s GPU1: 271 Sol/s GPU2: 272 Sol/s GPU3: 271 Sol/s GPU4: 275 Sol/s GPU5: 274 Sol/s GPU6: 273 Sol/s GPU7: 267 Sol/s GPU8: 270 Sol/s GPU9: 273 Sol/s GPU10: 273 Sol/s GPU11: 277 Sol/s 
Total speed: 3266 Sol/s

Code:
GPU0: 256 Sol/s GPU1: 261 Sol/s GPU2: 259 Sol/s GPU3: 268 Sol/s GPU4: 262 Sol/s GPU5: 259 Sol/s GPU6: 266 Sol/s GPU7: 262 Sol/s GPU8: 258 Sol/s GPU9: 271 Sol/s GPU10: 264 Sol/s GPU11: 260 Sol/s 
Total speed: 3146 Sol/s

Ethahsh:

Code:
m 01:03:35|ethminer Mining on #a77fc9dd… : 229.11MH/s [A19+1:R0+0:F0] 


Code:
m 01:03:58|ethminer Mining on #5355b83e… : 264.77MH/s [A98+0:R0+0:F0] 

As you can see its not a one gpu fault but all gpus hashing less than the other  Shocked
Swapped ssd drives to see if its a OS image problem, same problem on the lower rig

Any ideas ?


Are all the BIOS settings the same? Same on the PCI speeds, etc?
newbie
Activity: 9
Merit: 0
October 30, 2017, 05:04:00 PM
I'm getting a stratum authentication failed when trying to mine GRS. Anyone have a solution to this?
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
October 30, 2017, 04:57:45 PM
...Swapped ssd drives to see if its a OS image problem, same problem on the lower rig...
The issue followed the drive or was persistent to that hw?

If it was the drive I would never ask the question ...
And gpus are all fully utilize :

Code:
GPU UTILIZATION:  100 100 99 99 99 99 100 99 100 100 99 100
hero member
Activity: 1092
Merit: 552
Retired IRCX God
October 30, 2017, 04:53:08 PM
...Swapped ssd drives to see if its a OS image problem, same problem on the lower rig...
The issue followed the drive or was persistent to that hw?
full member
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
October 30, 2017, 04:39:49 PM
I'm going crazy ...


Today I setup 2 new fully identical rigs.
Both biostar btc-250 pro, core i5 6100, 12xGPU Zotac 1060, same power, ram, ssd, ...

Problem is one of them hashes much less than the other

Equihash

Code:
GPU0: 270 Sol/s GPU1: 271 Sol/s GPU2: 272 Sol/s GPU3: 271 Sol/s GPU4: 275 Sol/s GPU5: 274 Sol/s GPU6: 273 Sol/s GPU7: 267 Sol/s GPU8: 270 Sol/s GPU9: 273 Sol/s GPU10: 273 Sol/s GPU11: 277 Sol/s 
Total speed: 3266 Sol/s

Code:
GPU0: 256 Sol/s GPU1: 261 Sol/s GPU2: 259 Sol/s GPU3: 268 Sol/s GPU4: 262 Sol/s GPU5: 259 Sol/s GPU6: 266 Sol/s GPU7: 262 Sol/s GPU8: 258 Sol/s GPU9: 271 Sol/s GPU10: 264 Sol/s GPU11: 260 Sol/s 
Total speed: 3146 Sol/s

Ethahsh:

Code:
m 01:03:35|ethminer Mining on #a77fc9dd… : 229.11MH/s [A19+1:R0+0:F0] 
Code:
m 01:03:58|ethminer Mining on #5355b83e… : 264.77MH/s [A98+0:R0+0:F0] 

As you can see its not a one gpu fault but all gpus hashing less than the other  Shocked
Swapped ssd drives to see if its a OS image problem, same problem on the lower rig

Any ideas ?
member
Activity: 117
Merit: 10
October 30, 2017, 04:24:02 PM
why i can not run telegram script from terminal? thanks

m1@19_1_4:~$ ./telegram
-bash: ./telegram: Permission denied


Try bash telegram

The file does not have exec permission
member
Activity: 83
Merit: 10
October 30, 2017, 03:57:28 PM
Maybe its me but the speeds to download the OS are incredibly slow. I built a torrent and I am seeding it from my server and personal desktop here: https://www.cryptocurrencyfreak.com/2017/10/30/nvoc-mining-os-torrent/

Feel free to help seed!


I've posted the file over at the group's Discord (https://discord.gg/8YDFEvY) - feel free to grab it there and post it on your site.

I also have the torrent file posted here for anyone who wants to participate:

http://s000.tinyupload.com/index.php?file_id=00585421597763893895

That's nvOC_v0019_1.4_zip in a torrent; a couple of us are already seeding. (It may or may not DL faster for you than the Google link.)
newbie
Activity: 15
Merit: 0
October 30, 2017, 03:36:38 PM
Hey Everyone,

If you have more than 16 GPUs, the key is to have no more than 16 cards listed in the ServerLayout part of your xorg.conf. Those are the ones that will OC. You will have all 19 listed in the Device and Screen sections and the three that remain will run but won't OC. If you add a 17th under ServerLayout, the miner will not be able to OC any because X will crash when it starts when it hits the 17th card.

If you look at nvidia-smi output, you *should* see, at the bottom an instance of X AND a miner process for each GPU. The ones that only have a miner process attached cannot be OC'd. For me this is GPUs 17, 18, 19.

I've had to edit my rclocal.sh to copy a custom xorg.conf from ~ into /etc/X11 to keep it correct. The problem (for me) is that the script that auto creates the xorg.conf won't stop at 16 in the ServerLayout section and thus makes it so that X won't start and thus none of them OC.

Also, for my Gigabyte P106 cards (I'm running 19) for those first 16 (which will OC), I've not been able to get beyond 100 core and 250 mem, producing 18-18.1 MH/s for ETH only.

Let me know if this helps!
-z

```
# xorg.conf for 19 P106 on Asus ME that gets me 16 OC and 3 non-OC

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidiascreen-00"
    Screen 1 "nvidiascreen-01"
    Screen 2 "nvidiascreen-02"
    Screen 3 "nvidiascreen-03"
    Screen 4 "nvidiascreen-04"
    Screen 5 "nvidiascreen-05"
    Screen 6 "nvidiascreen-06"
    Screen 7 "nvidiascreen-07"
    Screen 8 "nvidiascreen-08"
    Screen 9 "nvidiascreen-09"
    Screen 10 "nvidiascreen-10"
    Screen 11 "nvidiascreen-11"
    Screen 12 "nvidiascreen-12"
    Screen 13 "nvidiascreen-13"
    Screen 14 "nvidiascreen-14"
    Screen 15 "nvidiascreen-15"
    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-00"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-00"
    Device "nvidia-00"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-01"
    Device "nvidia-01"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-02"
    Device "nvidia-02"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-03"
    Device "nvidia-03"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-04"
    Device "nvidia-04"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-05"
    Device "nvidia-05"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-06"
    Device "nvidia-06"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-07"
    Device "nvidia-07"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-08"
    Device "nvidia-08"
    Option "Coolbits" "28"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-09"
    Driver "nvidia"
    BusID "PCI:12@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-09"
    Device "nvidia-09"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-10"
    Device "nvidia-10"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

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

Section "Screen"
    Identifier "nvidiascreen-11"
    Device "nvidia-11"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-12"
    Driver "nvidia"
    BusID "PCI:15@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-12"
    Device "nvidia-12"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-13"
    Driver "nvidia"
    BusID "PCI:16@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-13"
    Device "nvidia-13"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-14"
    Driver "nvidia"
    BusID "PCI:17@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-14"
    Device "nvidia-14"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-15"
    Driver "nvidia"
    BusID "PCI:18@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-15"
    Device "nvidia-15"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-16"
    Driver "nvidia"
    BusID "PCI:19@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-16"
    Device "nvidia-16"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-17"
    Driver "nvidia"
    BusID "PCI:20@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-17"
    Device "nvidia-17"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Device"
    Identifier "nvidia-18"
    Driver "nvidia"
    BusID "PCI:21@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidiascreen-18"
    Device "nvidia-18"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "Coolbits" "28"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

```
newbie
Activity: 27
Merit: 0
October 30, 2017, 03:08:24 PM
why i can not run telegram script from terminal? thanks

m1@19_1_4:~$ ./telegram
-bash: ./telegram: Permission denied
member
Activity: 117
Merit: 10
October 30, 2017, 02:28:04 PM
This is a method to unpack Nvoc_v0019_1.4's image file to a windows file system:
1. Unzip nvOC_v0019_1.4
2. Flash the extrated file .img file to hdd, ssd or pendrive (Usually with HDDRawCopy)
3. Download DiskInternals Linux Reader from https://www.diskinternals.com/linux-reader/
4. Run DiskInternals Linux Reader and go to your drive with Nvoc
5. Use "Save" option to copy files from Linux Nvoc file system to windows file system (it takes a while)

Method should work with any Nvoc version

Hope helps
member
Activity: 83
Merit: 10
October 30, 2017, 01:41:51 PM
Maybe its me but the speeds to download the OS are incredibly slow. I built a torrent and I am seeding it from my server and personal desktop here: https://www.cryptocurrencyfreak.com/2017/10/30/nvoc-mining-os-torrent/

Feel free to help seed!

OK, wow... that's a lot of trackers. You handle that end, I'll help seed!



Correction: I was able to copy your list of trackers easily & create the torrent for v0019-1.4. I'm seeding. Not the world's fastest seedbox, but I run it 24x7.

I've posted the file over at the group's Discord (https://discord.gg/8YDFEvY) - feel free to grab it there and post it on your site.
member
Activity: 83
Merit: 10
October 30, 2017, 01:02:24 PM
Maybe its me but the speeds to download the OS are incredibly slow. I built a torrent and I am seeding it from my server and personal desktop here: https://www.cryptocurrencyfreak.com/2017/10/30/nvoc-mining-os-torrent/

Feel free to help seed!

Nice idea, but you decided to torrent to the 1.3 beta shortly after the 1.4 version came out!

I have 1.4 and would put it up and seed, but I don't have a private tracker.

Can find an appropriate public tracker for open-source software and put it up, there? What tracker did you use?

Also, 1.3 and 1.4 are Beta... I'd like to make sure we torrent the current Stable version, as well.

[EDIT]

I checked what trackers you set up:

Code:
udp://tracker.skyts.net:6969/announce
udp://tracker.safe.moe:6969/announce
udp://tracker.piratepublic.com:1337/announce
udp://tracker.pirateparty.gr:6969/announce
udp://tracker.coppersurfer.tk:6969/announce
udp://tracker.leechers-paradise.org:6969/announce
udp://allesanddro.de:1337/announce
udp://9.rarbg.com:2710/announce
udp://p4p.arenabg.com:1337/announce
http://p4p.arenabg.com:1337/announce
udp://tracker.opentrackr.org:1337/announce
udp://public.popcorn-tracker.org:6969/announce
http://tracker.opentrackr.org:1337/announce
udp://tracker2.christianbro.pw:6969/announce
udp://tracker1.xku.tv:6969/announce
udp://tracker1.wasabii.com.tw:6969/announce
udp://tracker.zer0day.to:1337/announce
udp://peerfect.org:6969/announce
http://91.218.230.81:6969/announce
http://tracker.mg64.net:6881/announce

OK, wow... that's a lot of trackers. You handle that end, I'll help seed!

newbie
Activity: 15
Merit: 0
October 30, 2017, 12:48:02 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?

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

I have exactly the same situation (nvOs version 0019v1.3).
I have rig made only of p106-100. With monitor attached to mobo output the xorg.conf is overwritten on each reboot. If I modify xorg.conf with the commands given above, switch to remote ssh mode and reboot with monitor disconnected, the file xorg.conf is not being overwritten, but the mining process does not start. I am also unable to start it manually with 'bash 1bash' (which doesn't work for me at all, but that's another story)

Please help to solve the p106-100 overclocking problem once and for all. I am struggling with it for days now and it's driving me crazy, especially that some people write that it works for them!

Could anybody answer to the p106-100 overclocking problem please?


Below is my post where I solve this issue after very long time investigation and search. Maybe it will help.

Hi fullzero, Hi Guys,

I've found the solution. Also, I have changed to "YES" the IAmNotAJeep_and_Maxximus007_WATCHDOG. It's working fine around one hour. I'll monitor and let you know, if something new will come up.
Below is the steps:

1. Changes in 1bash:

LOCALorREMOTE="REMOTE"
SSH="YES"
P106_100_FULL_HEADLESS_MODE="NO"


2. Reboot

NO Monitors starting from now!!!

3.
sudo -i
rm /etc/X11/xorg.conf
nvidia-xconfig -a --allow-empty-initial-configuration --cool-bits=28 --use-display-device="DFP-0" --connected-monitor="DFP-0"
reboot

4. Change in 1bash:

__CORE_OVERCLOCK=100
MEMORY_OVERCLOCK=500 (getting 22 Mh/s)

Need to check in process tab. for all GPU's should be exists "Xorg - /usr/lib/xorg/Xorg"

-------------
m1@miner1:~$ nvidia-smi
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1073    G   /usr/lib/xorg/Xorg                              30MiB |
|    0      1646    G   compiz                                          11MiB |
|    0      6160    C   /home/m1/eth/Genoil-U/ethminer                2253MiB |
|    1      1073    G   /usr/lib/xorg/Xorg                               7MiB |
|    1      6160    C   /home/m1/eth/Genoil-U/ethminer                2253MiB |
|    2      1073    G   /usr/lib/xorg/Xorg                               7MiB |
|    2      6160    C   /home/m1/eth/Genoil-U/ethminer                2253MiB |
|    3      1073    G   /usr/lib/xorg/Xorg                               7MiB |
|    3      6160    C   /home/m1/eth/Genoil-U/ethminer                2253MiB |

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


Hope this will help also to others.








Jump to: