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

Hey everyone.

As fullzero has already posted the instruction on OC of P106-100 rigs, I can confirm that this works and i am now using cc -200 and mc 1300(was stable for over 10 hours )  , I think it can go to 1400-1500 but I am in the process of testing the 12th card since it caused me issues everytime i connected before.

Also I have another question to ask fullzero : When I start the rig it sometimes doesn't swap the xorg files and giving me errors which lead to the OC being off(Sometimes even after autoreboot it doesn't autostart 1bash). This solves after a couple of reboots but I can't figure out how to reboot it so the OC will work and the miner also would start automatically since sometimes when I turn it on the miner doesn't autostart and this leads to further errors and no OC available. So far I haven't found any other problems so thank you again for solving OC issue.

Can you advise on what should I do in that case?

For people want to have log in direct terminal with perma update a simply command do the job and let u know which GPU fail and why
Open a terminal and type

Try a lower memory overclock offset: I get these errors when I overclock too much. To confirm, check the output of "dmesg" in the terminal; if you get messages like these:

[139035.343237] NVRM: Xid (PCI:0000:02:00): 31, Ch 0000001b, engmask 00000101, intr 10000000

Most probably that's the issue. If you get these messages but with a different Xid (in this example it's 31), report here, as each code has a different meaning.

Thank you so much for the quick respond. I'm getting GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered in claymore and CUDA failure 77: an illegal memory access was encountered ; in Genoil, after a few seconds of mining.

Also in ZEC it says CUDA: Device: 3 Thread exited with code: 77
or CUDA: Device: 3 Thread exited with code: 64

Am I doing something wrong?


I will make a donation for your lovely p106 1bash.

best regards

UPDATE :

Now I'm not getting the above error but get different issue; main terminal says mining starts in guake terminal; but on guake 'There is no screen to be resumed matching miner' error appears.

Will compare it with latest 1bash and see if there are any differences.

EDIT :

Sorry, I've overlooked, I'm still getting the above error and on guake getting this 'There is no screen to be resumed matching miner'

for 2, adding some reminder texts is fine, but don't force user to change password.

I've changed the time zone long back to my local time (GMT London), the profit switching was working even after the time zone change! Haven't touched/changed anything related to profit switching!!

Can u check date and hours on your linux / network ?
Failed certificate verify error came from this habitually

Any one had this sort of issue while using SALFTER_NICEHASH_PROFIT_SWITCHING ??

Feature Request:
1-
Add IP address to hostname at first boot to setup individual names for each rig.
So rigs names will become : m1-desktop-101 , m1-desktop-102 ....
I know we can edit our hostnames in /etc/hosts and /etc/hostanme.
It just make nvOC looks better at first start  

2-
Remind user to change the m1 password at first boot.
Its not safe.

So that specific rig is gigabyte Z270p-d3 mobo, 4 gb ballistix ram, 32 gb lexar usb, intel g4400 processor, 2 gigabyte gtx 1080ti and 1 1060 mini, and gold 750 power supply. nvOC v17, only changes made are to powerlimits, 1080's at 180w and 1060 at 125w (my buddy had me do that, I don't know much about setting them up for efficiency)

Reimaged multiple times and every time it tells me the error about the power limit and persistence mode, and always throws the teamviewer error. Only once has it actually kicked the power limit and just ran up to 250 on its own

Great!! But don't thank me for identifying this invalid entry in /etc/fstab, it was the merit of another user, as I mentioned, but I forgot his username! Nevertheless, Fullzero is aware of this, and said it will be fixed in v19.

Wow. Thank you dbolivar!

The slow boot time has always been my only issue with nvOC. Especially when I've got a sick riser that I'm hunting for. I commented out the swap line in /etc/fstab and BAM! It was like a rocket ship booting up.

SO loving this OS now. Even more than before! Thank you again FullZero for this awesome OS.

Not to minimize your efforts on enabling swap, but the long boot time happens not because there's no swap, but because there's a swap entry in /etc/fstab that points to an invalid (non-existent) partition. Therefore, some init scripts invoked by systemd at boot time enter a wait loop, just in case this partition becomes available after some time. This invalid entry in /etc/fstab has been identified by another user here in the forum some posts ago, and just commenting it out solves the long boot time.

Now, if someone actually needs a swap partition, that's a different story... From my experience (and some other users as well), with 4 GB+ of RAM, there's no need of swap. I kept monitoring my RAM usage, even with Claymore's dual-mining, and it never came close to requiring swap. Now, going a bit more technical, if you were using your operating system in a different scenario (heavy multitasking, VM host, database server, desktop system where you need suspend-to-RAM etc.), you *may* benefit of a swap space even with enough RAM (and in case of suspend-to-RAM, you do need it, and at least the same size of your installed RAM), because the operating system may decide that it would be best to swap old memory pages to disk instead of purging them from RAM (and this "swappiness", in Linux, can actually be defined at runtime, i.e. you can instruct the kernel how agressively it should swap memory pages to disk). I don't think mining fits in these scenarios, and a swap space in a very slow medium like USB stick doesn't make much sense (I know in your case you used a SSD, but that's an exception). In Windows, Claymore requires a huge swap space because of different reasons (and Windows virtual memory management is different than in Linux).

thank you !!! You guys are the best !!!

Yeap

if I use a server psu can it supply power to 006c version riser by the 6 pin slot? (without using the sata adapter)

hi,
here is what you need to do
for now you must have one GTX card it is not possible with 13* p106-100 card only 12 cards.

1. connect via GTX vga port its a must for now
2. open 1bash file and change rest
3. GPUPowerMizerMode_Adjust="YES"
4. # Set PowerMizerMode
GPUPowerMizerMode=1

5.
find this (bottom) and change only what i told you the CC and MC.

REBOOT_TIMEOUT_IN_MINUTES=720   # every 24 hours

POWERLIMIT="NO"                 # YES NO

POWERLIMIT_WATTS=115

__CORE_OVERCLOCK=95 ( THIS is what i set for my GTX only as this will only apply to GTX )
MEMORY_OVERCLOCK=950 ( THIS is what i set for my GTX only as this will only apply to GTX )

MANUAL_FAN="NO"                # YES NO

6. set GPU 1-12 via powermizer in the "nvidia x server settings" i put CC +99 and MC +1200 thats as stable as i got it 296-299 MH/s

7. Note every time you restart your rig you need to put setting in powermiser again only for GPU 1-12

hope this helps, ask if you need anything i can maybe help with.
------------------------------------------------------------------------------------------------------
if you want to donate here is my ETH: 0x1a83233f2dfFB6902A7875104ef1E00710Ef00Db

I'm ready to make a donation too, if the issue with P106 cards is finally solved, but it's been so long already ...

check your PM.  i send new acces for my rig.