3dcgminer
|
|
June 25, 2013, 07:01:48 PM Last edit: June 25, 2013, 09:25:44 PM by 3dcgminer |
|
Got my 7970 running again by lowering intensity from 13 to 11 and increasing TC from 8192 (--thread-concurrency 8192) to 10240 (--shaders 2048). Same worksize 256 and same g 2 and same --lookup-gap 2. Deleted the bin files before starting yaminer.
Reduced hash rate by over 60%, so there is a lot more tweaking to do...
Pool went from 35Mh to 7Mh, guess all GPU's got killed by the N factor.
EDIT Still getting HW errors, trying lower intensities
|
|
|
|
paulthetafy
|
|
June 25, 2013, 07:07:04 PM |
|
I'm still getting shares accepted, even with the HW errors. so what do the HW errors actually mean?
|
|
|
|
bitdwarf
Sr. Member
Offline
Activity: 406
Merit: 250
The cryptocoin watcher
|
|
June 25, 2013, 07:08:34 PM |
|
Well, I saw one accepted share, but I think the effective mining rate is very low now.
It's a 6850 with 1GB of memory, I wonder if GPU's with more memory are faring better.
|
𝖄𝖆𝖈: YF3feU4PNLHrjwa1zV63BcCdWVk5z6DAh5 · 𝕭𝖙𝖈: 12F78M4oaNmyGE5C25ZixarG2Nk6UBEqme Ɏ: "the altcoin for the everyman, where the sweat on one's brow can be used to cool one's overheating CPU" -- theprofileth
|
|
|
amytheplanarshift
|
|
June 25, 2013, 07:09:33 PM |
|
Looks like YAC is working as intended. I love this coin!
|
|
|
|
paulthetafy
|
|
June 25, 2013, 07:11:57 PM |
|
Looks like YAC is working as intended. I love this coin! maybe, but the botnets and server farm owners are in control again now
|
|
|
|
paulthetafy
|
|
June 25, 2013, 07:22:57 PM |
|
Back to LTC for me. YAC is a great idea and I mined it with CPU before the GPU miner came out, but the N increase has come around too quickly. Unless the price rises 50x I can't see why anyone would mine this with their own equipment.
|
|
|
|
eule
|
|
June 25, 2013, 07:30:28 PM |
|
Funny how noone has predicted that.
|
|
|
|
paulthetafy
|
|
June 25, 2013, 07:32:07 PM |
|
the botnets and server farm owners are in control again now
Back to LTC for me. YAC is a great idea and I mined it with CPU before the GPU miner came out, but the N increase has come around too quickly. Unless the price rises 50x I can't see why anyone would mine this with their own equipment.
Come back when you finaly learn how YAC works. Please enlighten me. Diff hasn't changed and I don't think reward has either (but I'm happy to stand corrected on both). So right now it is very far from profitable to mine this with a CPU or GPU.
|
|
|
|
eule
|
|
June 25, 2013, 07:33:29 PM |
|
Diff and reward change slowly.
|
|
|
|
paulthetafy
|
|
June 25, 2013, 07:36:26 PM |
|
Diff and reward change slowly. Yes that reinforces my point. Until the reward and diff change it is not profitable to mine with my GPU. I'll carry on CPU mining it like I have since day 1.
|
|
|
|
Thirtybird
|
|
June 25, 2013, 08:56:16 PM |
|
It doesn't appear to me that the hardware error messages are impacting the hashrate or the acceptance rate onto the pool I use.
For comparison, I utilized the original kernel hanzac distributed, and got ~87 KH/sec and 9 shares accepted in 5 minutes - it generated no hardware errors, it just had a low hash rate. Mikaelh's v5 kernel gives me ~ 143 KH/sec and 14 accepted shares in minutes even with the posted hardware errors. (This is with a 7850)
mine on folks...
|
|
|
|
xavenged
Member
Offline
Activity: 104
Merit: 10
|
|
June 25, 2013, 09:13:47 PM |
|
It doesn't appear to me that the hardware error messages are impacting the hashrate or the acceptance rate onto the pool I use.
For comparison, I utilized the original kernel hanzac distributed, and got ~87 KH/sec and 9 shares accepted in 5 minutes - it generated no hardware errors, it just had a low hash rate. Mikaelh's v5 kernel gives me ~ 143 KH/sec and 14 accepted shares in minutes even with the posted hardware errors. (This is with a 7850)
mine on folks...
which pool are you using?
|
|
|
|
Bakaboy
Newbie
Offline
Activity: 53
Merit: 0
|
|
June 25, 2013, 09:14:32 PM |
|
Diff and reward change slowly. With the pool I'm using, I'm getting block times of 35 - 45 minutes after the N change. Factoring in the very slow difficulty adjustment and the pending July 7 N factor change (12 days ETA), yields will probably be still recovering when it does a massive tank again. Gotta love this coin, it just wants to punch you in the face then chew on it for good measure.
|
|
|
|
eule
|
|
June 25, 2013, 09:22:43 PM |
|
Gotta love this coin, it just wants to punch you in the face then chew on it for good measure. Thanks for the clue with the first version of the miner, my 5770 got no accepted shares with v5 but v1 gets me a whopping 25kH.
|
|
|
|
fenican
|
|
June 25, 2013, 09:24:50 PM |
|
So it appears we'll have to all stop mining for awhile and let a few unprofitable bagholders hang on until the difficulty adjusts back down a level that matches the negligable reward
|
|
|
|
mikaelh
|
|
June 25, 2013, 09:38:24 PM |
|
Yeah, it's probably a good idea to hold off mining for a while. Difficulty should actually adjust faster that way. There's a bug in v5 causing the HW errors. I'll release a new kernel soon.
|
|
|
|
3dcgminer
|
|
June 25, 2013, 09:47:07 PM |
|
Yeah, it's probably a good idea to hold off mining for a while. Difficulty should actually adjust faster that way. There's a bug in v5 causing the HW errors. I'll release a new kernel soon.
Sweet, thanks mikaelh. tried all settings and all gave me HW errors sooner or later. The v5 script bug means that most GPUs are offline, for example http://yac2.ltcoin.net/ is down from 35 to 5 MH/s, so difficulty should adjust soon.
|
|
|
|
|
xavenged
Member
Offline
Activity: 104
Merit: 10
|
|
June 25, 2013, 10:15:49 PM |
|
Here's a new version which should fix HW errors for most people. scrypt-chacha-v6.clhttps://mega.co.nz/#!NhFFxSzC!I7gIqnxyL7LLR5rP8E60bAjAQQFGueDHv1wygufQm0c Remember to delete your *.bin files. If you are still getting HW errors, you need to increase either thread concurrency or lookup gap. thank you
|
|
|
|
ivanlabrie
|
|
June 25, 2013, 10:18:33 PM |
|
Here's a new version which should fix HW errors for most people. scrypt-chacha-v6.clhttps://mega.co.nz/#!NhFFxSzC!I7gIqnxyL7LLR5rP8E60bAjAQQFGueDHv1wygufQm0c Remember to delete your *.bin files. If you are still getting HW errors, you need to increase either thread concurrency or lookup gap. Trying it now...seems like yac either killed my card or my win 7 install got borked with your v5 kernel somehow (?) I can't mine other coins either, getting tons of hw atm. (this is when trying to mine ltc)
|
|
|
|
|