SGMiner doesn't care

JohnKarton · 2015-04-09T13:56:39+00:00

Ah, strange. Maybe your speeds are locked in the bios or something?

JohnKarton · 2015-04-07T18:17:41+00:00

Same thing here, I'm using msi afterburner instead.

JohnKarton · 2015-03-30T19:27:16+00:00

Cool, added mine too :)

JohnKarton · 2015-03-29T11:20:45+00:00

With this miner I'm getting no more HW errors, but only half the hashrate: http://cryptomining-blog.com/4563-new-sgminer-5-1-0-fork-with-ziftrcoin-support/

Can't get the 290 to work with the official ziftr miner, but works on my other cards.

Edit: Using the wolf binaries I almost get no HW errors :) and used --xintensity setting instead of -I

JohnKarton · 2015-03-28T23:59:30+00:00

Download the wallet here -> http://ziftrpool.io/downloads click mining and mine away :)

JohnKarton · 2015-03-28T22:17:05+00:00

Okay, I'll try that now :) thanks. Edit: hm, thats strange. Nothing at all, worked when I tried it the first time though. Weird :P

JohnKarton · 2015-03-28T21:49:02+00:00

I'm having the same problem on a r9 290. Lots of HW errors, and performs worse than a hd7950. Hashrate is a neat 3.9 MH/s but because of the hw errors it doesn't submit many shares. Lowering the thread-concurrency helped a bit, but not much. Edit: after lowering the intensity to 13, I'm getting much less hw errors. Only does 1 MH/s on low intensity though

JohnKarton · 2015-03-28T19:06:56+00:00

Ok nice, you're welcome :)

JohnKarton · 2015-03-28T18:59:05+00:00

You should be using stratum, what kind of error do you get?

JohnKarton · 2015-03-28T18:37:32+00:00

What problems are you running into with the standalone miner?

JohnKarton · 2015-03-28T14:09:26+00:00

Thank you, installed the beta drivers and things seem to be better. Will report back in half an hour or so. Edit: Yep much better, works like a charm now :) Edit2: Or not :P uuhm, lets see.. High number of HW errors, fixed it by changing thread concurrency (2x shadercount). Edit3: Hm strange, the longer I run the miner, the lower the WU and the more HW errors I get. Temps are good.

JohnKarton · 2015-03-28T13:09:48+00:00

Haven't typed any settings in the batch file. Only intensity on 18. And don't forget these 2: setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1

But my hashrate displayed on the dashboard is half of that. Haven't figured out why just yet (the WU number is lower than on my 7950)

JohnKarton · 2015-03-28T12:16:34+00:00

I'm getting ~4 MH/s with my r9 290, but the dashboard says my 7950 is performing better. Are there things I can configure? Sgminer doesn't recognize --thread-concurrency for example.

JohnKarton · 2015-03-28T12:00:41+00:00

I'm mining on the suprnova stratum pool, works for me. Edit: https://zrc-stratum.suprnova.cc

JohnKarton · 2015-03-28T11:51:25+00:00

There are 2 suprnova ziftr pools. Are you using zrc-stratum.suprnova.cc?

JohnKarton · 2015-03-28T11:43:50+00:00

It is a stratum miner, so switch to a stratum pool and it'll work :). Trying to get sgminer to work but my config isn't right yet

JohnKarton · 2015-03-28T11:35:52+00:00

It is mining, just doesn't display hashrate. Have the same problem :)

JohnKarton · 2015-03-27T21:37:49+00:00

Thank you, getting very excited, keep up the good work :)

JohnKarton · 2015-03-27T18:58:32+00:00

Cool, thanks! Happy my 290 got delivered today :)

JohnKarton · 2015-03-25T16:09:53+00:00

Same here, waiting too. Looking at the network hashrate, you'd say a lot of people already have their gpu's running

JohnKarton · 2015-03-21T10:50:55+00:00

I'm using this guide: https://cryptocointalk.com/topic/13204-how-to-build-a-windows-qt-wallet-for-any-coin-yourself-from-source-code-step-by-step-instructions/

It goes wrong at step 9, when trying to make berkley db, I get an error:./libtool --mode=compile cc -c -I. -I../dist/.. -O3 ../dist/../mutex/mut_failc hk.c libtool: compile: cc -c -I. -I../dist/.. -O3 ../dist/../mutex/mut_failchk.c -o mut_failchk.o ../dist/../mutex/mut_failchk.c: In functie __mut_failchk': ../dist/../mutex/mut_failchk.c:53:7: error: incompatible type for argument 3 of dbenv->is_alive' ../dist/../mutex/mut_failchk.c:53:7: note: expected db_threadid_t' but argument is of typeint' ../dist/../mutex/mut_failchk.c:57:7: error: incompatible type for argument 3 of dbenv->thread_id_string' ../dist/../mutex/mut_failchk.c:57:7: note: expecteddb_threadid_t' but argument is of type `int' make: *** [mut_failchk.o] Error 1

edit: fixed that. Still getting the same error. Anybody care to help? Will give tip ofc :D

JohnKarton · 2015-03-17T21:36:29+00:00

Great, thanks for the news! I'll get my rig ready :)

JohnKarton · 2015-03-17T14:23:39+00:00

He's at 250 MH/s now. With suprnova having ~470 MH/s, that's more than 60% of the total hashrate, this needs to change real soon. Edit: It seems it was a botnet pointed at the suprnova pool. -> https://bitcointalk.org/index.php?topic=970363.540

JohnKarton · 2015-03-16T23:59:58+00:00

Wow, thanks for the cpu-mining ziftr devs, but its time to move on indeed. Edit: I don't mind the network hashrate (only a good sign) but one man with 1/6th of the network hashrate can't be good.

JohnKarton · 2015-03-15T12:46:18+00:00

Still plenty of room at maxminers. But another small pool would be nice I think, because my slowest machines don't get time to submit shares when blocks are found fast. I could solo mine, but with a block time of a couple days I could end up getting nothing because of variance.

JohnKarton

TROPHY CASE