Author

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

legendary
Activity: 1050
Merit: 1001
question

when using this OS with nvidia cards, and the NV build.. we are only limited to ewbf or skunk/eth based mining programs right?

because my 1080TI's on ewbf seem to get half of what they should be hashing at

the claymore zec miner is not working with the NV build... why is this?
dzp
newbie
Activity: 1
Merit: 0
I am beginner, trying to set the wallet in simplemining. When ever I check the mining stats it shows me the page with invalid wallet message...
What am I doing wrong?
newbie
Activity: 21
Merit: 0
Quick question is the Gpu order consistent with motherboard order?
sr. member
Activity: 490
Merit: 264
| Privacy Advocate | Game Theory | Free Thinker |
Yes im getting also problems...the rigs that reboot all get stuck again on launching "unexpected inconsistency run fsck manually... fsck exited with status code 4..." Only flashing new pens i could solve the problem in other rigs but do i have to do it and not allow any reboot? Whats going on?

Edit Only flashing a new bios on MOBO i can get a new pen to work... wich leads me to think of corrupted update?
sr. member
Activity: 378
Merit: 250
thanks for the settings, what hashrate you have with those ?

~22.5 MH/s per GPU.
sr. member
Activity: 440
Merit: 250
@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 ?

Not all the cards will overclock as well as others, so 1 badly working card can cause a reboot.
That being said, SMOS has some weird behavior with NVIDIA cards.
Until they are fixed, you're better off mining ETH with (H110+ 13 x P106) with the following overclock settings:

GPU Core: -200
Memory MHz: 500
Power Limit (watt): 70
Target Temperature ℃: 75
Minimum Fan speed %: 20

I have about 12 rigs, all of them with those settings.. no reboots, less noise and less heat.

thanks for the settings, what hashrate you have with those ? btw if I put 500 on memory clock my cards don't overclock with 500mhz but something like 200 only, that's why if I want to reach +900 i put 1600... very strange Sad
newbie
Activity: 18
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 ?

Not all the cards will overclock as well as others, so 1 badly working card can cause a reboot.
That being said, SMOS has some weird behavior with NVIDIA cards.
Until they are fixed, you're better off mining ETH with (H110+ 13 x P106) with the following overclock settings:

GPU Core: -200
Memory MHz: 500
Power Limit (watt): 70
Target Temperature ℃: 75
Minimum Fan speed %: 20

I have about 12 rigs, all of them with those settings.. no reboots, less noise and less heat.

Thanks for the settings, are any of your rigs 1070s? My 7 card rigs work fine on 0/1400 110w but on the 13 GPU Asrock I can only OC 0/400 110w or it reboots like you are saying. I've even swapped the cards to the other rig and they work fine at 1400 on it with no resets for days.
newbie
Activity: 7
Merit: 0
my amd vega54 isnt recognised by simplemining OS
is this for real?? update please @tytanick

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.
There will be OPTIONAL UPDATE near each RX OS rig which has old kernel (without dagfix)
This update will install dgfix kernel and packages but ONLY when you will click on it.
I dont want install it automatically.
If someone has already dagfix OS RX then no need to install this update.

On top of this there will be auto update which will fix some scripts in system.
After that you will be able to write undervolting values in Overclocking Modal under rig options.

After all of that you will have restored ethereum mining speed andnormal power wattage.
Probably even some less power draw in certain gpus but i will leave that for users to test Smiley

AFTER that will be done and fixed, the next in line is NVIDIA some problems with some p106 and gtx1060 gpus.
AFTER fixing nvidia i will focus on VEGA which is already laying on my desk and waiting for support.

In a mean time there will be builded some HELP/FAQ page.

So right now please dont write me any more emails "when" and "how" Cheesy - i really need to fix this shit once for all.

@tytanick, you are the boss, thank you for this new!
newbie
Activity: 1
Merit: 0
Just startet to use SMOS. Thus far it looks great.

Is a way to target the GPU power limit for each card separately for NVIDIA cards? Claymore does not support target clocks and temp on NVIDA gpu for some reason. Also want to meantion experiencing the same issue as in previous posts about offsetting power limits.

Keep up the great work.
sr. member
Activity: 378
Merit: 250
@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 ?

Not all the cards will overclock as well as others, so 1 badly working card can cause a reboot.
That being said, SMOS has some weird behavior with NVIDIA cards.
Until they are fixed, you're better off mining ETH with (H110+ 13 x P106) with the following overclock settings:

GPU Core: -200
Memory MHz: 500
Power Limit (watt): 70
Target Temperature ℃: 75
Minimum Fan speed %: 20

I have about 12 rigs, all of them with those settings.. no reboots, less noise and less heat.
sr. member
Activity: 440
Merit: 250
@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 ?
member
Activity: 111
Merit: 10
what the heck is going on today with sm
just shut down all my rigs to do basic maintenance, after rebooting them manuall getting plenty of UNKNOWN OPTION, No session found and  0h/s 0h/s

Quote
GPU4 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
GPU4 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #144 for GPU0
Create GPU buffer for GPU0
GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
GPU0 - OpenCL error -61 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
GPU 2 failed
Setting DAG epoch #144 for GPU2
GPU2, OpenCL error -38 - cannot write buffer for DAG
GPU 5 failed
GPU 3 failed
GPU 1 failed
GPU 0 failed
GPU 4 failed
Setting DAG epoch #144 for GPU5
GPU5, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #144 for GPU4
GPU4, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #144 for GPU3
GPU3, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #144 for GPU1
GPU1, OpenCL error -38 - cannot write buffer for DAG
Setting DAG epoch #144 for GPU0
GPU0, OpenCL error -38 - cannot write buffer for DAG
GPU 2 failed
GPU 4 failed
 
newbie
Activity: 18
Merit: 0
Hi all,

i'm now setting up several 12 GPU rigs made of AMD RX 580 8G only.

I have my moded bios file. Can I flash it with SMOS or i need to flash my cards with windows and install SMOS later ?

What is this "OFFSET" setting tytanick is talking about ??


Many Thanks  Grin

Offset is lets say global parameter in gpu whch told gpu to undervolt by specified value.
For exampel if gpu has values for different stages like 900, 950, 1000 tehn offset of 100 will make those values 800,850,900.
Anyway after this update there will need to set  value in standard format and not offset one.
So for example 850 [mv].
I am dont have experience in this field of modding bioses in GPU and only that i heard here and there.

Wow First post and reply by the boss  Grin
Thank you !
By the way i'm pretty sure that my modded bioses will perform better than stock ones.
I will switch my 8 rigs to smos When proper oc will be released (can't wait)  i run my 580s at 1200/900 // 2250/900
I push 31,7 mhs eth + 1000mhs dcr... I hope i will get similar perf... Roll Eyes

I got 30.4mh/s with my 580s in windows but in smos they fluctuate from 24-30, I average about 366mh/s for the 13 cards. I wish it was faster, as fast as windows.
I'd love to know what you get, I'm torn between 7 cards at 30.4 in windows and 13 cards at less in SMOS.
I'm hoping the updates will resolve the speed issues.

My 580 8GBs run 1250/2115 only 29.1mh/s so I usually run them at 1150/2100 to save power, they get about 28.2 mh/s. Can't seem to find a good setting, MH/s drops off at lot at 1100 unlike the 480s they will run 1050/1100 and 1950 and get 27.5mh/s. using way less power Huh
newbie
Activity: 18
Merit: 0
Anyone able to get more than 13 cards on Asrock H110 Pro BTC+? I've tried m.2 and a couple pcie multipliers. The board will not boot with the 14th card plugged in but the multiplier works, if I unplug another card the 13 with the splitter still works, I even tried with 3 cards plugged into the splitter and it boots with 2 empty pcie slot 13 cards. However 14th card = no boot/post. I have no problem getting 13 to work though, EZ plugged in and booted right up with 13.

Curious if anyone is getting more than 13 from H110 Pro BTC,

Thanks
member
Activity: 70
Merit: 10
Hi all,

i'm now setting up several 12 GPU rigs made of AMD RX 580 8G only.

I have my moded bios file. Can I flash it with SMOS or i need to flash my cards with windows and install SMOS later ?

What is this "OFFSET" setting tytanick is talking about ??


Many Thanks  Grin

Offset is lets say global parameter in gpu whch told gpu to undervolt by specified value.
For exampel if gpu has values for different stages like 900, 950, 1000 tehn offset of 100 will make those values 800,850,900.
Anyway after this update there will need to set  value in standard format and not offset one.
So for example 850 [mv].
I am dont have experience in this field of modding bioses in GPU and only that i heard here and there.

Wow First post and reply by the boss  Grin
Thank you !
By the way i'm pretty sure that my modded bioses will perform better than stock ones.
I will switch my 8 rigs to smos When proper oc will be released (can't wait)  i run my 580s at 1200/900 // 2250/900
I push 31,7 mhs eth + 1000mhs dcr... I hope i will get similar perf... Roll Eyes

I got 30.4mh/s with my 580s in windows but in smos they fluctuate from 24-30, I average about 366mh/s for the 13 cards. I wish it was faster, as fast as windows.
I'd love to know what you get, I'm torn between 7 cards at 30.4 in windows and 13 cards at less in SMOS.
I'm hoping the updates will resolve the speed issues.
full member
Activity: 350
Merit: 100
Yeah but my SSD doesnt show up in there. I have downloaded it.  Tongue


reformat the SSD with rufus-2.9.exe then try it may be windows doesn't see it,  I have had  the same issues using some SSD , SD, USB sticks etc  or try disk part in a windows cmd.the SSD might be formatted with some other OS that windows doesn't  like or see for windows fat . if that's your issue .
If you have that issue still then you can format again the SSD with Rufus then you can try it again. Sometime windows doesn’t see that due to which the problem occur. I have solve my friend problem with this solution
member
Activity: 102
Merit: 10
MY rigs rx sapphire 580s and 570s(gigabyte mainboards 970ds3p ) dont run with your published iso files..
After some commands flows up , the screen came with a black screen... I return to windows till you solve it..

I booted my flash disk with dagfix iso 17.30 vers. I mention this above.

How can i solve ?
i only get 26.5 with old version of smos.

dag fix file ?
sr. member
Activity: 490
Merit: 264
| Privacy Advocate | Game Theory | Free Thinker |
So basicaly one of my rigs downloaded a new config and after that was giving me a Magic Cookie error and now the rig is hashing at 1mh per gpu... anyone got same problem?

Now after 3 new flashed pens i still cant get the rig online... Everytime the OS starts to boot it turns off the ethernet connection... Anyone can help?

# dmesg

Might show something useful

Thank you mate, for some unknown reason the rig just came online has i saw your post... Wich means that somehow the ethernet port turned on again... Anyway ill monitor it for 12h to see.. Thanks again
sr. member
Activity: 378
Merit: 250
So basicaly one of my rigs downloaded a new config and after that was giving me a Magic Cookie error and now the rig is hashing at 1mh per gpu... anyone got same problem?

Now after 3 new flashed pens i still cant get the rig online... Everytime the OS starts to boot it turns off the ethernet connection... Anyone can help?

# dmesg

Might show something useful
sr. member
Activity: 490
Merit: 264
| Privacy Advocate | Game Theory | Free Thinker |
So basicaly one of my rigs downloaded a new config and after that was giving me a Magic Cookie error and now the rig is hashing at 1mh per gpu... anyone got same problem?

Now after 3 new flashed pens i still cant get the rig online... Everytime the OS starts to boot it turns off the ethernet connection... Anyone can help?
Jump to: