Please upload image nvos v0018 to another place, links in first post not working.
He is currently is not on as usual with stable internet, he posted I think one page back. I am currently uploading the v0018 to google drive for those who want to download.
|
|
|
@salfter : I'd like to suggest an idea to your switcher: when the most profitable algorithm is Ethash, give the option to dual-mine automatically with the second most profitable algorithm if it's able to do so. A rough draft: * Give the user the choice to dual-mine or not in conf.json * List the safe algorithms to dual-mine with Ethash (Decred, Lbry, Sia, Pascal, ...?) * List NiceHash's most profitable algorithms after Ethash, if it's the first one; for each one, check if it's in the safe list, and select the first match (most profitable AND in the safe list) * Profit Of course I'm oversimplifying, as the switching itself will have to consider a higher power limit, more complex profit calculation and perform a "switch inside a switch" (Ethash fixed + switching second algo). But I think we can get a few more bucks this way, at least from my short mining experience it's usually profitable to dual-mine when Ethash is the most profitable. What do you think? Biggest issue I see with this is power. To dual mine the rigs need considerably more power then solo mining. Example is 1070 rig with solo mine can do same OC with PL around 110-115, while on dual mining needs 120-125. Some people may have stability problems with this type of switch if they are not aware of the power needed to support it.
|
|
|
As for NiceHash vs. MiningPoolHub, that's something I'm figuring out for myself right now. MPH takes 0.9% on all coins mined and imposes a BTC0.0003 miner fee on withdrawals, so by raising the auto-withdraw threshold to BTC0.03 (NiceHash is fixed at BTC0.01), the miner fee ends up being only 1% of the total. As for which is more productive (read: produces more BTC per week), that's something I hope to get a handle on over the next couple or so weeks. I eagerly await your findings here. Always want to make sure I'm on top of the most profitable way to use my rig. Same here, be some very good information
|
|
|
my rigs keep restarting after few minutes. Some after 5 mins some after 30. Im not sure why this keeps happening.
im using all 1070's with core 100 / 1050 also i tried 150-200 / 1100-1600. No luck
what is your power limit on them? for 1070s I would push around 120-125 with a moderate/heavy OC. Anything less can cause stability problems. my power limits are all at 125 Anyone have any idea on this? its driving me crazy Not sure if you saw my reply above: With your core around 100, 125 may not be enough for the card. Try running 100cc and put it around power level 130-135, if you are doing ETH, it is sometimes better to do negative core since it has very little affect on hash rate and uses a lot more power. My 1070 ETH rig runs -100 cc and between 1200-1275 mem. If that does not solve the problem, I would check to make sure everything is connected properly, I had one time one of my riser USB was not in all the way and had intermittent connection and was causing my problems.
|
|
|
my rigs keep restarting after few minutes. Some after 5 mins some after 30. Im not sure why this keeps happening.
im using all 1070's with core 100 / 1050 also i tried 150-200 / 1100-1600. No luck
what is your power limit on them? for 1070s I would push around 120-125 with a moderate/heavy OC. Anything less can cause stability problems. my power limits are all at 125 With your core around 100, 125 may not be enough for the card. Try running 100cc and put it around power level 130-135, if you are doing ETH, it is sometimes better to do negative core since it has very little affect on hash rate and uses a lot more power. My 1070 ETH rig runs -100 cc and between 1200-1275 mem. If that does not solve the problem, I would check to make sure everything is connected properly, I had one time one of my riser USB was not in all the way and had intermittent connection and was causing my problems.
|
|
|
my rigs keep restarting after few minutes. Some after 5 mins some after 30. Im not sure why this keeps happening.
im using all 1070's with core 100 / 1050 also i tried 150-200 / 1100-1600. No luck
what is your power limit on them? for 1070s I would push around 120-125 with a moderate/heavy OC. Anything less can cause stability problems.
|
|
|
fullzero, After testing this week it seems the problems were the flash drive nothing more. It must have been getting write errors for quite some time that finally it just died causing the rig instability. I appreciate all the hard work!
|
|
|
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it. It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs. Or relaxed in general. If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected. I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash. What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING? I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now. Not sure what it is but I am rolling back to VER17 on this rig, as it just restarted again and then hard locked up after initial start-up showing a black screen then the flash drive was corrupted and refused to boot. Just found out it may have been the flash drive the last 48 hours as it just died. LOL write errors all over it. I am testing now with a new flash drive. What program are you using to image you USB key? If your using a Windows build computer; I would use hddrawcopy for v0018. Let me know if this is working with your new USB key. I am using hddrawcopy on windows 10. It seems to be the flash drive, been over 20 hours now no issues with a new flash drive. Love new flash drive dies within a week, time to contact newegg! I am using hddrawcopy on windows 10, it was the flash drive.
|
|
|
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it. It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs. Or relaxed in general. If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected. I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash. What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING? I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now. Not sure what it is but I am rolling back to VER17 on this rig, as it just restarted again and then hard locked up after initial start-up showing a black screen then the flash drive was corrupted and refused to boot. Just found out it may have been the flash drive the last 48 hours as it just died. LOL write errors all over it. I am testing now with a new flash drive.
|
|
|
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
I have noticed a problem when using both PROFIT_SWITCHING and or WATCHDOG together; I will make changes to the next 1bash to fix it. It is also possible that the timeouts between checks in the WATCHDOG should be relaxed when mining Ethash COINs. Or relaxed in general. If the timing is right; PROFIT_SWITCHING will switch close to the WATCHDOG check and a low utilization will be detected. I will make a flag for both IN-SWITCHING and DAG-BUILDING to prevent this in the next 1bash. What COIN selection are you using or are you using SALFTER_NICEHASH_PROFIT_SWITCHING? I am not currently using SALFTER_NICEHASH_PROFIT_SWITCHING since Ethash is so close with the profit switching right now.
|
|
|
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
60 x 12 = 720 mns the description is wrong in the 1bash file I did catch that and changed it to 3600 minutes or 2.5 days Thank you though!
|
|
|
Fullzero, IAmNotAJeep or Maxximus007,
Have a question on the watchdog script. I noticed it has triggered twice in the last 24 hours but not sure why as it seems there is not much information within the logs to try to troubleshoot.
The one I am getting is: utilization is too low; reviving did not work so restarting system in 10 seconds. With the restart knocks the miner out for about 20 minutes. I am trying to figure out what is going on and only started having this happen when I went to VER18. I changed the utilization under the script to 80 instead of 90 today to see if that helps.
I appreciate any help or insight into the possible problem, as with the restarts wipes out the other logs.
|
|
|
Yes, that is the problem, I have ran it later after copying the files, can see it working but crashed whole OS, I might need to use the latest files and give it a try again (now I'm sure it works with the latest fixes). Also I'm seeing low hashrates sometimes while using 'NICE_ETHASH', dropping to 100 MH and going to 250 MH (saw that on nicehash portal, but on terminal it averages 185 MH always) My OC settings cc-150 mc-1200 pl-95W (8 GTX 1060 6G on Z270P), does it have something to do with my OC settings? any idea? Thanks for answering all my silly questions Nicehash uses the instantaneous hashrate; this will have variance as your rig produces more or less shares per second (ie dropping to 100 MH and going to 250 MH). Nicehash should probably also include a 6hr average both for hashrate and projected payouts (as now all of these are calculated based on your instantaneous hashrate. That's what I thought but when my I lowered my OC a little it has improved the share rate (tested it for 10 hours or so), impressive. Just want to ask your opinion about choosing between 'SALFTER_NICEHASH_PROFIT_SWITCHING' and 'NICE_ETHASH', which one you think and prefer is best to gain more from any rig? (please ignore this question if it sounds silly ) Thanks for the v0018 will do share my hashrate for a day or two. Dear Community Members : Can you guys please share your OC settings while using 'SALFTER_NICEHASH_PROFIT_SWITCHING' with your yield per day. Currently I'm on cc -100, mc - 1000, pl - 95 (180 MH on console), getting BTC 0.0053xxxx per day with my GTX 1060 6G (8 GPU) RIG mining 'NICE_ETHASH'. I only have one RIG (can't afford another ), not sure I'm getting the best of it or not, would like to get best out of it with your suggestions. Thanks in advance I haven't used the Salfter nichhash profit switching, does that use the genoil miner ? If so I can give you some of the settings I have for my 1060s.
|
|
|
I just recalled that when using claymore you can use Ethminer remote manager along with it and just set it up on one of my comptuers to notify me.
Problem solved now. Now I have to look at the Wemo for remote power reset. That is kinda cool for a oh crap situation.
|
|
|
Had a rig today at work hard lockup and needed a hard reset. How would I pass the worker email for claymore or eth to get a notification? Was down for about 8 hours With the new update that should help any resets, but I totally recommend getting the wemo. I often use it if i can't get into my rig remotely it's excellent for hard resetting plus it also gives you a remote power consumption monitor, smart plugs are pretty great if you get the right one. Not a bad idea for a remote reset for the power, hummmm. I do like this but I still need a way to be notified when the miner goes down.
|
|
|
Had a rig today at work hard lockup and needed a hard reset. How would I pass the worker email for claymore or eth to get a notification? Was down for about 8 hours
|
|
|
Yup, I am ready to go for this ICO!!! can't wait.
|
|
|
Hi,
I have few Gigabyte Z270-gaming K3 mobos...they have killer networks E2500 LAN and nvOC boots without LAN. I assume there is no driver support in this distribution. So can you tell me how to install LAN driver, manually or can it be inserted in next version (18) ?.
Or any other solution...
Let me know
Best regards
Personally I dislike Killer Ethernet NICs. I would get one of these or similar for each mobo and never use the Killer NICs. https://www.amazon.com/Cable-Matters-Ethernet-Network-Adapter/dp/B00ET4KHJ2Any of the usb 2.0 adapters should be more than enough for a mining rig. Hi Fullzero... I have managed to find solution in order that existing drivers works for killerNIC E2500 (device ID 1969) sudo modprobe alx echo 1969 e0b1 | sudo tee /sys/bus/pci/drivers/alx/new_id However , this need to be done after every reset...is there way to insert this to autostart after system boots...sorry for noob questions. I received 10 of these motherboards and need to get them to work. USB NIC are last option... let me know if you can help me to solve this...probably more other owners of GA mobos with Killer NICs. Best regards First make the command above you have it into a script. Once you have done this you can then call it to your cron job so it will execute on every startup. Now run "crontab -e" this will allow you to edit cron Now add this to cron @reboot /path/to/myscript
|
|
|
please help. How can i add dcri argument to my onebash settings? what and where exactly i should whrite?
It's not set by default in oneBash So you can set it in $ETH_EXTENTION_ARGUMENTS. Use 40 or even 20 (depending your cards etc). ETH_EXTENTION_ARGUMENTS="" # add any additional claymore arguments desired here
So: ETH_EXTENTION_ARGUMENTS="-dcri 40" # add any additional claymore arguments desired here
Thankyou When dual mining it requires a lot more power, my dual mining rig I have to have minimum 120 watts. This is on Claymore 9.7. 6x 1070 rig dcri 20 Core: -200 Mem: 1210-1270 Stats: ETH - Total Speed: 186.968 Mh/s, Total Shares: 410(85+78+67+77+66+54), Rejected: 0, Time: 03:04 ETH: GPU0 31.300 Mh/s, GPU1 31.268 Mh/s, GPU2 31.224 Mh/s, GPU3 30.860 Mh/s, GPU4 31.256 Mh/s, GPU5 31.059 Mh/s SC - Total Speed: 1246.454 Mh/s, Total Shares: 81(15+16+8+14+17+11), Rejected: 0 SC: GPU0 208.669 Mh/s, GPU1 208.454 Mh/s, GPU2 208.163 Mh/s, GPU3 205.734 Mh/s, GPU4 208.372 Mh/s, GPU5 207.062 Mh/s Incorrect ETH shares: none 1 minute average ETH total speed: 186.468 Mh/s
|
|
|
|