Hi,
Can you Add OptiminerZero as i would like to mine Zero coin.
I was trying to mine GOBYTE coin using ccminer-tpruvot-v2.1 and ccminer-tpruvot-v2.2.5-cuda8.0 but it says not-supported.
Some one help me to mine GoByte and Zero coin
Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 192. (Read 836197 times)
March 19, 2018, 09:39:32 PM
March 19, 2018, 06:06:12 PM
I have same problem but I can't solve this problem...
I have motherboard H110 Pro BTC+ and I flash with last BIOS update.
I already did installation recomendations that are in SimpleMining Site.
I attach error that I have when I boot SimpleMining OS.
I already reflash my pen drive and have same problem...
Anyone can help to explain to me what I have to do?
https://mega.nz/#F!FEJ3xRQQ!sxivx5tR-Biip2f8wSH9MQ
I have motherboard H110 Pro BTC+ and I flash with last BIOS update.
I already did installation recomendations that are in SimpleMining Site.
I attach error that I have when I boot SimpleMining OS.
I already reflash my pen drive and have same problem...
Anyone can help to explain to me what I have to do?
https://mega.nz/#F!FEJ3xRQQ!sxivx5tR-Biip2f8wSH9MQ
March 19, 2018, 04:48:54 PM
So after about 2 straight weeks of mining perfectly, the SMOS just went down with no error code, overheating, or anything I could see.
I tried the internet connection, a new USB, and unplugging/restarting the rig.
Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.
The monitor code says that it wants me to connect to the rig that I can't see.
What am I missing?
Please connect LCD to your rig and see what happens there, make a video and if it will be unclear please send it to our support at [email protected]I tried the internet connection, a new USB, and unplugging/restarting the rig.
Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.
The monitor code says that it wants me to connect to the rig that I can't see.
What am I missing?
MR TYTANICK
Can you please add optiminer 2.1.2 i would very much appreciate https://github.com/Optiminer/OptiminerEquihash
I am looking into this.Can you please add optiminer 2.1.2 i would very much appreciate https://github.com/Optiminer/OptiminerEquihash
Also looking into this miner but first approach failed on compilation under linux. We will be trying.
Also we need to make few adjustments in Telegram BOT notification system and i think that it will be soon live
March 19, 2018, 03:55:13 PM
So after about 2 straight weeks of mining perfectly, the SMOS just went down with no error code, overheating, or anything I could see.
I tried the internet connection, a new USB, and unplugging/restarting the rig.
Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.
The monitor code says that it wants me to connect to the rig that I can't see.
What am I missing?
I tried the internet connection, a new USB, and unplugging/restarting the rig.
Lastly, I deleted the current rig that was not connecting and now when I plug in SMOS can't find any rig in my dashboard.
The monitor code says that it wants me to connect to the rig that I can't see.
What am I missing?
March 19, 2018, 11:11:14 AM
MR TYTANICK
Can you please add optiminer 2.1.2 i would very much appreciate https://github.com/Optiminer/OptiminerEquihash
Can you please add optiminer 2.1.2 i would very much appreciate https://github.com/Optiminer/OptiminerEquihash
March 19, 2018, 02:54:27 AM
March 19, 2018, 02:21:02 AM
Update v1150
- fix for ethminer blocking stats in dashboard
- fix in Nvidia OC script on p104 p106
- fix for ethminer blocking stats in dashboard
- fix in Nvidia OC script on p104 p106
Thank You very much, sure nobody can imagine the load you have with such amount of users, all demanding new miners, improvements etc.
But from the other hand, we have to give some sort of feedback.
I have p104 with modded bios. On win i can hit 40Mhs eth @ 100watt per card from the wall with underwolt and memory boost.
On smos no matter what i do i can't go over 35.xx Mhs @ 110 watt...
March 19, 2018, 12:17:18 AM
Tytanick,
Can you please update Nvidia driver to latest 390.42:
http://www.nvidia.com/download/driverResults.aspx/131853/en-us
Your current one is 390.25
Can you please update Nvidia driver to latest 390.42:
http://www.nvidia.com/download/driverResults.aspx/131853/en-us
Your current one is 390.25
March 18, 2018, 11:19:14 PM
Been using SMOS for a few weeks now. Not bad at all and overall and I am making about 2-3 more a day on each of my 8 x rigs... The only drawback for me is that I really miss having CPU mining capabilities built in to a single system.
I need to touch up on my Ubuntu...
I need to touch up on my Ubuntu...
March 18, 2018, 11:12:15 PM
http://
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+
"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.
would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?
If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.
As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.
To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.
i've been using putty "screen -x miner" since I use SMOS, it is also in the help section.
like just now, one of my rig stopped, and screen can only show the hash rate has dropped to 8Mhs across all 6GPUs..
"Digging through logs will take hours of your time" SMOS is designed for a farm setup, so it will be impractical to dig all of your rig.
having a log that show only what caused the crash will help, we are not asking for the whole log, we are only interested what caused the crash.
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+
"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.
would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?
If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.
As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.
To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.
i've been using putty "screen -x miner" since I use SMOS, it is also in the help section.
like just now, one of my rig stopped, and screen can only show the hash rate has dropped to 8Mhs across all 6GPUs..
"Digging through logs will take hours of your time" SMOS is designed for a farm setup, so it will be impractical to dig all of your rig.
having a log that show only what caused the crash will help, we are not asking for the whole log, we are only interested what caused the crash.
March 18, 2018, 10:09:31 PM
undervolting on rx series still not working...
March 18, 2018, 09:26:34 PM
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+
"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.
would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?
If you want to dig through the log you can also do that. The log is there, just SSH into the miner and pull it up. The way I suggested is much more efficient use of your time. You don't need 24/7 monitoring. Just run it on your personal computer, and when the miner reboots you'll see the cause in PuTTY whenever you're back at your personal computer. Do this for a couple days until you eliminate the cause of your reboots.
As you said, the miner reboots a couple times and hours before you get to look into it. Digging through logs will take hours of your time to scroll back to try and find the crashes. My suggestion will put the cause of the crash immediately in front of you with minimal effort.
To answer your question, PuTTY works well as an SSH client on Windows. If you hover over your rig's name in SMOS you'll see the ip address of the rig. log into that address with PuTTY. username: "miner", password "miner". once you log into it type "screen -x miner" and you'll pull up the miner screen. let it run until the miner reboots/crashes. when it crashes you'll get a pop-up in PuTTY that the connection disconnected, but you'll be able to see what caused the drop.
March 18, 2018, 08:18:36 PM
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+
"SSH session will end, but whatever happened to cause the crash will still be displayed" this means monitoring the rig like 24/7 with a display, this defeats the purpose of SMOS, the point of the log is to check what happened after several hours/days in operation because after a day or two my rig has restarted already a couple of hours ago.
would like also to ask (not so technical person), is the SSH in PuTTY any different from direct SSH?
March 18, 2018, 06:43:07 PM
Disabled everything under ACPI settings in bios, only HPET is enabled (but did try both ways), what should I look into, to remove the below while booting?
It sometimes is rebuilding journal after these ACPI errors as well..
https://ibb.co/dx5jAH
It sometimes is rebuilding journal after these ACPI errors as well..
https://ibb.co/dx5jAH
March 18, 2018, 01:14:56 PM
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
SSH into your rig. When it reboots the SSH session will end, but whatever happened to cause the crash will still be displayed. Very easy/fast way to troubleshoot. likely you have a card overclocked too high for the new Claymore improvements in 11.3+
March 18, 2018, 03:48:54 AM
Is SMOS chat down or something? 
Yes it was down. I fixed it just now. The rocket chat script stopped working.
March 18, 2018, 01:35:28 AM
Hello,
When simplemining add ccminer xevan algo?
When simplemining add ccminer xevan algo?
March 18, 2018, 01:13:33 AM
Is SMOS chat down or something?
March 17, 2018, 11:40:39 PM
the log on the dashboard containing like 5 last reboot reasons would be great. As logging locally just corrupts usb flash memory within a week or two, already gone through that couple of times...
Respected Admin,
that's really a good idea, by this way we will understand the problems with our rig. plz install a button in dash board where restart rig button is available for log in front of each rig.
that will be great,
after claymore 11.0 , my rig are restarting every few hours, i am unable to understand the problem so till now i am using claymore 11.0, plz do some for your customers...
thanks in advance.
Gaurav
March 17, 2018, 11:38:49 PM
I am really new to this GPU thing.
I have a bunch of EVGA 1070s, will it work with this? the nvidia/rx etc. throws me off? which os will support my EVGA 1070?
Thank you
I have a bunch of EVGA 1070s, will it work with this? the nvidia/rx etc. throws me off? which os will support my EVGA 1070?
Thank you
Jump to: