Be advised, you have an incoming bitcoin targeted at the Kenya humanitarian expedition.
You guys rock!

try -p ""

Try Noiseblocker:
http://www.noiseblocker.de/en/BlackSilentPro120.php
http://www.noiseblocker.de/en/Multiframe120.php

Very quiet for their rotation speeds - I use the 140mm Blacknoise Silent Pro PK3 fans and at 1700RPM the motor noise is totally thwarted by the whooshing of air rushing through the fan.

The 6 year warranty and declared MTBF of up to 180000 hours do confirm that the manufacturer did an awesome job with the fan bearing.

Some AirPenetrator fans by Silverstone are capable of delivering very decent airflow (I love the gargantuan 180mm fans that came with my Raven case) but they are noticeably louder than their Noiseblocker equivalents.

Why couldn't you?
It's still a legitimate PCIe connection, all protocols will work as expected. The only difference is you get far less bandwidth (fewer receiver/transmitter lanes) this way.

Yes, such adapters are widely used.
You should experience no bottleneck due to minimal bandwidth utilization while mining.
Yes, go for it.

You might also consider externally powered adapters like this one for energy hungry multi GPU configurations.

I'm shocked at how easily you judge a man based on a single graphic file found online.
As far as I'm concerned, P4man needs to disclaim or explain nothing, least of all to you.

Stickied? Well done, let's hope the hash rate skyrockets to 3xx where it belongs.
Thanks for all your hard work Doc.

...luckily for you since you really shouldn't mess with that PSU of yours.

It's mostly the bridge rectifiers and power mosfets one needs to worry about in a PSU.
You won't find any obvious differences between these because they come in industry standard packages (e.g. TO-220).
You need to study the datasheets to learn the exact specifications.
The fact that you're not even aware of this is proof positive that you shouldn't think of tampering with the PSU.

BTW, capacitors are merely used for filtering and ripple suppression.
Replacing that "grain silo" will not increase the output power.

A few data points pertinent to those PSUs:

OCZ ModXStream 700W:
- Very unimpressive - by today's standards - 550W at 12V rails due to the unit being a...
- ...dated design. (it's a 2008 PSU, folks)
- Cheap^WHigh-value components made the unit struggle at higher loads. (HardOCP)
- Very few PCIe connectors (one 6 pin, one 8 pin) necessitate the use of adapters.

OCZ Fatal1ty 750W:
- Quad rail design means you need to pay close attention to how you wire things.
  Moreover, the rail distribution is wacky:
    12V1 (solid yellow wires): Main motherboard cable.
    12V2 (yellow/red wires): Half of the ATX12V/EPS12V connector (ummm... wtf?).
    12V3 (yellow/green wires): Half of the ATX12V/EPS12V connector, half of the modular connectors (two for video cards and two for SATA/peripheral).
    12V4 (yellow/black wires): EPS12V connector, half of the modular connectors (two for video cards and two for SATA/peripheral). (HardwareSecrets)
- Two hardwired CPU connectors might necessitate the use of an ATX12V->PCIe adapter.
- The unit burnt down under an overload condition instead of safely shutting down. (HardwareSecrets)


As long as the limitations of both units are understood, the rebated price tags make this opportunity a no-brainer.

Death, when using USB drives add these two lines to your .bashrc file⁽¹⁾ and never worry about issuing the command by hand:
alias poweroff='sync ; poweroff'
alias reboot='sync ; reboot'

Notes:
(1) and to /root/.bashrc as well

Ummm... no, I really believe it's some user error on your part.

You REALLY want to supplement the aticonfig --initial --adapter=all command with the -f flag, otherwise aticonfig will only modify your current xorg.conf if it appears broken.
Naturally, adequate (root) privileges are required to modify the file.

Those warnings basically say
"Hey dude, Gavin says this file here is his public key but no trusted Certificate Authority is backing up the validity of this claim.
Tell Gavin to pony up some big bucks and make Verisign, Thawte, Comodo, Equifax, Hongkong Post, TurkTrust⁽¹⁾, or DigiNotar⁽²⁾ happy."


If a hacker were able to breach bitcoin.org's server and replace Gavin's public key and they were then able to breach the SourceForge repositories and replace the files with malicious ones, anyone validating the bad executables with the bad public key could be cheated into thinking that everything is fine.
In short, if a hacker gets full control over everything, we're screwed - film at 11.

For the record, the fingerprint of Gavin's public key is indeed 2664 6D99 CBAE C9B8 1982  EF60 29D9 EE6B 1FC7 30C1



Notes
(1) You may not have known but your system trusts hundreds of entities. From its POV Hongkong Post is just as trustworthy as Verisign. Better believe someone in Hongkong did their due dilligence when signing those SSL certificates.
(2) I put DigiNotar in as a joke; this CA fell victim to a hacker attack last year. As a result, they went keel up and sank.
     The SSL certificates the hackers were able to generate were inherently trusted by any machine in the world. So much for trusted CAs.
     You better believe TurkTrust and Hongkong Post really know what they are doing
     There have been several initiatives to mitigate the flaws in the current trusted CA model.

Reposted from Newbies as requested by Cyberdyne
Contact Cyberdyne, not me.

Reposted from Newbies as requested by Cyberdyne
Contact Cyberdyne, not me.

Righto.
Just make sure your solid state relay uses optical coupling (most do) or add a photocoupler yourself.

Nothing prevents you from launching a separate cgminer instance for each of your GPUs.

The issue with AMD cards from 6xxx generation onwards is that when they go down, they usually go down hard - not only will you be unable to resurrect them but if it is the system's primary⁽¹⁾ GPU that dies it can effectively take the whole system down by introducing freeze periods of a few dozen seconds each time the kernel is trying to access the non-responsive card.
Luckily, reboot -f has worked quite reliably for me, though situations where cycling the power was necessary have been reported in these forums.

Notes:
(1) usually closest to the CPU socket unless GPU ordering is changed in BIOS

...or (memory) underclock.
Not only am I talking about going below the physical capabilities of the ram chips but some particularly bad core-to-memory clock ratios can erally destabilize the GPUs with symptoms ranging from performance holes, through HW errors, to hard crashes.
I personally believe this rare but repeatable stability loss might be the core reason for AMD imposing the memdiff since the 6xxx generation cards.

I like some of your posts here, Death, especially your touching on the extremely subjective notion of card stability.
How about we formalize (in an informal way ) and shorten some of your stability thresholds:
#define CIS "crash in seconds"
#define CIH "crash in hours"
#define CIW "crash in weeks"
#define CIM "crash in months"
#define CIY "crash in years"       //the holy grail of overclocked mining

I've seen the CIS to CIM delta to range from an astounding 8 MHz (that's a great overclock) to the unimpressive 35 MHz (an XFX 6970 that really pissed me off until I understood its finickyness).

use AdblockPlus:
|http://www.examiner.com/images/blog/wysiwyg/image/yoga_-_urdhvamuka_tiny_0_0.jpg

I thank thee kindly, Dave, just got the stone.
Gorgeous indeed.

Perhaps this will help you:
regedit -> navigate to (create keys if necessary) HKLM\software\policies\microsoft\windows\windowsUpdate\au -> create a new DWord value named NoAutoRebootWithLoggedOnUsers and set its value to 1

If you really don't like messing with the registry and happen to be using the Professional/Enterprise edition, many configuration settings can be tweaked via the Group Policy Editor (gpedit.msc). More info.

IMPO, gpedit is one of the greatest benefits of the Professional and higher editions of Windows7, along with a free Windows XP virtual machine (XPMode) and virtual hard drives support.