Topic: ★★★ MaruCoin ★★★ NEW X13 ALGO ! ★★★ MINE NOW ! [KGW+DGW] ★★★ NO IPO/PM EXCHANGE! - page 32. (Read 96477 times)
April 24, 2014, 07:25:02 AM
From P2P pool.
April 24, 2014, 06:41:46 AM
@Ibinsad
Are we looking at the same coin ?
I can see that the diff is below 20, and network hashrate around 150 ? Now is 550
Price is a lot lower that on two exchanges that are listed on the first page.
Are we looking at the same coin ?
I can see that the diff is below 20, and network hashrate around 150 ? Now is 550
Price is a lot lower that on two exchanges that are listed on the first page.
Yes, i notice diff from 15 to 30
Where you retrieve 150 as network hashrate?
So good time to buy before sharks come!
April 24, 2014, 06:37:49 AM
Qiú kuàng chí qiú shuǐchí yǒu kuàng chí ma yǒu shuǐchí ma?Seeking mineral pools are mine seek pool pool pool you have it?
April 24, 2014, 06:31:48 AM
求矿池 求水池 有矿池吗 有水池吗？
April 24, 2014, 05:36:17 AM
@Ibinsad
Are we looking at the same coin ?
I can see that the diff is below 20, and network hashrate around 150 ?
Price is a lot lower that on two exchanges that are listed on the first page.
Are we looking at the same coin ?
I can see that the diff is below 20, and network hashrate around 150 ?
Price is a lot lower that on two exchanges that are listed on the first page.
April 24, 2014, 03:14:38 AM
Looks like nethash is steadily growing (the block rewards are falling).
Early miners will be rewarded!
I'm buying all I can at these prices...you guys are CRAZY for selling so low.
Early miners will be rewarded!
I'm buying all I can at these prices...you guys are CRAZY for selling so low.
nethash at the beginning was 200Mh/s, then 300Mh/s, now is from 500-600Mh/s
If it will increase again.. it will more profitable to buy at 0.00002888 , instead of mining.
April 24, 2014, 01:16:38 AM
i actually ended up doing really similar if not the exact same as what you posted.. last 24hrs
2 threads..
queue at 0 with low scan and expiry etc
Intensity at 12 the whole time (with low TC although high seems to cause crashing a but more)
and the shaders setting i am sure makes no difference because if you specify TC it get overridden and then shader setting does nothing.
guys i know what i am doing this ain't my first dance
i'm telling you it's causing my driver to crash on the weakest of weak setting no matter what
and another guy was getting the same thing mentioned on sgminer topic too on ALL the various builds.
so i guess we have to be doing something wrong though..
but it really makes me wonder if the sgminer algo code is optimized properly.
It really shouldn't be that buggy..
Like there is extremely different code bases used for Quark written in c..
They had been written using different approaches and are vastly different.
i have to keep reminding people i have coded miner moods of my own for a year too so your not talking to a noob
after i started a year ago i had a 90% complete working miner program ported from Cudaminer that was a windows GUI based
i wrote it in MFC and as far as i am aware that is the ONLY real miner with a windows gui in existence.
And i dropped it because it was 100x faster to do coding work and compile for a console app.. dev laziness lol
But i could finish it and release it pretty easily if i wanted to..
I have spent huge amounts of my life in the last year staring at and working on miner code.
and something is not right here guys.. THAT is what i am trying to say.
There is no way that the miner should be crashing the display driver that easily when it has never happened once in my life until this coin.
get what i am saying ?
I appreciate all the feedback in response to my asking..
Seriously thanks a lot guy for taking the time to post and YES it is helpful.. all can do is experiment i suppose and lower the crash frequency.
I didn't want this comment to seem like an ungrateful know it all and your idiots kinda comment.
BUT.. it is.. i am the best and smartest
PS:
jk
but seriously though, i am still stuck at square one and i have to fix the problem myself.
it's clear what the deal is.. to me anyway.
i think what has happened is you guys all just think this is normal but why should i be doing 90% usage with no HW errors
using ultra weak settings and have my driver crash like a broken record ? If i told you all i was mining scrypt or scrypt- and said that what would you all think ?
I really think there must be a problem with implementation and coding of a dozen+ algo's in sgminer
i was pretty damn stunned to such bad performance and temperamental behavior.
Like i have not crashed my driver on any other coin once.. what happens faaar before that usually on other algo's is i get HW errors or lower performance.
does anyone see what i am saying yet ?
2 threads..
queue at 0 with low scan and expiry etc
Intensity at 12 the whole time (with low TC although high seems to cause crashing a but more)
and the shaders setting i am sure makes no difference because if you specify TC it get overridden and then shader setting does nothing.
guys i know what i am doing this ain't my first dance
i'm telling you it's causing my driver to crash on the weakest of weak setting no matter what
and another guy was getting the same thing mentioned on sgminer topic too on ALL the various builds.
so i guess we have to be doing something wrong though..
but it really makes me wonder if the sgminer algo code is optimized properly.
It really shouldn't be that buggy..
Like there is extremely different code bases used for Quark written in c..
They had been written using different approaches and are vastly different.
i have to keep reminding people i have coded miner moods of my own for a year too so your not talking to a noob
after i started a year ago i had a 90% complete working miner program ported from Cudaminer that was a windows GUI based
i wrote it in MFC and as far as i am aware that is the ONLY real miner with a windows gui in existence.
And i dropped it because it was 100x faster to do coding work and compile for a console app.. dev laziness lol
But i could finish it and release it pretty easily if i wanted to..
I have spent huge amounts of my life in the last year staring at and working on miner code.
and something is not right here guys.. THAT is what i am trying to say.
There is no way that the miner should be crashing the display driver that easily when it has never happened once in my life until this coin.
get what i am saying ?
I appreciate all the feedback in response to my asking..
Seriously thanks a lot guy for taking the time to post and YES it is helpful.. all can do is experiment i suppose and lower the crash frequency.
I didn't want this comment to seem like an ungrateful know it all and your idiots kinda comment.
BUT.. it is.. i am the best and smartest
PS:
jk
but seriously though, i am still stuck at square one and i have to fix the problem myself.
it's clear what the deal is.. to me anyway.
i think what has happened is you guys all just think this is normal but why should i be doing 90% usage with no HW errors
using ultra weak settings and have my driver crash like a broken record ? If i told you all i was mining scrypt or scrypt- and said that what would you all think ?
I really think there must be a problem with implementation and coding of a dozen+ algo's in sgminer
i was pretty damn stunned to such bad performance and temperamental behavior.
Like i have not crashed my driver on any other coin once.. what happens faaar before that usually on other algo's is i get HW errors or lower performance.
does anyone see what i am saying yet ?
April 23, 2014, 10:12:05 PM
i have got it up running for a while with badass's build..
it needed lower settings i think.
i went with this on my 7950 (so far / still toying with these of course)
Intensity = 12
"worksize" : "128",
"thread-concurrency" : "8192",
"gpu-threads" : "1",
"scan-time" : "10",
and that is getting steady shares accepted and running at about 700kh/s (on my OC'd Powercolor PCS+ Radeon 7950)
"shaders" : "1792",
"gpu-engine" : "1060",
"gpu-fan" : "70",
"gpu-memclock" : "1500",
10 minutes now no crash yet.. 49 degrees and 95% usage
Numbers !!!! i have them all ..they are all miiiiiiiiiiiiiine !!
it needed lower settings i think.
i went with this on my 7950 (so far / still toying with these of course)
Intensity = 12
"worksize" : "128",
"thread-concurrency" : "8192",
"gpu-threads" : "1",
"scan-time" : "10",
and that is getting steady shares accepted and running at about 700kh/s (on my OC'd Powercolor PCS+ Radeon 7950)
"shaders" : "1792",
"gpu-engine" : "1060",
"gpu-fan" : "70",
"gpu-memclock" : "1500",
10 minutes now no crash yet.. 49 degrees and 95% usage
Numbers !!!! i have them all ..they are all miiiiiiiiiiiiiine !!
Leave the shaders at "0" and try 2 threads with the intensity at 12-13. Or vice/versa, if you manually set the shaders, leave the TC at "0".
I used badass' .bat to get it going then slightly modified it so it runs using the .conf.
start.bat
Code:
setx GPU_MAX_ALLOC_PERCENT 100
sgminer --algorithm marucoin
sgminer.conf
Code:
{
"pools" : [
{
"url" : "http://127.0.0.1:7745",
"user" : "uber",
"pass" : "noob"
}
]
,
"intensity" : "13,13,12",
"xintensity" : "0,0,0",
"rawintensity" : "0,0,0",
"worksize" : "256,256,256",
"kernel" : "marucoin,marucoin,marucoin",
"lookup-gap" : "0,0,0",
"thread-concurrency" : "14208,14208,14208",
"shaders" : "0,0,0",
"gpu-threads" : "2,2,2",
"gpu-engine" : "0-0,0-0,0-0",
"gpu-fan" : "0-25,0-25,0-53",
"gpu-memclock" : "0,0,0",
"gpu-memdiff" : "0,0,0",
"gpu-powertune" : "0,0,0",
"gpu-vddc" : "0.000,0.000,0.000",
"temp-cutoff" : "95,95,95",
"temp-overheat" : "85,85,85",
"temp-target" : "75,75,75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "20",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"no-client-reconnect" : true,
"queue" : "0",
"scan-time" : "10",
"tcp-keepalive" : "30",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}
GPU 0-1 7870xt/Tahiti LE @ 1150/1500, GPU 2 7870/Pitcairn @ 1150/1200
April 23, 2014, 06:12:52 PM
Looks like nethash is steadily growing (the block rewards are falling).
Early miners will be rewarded!
I'm buying all I can at these prices...you guys are CRAZY for selling so low.
Early miners will be rewarded!
I'm buying all I can at these prices...you guys are CRAZY for selling so low.
April 23, 2014, 06:12:08 PM
well some data would be nice if it works ok for you..
look at what that guy said he was using lol
obviously it requires using weird settings so telling us what they are would be nice
i have said that like 5x now lol
look at what that guy said he was using lol
obviously it requires using weird settings so telling us what they are would be nice
i have said that like 5x now lol
I'm using my normal settings...256 worksize and everything.
What issues are you having?
April 23, 2014, 04:52:25 PM
well some data would be nice if it works ok for you..
look at what that guy said he was using lol
obviously it requires using weird settings so telling us what they are would be nice
i have said that like 5x now lol
look at what that guy said he was using lol
obviously it requires using weird settings so telling us what they are would be nice
i have said that like 5x now lol
April 23, 2014, 03:20:40 PM
Actually, its not new algo, but combination of 13 old REAL algos, like with almost all "new" coins.
April 23, 2014, 02:03:04 PM
Great coin with newest great algo. Lets see
April 23, 2014, 02:00:04 PM
Dev, any news?
+1
It would be nice to hear him say anything.
April 23, 2014, 01:11:10 PM
Dev, any news?
+1
It would be nice to hear him say anything.
April 23, 2014, 12:32:46 PM
scantime and expiry @ 1 and a queue @0 are the common settings for a P2P pool
when I mine a mpos pook I mostly take 5 for scantime and expiry and 1 for queue
when I mine a mpos pook I mostly take 5 for scantime and expiry and 1 for queue
April 23, 2014, 12:30:31 PM
Dev, any news?
April 23, 2014, 12:18:58 PM
For me too. X13 working so smooth. I love this algo
April 23, 2014, 12:00:26 PM
No Problems for me also...
Rigs running stable for days
Rigs running stable for days
April 23, 2014, 11:58:18 AM
those are some seriously crazy settings.. see what i mean guys ?
work size of 64 ?
a thread-concurrency maxed out..
lookup-gap at 0
expiry at 1
on 1 gpu-thread (i usually use 1 thread and higher settings myself)
scan-time at 1
queue at 0
those are sure as hell not your average settings
looks like you had been doing some serious tinkering to get it working lol
THANKS for sharing
edit:
it's funny the cpu miners have not had one bad share one crash or one error of any kind they work flawlessly best i can tell..
cgminer mods are all dog shit lol
not sure of the problems you guys are having but my gpu miner is up and running without problems.work size of 64 ?
a thread-concurrency maxed out..
lookup-gap at 0
expiry at 1
on 1 gpu-thread (i usually use 1 thread and higher settings myself)
scan-time at 1
queue at 0
those are sure as hell not your average settings
looks like you had been doing some serious tinkering to get it working lol
THANKS for sharing
edit:
it's funny the cpu miners have not had one bad share one crash or one error of any kind they work flawlessly best i can tell..
cgminer mods are all dog shit lol
Jump to: