Hi guys, new to the forum, I've recently put together a rendering HPC and having hell getting this board to detect my GPU.
I'm running a PNY Quadro K5000 and have heard this issue affects GTX 6XX series GPU's as well (however I believe they are both PCIe 3.0 cards using the same Kepler chipset - GK104). Please note, I have made absolutely certain all power connectors (2x 8 EPS etc) are connected. I'm actually typing this from the HPC in question, so the build is solid, just the BIOS config/Firmware is in question. I've found the following (dot pointed for easier reading);
1. The card WILL NOT work in PCIe Slot 1 - period.
2. The card WILL work one out of perhaps 3-4 times in PCIe Slot 3 (but no other slot). This is purely random.
3. When the card fails to be detected I get a single beep, followed by three beeps at Q-Code 62, then another single beep and 8 short fast beeps.
4. My GTX 480 works flawlessly in ANY PCIe slot.
I have tried the following to correct the issue. Note; nothing has worked so far;
1. Cleared CMOS
2. Updated the BIOS to 3302 (updating from 0503 in steps, testing in various PCIe slots each update)
3. Although this is a BIOS POST issue, when booting was successful in PCIe Slot 3, I tried both nVidia Quadro/Tesla drivers 307.45 and 310.70
3. Tried different cards (GTX 480, 690) *Note, the 690 suffers from the PLX issue
5. Tried different slots (Only PCIe Slot 3 works (albeit randomly)
6. Enabled "VGA Palette Snoop", thinking this may force detection (it has worked for some, but not me)
7. Reseated RAM/CPU etc... no luck
8. Contacted PNY for any firmware updates - Their response; sorry this card has no updates - please return the card to the store for a refund (yes really!!!?)
9. Logged a ticket with ASUS - Their response; "Please clear CMOS for a try", "Also, please keep latest firmware of your vga card." (naturally i'd attempted both already)
10. Detailed the issue on the ASUS forums -
http://vip.asus.com/forum/view.aspx?id=20121229093923207&board_id=1&model=Z9PE-D8+WS&page=1&SLanguag... ... no response as at the time of this post
11. The PNY Quadro K5000 works flawlessly in any other single CPU board (ASUS P8P67 LE, EVGA X58 Micro)
12. The SMB(?) Error log shows Error 0x55 and the odd 0x00 (I think the latter is from mashing the reset button).
I've also left a review note on the Newegg.com PNY Quadro K5000 product page (as had two others) to warn people that Dual CPU boards don't seem stable enough yet to handle PCIe 3.0 lanes with newer generation GPUs. My guess is that perhaps firmware will be released to resolve this, else none of the newer generation GTX 6XX or Quadro cards will work in the ASUS Dual CPU boards (hell it won't even detect in an EVGA SR-X i'm told). One reviewer says he has the card running flawlessly in PCIe slot 2 (maybe he means x16 slot 2.. which would be PCIe Slot 3? i'd love to know his BIOS config for this!). This is the Newegg.com product review page -
http://www.newegg.com/Product/Product.aspx?Item=N82E16814133468&Tpk=quadro%20k5000The only way I can get the card working is to mash the reset button until the screen throws up the ASUS BIOS splash screen - sometimes I get lucky, others it takes up to 3-4 goes. I will note that once it has booted past the BIOS POST, the platform is rock solid and one hell of a performer! I just don't like to think i've thrown $9000AUD at a HPC that I have to mash the reset button on to get past POST. The issue is clearly in the detection of the card and should seriously be considered in the next firmware release as the board seems to be the common denominator here.
System specifications are below;
Mobo - ASUS Z9PE-D8 WS flashed up to BIOS 3302
CPU - 2x Intel Xeon ES 2600 series (C1 Stepping) 3.0GHz 8 Core (roughly E5-2687w equivalent)
SSD - 1x Intel 520 480GB (400i Firmware)
GPU - 1x PNY Quadro K5000 4GB
GPGPU - 1x nVidia Tesla K20 (For Maximus 2.0 configuration)
RAM - 64GB (8x8GB) Corsair Vengeance 1600MHz CL9
PSU - XFX Black Edition 1250w (modular, gold rated 80+)
BRD - ASUS BW-12B1ST Blu-ray Burner
If anyone has any ideas as to what options I could try in the BIOS (or anything else for that matter), i'm all ears! (or eyes as it were).