Quote from: lards on August 24, 2017, 05:06:31 PM

Quote from: fullzero on August 24, 2017, 04:56:08 PM

Quote from: lards on August 24, 2017, 04:10:57 PM

Quote from: fullzero on August 24, 2017, 04:00:24 PM

Quote from: lards on August 23, 2017, 02:49:10 PM

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?

When remoting in; it is important to realize that you can SSH in before all system init has occurred. Think of when you are watching nvOC load on a monitor. When Ubuntu is loading; there is a period where you cannot use the keyboard or mouse / guake has not started / 2unix (via gnome-terminal) hasn't launched. You can SSH in before this interval in system init. If you do, this act alone may change the init sequence, or it might only be launching bash earlier which may do this.

It could also be something else entirely; such as x intermittently launching or not launching which is causing the problem. This is the type of thing It will be much easier to isolate with my own p106-100 test rig.

For now I would try waiting longer after reboot before SSHing into the rig and seeing if that resolves the problem. Let me know how it goes.

I was trying to reboot away from the rig by turning on/off the power plug so I wasn't even connecting via SSH at all. Waited for over 15 minutes, no reported rate on pool made me think that it hasn't started so to turn it on I had to come to the home network of the rig but after another reboot it started fine with no errors after starting 1bash.

When 1bash is started automatically no errors appear at all and OC works fine but mostly it doesn't autostart and I have to use console to start it , it reports problems with replacing xorg + some other errors and OC doesn't work.

Maybe that info would help you to work out why does it do such thing.

Thanks for your reply.

In that case, it is probably x intermittently launching or not launching most likely do to modification of the xorg.conf. It is probably best to only conditionally change the xorg; but making / testing a configuration that works more smoothly will be much easier with my own p106-100 rig. I set the current p106-100 1bash to always modify the xorg.conf to avoid potential infinite boot loop problems vs only having a single boot that doesn't OC.

So what would you suggest to get rid of this problem? To reboot until the xorg and the miner start correctly or can I modify the 1bash somehow to make sure I don't have to reboot 5 times in a row to get it up and running?

I made a conditionally updating 1bash (in addition to lowering the default OC on the original p106-100) for you to try. There is a download link on the OP; let me know if it works better.