For all the guys having stability issues, try moving to Claymore 9.5. I had issues a few days ago that I mentioned a few pages back. Same weirdness with rigs going to 0 hashes or rebooting continuously.
Manually rolling my systems to Claymore 9.5 fixed that for me.
Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 421. (Read 835818 times)
June 15, 2017, 01:01:03 AM
June 15, 2017, 12:34:25 AM
I've hardtime starting my rig to mine after the recent update. I often stumble on GPU fault detected 146 and 147. Anyone have the solution?
June 14, 2017, 11:25:30 PM
Hi I need some assistance. I recently started using SimpleminingOS about 2 weeks ago & it has been great. I paid my funds for the rig fee and until last night everything has been running smooth(Do I need to keep the balances above 2.00 for each rig?)I have two computers that were mining Eth last night and when I woke up in the morning they were idle & would not connect back to dwarfpool. So I switched over to UBIQ(Eth Fork?) for the day. The rigs seemed to have been running for most of the day until I got home and saw the rigs sitting idle again. It looks like they keep rebooting. I removed the slight overclock settings I had and still nothing. I connected a monitor to the rig & noticed the GUI interface with the miner terminal is gone. I'm guessing there was some kind of an update last night because all I see is a fullscreen console. If anyone could point me in the right direction on how to resolve my issue I would appreacite it. Thanks!
(I was running these configs)
-wd 1 -r 1 -epool stratum+tcp://eth-us2.dwarfpool.com:8008 -ewal $walletETH/$rigName -esm 0 -epsw x -allpools 1 -mode 1 -mport -3333
-epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0x571F5156db8Da859E3bC539Ea4ddA84ED6BFB4C6 - epsw x -eworker I7RX470 -allcoins 1
(screenshots)
https://i.imgur.com/fIjbBVM.jpg
https://pasteboard.co/iHo2UAdxo.jpg
https://pasteboard.co/iHqGg0XiS.jpg
(I was running these configs)
-wd 1 -r 1 -epool stratum+tcp://eth-us2.dwarfpool.com:8008 -ewal $walletETH/$rigName -esm 0 -epsw x -allpools 1 -mode 1 -mport -3333
-epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0x571F5156db8Da859E3bC539Ea4ddA84ED6BFB4C6 - epsw x -eworker I7RX470 -allcoins 1
(screenshots)
https://i.imgur.com/fIjbBVM.jpg
https://pasteboard.co/iHo2UAdxo.jpg
https://pasteboard.co/iHqGg0XiS.jpg
June 14, 2017, 10:56:59 PM
what is the Username/password for Login to Linux? I want to assign static IP Addresses.
June 14, 2017, 10:46:35 PM
Use Gen2 on PCI. This setting in 3 places in BIOS.
100% 6x580 worked.
100% 6x580 worked.
June 14, 2017, 10:37:15 PM
Hello, I'm having some strange problems whenever I try to get more than two cards working on any of my systems. I've managed to get 3 cards working with some bios fiddling, but I couldn't reproduce it.
I'm running
Intel 3900 (Skylake)
Asus PRIME z270-P
8gb Ram
A mixture of various 580 4gb and 8gb
I've enabled 4g and find that I'm most stable with everything (PCI, etc) set up to Gen 1. Are there any other settings that need to be changed?
I'm using a 16gb usb 2.0 pen drive. I've tried both the normal and z170 Simple Mining versions.
When I boot it, regadless of success, I get a few flashing screens of this weird rainbow static.
https://i.imgur.com/tl1W0bN.jpg
Then, I boot in Xubuntu, as normal, but then get this.
https://i.imgur.com/LUeBvEK.jpg
There's another similar error that just locks the system up until you press a button and it resets the entire system, but I haven't been able to reproduce it. My biggest issue is that I'll have my system be stable at 3 cards, but when I restart it it'll not boot up normally again.
Any one have any ideas/bios settings? I've had some success, but I really want to reproduce that 8 GPU z270 build I saw.
I'm running
Intel 3900 (Skylake)
Asus PRIME z270-P
8gb Ram
A mixture of various 580 4gb and 8gb
I've enabled 4g and find that I'm most stable with everything (PCI, etc) set up to Gen 1. Are there any other settings that need to be changed?
I'm using a 16gb usb 2.0 pen drive. I've tried both the normal and z170 Simple Mining versions.
When I boot it, regadless of success, I get a few flashing screens of this weird rainbow static.
https://i.imgur.com/tl1W0bN.jpg
Then, I boot in Xubuntu, as normal, but then get this.
https://i.imgur.com/LUeBvEK.jpg
There's another similar error that just locks the system up until you press a button and it resets the entire system, but I haven't been able to reproduce it. My biggest issue is that I'll have my system be stable at 3 cards, but when I restart it it'll not boot up normally again.
Any one have any ideas/bios settings? I've had some success, but I really want to reproduce that 8 GPU z270 build I saw.
June 14, 2017, 10:15:07 PM
so I will run 2 gigabyte 1070 itx cards on eth
hoping to get more support in a few days
ewbf_ 3.4
would be nice
better clocks
would be nice
I can only do 2 cards on a mobo that did 4 amd cards
so being able to do 4 cards would be nice.
hoping to get more support in a few days
ewbf_ 3.4
would be nice
better clocks
would be nice
I can only do 2 cards on a mobo that did 4 amd cards
so being able to do 4 cards would be nice.
June 14, 2017, 09:55:24 PM
was going to switch to this on my NVidia rigs, but with no zec support ill hold off for now
June 14, 2017, 08:35:24 PM
Hey im having an issue where when the miner starts up the miner says there are no gpus for the miner.
the os it self see's 4 on the rig. any suggestions?
the os it self see's 4 on the rig. any suggestions?
June 14, 2017, 07:56:49 PM
okay lots of testing of beta nvidia build.
I can get 95 watts on gigabyte 1070 itx cards
pretty good compared to 150 stock.
the clocking does not work for my msi 1070 itx cards
I can get 95 watts on gigabyte 1070 itx cards
pretty good compared to 150 stock.
the clocking does not work for my msi 1070 itx cards
June 14, 2017, 07:14:16 PM
If this is not fixed by tomorrow morning i guess i'll make my own Ubuntu distro like i did for my Nvidia rigs.
This auto updating should be optional in my opinion.
This auto updating should be optional in my opinion.
I use a customized Arch-based image - but if you don't wanna do that, IMO, give EthOS a try. Auto-update is not only fucking stupid from the POV of possible breakage, but if this OS is ever super popular, the mechanism will almost certainly be compromised and malicious updates pushed to all the poor bastards who use it.
I wish I had the ability to make something like that!
June 14, 2017, 06:52:29 PM
If this is not fixed by tomorrow morning i guess i'll make my own Ubuntu distro like i did for my Nvidia rigs.
This auto updating should be optional in my opinion.
This auto updating should be optional in my opinion.
I use a customized Arch-based image - but if you don't wanna do that, IMO, give EthOS a try. Auto-update is not only fucking stupid from the POV of possible breakage, but if this OS is ever super popular, the mechanism will almost certainly be compromised and malicious updates pushed to all the poor bastards who use it.
I share your opinion on auto updates. I had perfectly stable rigs for over a month, and now that is out the window. I understand if Tytanick decides that he will only help troubleshoot rigs that are completely up to date, but for those of us that have a good thing going, let us be.
June 14, 2017, 06:47:40 PM
Ok something is obviously wrong with SMOS after 1098 update, my cards hangs randomly, they drop to 0MH/s and then rig restarts. This never happend to me before, Tyt can you please take a look at this issue? from what I can see I am not the only one struggling with SMOS stability issues after patch 1098. Thanks.
In my case, I have a theory ... I have 2 diferents memory values in my rig for diferent cards. What I believe is hapening, its if the system is rebooted for any cause, the gpu order is mixed, and the wrong memory clock are applied. That causes fails on different VGAs ... For final test, I get all the cards for the lower memory clock and now I'm waiting to see whats going to hapen.
Any sugestion?
I am experiencing the problem, and I have the same OC settings for all cards.
June 14, 2017, 06:01:48 PM
Pretty sad that no answers on the issue with cards dropping to 0 mh/s from Tytanick.
okay show a screen shot of your rigs
with your clocks
June 14, 2017, 05:34:57 PM
If this is not fixed by tomorrow morning i guess i'll make my own Ubuntu distro like i did for my Nvidia rigs.
This auto updating should be optional in my opinion.
This auto updating should be optional in my opinion.
For the life of me I can't find where to skip or disable the auto-update feature either. What's the point of offering older builds if it just updates to the newest as soon as it boots?
June 14, 2017, 05:29:42 PM
If this is not fixed by tomorrow morning i guess i'll make my own Ubuntu distro like i did for my Nvidia rigs.
This auto updating should be optional in my opinion.
This auto updating should be optional in my opinion.
June 14, 2017, 05:26:04 PM
smOS is changing some of my card's core clock speeds without any input.
The snapshot below is a of a rig running 7 RX 570s, all with stock bios, and no OC settings applied (ever) via the Dashboard.
As you can see, two of them have switched from the default 1128 to 1191.
This seemingly happens at random to different GPUs across all of my rigs.
The change to 1191 is not random, however. A couple of my rigs currently have some GPUs with a custom bios which has a default core clock of 1191. The rig in the photo has not ever had anything but cards with the stock bios connected. I have also manually input 1191 as the core clock on other rigs of mine, but I have never applied an OC to the rig in the picture.
Changing the core clock settings in smOS does not seem to have any effect. It will change the clock upon startup, but it may change again before mining even starts, without any notice in the terminal.
edit: 1128 is not even the stock clock according to MSI spec sheet, it is actually 1268. So why is smOS automatically downclocking my cards???
The snapshot below is a of a rig running 7 RX 570s, all with stock bios, and no OC settings applied (ever) via the Dashboard.
As you can see, two of them have switched from the default 1128 to 1191.
This seemingly happens at random to different GPUs across all of my rigs.
The change to 1191 is not random, however. A couple of my rigs currently have some GPUs with a custom bios which has a default core clock of 1191. The rig in the photo has not ever had anything but cards with the stock bios connected. I have also manually input 1191 as the core clock on other rigs of mine, but I have never applied an OC to the rig in the picture.
Changing the core clock settings in smOS does not seem to have any effect. It will change the clock upon startup, but it may change again before mining even starts, without any notice in the terminal.
edit: 1128 is not even the stock clock according to MSI spec sheet, it is actually 1268. So why is smOS automatically downclocking my cards???
it is using linux drivers not windows which may vary a bit
Well that may explain why they seem to default to 1128. But I'm still unsure as to why the core clock would be changed, sometimes after booting/passing the "OC Phase" of startup, but before/just as mining starts.
On another note, one of my rigs spits this out before eventually booting:
Then mines at a severely reduced hashrate, sometimes with as little as 2 or as many as 6 cards, eventually crashing and rebooting.
June 14, 2017, 05:22:24 PM
I have some RX570's that had no overclocking set at all that ran solid no crashes or reboots for a few days. I made a change and reloaded the miner with 1098 and now I'm getting GPU FAULT PROTECTION across the screen then eventually a crash and reboot. 1098 is the only change that made a difference. i switched back to claymore 9.4 and that made no difference.
June 14, 2017, 05:11:42 PM
Ok something is obviously wrong with SMOS after 1098 update, my cards hangs randomly, they drop to 0MH/s and then rig restarts. This never happend to me before, Tyt can you please take a look at this issue? from what I can see I am not the only one struggling with SMOS stability issues after patch 1098. Thanks.
In my case, I have a theory ... I have 2 diferents memory values in my rig for diferent cards. What I believe is hapening, its if the system is rebooted for any cause, the gpu order is mixed, and the wrong memory clock are applied. That causes fails on different VGAs ... For final test, I get all the cards for the lower memory clock and now I'm waiting to see whats going to hapen.
Any sugestion?
June 14, 2017, 05:05:33 PM
Pretty sad that no answers on the issue with cards dropping to 0 mh/s from Tytanick.
Jump to: