Article index:
Install AMD FirePro M5100 driver for Windows 10 x64, or download DriverPack Solution software for automatic driver installation and update. Is the AMD Radeon HD - FirePro D500 fully supported? Even though support is enabled, I see no load on the GPU in the performance monitor when I move sliders in the development module. No matter which.
The d500 is a bit odd- nothing has that number of stream processors in the current firepro world. Macvidcards said in another thread on this site that he thinks it's a radeon 7870, and he's got a point since 7870's apparently identify themselves as d500's when run in mavericks. Download the latest AMD FirePro M5950 device drivers (Official and Certified). AMD FirePro M5950 drivers updated daily. These release notes provide information on the AMD FirePro Windows 10 WHQL Driver version. Workstation Features: - CF Dual, CF Tri/Quad, Display Overlap, Display Overlap Post Processing, EDID/MST, Framelock/ Genlock, SDI, SLS, MGPU-SLS, Stereo (Active, Display based, Passive), 10 bit (native, packed pixel, SLS), Custom timing, Stereo.
1 – Overview
I had the opportunity yesterday (thanks to anirul) to quickly test one of the new Mac Pro (a late 2013 model) equipped with two FirePro D500 graphics cards. The FirePro D500 is based on a variation of the Tahiti GPU and packs 1536 stream processors (and not 1526 as it’s mentioned on the spec page):
The 1536 stream processors are spread over 24 compute units. The FirePro D500 is an OpenGL 4.4 capable graphics hardware (limited to OpenGL 4.1 under OSX 10.9) and supports OpenCL 1.2.
| A quick note for OpenGL developers: it seems that FirePro drivers for D300/D500/D700 under OS X are very sensitive when it comes to hardware limits. I recently fixed a bug that occurred only on FirePro Dxxx under OS X 10.9 related to the max number of generic vertex attribs that can be used (GL_MAX_VERTEX_ATTRIBS = 16 on most GPUs including the FirePro Dxxx). 17 vertex attribs were used in a demo (which is clearly a bug) and only the FirePro D500/D700 (not tested on D300) crashed when the GL_MAX_VERTEX_ATTRIBS limit was exceeded. The bug was not visible with a Radeon HD 5000/6000 or a GeForce under OS X. So with current FirePro drivers, do not forget to check hardware limits! |
Some basic OpenGL info for the FirePro D500 under OS X 10.9:
2 – Gallery
The Mac Pro is small:
The I/O connectors include four USB 3 ports, 6 thunderbolt ports, two Gigabit-Ethernet and one HDMI 1.4 ports:
The graphics cards: two FirePro D500. A 256-GB SSD is fixed on the right graphics card.
3 – OpenGL benchmarks
For this quick test, I used GpuTest 0.7.0 for Mac OS X. Only one FirePro D500 is OpenGL-ized in this benchmareking session.
Graphics settings for all tests: 1920×1080 fullscreen, no AA, 60 seconds.
The FirePro D500 is compared to the GeForce GT 650M (Macbook Pro) and a Radeon HD 5770 (hackintosh setup). I wanted to add a Radeon HD 7970 in the loop but the hackinstosh said NO!
3.1 – FurMark
- GeForce GT 650M: 798 points, 13 FPS
- Radeon HD 5770: 1412 points, 23 FPS
- FirePro D500: 2056 points, 34 FPS (GPU database entry)
3.2 – TessMark X8
- GeForce GT 650M: 8200 points, 136 FPS
- Radeon HD 5770: 18016 points, 300 FPS
- FirePro D500: 35525 points, 592 FPS (GPU database entry)
3.3 – TessMark X16
- GeForce GT 650M: 6759 points, 112 FPS
- Radeon HD 5770: 9683 points, 161 FPS
- FirePro D500: 16624 points, 277 FPS (GPU database entry)
3.4 – TessMark X32
Amd Firepro D500 3gb Driver Mac
- Radeon HD 5770: 3429 points, 57 FPS
- GeForce GT 650M: 4413 points, 73 FPS
- FirePro D500: 4792 points, 79 FPS (GPU database entry)
3.5 – TessMark X64
- Radeon HD 5770: 995 points, 16 FPS
- FirePro D500: 1291 points, 21 FPS (GPU database entry)
- GeForce GT 650M: 2192 points, 36 FPS
3.7 – GiMark
- GeForce GT 650M: 784 points, 13 FPS
- Radeon HD 5770: 1479 points, 24 FPS
- FirePro D500: 2501 points, 41 FPS (GPU database entry)
3.8 – Julia FP32
- GeForce GT 650M: 2734 points, 45 FPS
- Radeon HD 5770: 4808 points, 80 FPS
- FirePro D500: 28514 points, 474 FPS (GPU database entry)
3.9 – Julia FP64
- Radeon HD 5770: *** FAILED *** (driver issue)
- GeForce GT 650M: 427 points, 7 FPS
- FirePro D500: 9830 points, 163 FPS (GPU database entry)
3.10 – Volplosion
- GeForce GT 650M: 364 points, 6 FPS
- Radeon HD 5770: 925 points, 15 FPS
- FirePro D500: 1008 points, 16 FPS (GPU database entry)
4 – Selected reviews
Related posts:
The unwillingness of both Apple and AMD to provide up-to-date bootcamp video drivers, is totally unprofessional. It is a slap in the face to every customer that uses bootcamp. For this sector of customer base I believe it is damaging to their brand. To be the only customer of which AMD's website says 'This driver is not intended for use on AMD products running in Apple Boot Camp platforms.' And to have Apple standing by doing NOTHING to pass on updates to their customer base is appalling. And it isn't like a driver update is a huge technical feat. The code base is being maintained for every other AMD chipset out there. People are able to hack it to get it to work. For Apple to provide a stable driver is maddeningly trivial, which makes it clear that denying it is likely the internal policy of some jerk manager(s) that want to kick in the nards anybody that dares to seriously use Windows on Apple hardware.
Amd Firepro D500 Drivers Mac
Amd Firepro D500 Driver Windows 10
A comparison, Apple has fired missiles at the Android community because their phones are notorious for getting no updates pushed from the manufacturers. Well, Apple is acting from the same playbook. When it comes time to get a new workstation, am I going to get an Apple again? NOOOOO! Will I buy anything with an AMD card? NOOOOO! Your brand is mud. Can you, Apple and AMD, fix this? Yes, just provide driver updates for the video chipset in my $10K computer! It is insulting that I have to beg for you to do this. But ultimately, the future will be a vote with the wallet. You will have no body to blame but yourself for lackluster sales. Is it due to product design? No. Is it due to lost 'halo' effect? No. Is it due to atrocious customer support? Absolutely yes.
Aug 9, 2015 8:14 PM