The problem with my Version 2.2 boards is the board would not boot with just 2 x PCI-E connectors on the board.  I had to still hookup a power cable to the +12V and  Ground screws AND also hookup the 2x PCI-E power cables.

Then the board booted.  I tried to boot 2 different Rpis and 2 Different M-boards with 2 different h-boards only on 2 x PCI-E power cables to the PCI-E power connectors and they simply would not boot properly.

I've got the same problem as ninja. I'm trying to figure out what I can do while I wait for the molex cables in the mail.

Would it make sense to use another Pcie cable, and cut the ends off of it to use the bare wires for this? would I need 2 different PCIE cables or would 1 that splits into 2 be enough?

Thanks

   Are you sure that you cant buy it for Oct. delivery?

 ... one of the reasons I have him on ignore =/ I feel bad for Con having such a polarizing teammate

 Even worse that it was Kano's attitude that drove me to use bfasjdhfgkahsdfghalkgMiner instead of CGminer over his constant crying over not getting free hardware in a timely manner.

 *additionally mentions something about bfasjdhfgkahsdfghalkgMiner having an uptime of over 8 days driving Erupter USB's on Windows vs CGMiner consistently crashing after 24-48 hours of use. Mumbles something about "gg libusb"*

OK - I've got a serious problem here.  My main-board just smoked two Raspberry PI's.  One will no longer come on at all, the other will turn the red light on connected to an external source away from the m-board, but a couple of the chips on the RPi get extremely hot very quickly, to the point where they burn your fingers if you touch them.  I know that's not right.

The chip that now gets so hot on the RasPi is labelled RG2.  I have one other m-board and a personal RasPi that I'll try, but I don't know for certain that the replacement board I received doesn't have the same problem - I've never tried it because I've been running both h-cards in one main board - the one that just smoked the RPis...

hmmm... I smoked Raspberry tobacco, it smelled nice. 

Version 1.  It's been running 24 x 7 since early this month.  Noticed sudden hashrate drop at Slush.  Sniffed.  Smelled hot electrical components.  Shut everything down.  Chip extrememly hot, Raspberry Pi completely dead.   Removed hashing cards, checked voltages on m-board.  5.06 on the appropriate GPIO pins.  Shut everything down, plugged the RasPi into the m-board and powered up with no hashing cards in it.   Red light came on and I had my hand on the back of the Pi on the side opposite of the chip that got so hot on the first one - it got very hot, very fast, so I shut down.  

This Pi not as completely dead as the first one, if you remove it from the m-board and plug it into external power, the red light comes on, but that's it, won't boot, no light for the network cable.

Pulled the case of a third Pi that I had hashing with some Block Erupters and switched main boards.  Worked fine.  Tried both RPis in the second mother board - neither work.  Switched over the hashing cards and am hashing with the second m-board...

At least I'm up and running again, but I appear to have a main board that went bad and produced two crispy, burned up, RaspberryPIs ...

    Did you get EOL Hboards?

ps: you are scaring me and I am going to check my RBpi for any overheal.

bringing my tech problems back to this thread (i got some fast replies last time):

i got a monitor and keyboard now to manually get the rpi running, and cannot even login.

It appears to load the entire code, and gets to

"(none) login:"

I enter pi as the username and get this response:

"unable to determine your tty name.
Debian GNU/Linux 7 (none) ttyl

(none) login: "


whats going on?