Where do you find your extenders? And are extenders no good for gaming?!
cards that are connected with extenders are terrible for gaming. My evaluation of your rig was on a pure mining basis. . You could always stick with 1 or 2 cards (connected via x16) while you game, and connect the rest of the cards using extenders. it's highly unlikely that you will use ALL of your card's processing power, but you'll save a ton of money. extenders can be obtained here: https://forum.bitcoin.org/index.php?topic=6128.0 (already pre-cut for x16 cards) or ebay (not pre-cut, but only $4 vs $16)
|
|
|
if you use sdk 2.4 + modified kernel for phoenix, the speeds are the same (or better) than sdk 2.1 + stock kernel. edit: and the colors in the chart mean nothing! see discussion: https://en.bitcoin.it/wiki/Talk:Mining_hardware_comparisonWhat is the color coding indicative of?
I think it is just a way to easily group cards of each type Fnord123 15:44, 23 May 2011 (GMT)
|
|
|
also, from a mining standpoint, crossfire is bad idea. (degrades performance)
|
|
|
don't buy that expensive motherboard. just get a cheap one, and use risers/extenders to utilize all the pci-e x1 slots. Also, you're wasting money with your i7, just get a AMD motherboard + cheapest CPU.
Everything i said above only applies to a dedicated miner, if you're using this for gaming, this build looks decent.
|
|
|
uh, no.
due to AMD/ATI's messed up naming scheme. the 6xxx cards have their second digit increased by 1. so a 6870 is comparable to a 5770, NOT a 5870
That's just the higher end Barts cards. The 6670 is an improved 5670 in essence. I see. Thanks for the correction
|
|
|
how much are you selling the 6970 for?
|
|
|
But yeah, a 5670 gets about 80 Mh/s and the 6670 is supposed to be the 5670's big brother, so if you're getting over 100 Mh/s you're doing quite well with that card.
uh, no. due to AMD/ATI's messed up naming scheme. the 6xxx cards have their second digit increased by 1. so a 6870 is comparable to a 5770, NOT a 5870
|
|
|
I guess I see the error in my logic now... In a perfect world, if reward was based just on Mhash/s and nobody was pool-hopping, I would earn the same reward no matter how long the round took.
I don't think that pool-hopping is an issue. When I watch the stats for the pool, they hardly change. And that sure seems like a lot of work for a few fractions of BTC's.
I got a script set up that does it for me :3
|
|
|
Wait, WHAT? So all that stuff about "bitcoins are divisible to the 8th decimal point, so deflation is handled by using smaller fractions of a coin" is all bullshit? How the FUCK are we supposed to use fractions of a coin if the fee is going to be many times the amount being actually sent?
Wow... I guess as bitcoin rises in value this problem will become more visible. Time to bail on the whole thing then.
it's going to be patched next version
|
|
|
your should be able to overclock your 5870 way more. i get 400 MH/s with my 5850. 1010 core, 250 mem
|
|
|
Ok, I guess i was being too cautious, probably because i read somewhere that this wasn't good for crossfiring. thanks for all your input guys.
|
|
|
too lazy to type address manually
|
|
|
However, since registering those names, the other 8 blocks I mined have not shown up in my wallet, and I have not mined another block successfully for nearly a two day period (when I was mining about one every two hours before.)
Any idea what has gone wrong, and how I can get this up and running again? Thanks.
orphan blocks. if you're using the latest binaries, listtransactions should be able to reveal which blocks are orphaned.
|
|
|
I am slashing the price down to 250 BTC.
your original price was 400 btc, which was less than $20(February prices). now you're selling it at 250, which is approximately $2100.
|
|
|
would you sell one for 18 19 btc?
|
|
|
I recommend not crossfiring your cards, and instead using a VGA dummy plug for each.
can you explain more 1. search for "VGA dummy" 2. you're done!
|
|
|
Forbidden You don't have permission to access / on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
|
|
|
|