Latest posts of: rednoW

Show Posts
Pages: « 1 ... 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 [76]

1501

on: February 04, 2015, 07:04:16 PM

Quote from: Schleicher on February 04, 2015, 04:27:15 PM I see no reason why it shouldn't work. Code: accepted: 32/32 (100.00%), 709.96 khash/s yay!!! What card and what intensity? card gtx 750, intensity not set, default, yaamp

1502

on: February 04, 2015, 03:42:49 PM

Quote from: DougB62 on February 04, 2015, 11:21:38 AM Quote from: ltc_bilic on February 04, 2015, 10:56:36 AM lyra2re algo appears to be broken in latest release I noticed this as well, though I only tried it on Westhash (Nicehash). lyra: release 34 - not working, only few khashes rate release 31 - working near ~860kh but consumes a lot of cpu release 32 - the best, ~860kh, near zero cpu consumption

1503

on: February 03, 2015, 03:18:33 PM

Quote from: sp_ on February 03, 2015, 01:40:34 PM try d=0.01 or d=0.005. Or empty diff parameter. I get a higher hashrate. but my rig has more than one card. yeah, looks like a little bit more in miner ~2930. and a 5% "reject reason: Invalid job id" upd: rate is floating - now again closer to ~2850

1504

on: February 03, 2015, 01:32:38 PM

Quote from: sp_ on February 03, 2015, 01:10:42 PM What rates are you getting in x11? ~2830 khash/s same on release 31 and 34 (as miner shows). Have no long run to test pool shown rate d = 0.02

1505

on: February 03, 2015, 12:41:32 PM

Quote from: sp_ on February 03, 2015, 11:13:02 AM yeah. It might work on compute 3.5 though.. Use this version (1.5.2-git) https://bitcointalk.org/index.php?topic=770064.0 it works. yes, it works. Good in "fresh". Strange but for "quark" on compute 3.0 original ccminer 1.2 is the best, just for fun Tried to build your release 34 in x64 mode. Small performance drop in all algos. Test comp: Athlon64X2 3ghz, gtx 750 (1470gpu/1550mem), win7x64 rates on your original release34 build are fresh: ~3450kh quark: ~5550kh (on release 31 is ~5600kh) up to 61% of modded TDP 65w (cool) release 34 seems to work better with yaamp then release 31

1506

on: February 03, 2015, 10:30:22 AM

Quote from: sp_ on February 02, 2015, 09:14:48 PM K4000 is using Compute 3.0. Should work If you build yourself. My binaries are always build with compute 5.0 and 5.2. just changing settings to compute_30,sm_30 in CUDA C/C++ -> Device -> Code Generation in VS2013 project preferences leads to results not approved by CPU. Not that i need it, just tried ))). As well as trying to compile with CUDA 7.0 Any step from default config leads to not working code ...

1507

on: January 24, 2015, 03:00:40 PM

Quote from: Bombadil on January 24, 2015, 02:40:53 PM I'm gonna keep repeating it: setting to high, higher than high, stoned high, doesn't make a difference. Setting it to realtime does, but might lock up your system. that's right

1508

on: January 24, 2015, 12:17:20 PM

Quote from: RD965 on January 24, 2015, 08:48:16 AM Cmon guys I need my computer as a heater! Scrypt or X11? best heaters are scrypt-n and quark. You need a good optimized miner. But only a heater, no profit as with all other algos

1509

on: January 24, 2015, 12:11:20 PM

Quote from: duboisi on January 24, 2015, 11:28:44 AM I got about 9% of "reject reason: Duplicate share" with Release 32. 750 TI @ YAAMP QUARK. it's the pool problem, same on Release 31

1510

on: January 24, 2015, 07:01:22 AM

I've used this command to start miner in windows start /realtime ccminer.exe it gives me more hashes. Now with release 32 it starts with high but not with realtime priority and gives less hashes. I need to go to Task Manager and change priority manual to realtime. No good. And no improvements for gtx750 ... i think - some worse hashrate even with manual setting to realtime... So release 32 no good for me (( Release 31 rulez ))