 Show Posts
|
|
Pages: « 1 2 [3] 4 5 6 »
|
|
Yes I think so because until now the bitcoin is still the best coin. Bitcoin is very popular and it is in high demand by both the crypto and external community.
|
|
|
|
|
I have no doubt about the qualitative improvement of our life in the coming years precisely thanks to the crypto-currency and Blockchain.
|
|
|
|
|
I think it will be a good news for us who, this will bring a big benefits to bitcoin. Project will certainly attract a lot of attention.
|
|
|
|
|
Satoshi Nakamoto is more a mystery than a person. There might be several reasons as to why the real identity is kept hidden whatever.
|
|
|
|
|
I would say alt coins are good for very quick earnings while Bitcoin is good for keeping as a store of value.
|
|
|
|
|
To an extent, telegram is the major determinant of a project success. Through telegram group admin gives regular updates about the project.
|
|
|
|
|
For the investor and the campaign itself, a large number of participants is the success of the project.
|
|
|
|
|
Ethereum is a good Coin. Ethereum has gained trust from different big companies to invest in it.
|
|
|
|
|
Rewards will be distributed soon I believe. I'd like to get involved in the project myself but it looks like I missed out on the program.
|
|
|
|
It spits out the error line of: GPU xxxx failure, disabling! Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,> Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod ) Ninja edit: Ooooo thats what dont use --kernel use --algorithm also TC is only used for scrypt/nscrypt Okay so I installed 2 more gig of ram... and windows... I run the sgminer 5.0 before I install VNC and it works just great. Now, I wonder if VNC is the issue .... I almost think so. i found teamviewer works better for me and much easier, though my extra miners are running pimp at the moment I use TightVNC with no issues. You need a VNC program that doesn't mess with your display when connecting. |
|
|
|
Keep it up guys - people like you ensure GPU-mining will never die  |
|
|
|
I'm amazed we're still doing all this tweaking blindly with so much guesswork and trial and error. There's got to be a way to accurately and precisely measure what's possible/stable, based on the numbers alone.
Everybody's clocks have different tolerances. It'd be easier just to say stock clocks and unedited .cl files, but fuckit; gotta try and get that extra 200Kh/s. If you don't somebody else might. But why would they have different tolerances if they're built exactly the same? Are we talking differences in heat/humidity or something? |
|
|
|
|
I'm amazed we're still doing all this tweaking blindly with so much guesswork and trial and error. There's got to be a way to accurately and precisely measure what's possible/stable, based on the numbers alone.
|
|
|
|
Honestly man, I haven't been able to get close to this. I've applied all your settings. I max out at 5.4MH with X11, but I have to throttle back because the same clocks on X15 give me dead cards. My stable settings are 1030/1300 for all three X algos, and I hit 5.2MH for X11 and 3.2MH for X15. This is for two Sapphire R9 290x BF4 editions, one with Hynix and one with Elpida. I'm using the 7/20 daily build, and driver 14.4 + the 14.6 CLs. (multidriver trick) I guess maybe the problem is I'm not using 14.7, but I was under the impression they yield the same performance. Try my darkcoin bin , I get ~6mh/s so does others https://bitcointalk.org/index.php?topic=632503.msg7883228#msg7883228I went ahead and updated to 14.7, and now I'm getting 5.9MH with my own bins. So let the record show that using the 14.4+14.6 multidriver trick does not work as well as 14.7. Using sgminer daily build 7/20. -------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 77.0C 56% | 5.903M/5.860Mh/s | R: 0.0% HW:0 WU:0.107/m rI:21
GPU 1: 78.0C 65% | 5.894M/5.874Mh/s | R: 0.0% HW:0 WU:0.033/m rI:21
------------------------------------------------------------------------- 5.9 is fine with me. I'm leaving town for 4 weeks, so I need this to be safe and stable anyway. My settings, a little different than yours (higher diff, lower clocks): {
"pools" : [
{
"name" : "NiceHash_X11_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "x",
"pass" :
"d=0.08;f0=0;f2=0;f3=5.5;f4=4;f5=0;f6=3.5;f7=0",
"profile" : "x11"
},
{
"name" : "NiceHash_X13_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "x",
"pass" :
"d=0.08;f0=0;f2=0;f3=5.5;f4=4;f5=0;f6=3.5;f7=0",
"profile" : "x13"
},
{
"name" : "NiceHash_X15_AS",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "x",
"pass" :
"d=0.08;f0=0;f2=0;f3=5.5;f4=4;f5=0;f6=3.5;f7=0",
"profile" : "x15"
},
{
"name" : "NiceHash_X11_BACKUP",
"url" : "stratum+tcp://stratum.nicehash.com:3336",
"user" : "x",
"pass" : "d=0.08",
"profile" : "x11"
}
],
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"worksize" : "64",
"gpu-engine" : "1030-1030",
"gpu-memclock" : "1300-1300"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"worksize" : "64",
"gpu-engine" : "1030-1030",
"gpu-memclock" : "1300-1300"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"worksize" : "64",
"gpu-engine" : "1030-1030",
"gpu-memclock" : "1300-1300"
}
],
"vectors" : "1",
"rawintensity" : "211200",
"shaders" : "2816",
"gpu-threads" : "2",
"gpu-fan" : "0-95",
"gpu-powertune" : "20",
"temp-cutoff" : "99",
"temp-overheat" : "85",
"temp-target" : "80",
"auto-fan" : true,
"auto-gpu" : true,
"log" : "5",
"log-dateformat" : "1",
"failover-only" : true,
"failover-switch-delay" : "300",
"no-pool-disable" : true,
"no-submit-stale" : true,
"scrypt" : true,
"queue" : "1",
"scan-time" : "7",
"expiry" : "28",
"api-listen" : true,
"api-mcast-port" : "4028",
"api-port" : "4001",
"api-allow" : "W:127.0.0.1"
}
|
|
|
|
Honestly man, I haven't been able to get close to this. I've applied all your settings. I max out at 5.4MH with X11, but I have to throttle back because the same clocks on X15 give me dead cards. My stable settings are 1030/1300 for all three X algos, and I hit 5.2MH for X11 and 3.2MH for X15. This is for two Sapphire R9 290x BF4 editions, one with Hynix and one with Elpida. I'm using the 7/20 daily build, and driver 14.4 + the 14.6 CLs. (multidriver trick) I guess maybe the problem is I'm not using 14.7, but I was under the impression they yield the same performance. |
|
|
|
|
Cool... slowly testing.
Able to get 5.4MH stable with RI:225280 and 1025/1250, as well as the Luffa_Parallel trick. Will nudge it up from here and see if I can get the fabled 6MH.
|
|
|
|
Wow. Confirmed, this works. A little shaky on x15 though... I'm behind... is this unnecessary now that we have 14.7  |
|
|
|
Wow. Confirmed, this works. A little shaky on x15 though... |
|
|
|
Don't know if this helps, but I tend to get rejects when this happens: [15:21:35] Accepted 01fff32d Diff 0.500/0.080 GPU 0 at NiceHash_X11_AS
[15:21:52] NiceHash_Scrypt_AS alive, testing stability
[15:22:47] Rejected 09cc36bf Diff 0.102/0.080 GPU 1 NiceHash_X11_AS (Job not found.)
[15:23:16] Rejected 0c688d36 Diff 0.081/0.080 GPU 0 NiceHash_X11_AS (Job not found.)
It's like the new alive pool interrupts and causes a delay... so the shares X11 was working on are invalid and rejected by the time it gets to submit. |
|
|
|
|
Update - I get the HW errors when switching from X11 to Scrypt-N. No crash, but it calms down after a few minutes.
|
|
|
|
|
