vs3
|
|
June 18, 2013, 09:48:03 PM |
|
If you're using a non-ATI (non-reference) card make sure to use the drivers from that card's manufacturer. I had the same issue with a non-reference MSI card - I had to use MSI's drivers.
.....they dont make there own drivers I didn't say they made their own drivers entirely by themselves. They most likely started with ATI's drivers and customized them to work with their card's design. What I said is that ATI's drivers will not work (since the card is not an ATI-reference one). So you have to use the drivers that are customized for that card.
|
|
|
|
not.you
Legendary
Offline
Activity: 1726
Merit: 1018
|
|
June 18, 2013, 09:52:39 PM |
|
2013-06-17 22:37:11: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:11, Verification failed, check hardware! (0:0:Barts, ce5273db) 2013-06-17 22:37:13: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:13, Verification failed, check hardware! (0:1:Cypress, 727d93c7) 2013-06-17 22:37:20: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:20, Verification failed, check hardware! (0:0:Barts, a2952421) 2013-06-17 22:37:29: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:1:Cypress, 70fe5733) 2013-06-17 22:37:29: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:0:Barts, 0df11781) 2013-06-17 22:37:31: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:31, Verification failed, check hardware! (0:1:Cypress, 0558f90a) 2013-06-17 22:37:37: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:37, Verification failed, check hardware! (0:1:Cypress, 1e22764a) 2013-06-17 22:37:40: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:40, Verification failed, check hardware! (0:2:Juniper, 00d0bf18) 2013-06-17 22:37:44: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:2:Juniper, a415432f) 2013-06-17 22:37:44: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:0:Barts, fb1cb804) 2013-06-17 22:37:45: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:45, Verification failed, check hardware! (0:1:Cypress, 9e719e0e) please help me diaganosis this
Probably a Catalyst problem. Are you using 12.8, and what driver version? I would backoff to catalyst 11.11 for the older graphics cards. This worked for me. +1. I had this when I updated drivers on my 6xxx series cards. Easy fix steps are here: https://bitcointalk.org/index.php?topic=177855.0
|
|
|
|
EasyQuest
Full Member
Offline
Activity: 198
Merit: 100
Brony Bitcoin, Litecoin Miner
|
|
June 19, 2013, 12:44:35 AM |
|
Glitchy sometimes but it fixes itself
|
|
|
|
guytechie
|
|
June 19, 2013, 01:31:07 AM |
|
2013-06-17 22:37:11: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:11, Verification failed, check hardware! (0:0:Barts, ce5273db) 2013-06-17 22:37:13: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:13, Verification failed, check hardware! (0:1:Cypress, 727d93c7) 2013-06-17 22:37:20: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:20, Verification failed, check hardware! (0:0:Barts, a2952421) 2013-06-17 22:37:29: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:1:Cypress, 70fe5733) 2013-06-17 22:37:29: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:29, Verification failed, check hardware! (0:0:Barts, 0df11781) 2013-06-17 22:37:31: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:31, Verification failed, check hardware! (0:1:Cypress, 0558f90a) 2013-06-17 22:37:37: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:37, Verification failed, check hardware! (0:1:Cypress, 1e22764a) 2013-06-17 22:37:40: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:40, Verification failed, check hardware! (0:2:Juniper, 00d0bf18) 2013-06-17 22:37:44: Listener for "6750": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:2:Juniper, a415432f) 2013-06-17 22:37:44: Listener for "6850": stratum.bitcoin.cz:3333 17/06/2013 22:37:44, Verification failed, check hardware! (0:0:Barts, fb1cb804) 2013-06-17 22:37:45: Listener for "5850": stratum.bitcoin.cz:3333 17/06/2013 22:37:45, Verification failed, check hardware! (0:1:Cypress, 9e719e0e) please help me diaganosis this
Probably a Catalyst problem. Are you using 12.8, and what driver version? I would backoff to catalyst 11.11 for the older graphics cards. This worked for me. +1. I had this when I updated drivers on my 6xxx series cards. Easy fix steps are here: https://bitcointalk.org/index.php?topic=177855.0I have the same problem, too. I have a 6970 and found that reaper works fine with the newest driver and SDK. If I want to use other miners, should I pair the newest SDK (2. with driver version 11.11?
|
Put something in my tip jar if I made your day. BTC: 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu
|
|
|
stephengillon
Newbie
Offline
Activity: 56
Merit: 0
|
|
June 19, 2013, 01:55:18 AM |
|
If you're using a non-ATI (non-reference) card make sure to use the drivers from that card's manufacturer. I had the same issue with a non-reference MSI card - I had to use MSI's drivers.
.....they dont make there own drivers I didn't say they made their own drivers entirely by themselves. They most likely started with ATI's drivers and customized them to work with their card's design. What I said is that ATI's drivers will not work (since the card is not an ATI-reference one). So you have to use the drivers that are customized for that card. the drivers on there website are for idiots that dont know how to get them from amd nonrefrence has nothing to do with a driver
|
|
|
|
vs3
|
|
June 19, 2013, 07:18:13 AM |
|
If you're using a non-ATI (non-reference) card make sure to use the drivers from that card's manufacturer. I had the same issue with a non-reference MSI card - I had to use MSI's drivers.
.....they dont make there own drivers I didn't say they made their own drivers entirely by themselves. They most likely started with ATI's drivers and customized them to work with their card's design. What I said is that ATI's drivers will not work (since the card is not an ATI-reference one). So you have to use the drivers that are customized for that card. the drivers on there website are for idiots that dont know how to get them from amd nonrefrence has nothing to do with a driver Well, I guess I'm an idiot then. I tried every driver available from AMD and none of them worked until I installed the one from MSI. Edit: they worked sufficiently well for Windows. Just not for mining (no matter which client - I tried about a dozen). For mining though I had to use MSI's (or enjoy looking at "hardware error" messages).
|
|
|
|
Frizi
Newbie
Offline
Activity: 14
Merit: 0
|
|
June 19, 2013, 10:33:44 AM |
|
The miner's Mhash/s calculation is based on number of shares. When i jump in during the round, it stays low because of that, but my score is OK after a short time. Shouldn't the calculation be based on score? It would be much more trustworthy.
|
|
|
|
trasla
|
|
June 19, 2013, 10:49:40 AM |
|
If i got this right, later shares give higher scores, to prevent pool hopping. Calculating the hashing speed based on score would not be correct. If its the way you state, maybe the current hashing speed should not be calculated via shares/round but lets say shares/last five minutes.
|
|
|
|
sundownz
|
|
June 19, 2013, 12:20:52 PM |
|
Does Slush's pool support CPU miners ? I have 10 dedicated machines currently on electricity that is included in my rent -- so I'd like to go ahead and activate most of the cores for mining. I started 7 of 8 cores on my office computer on mining (I use it for e-mails mostly) but it doesn't seem to be getting any shares in about 15 minutes; just keep waiting perhaps ?
|
|
|
|
EasyQuest
Full Member
Offline
Activity: 198
Merit: 100
Brony Bitcoin, Litecoin Miner
|
|
June 19, 2013, 12:23:01 PM |
|
Does Slush's pool support CPU miners ? I have 10 dedicated machines currently on electricity that is included in my rent -- so I'd like to go ahead and activate most of the cores for mining. I started 7 of 8 cores on my office computer on mining (I use it for e-mails mostly) but it doesn't seem to be getting any shares in about 15 minutes; just keep waiting perhaps ?
CPU mining is pointless now that ASICs is dominating the market and shares are far and between with CPU so 15 minutes is normal.
|
|
|
|
sundownz
|
|
June 19, 2013, 12:34:42 PM |
|
Okay thanks. It did just get one share a minute ago Already running these systems + no cost for power so figure it won't hurt !
|
|
|
|
diskodasa
|
|
June 19, 2013, 01:03:00 PM |
|
Really!? Pool luck (1 day, 7 days, 30 days): 44%, 84%, 95%
|
|
|
|
ZipTheRip
Member
Offline
Activity: 75
Merit: 10
|
|
June 19, 2013, 01:11:04 PM |
|
it was a catalyst/ driver prob.. reinstalled OS and just rebuilt my rig from there.. hashing away now again!!! thanks for all of the help!!
|
|
|
|
gourmet
|
|
June 19, 2013, 01:30:24 PM |
|
If i got this right, later shares give higher scores, to prevent pool hopping. Calculating the hashing speed based on score would not be correct. If its the way you state, maybe the current hashing speed should not be calculated via shares/round but lets say shares/last five minutes.
This would raise the variance/inaccuracy especially for slow miners. I believe it's better to keep it as it is, it works fine for full-time miners, and for the others - they have to remember that non-complete round just displays false speed.
|
|
|
|
|
gourmet
|
|
June 19, 2013, 01:41:26 PM |
|
It's too early to predict... Graph says, just for now, network rate is going down. But I don't believe this will last for a long time, it looks more like a fluctuation. Maybe whole network is now so "lucky" as our pool is... ;-) http://bitcoin.sipa.be/I'd be very glad if the difficulty did not go up too much next time. Just not believing it will go down.
|
|
|
|
gourmet
|
|
June 19, 2013, 01:43:17 PM |
|
Really!? Pool luck (1 day, 7 days, 30 days): 44%, 84%, 95%
I was just about to post this. Yes, luck is really compensating us for the last days... :-))))))))
|
|
|
|
Tamis
|
|
June 19, 2013, 02:19:05 PM |
|
I was wondering too about the lowering of the total network hashrate !
Anyone knows what is happening ? I'm really surprised about this...
|
|
|
|
Trongersoll
|
|
June 19, 2013, 02:27:43 PM |
|
I was wondering too about the lowering of the total network hashrate !
Anyone knows what is happening ? I'm really surprised about this...
Well, based on what i've read on the forums here, Avalon has stopped using customer's rigs for mining. Also, i saw that, i think it is BFL is playing with a 500 Gh/s rig, no sure how much difference that makes.
|
|
|
|
n0creativity
Member
Offline
Activity: 65
Merit: 10
|
|
June 19, 2013, 02:51:16 PM |
|
I was wondering too about the lowering of the total network hashrate !
Anyone knows what is happening ? I'm really surprised about this...
Well, based on what i've read on the forums here, Avalon has stopped using customer's rigs for mining. Also, i saw that, i think it is BFL is playing with a 500 Gh/s rig, no sure how much difference that makes. Well that's just obnoxious... I may be wrong here but from what I understand, the difficulty jumps as a method of keeping found blocks at about 10 minutes apart. The higher the network hashrate, the quicker the blocks are found (at any single given difficulty). So the network hashrate being around 125,000-140,000 caused the difficulty to jump significantly in attempt to reduce block frequency and then whatever\whoever accounted for the 15,000-30,000 drops out and we are left with too high of a difficulty for the current hashrate. Hence the find rate is about 12.5 minutes right now according to blockchain.info. I know network hashrate with grow again, maybe naturally or maybe when that 15,000-25,000 come back but it really screws with the rest of us. I would hope there would be some level of self-imposed responsibility when people have enough hashing power at their disposal to significantly affect the entire network... Then again, I'm not too surprised that hope is in vain. Whatever, I'll keep plugging away with my 1.5GH/s and continue to catch the scraps off the table of the huge miners. -n0c
|
|
|
|
|