Radeon R9 Cards Not Passing POST

Message boards : Number crunching : Radeon R9 Cards Not Passing POST
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 33181
Credit: 79,922,639
RAC: 80
Germany
Message 1511938 - Posted: 3 May 2014, 22:12:47 UTC

I`m using a HD 7970 which is almost identical to the 280x PCIe 3.0 card in a PCIe 2.0 board without any problems.
With each crime and every kindness we birth our future.
ID: 1511938 · Report as offensive
Profile dnolan
Avatar

Send message
Joined: 30 Aug 01
Posts: 1228
Credit: 47,779,411
RAC: 32
United States
Message 1512005 - Posted: 4 May 2014, 0:50:03 UTC

I have an HD 7950 that works fine in an Asus P5Q Deluxe board, too, and that is a pcie 2.0 spec motherboard... Also have an old Dell XPS 420 running an R7 265 which is a newer version of the HD 7850, the chipset is X38, which I think is the same as the p5e. How powerful is the power supply in that system?

-Dave
ID: 1512005 · Report as offensive
Wedge009
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 451
Credit: 431,396,357
RAC: 553
Australia
Message 1512036 - Posted: 4 May 2014, 2:04:53 UTC

Hmm, that's interesting indeed. Yes, the P5E3 uses X38.

The power supply is rated for 850W, certified 80 Plus Gold. I believe that should be sufficient for these two GPUs. The system used to run a HD 6970 (till the card died) together with the existing GTX 580 - both have a TDP of about 250W, which is also what the HD 7970 / R9 280X are specified as.

I wondered if there was any difference with regards to the BIOS between the HD 7000 series and the rebadged R9 200s, but as you say you're running the R7 265 okay. As I said before, I didn't have any success with the R9 270 either. Unfortunately I don't have a way of testing if it's just the Gigabyte cards that disagree with the motherboard. Then again, the HD 6950 and GTX 580 are also Gigabyte branded (I don't have any particular brand loyalty, I just happen to have a lot of Gigabyte cards).
Soli Deo Gloria
ID: 1512036 · Report as offensive
johds

Send message
Joined: 21 Feb 00
Posts: 1
Credit: 191,069
RAC: 0
Denmark
Message 1514189 - Posted: 9 May 2014, 18:46:44 UTC - in response to Message 1512036.  
Last modified: 9 May 2014, 18:50:04 UTC

Wedge, you stated 2 R9-280x's and 1 R9-270. Thats a TDP of 680 watts alone in the GPU's. Might be a PSU issue, since it also depends on how many amps each plug in your PSU can deliver at the same time.

As for your blank screen issue - Logical debugging is needed :
Start with just one R9-280X card in. Does it boot ? yes, then proceed to windows, install the drivers. Reboot. Then after a successfull reboot, do a shutdown.
Add the next R9-280x card. Boot, and see if it starts up in windows. Make sure that the Device Manager shows that the card is detected and has drivers installed.
Reboot. Verify you can reboot, then shut down.
Add the R9-270 card. Same procedure.

I ran into the same problem, when I switched to a R9-280X card, and had a R7-260x card as well. Had to remove the R7-260x, then remove all ATI drivers after a successfull boot. Then reboot, reinstall the 13.4 Catalyst drivers (only one that gives CAL support for the Bonaire GPU), then reboot, and add the R7-260X card, and let windows find it.

The only issue I have now, is that the bios messages appear on the R7-260X cards output during boot, but as soon as windows 7 gets loaded, the R9-280X takes over.

Oh, btw, my motherboard is only supporting PCIE 2.0, and only x16 on one PCIE slot, the rest is x8. Doesn't matter for the crunching though, since its not memory transfer intensive. (ASUS Z8P(E)-D12X, dual Xeon X5570, 48 GB DDR3 ECC Ram)
ID: 1514189 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6533
Credit: 196,805,888
RAC: 57
United States
Message 1514232 - Posted: 9 May 2014, 20:42:26 UTC - in response to Message 1514189.  
Last modified: 9 May 2014, 20:42:39 UTC

ID: 1514232 · Report as offensive
Wedge009
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 451
Credit: 431,396,357
RAC: 553
Australia
Message 1514242 - Posted: 9 May 2014, 21:03:25 UTC

Thanks for the input. As HAL pointed out, the issue occurs on single card set-ups as well. The PSU is rated for a maximum of 70A on 12V.

Also, I'm fine with debugging OS issues, be it Windows or Linux. My particular problem is that I don't even get to the OS, the POST is either failing or not being properly displayed.

I just got a new - albeit PCIe 2.x - motherboard and am surprised to find the same issues occurring: old card boot okay, R9 280Xs display nothing. Although this time, I get nothing with HDMI, something - though garbled - on DVI. Hopefully I can get some further testing/experimenting done since it's Saturday for me.
Soli Deo Gloria
ID: 1514242 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 33181
Credit: 79,922,639
RAC: 80
Germany
Message 1514341 - Posted: 10 May 2014, 9:59:27 UTC

I think it depends on the brand of the card.
Maybe some dont use reference design.

This guy is running 2 280X and the cards are fully recognized by Boinc as well.

http://setiathome.berkeley.edu/hosts_user.php?userid=8533625
With each crime and every kindness we birth our future.
ID: 1514341 · Report as offensive
Wedge009
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 451
Credit: 431,396,357
RAC: 553
Australia
Message 1514364 - Posted: 10 May 2014, 11:23:29 UTC

Perhaps.

But I feel pretty stupid now - turns out it was the specific combination of the Gigabyte R9 cards and a certain monitor that was the issue. Don't know why the monitor only likes the POST output from older cards, but I tested it on other monitors and POST, start-up screens, etc all worked without issue.

Oh well, at least that hurdle is over. Bit bummed that buying the new motherboard was completely unnecessary, but that's the way it goes.

Now for a completely separate topic (for which I'll start another thread if necessary)... why Linux BOINC isn't detecting the GPUs. I have run GPU tasks on Linux in the past, but all that was necessary back then was installing the appropriate proprietary driver. libcuda.so, libOpenCL.so, and libaticalrt.so are all there in /usr/lib/ (or at least sub-directories therein) and BOINC coproc_debug messages say drivers are there, it just can't pick up the GPUs. Looks like it's back to more tinkering/testing...
Soli Deo Gloria
ID: 1514364 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 33181
Credit: 79,922,639
RAC: 80
Germany
Message 1514383 - Posted: 10 May 2014, 13:55:16 UTC

I`m glad you could get it work.
With each crime and every kindness we birth our future.
ID: 1514383 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6533
Credit: 196,805,888
RAC: 57
United States
Message 1514419 - Posted: 10 May 2014, 16:11:24 UTC - in response to Message 1514364.  

Perhaps.

But I feel pretty stupid now - turns out it was the specific combination of the Gigabyte R9 cards and a certain monitor that was the issue. Don't know why the monitor only likes the POST output from older cards, but I tested it on other monitors and POST, start-up screens, etc all worked without issue.

Oh well, at least that hurdle is over. Bit bummed that buying the new motherboard was completely unnecessary, but that's the way it goes.

Now for a completely separate topic (for which I'll start another thread if necessary)... why Linux BOINC isn't detecting the GPUs. I have run GPU tasks on Linux in the past, but all that was necessary back then was installing the appropriate proprietary driver. libcuda.so, libOpenCL.so, and libaticalrt.so are all there in /usr/lib/ (or at least sub-directories therein) and BOINC coproc_debug messages say drivers are there, it just can't pick up the GPUs. Looks like it's back to more tinkering/testing...

I have a similar issue. I have an Princeton LCD I bought in '04 or '05 that doesn't work with ATI cards when using the DVI connection at post or in Windows unless you only use the standard VGA driver. The VGA connection works fine however.
At the time I bought it I spent quite a long time troubleshooting & then found it is a known issue with the monitor. :/ It still happens with with current drivers & my HD6850. The DVI does work fine with Intel GPU's.
So I have just stuck with Samsung monitors since then and not had any issues.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!
ID: 1514419 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : Radeon R9 Cards Not Passing POST


 
©2022 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.