I still think it would be hard to create a water block that will be able to absorb 3000W of heat from a square inch. i think you would then need micro channels or tubes through the GPU chip itself to remove the heat.
No reason for it to be 3000W from 1" squared. Even if you could do that the outer chip layers would act as an insulator and "cook" the inner chips. You could simply have a chip-waterblock sandwhich. waterblock chip waterblock chip waterblock chip waterblock chip waterblock or maybe something more like a stacked grid array (4x4 chips under a waterblock and then stacked) I think I saw something about interleaving chips with liquid cooling pathways... i think it was IBM?
|
|
|
what driver version are you on?
|
|
|
if AMD would just make gpu chips stack-able in to arrays that would be something
that would be awsome get 10 HD6970 chips stacked together.. it could dump 3000 watts of heat in a square inch. just have to figure out how to cool it with a very cold liquid
|
|
|
what's postulated here regarding botnets and bitcoin is lala-land...
no-one is going to not notice GPU being in use and they will figure it out...
further more, botnet'ed computers are probably not modern systems with up to date security (unless it got disabled, yeah, sure there maybe a small number, but not constant like this)... so that leaves botnets to be full of "older" poorly attended to/neglected computers... this is not going to be a system with lots of computing power by any good measure.
so, CPU is the only thing a botnet is good for for bitcoin hashing...
so if we assume that this really is out there on a MASSIVE scale of 50K machines and if you assume 2 Megahashes per CPU (could be hidden when idle), we then have ~100,000 Mhashes/sec. or 100 Gigahashes? is that right?
this would be hardly noticeable...
does this make sense?
|
|
|
Don't forget the botnets! Since there is now malware out that can utilize a person's GPU to mine coins, I wouldn't be surprised if as much as 1/3 of all the TH/s is acquired through botnet activity.
1/3rd??? how do you figure that number? that would be PR disaster for bitcoin...
|
|
|
drivers are recognizing a flashed/changed bios and crapping out... Also, apparently AMD has put stuff in to disallow downcklocking memory. https://bitcointalk.org/index.php?topic=43990there are other treads I've posted on to this effect, just too lazy to dig them all up right now... I thought this only affected Windows users? Right now I'm running with 3 6970's and 1 6990 in the case, and I've already BIOS flashed the 6970's to run @ 300MHz memory speeds, and there's no problems with them.. only the 6990 is causing a problem with booting into Ubuntu. nope... it's in drivers AMD writes...
|
|
|
it's bad, you don't want it anymore... just give it to me...
|
|
|
drivers are recognizing a flashed/changed bios and crapping out... Also, apparently AMD has put stuff in to disallow downcklocking memory. https://bitcointalk.org/index.php?topic=43990there are other treads I've posted on to this effect, just too lazy to dig them all up right now...
|
|
|
I can't believe we're another 6 months into this experiment and people still don't understand that the auto-adjusting difficulty means that # of miners has absolutely nothing to do with the supply of bitcoins, thus nothing to do with the demand for bitcoins except in really indirect ways (a miner being perhaps more likely to increase demand for bitcoins by evangelizing about them or convincing a local retailer to accept them, etc)
spot on!
|
|
|
Which only helps those who currently run a business. The average person can't deduct anything like that from their taxes. And as soon as you're filing taxes for a business, H&R Block charges you $350, not $35.
turbotax.
|
|
|
Calculating ROI by speculating on future BTC value is fallacious. If you want to speculate, you can just buy BTCs with dollars. The same dollars you need to buy hardware and electricity cost, so they compete.
pretty much all ROI calculations are based on assumptions and "speculating on future" BTC is not immune to that. you just have to try to some close to "guessing" what reality/future will be... variance is used to create several situations/expected outcomes and then you can use probability to pick a scenario that is most likely to happen.
|
|
|
Yeah IIRC, your internet connection has a lot to do with stales. High latency = more stales, but I'm not sure why.
doesn't get there fast enough?
|
|
|
it probably is not counterfeit at all. Most likely it's an "illegal" run on same production/assembly lines. or maybe these are slightly outside of quality control specs by AMD? They may work for some time just fine, but could fail at a higher rate than "good" cards...
|
|
|
That's weird, I definately searched first, but I might have messed up and done it under a sub category.
Sorrys. Can I delete my thread somehow?
no, but if you have another question for this sub, you can edit your post and change the words...
|
|
|
Did you contact the Bitcoin Police?
how do I do that anonymously?
|
|
|
Well... this bitcoinbonus does appear to be a scam...
nothing. no replies, no bitcoins.
how do I get this info sticky so that other miners do not get ripped off?
|
|
|
Well... this bitcoinbonus does appear to be a scam...
nothing. no replies, no bitcoins.
how do I get this info sticky so that other miners do not get ripped off?
|
|
|
2052 Mhashes (2 5970 + 1 5850): Is that a Silverstone Raven 2 case? Silverstone TJ11
|
|
|
I'm having the same trouble (though memory clock jumps to 300) under Linux.
Is there an aticonfig command I've missed out? I've enabled overdrive and set the peak memory clock to 300, but the utility reports that I'm running 1050.
I've had this issue with every 6XXX series card I've used in Linux (Ubuntu 10.10). Using aticonfig I've never been able to set my XFX 1GB 6950s memory clocks less than 125mHz lower than the GPU clock. In order to set memory clocks outside of the default ranges at all, I have to use AMDOverdrivectrl to set the default clocks for each power state, but even those don't 'stick' - as soon as I 'push' the card the memory clock ramps up to max. The 6870 I picked up recently won't drop below 100mHz less the GPU clock. It seems to be the same issue as Windows boxen, but at least there the manufacturers have specific utilities to get around it. It also appears that it may be vendor/card version specific, as some people have had success underclocking mem on a handful of these cards in Linux. With the BTC prices so low and my power usage so high lately, I'm resorting to bios flashing a lower memory clock and voltages on all of these cards this weekend. Totally kills their use in Windows or for gaming (unless you flash them back), but will be worth it for mining - at this point I need to eek out every bit of efficiency I can in order to stay above water. https://bitcointalk.org/index.php?topic=35792
|
|
|
|