Author

Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 328. (Read 835838 times)

legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
motherboard TB250 PRO
i was not able to install SMOS on this MB ....

For this motherboard you need to user this motherboard version:
Use this bios firmware version: B25CF330.BSS

Then it should work like a charm.
Can you write to email and tell me what happened with this last update ?
[email protected]
Introduce yourself and please describe whats going on.
legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
Drop from 950w to 810w with 890mV,great:)
Also this is THX to Wolf0 tool which accually works with dagfix kernel Tongue
legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
OMG My 8 rigs autoupdate and shutdown after 30 min, 12 RX 560 and H110 pro btc+.

[07:28:17] GPU0: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU0: Attempting to restart
[07:28:17] Thread 0 still exists, killing it off
[07:28:17] GPU2: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU2: Attempting to restart
[07:28:17] GPU5: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU5: Attempting to restart
[07:28:17] GPU10: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU10: Attempting to restart
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 0 restarted
[07:28:18] Thread 2 still exists, killing it off
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 2 restarted
[07:28:18] Thread 5 still exists, killing it off
[07:28:20] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:20] Thread 5 restarted
[07:28:20] Thread 10 still exists, killing it off
[07:28:21] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:21] Thread 10 restarted
[07:28:44] Accepted 58436698 Diff 190K/120K GPU 7
[07:28:50] Accepted 318c2b88 Diff 339K/120K GPU 6
[07:29:51] Accepted 2299ae17 Diff 485K/120K GPU 6
(5s):4.096K (avg):0.02412h/s | A:15240168 R:0 HW:0 WU:0.000/m
How do I roll back an update?
And I still have not been able to correctly launch all 13 cards(rx560) on the H110 motherboard
HELP!!!
But there Dagfix isnt auto update, its optional, you have click it first to make it work.
Also i fixed RX Oc script so that might cause it if you have different OC clocks for each GPU and also integrated turned on gpu.
newbie
Activity: 16
Merit: 0
Drop from 950w to 810w with 890mV,great:)
legendary
Activity: 2660
Merit: 1096
Simplemining.net Admin
"OK guys. I have some progress in undervolting and it might accually work.
If you guys want time frame then in next 2-6 days it should be released
."
Can't wait anymore...
When will we be able to handle speed and voltage properly   Huh
As soon as he finishes ripping off the (buggy) voltage control code from EthOS. Tongue
Wolf0 why so rude ?
Why do you think i ripped off anything from ETHOS ?
Because we dont. We never copied anything from ETHOS. and thats a fact.
I dont know if vice versa it works the same but i am judging as i dont look at their code and scripts.
We are using your tool that i paid you for.
Why are you so jealous anyway Wolf0 - did i do something to You ?
You told me many things about Bios and undervolting but why so rude ?


Anyway there was update with few things
RX OS dagfix undervolting + Nvidia adjustments Smiley
In some rigs you can see now red uptional update (if you dont hae dagfix RX OS version already). This will upgrade your rig to dagfix kernel - so you will again see restored hashrate but you will be also able to do undervolting. Be carrefoul and read all info about it becasue update can just simply not work on your rig.
Also fixed OC script for syntax 1000,1050,1100 in case when Intel GPU was trying to eat first value.
Nvidia: If you had problem with Nvidia Rigs (slow speed or OC didnt worked) just reboot your rig and it should now be working ok Smiley
Especially some p106-090 cards which had 2MH/s
newbie
Activity: 25
Merit: 0
I try to test the undervolting with my 11x RX580, Asrock 110.

The card bios need to have the factory mV settings, like this (my original backup):
https://gyazo.com/01dbd07f38198fd6e5076c027653e440


Until now I did the undervolting directly in card-bios, so I have lower wattage.
https://gyazo.com/6e882a10110e923b83ad2177ca4f4ec6


Also I have now flashed on the cards the second (lower mV directly in bios). I setup in dashboard/overclocking nothing than 1000mV than 800mV to test,
but the result is always the same, 2130Watt from Wall with 11x RX580.
smOS dont can to overwrite the modified bios, right?

jr. member
Activity: 74
Merit: 1
Just started using simple mining and noticed there might be a glitch. When I turn off my monitor all my settings go haywire. Does the software require a monitor hooked up at all times and turned on to work properly. Seems like all kinds of bad things happen when the bootable flash drive operating system cant detect a monitor to your rig.
sr. member
Activity: 366
Merit: 250
OMG My 8 rigs autoupdate and shutdown after 30 min, 12 RX 560 and H110 pro btc+.

[07:28:17] GPU0: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU0: Attempting to restart
[07:28:17] Thread 0 still exists, killing it off
[07:28:17] GPU2: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU2: Attempting to restart
[07:28:17] GPU5: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU5: Attempting to restart
[07:28:17] GPU10: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU10: Attempting to restart
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 0 restarted
[07:28:18] Thread 2 still exists, killing it off
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 2 restarted
[07:28:18] Thread 5 still exists, killing it off
[07:28:20] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:20] Thread 5 restarted
[07:28:20] Thread 10 still exists, killing it off
[07:28:21] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:21] Thread 10 restarted
[07:28:44] Accepted 58436698 Diff 190K/120K GPU 7
[07:28:50] Accepted 318c2b88 Diff 339K/120K GPU 6
[07:29:51] Accepted 2299ae17 Diff 485K/120K GPU 6
(5s):4.096K (avg):0.02412h/s | A:15240168 R:0 HW:0 WU:0.000/m


How do I roll back an update?


And I still have not been able to correctly launch all 13 cards(rx560) on the H110 motherboard

HELP!!!

just flash usb once again
sr. member
Activity: 440
Merit: 250
wow this is the 2nd time i would bring this topic again - performing update on production environment without notifying users!?
When the new update hit i was lucky to be around the machine, it went from 1200W to 1600W and i was lucky my PSUs did not blow.

@Tytanick - last time long time ago you did something similar and we discussed it that it's not right approach and you agreed, what happened today ?
newbie
Activity: 14
Merit: 0
AMD RX 570 with dag fix works perfect! 950W in dual mode @ 6 GPUs. Undevolting @ 880 mV stable.

I'm before migrating to SMOS on my other RIGs is there possible to define different undevolting values for any cards like OC?
newbie
Activity: 10
Merit: 0
NV 1127 Fixed my 1060 overclock! Had to reboot after it updated, but now it works again. Thanks!
newbie
Activity: 27
Merit: 0
@ tytanic - so it is still the same old DAGFIX which causes also more power Consuption ?

newbie
Activity: 1
Merit: 0
OMG My 8 rigs autoupdate and shutdown after 30 min, 12 RX 560 and H110 pro btc+.

[07:28:17] GPU0: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU0: Attempting to restart
[07:28:17] Thread 0 still exists, killing it off
[07:28:17] GPU2: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU2: Attempting to restart
[07:28:17] GPU5: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU5: Attempting to restart
[07:28:17] GPU10: Idle for more than 2 minutes, declaring SICK!
[07:28:17] GPU10: Attempting to restart
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 0 restarted
[07:28:18] Thread 2 still exists, killing it off
[07:28:18] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:18] Thread 2 restarted
[07:28:18] Thread 5 still exists, killing it off
[07:28:20] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:20] Thread 5 restarted
[07:28:20] Thread 10 still exists, killing it off
[07:28:21] Initialising kernel cryptonight.cl with nfactor 10, n 1024
[07:28:21] Thread 10 restarted
[07:28:44] Accepted 58436698 Diff 190K/120K GPU 7
[07:28:50] Accepted 318c2b88 Diff 339K/120K GPU 6
[07:29:51] Accepted 2299ae17 Diff 485K/120K GPU 6
(5s):4.096K (avg):0.02412h/s | A:15240168 R:0 HW:0 WU:0.000/m


How do I roll back an update?


And I still have not been able to correctly launch all 13 cards(rx560) on the H110 motherboard

HELP!!!
newbie
Activity: 21
Merit: 0
The way these guys work, this should be fixed soon so you guys should not panic.
But this is a really big issue though, this needs a fix as soon as possible priority number 1

Didn't try yet, but can you revert back to normal drivers after update?
newbie
Activity: 1
Merit: 0
@tytanik - i experience the same issue issue like most of users with NV and more cards.
H110+ 13 x P106 setup, found everything from the start, have the following problems:
1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something.
2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.

So how to fix those nonsense reboots ?

Yes, please do let us know how to fix these constant reboots on H110+ 13 x 1070 setups. Thank you.

@tytanik I experience the same issue and my 2 cents are, that the issue is a side-effect from server side changes for v1125 where you fixed some OC stuff for RX cards, but now configuration files for NV cards are not properly generated anymore from settings that perfectly worked before.

Following message appears when trying to apply the OC settings:

Invalid MIT-MAGIC-COOKIE-1 key Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: connection refused

ERROR: The control display is undefined: please run `nvidia-settings --help`for usage information.


It would be nice to see a fix for this issue! Thx a lot!
newbie
Activity: 10
Merit: 0
Same here. 1060's do not overclock, but the RX core undervolting is working!
newbie
Activity: 18
Merit: 0
Nvidia overclock broken for me also. 13 1070s h110 pro btc+
newbie
Activity: 14
Merit: 0
Overclocking nVidia stopped working today with the latest update.

SCREEN DUMP:


Available core offset for GPU 5 is in
Applying CoreOffset:
Applying PowerLimit: 150 watt for GPU 5
Applying CoreOffset: 150 MemoryOffset: 1000 for GPU 6 with GPU Type: 3
Invalid MIT-MAGIC-COOKIE-1 keyFailed to connect to Mir: Failed to connect to ser
ver socket: No such file or directory
Unable to init server: Could not connect: Connection refused

ERROR: The control display is undefined; please run `nvidia-settings --help`
       for usage information.
legendary
Activity: 2128
Merit: 1657
Waiting for some positive feedback from the optional dag fix update ? If everything is running smoothly with stable undervolting control after the DAG fix, I'll install it immediately...
newbie
Activity: 1
Merit: 0
I confirm, performance has dropped. The system does not overclock the graphics card. Sad (NVIDIA)
Jump to: