Quote from: TenaciousJ on August 20, 2017, 02:58:11 AM

Quote from: fullzero on August 19, 2017, 05:41:42 PM

Quote from: Bibi187 on August 19, 2017, 04:54:06 PM

Quote from: TenaciousJ on August 19, 2017, 04:09:04 PM

Quote from: Bibi187 on August 19, 2017, 03:59:33 PM

Quote from: TenaciousJ on August 19, 2017, 03:56:40 PM

Quote from: damNmad on August 19, 2017, 10:02:17 AM

Quote from: Bibi187 on August 19, 2017, 08:48:34 AM

Quote

Thanks for posting this info - I banged my head against a wall for quite a while trying to figure this error out before giving up on it. This worked like a charm for me.

Though I think I'm still getting really low hashrates for skunk - whattomine thinks I should be getting 450mh/s with 5 1080 Tis and 7 1070s but I was only getting around 300mh/s. With the new krnlx miner I'm still only getting about 370Mh/s, which still seems pretty low. My miner also restarts with the watchdog reporting under utilization. My 1080 Tis are only running at about 60% and 1070s at 80-85% capacity. Can't figure out what's causing that.

EDIT: I added the '-i 25' flag to the command line and boosted core clock on the 1070s to +125 now I'm up at 480mh/s =)

Hum just stay away from krnlx release ... Low report share is a "know" problem ...
I lost one week of mining on this stupid release ... Just dont USE krlnx this dev drop a brocken build and vanish ... First and last one i use something from him ...
So a basic; krlnx mod boost your hashrate but you loose 30% expected share ... Use new ccminer release from tpru u get same hashrate and REAL SHARE.
For 1070 u can push -i 25, Coreclock + 100/140 depend on card, MemoryClock -1500. I dont use 1080, but i bet u can push them to -i 26, to grab a solid 50mh/s+ per 1080ti

https://github.com/tpruvot/ccminer/releases link to tpruvot version.

Yes indeed...

How do you lose 30% of expected shares? You mean rejected shares?

Not rejected shares, is a weird thing and i dont analyze deeper on this. I get 70% of expected share with this hashrate report, so remove 30% of your hashrate when u use krnlx

Where are you getting your expected shares tally from? I think that varies based on difficulty of the shares calculated which is determined by the stratum server, not your machine, so i don't know how you'd reliably determine expected shares in order to reason that you're losing 30%. Right now with 460-480Mh/s I'm getting about 22 coins an hour, which seems to be in line with the predictions of whattomine.com's mining calculator profit wise, ~ 525-550 coins a day @ $.07 per coin = ~$37-38.00 /day.

I haven't mined at length with TPruvot ccminer 2.2 with the current configuration on my system, so I don't know if it would result in higher profit, but krnlx seems to be on point for profitability estimates now that I've got it properly configured and my clock settings are dialed in. FWIW, I'm not sure why you're downclocking your memory so much. I overclock mine +100 on 1070s and +800 on 1080 Tis. I see no benefit from underclocking memory on Nvidia cards really since power usage comes from core clock speed primarily, and it could result in unstable mining to underclock memory too much.

EDIT: I had the under use problem with Watchdog as well, but I took care of that by raising my clock speed on my GPUs from +100 to +125 and setting intensity to -i 25, now I don't have watchdog restarts at all.

I get same result on suprnova or pool.mn, for 2 days on each after i install krnlx, i lost 30% income and lost 30% on wathtomine prediction.
I give a try to push my MemoryClock to +100 and i lost hashrate instant, prolly depend from the card. Maybe try to lower your MemoryClock u gona gain more hashrate. I use 8 x ASUS 1070 8OG, i have stable for more them 24h running and get 242+mh/s

After reading this: I don't want to include the krnlx fork. Instead I will update the tpruvot to the newest version for v0019. Is this the optimal client right now for skunk?

I ran the 2.2 version of TPruvot ccminer w/ skunk and got horrible hashrates. I will recompile and test it again, but for now, krnlx is the fastest for me. I'm not sure why there is a perceived drop of 30% in his setup, but I'm not seeing that at all. I'm mining exactly at the expected coin rate per day based on both whattomine.com and crypto-economy.com calculators (450mh/s nets me around 550 coins a day +/- 25). I will note that when I tried changing clock settings a little higher it really affected hashrates, dropping them over time considerably. There is definitely a 'sweet spot' clock rate for skunk, and deviation appears to create greatly reduced production. Also mining at -i 26 seems to have reduced my hashrates, so -i 25 is the proper setting for 1070 / 1080 Ti at least. Lower settings or leaving -i blank greatly reduce hashrates, as is to be expected.

I'll update with the results of a recompile with tpruvot's most recent ccminer release on 0018.

Thanks for keeping an eye on this.

EDIT: the latest tpruvot ccminer release runs at just about the same hashrate as krnlx within 1-2mh/s (463mh/s vs. 462mh/s) and in a 2 hour test it mined 26-27 coins an hour on sigt.pool.mn which is a small number more than I was mining before, but it's a shjort test length so I'll update again after 24 hours to get a better average. I was able to run tpruvot with skunk from command line in guake, but it crashes for some reason when running from the script almost immediately after it starts mining (before watchdog kicks in). Not sure why that's happening, the command line is the same in both as I have it configured.

In the end, I don't see a dramatic difference between the two miners' performance except that I know krnlx runs from the script properly, whereas TPccminer 2.2 does not work in the script yet. I'll keep playing around with it to see if some code in the script I added has an error. It's strange because the miner actually starts mining properly, but then errors out, rather than just not running at all which is normally how that goes.

Yeap skunk have sweet spot for every brand i think. U have to manage to find the fine tunning. I am not sure about this but i bet 1080ti can grab better performance on -i 26, i think u assign intensity per gpu like -d 0,1,2,3,4,5,6 -i 25 -d 7,8,9,10,11 -i 26
Anyway i get a bad experience with krnlx, before ccminer update, i was thinking about going back to palginmod with -20% hashrate ( not the new one )
I try to fix my variation GPU volatility, i cant run watchdog without lot of reboot by GPU sometime go to 0% for 1 second, everything is fine but watchdog dont like this Wink

When u try to reboot miner via quake, i dont know why but on ccminer build, script cant kill "irq" is state in zombie mode. So when u launch miner again, GPU cant assign correct value cause if this "irq" zombie, just do "sudo pkill -e irq" and u can launch it Wink