darkip Posted June 15, 2015 Share Posted June 15, 2015 Depending how (disappointing?) the Fury X launch tomorrow is, I'll probably be upgrading to a 980 Ti soon. It's already leaked, at least 390x is a rebrand of the 290x with a few more cores, very little improvement. I'd upgrade to a 980 Ti myself, but the double precision performance is absolutely terrible on Maxwell. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted June 15, 2015 Share Posted June 15, 2015 The 390X is a 290X GDDR5 8GB rebrand with the codename Grenada. I wonder if they made some improvements there, e.g. GCN 1.2+, DirectX 12_1, etc. I highly doubt it though in this case. The Fury X on the other hand, is the first GPU to use HBM instead of GDDR5 - it's also the first Fiji card. But it's supposed to be more expensive than a 980 Ti even though according to the rumors it doesn't match it in performance (it *might* beat the Titan X, we'll see hopefully tomorrow). And sadly it looks like no full Tonga either, pity. People are already flashing 290X 8GB cards to 390X. Link to comment Share on other sites More sharing options...
BBond007 Posted June 15, 2015 Author Share Posted June 15, 2015 The Fury X on the other hand, is the first GPU to use HBM instead of GDDR5 - it's also the first Fiji card Yeah, which is why its not full potential yet. The 8GB HBM card might well be worth the wait. I gave the MSI gamer BIOS a go but no luck unfortunately. The fan still fails to spin up on my card (it does in windows so I know it's not faulty!). That is really strange. I wonder if its something entirely different... Have you tried the GPU dip switch in different directions? Which model smbios are you using? Link to comment Share on other sites More sharing options...
darkip Posted June 15, 2015 Share Posted June 15, 2015 I'm using iMac14,2 (automatic from Clover). So I had a spare Z68 board around and I thought I'd try the GPU in there. Turns out the fans sped up correctly on that board. Need to double check this. So I investigated further and found that only on the Z68 board did the gpu-control entry appear: So maybe this is something that needs to be patched with a DSDT / SSDT edit? Link to comment Share on other sites More sharing options...
Awesome Donkey Posted June 15, 2015 Share Posted June 15, 2015 Are you using a patched DSDT? I'm using one of Rampage Dev's. Might be worth asking him about that one. Link to comment Share on other sites More sharing options...
darkip Posted June 15, 2015 Share Posted June 15, 2015 Hmm, seems like this may have been a false alarm. I managed to get the gpu-control device to show up but the fan still isn't spinning up which makes me wonder if it was actually spinning up in the other machine before. I'll check again tomorrow. Link to comment Share on other sites More sharing options...
BBond007 Posted June 16, 2015 Author Share Posted June 16, 2015 Hmm, seems like this may have been a false alarm. I managed to get the gpu-control device to show up but the fan still isn't spinning up which makes me wonder if it was actually spinning up in the other machine before. I'll check again tomorrow. I don't have that gpu-control on the machine with the 2 MSI gamers. I can check the machine with the Lightning this weekend. Link to comment Share on other sites More sharing options...
darkip Posted June 16, 2015 Share Posted June 16, 2015 So I double checked the GPU in the other board (Z68) and the fans definitely do spin up. I also tried setting the SMBIOS of the Z68 machine to MacPro6,1 and despite the gpu-control device disappearing from the ioreg, the fans still worked. So unfortunately that doesn't seem to be related. Here's a comparison of the IOReg GPU area for the from the Z68 machine and the Z97 (no fan speedup). Both are using MacPro6,1 SMBIOS: Z68 Z97 I wonder if the controller being underneath this "display@0" node rather than "PEGP@0" is causing a problem? Link to comment Share on other sites More sharing options...
darkip Posted June 16, 2015 Share Posted June 16, 2015 I had a closer look at the device-id's and I think the problem is the PLX chip on our boards. The PLX chip sits between PEG0 (the PCI-E controller on the processor) and what is being labelled "display" (what I believe is the actual GPU device). I'm guessing the PLX chip being labelled PEG0 rather than actual GPU device is preventing the driver talking to the card for some reason. I think we need DSDT modification assistance. Link to comment Share on other sites More sharing options...
Awesome Donkey Posted June 16, 2015 Share Posted June 16, 2015 Probably best to ask Rampage Dev, and see what he thinks. Link to comment Share on other sites More sharing options...
darkip Posted June 16, 2015 Share Posted June 16, 2015 Pavo and WarDocsRevenge both have builds with 290x's where the fan(s) work. Neither of their boards have PLX chips so this is looking more likely. 1 Link to comment Share on other sites More sharing options...
Pavo Posted June 16, 2015 Share Posted June 16, 2015 Pavo and WarDocsRevenge both have builds with 290x's where the fan(s) work. Neither of their boards have PLX chips so this is looking more likely. Link to comment Share on other sites More sharing options...
BBond007 Posted June 16, 2015 Author Share Posted June 16, 2015 Pavo and WarDocsRevenge both have builds with 290x's where the fan(s) work. Neither of their boards have PLX chips so this is looking more likely. no PLX on Fatal1ty z87 Killer Link to comment Share on other sites More sharing options...
darkip Posted July 3, 2015 Share Posted July 3, 2015 So I've fixed my fan issue. All it took was disassembling the driver and finding some hidden debugging flags Add the following to AMD8000Controller/Contents/Info.plist in the aty_properties dictionary <key>PP_PcieDpmDisabled</key> <integer>1</integer> I'm now running into 2D acceleration issues - When I play a flash video fullscreen it's very stuttery. Anyone else with similar issues? Link to comment Share on other sites More sharing options...
Adom Doledas Posted July 3, 2015 Share Posted July 3, 2015 Anyone with R9 290X and multiple monitors run into issues on 10.10.4 (no matter fresh install or update from 10.10.3)? More detail on the issue here, still unanswered: http://www.insanelymac.com/forum/topic/306924-10104-core-graphics-changed-vs-10103-dual-r9-290x/ Link to comment Share on other sites More sharing options...
darkip Posted July 3, 2015 Share Posted July 3, 2015 Anyone with R9 290X and multiple monitors run into issues on 10.10.4 (no matter fresh install or update from 10.10.3)? More detail on the issue here, still unanswered: http://www.insanelymac.com/forum/topic/306924-10104-core-graphics-changed-vs-10103-dual-r9-290x/ My patch posted earlier in this thread still works in 10.10.4. I have an Asus R9 290x Reference model. Link to comment Share on other sites More sharing options...
Adom Doledas Posted July 3, 2015 Share Posted July 3, 2015 My patch posted earlier in this thread still works in 10.10.4. I have an Asus R9 290x Reference model. I think it has something to do with the drivers from OS X 10.10.4 rather than connectors patching, no patch will work, because mine (if you want I can post my patch) works percectly (both DVI running on Dual Link instead of Single Link to support 144Hz) on both 10.10.3 and 10.10.4. The issue is that it takes like forever (well, 1 minute in this era is now considered very slow) to boot on 10.10.4 (no matter if I inject ATI + patch connectors or just let OS X detects my monitors itself), from the Apple logo loading until the login screen, after that everything works fine. Somehow I'm lucky enough to have it run smoothly (no fans craziness) and no 2D/3D acceleration bug. On 10.10.3 my systems works smoothly, no waiting hassles, the login screen appeas RIGHT after the Apple logo loading, instead of blackening the screen for a minute like 10.10.4. The only downside that 10.10.3 can't detect my monitors on its own, I have to inject ATI + patch the connectors in Clover config.plist boot. But yeah, in order for OS X to detect the cards correctly (R9 290X instead of AMD 8xxx), I have to inject ATI anyway, on both 10.10.3 and 10.10.4. Be mindful that connectors patch DO affect the fans, and graphics FB names do also affect the connectors usability. For example sometimes I change from Baladi to Exmoor and not change my connectors patch, only 2 of my 3 screens work and fans kick up 100%. If I change the connectors patch then the fans returns to normal (still on Exmoor). But yeah, Baladi works better for me if I'm using 3 screens through Display Port + Top&Bottom DVI (HDMI unused), since HDMI is more like a "media port" than a "displaying solution" (hence it's a lot trickier therefore I didn't even bother trying, but who knows if in the future I will have to tweak around with it if I ever want to add a 4th monitor). So if your fan kicks up when using "Baladi", try changing your connectors patch before changing FB name. Link to comment Share on other sites More sharing options...
darkip Posted July 3, 2015 Share Posted July 3, 2015 Baladi/Exmoor/No injection makes no difference for my fan problems. Your problem sounds like it might be rectified by trying a different SMBIOS. I'm using iMac14,2, I'd recommend giving that a try. Link to comment Share on other sites More sharing options...
Adom Doledas Posted July 3, 2015 Share Posted July 3, 2015 Baladi/Exmoor/No injection makes no difference for my fan problems. Your problem sounds like it might be rectified by trying a different SMBIOS. I'm using iMac14,2, I'd recommend giving that a try. Yeah, it depends on the connectors patch tho. As for the SMBIOS, I've been using exactly what you suggested me to try, since it's the product with closest specs to my system . Thanks for taking time looking into it tho. I appreciate it bro. Sigh with Apple. Hope I will have more luck with El Capitan in the next few months. For now I'm trying to find a 10.10.3 installer. Geez! Link to comment Share on other sites More sharing options...
darkip Posted July 3, 2015 Share Posted July 3, 2015 Another thing I can recommend is disabling CSM in your BIOS. Link to comment Share on other sites More sharing options...
Adom Doledas Posted July 3, 2015 Share Posted July 3, 2015 Another thing I can recommend is disabling CSM in your BIOS. Yeah, it's already disabled (running on full UEFI). That's why I feel so hopeless. Link to comment Share on other sites More sharing options...
darkip Posted July 3, 2015 Share Posted July 3, 2015 It's probably also worth saying that I still need to inject on 10.10.4 Link to comment Share on other sites More sharing options...
Adom Doledas Posted July 3, 2015 Share Posted July 3, 2015 It's probably also worth saying that I still need to inject on 10.10.4 Yes, 10.10.4 sure does detect graphics on its own better to have things work automatically. But in other to have your card run fine, or at least have your Mac detect it as a 290X properly ("About this Mac"), you have to inject ATI. I myself suffered a few freezing (maybe kernel panic) while using 10.10.4 without injection. 10.10.4 should have been awesome if I didn't get the stupid "1 min black screen" before being able to use it... Link to comment Share on other sites More sharing options...
darkip Posted July 5, 2015 Share Posted July 5, 2015 So I had a go with 10.11 (dp2) this weekend and turns out it fixes most of my issues: The fan on my card works with no driver modification 2D acceleration is fully functional so video playback is no longer stuttery/laggy I still needed to patch the framebuffer and I also had to update the data I wanted to patch as Exmoor has changed with 10.11: Kext /System/Library/Extensions/AMD8000Controller.kext/Contents/MacOS/AMD8000Controller Personality: Exmoor ConnectorInfo count in decimal: 6 Disk offset in decimal 1859360 0000000 02 00 00 00 00 01 00 00 00 01 01 03 22 05 02 04 0000010 02 00 00 00 00 01 00 00 00 01 02 03 12 04 01 03 0000020 00 04 00 00 04 03 00 00 00 01 03 07 11 02 03 01 0000030 00 04 00 00 00 01 00 00 00 01 04 03 21 03 05 05 0000040 00 04 00 00 04 03 00 00 00 01 05 07 10 00 04 02 0000050 00 04 00 00 00 01 00 00 00 01 06 03 20 01 05 05 0000060 Personality: Baladi ConnectorInfo count in decimal: 6 Disk offset in decimal 1859712 0000000 00 04 00 00 04 03 00 00 00 01 03 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 01 00 11 02 01 01 0000020 00 04 00 00 04 03 00 00 00 01 02 00 21 03 02 02 0000030 00 04 00 00 04 03 00 00 00 01 04 00 22 05 04 04 0000040 00 04 00 00 04 03 00 00 00 01 05 00 10 00 05 05 0000050 00 04 00 00 04 03 00 00 00 01 06 00 20 01 06 06 0000060 Although the GPU drivers seem to work perfectly 10.11 is pretty unstable at the moment (lots of USB issues) so I thought I'd have a go at backporting the drivers in a similar way to what netkas did for 10.9. This worked perfectly and I now have the 10.11 drivers working on 10.10.4! To do this start in single user mode (-s) and copy the following files from 10.11 to 10.10. The source/destination folder is listed for each set of files. DO NOT copy the entire directories. BACK UP THE FILES YOU'RE REPLACING. Folder: /System/Library/Extensions AMD2400Controller.kext AMD2600Controller.kext AMD3800Controller.kext AMD4600Controller.kext AMD4800Controller.kext AMD5000Controller.kext AMD6000Controller.kext AMD7000Controller.kext AMD8000Controller.kext AMD9000Controller.kext AMDFramebuffer.kext AMDMTLBronzeDriver.bundle AMDRadeonVADriver.bundle AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle AMDShared.bundle AMDSupport.kext ATIRadeonX2000.kext ATIRadeonX2000GA.plugin ATIRadeonX2000GLDriver.bundle ATIRadeonX2000VADriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily.kext IOAcceleratorFamily2.kext Folder: /System/Library/Frameworks IOSurface.framework OpenCL.framework OpenGL.framework Folder: /System/Library/PrivateFrameworks GPUCompiler.framework GPUSupport.framework IOAccelerator.framework Once you've finished copying, repair disk permissions and rebuild the cache: diskutil repairPermissions / touch /System/Library/Extensions kextcache -Boot -U Link to comment Share on other sites More sharing options...
Pavo Posted July 5, 2015 Share Posted July 5, 2015 So I had a go with 10.11 (dp2) this weekend and turns out it fixes most of my issues: The fan on my card works with no driver modification 2D acceleration is fully functional so video playback is no longer stuttery/laggy I still needed to patch the framebuffer and I also had to update the data I wanted to patch as Exmoor has changed with 10.11: Kext /System/Library/Extensions/AMD8000Controller.kext/Contents/MacOS/AMD8000Controller Personality: Exmoor ConnectorInfo count in decimal: 6 Disk offset in decimal 1859360 0000000 02 00 00 00 00 01 00 00 00 01 01 03 22 05 02 04 0000010 02 00 00 00 00 01 00 00 00 01 02 03 12 04 01 03 0000020 00 04 00 00 04 03 00 00 00 01 03 07 11 02 03 01 0000030 00 04 00 00 00 01 00 00 00 01 04 03 21 03 05 05 0000040 00 04 00 00 04 03 00 00 00 01 05 07 10 00 04 02 0000050 00 04 00 00 00 01 00 00 00 01 06 03 20 01 05 05 0000060 Personality: Baladi ConnectorInfo count in decimal: 6 Disk offset in decimal 1859712 0000000 00 04 00 00 04 03 00 00 00 01 03 00 12 04 03 03 0000010 00 04 00 00 04 03 00 00 00 01 01 00 11 02 01 01 0000020 00 04 00 00 04 03 00 00 00 01 02 00 21 03 02 02 0000030 00 04 00 00 04 03 00 00 00 01 04 00 22 05 04 04 0000040 00 04 00 00 04 03 00 00 00 01 05 00 10 00 05 05 0000050 00 04 00 00 04 03 00 00 00 01 06 00 20 01 06 06 0000060 Although the GPU drivers seem to work perfectly 10.11 is pretty unstable at the moment (lots of USB issues) so I thought I'd have a go at backporting the drivers in a similar way to what netkas did for 10.9. This worked perfectly and I now have the 10.11 drivers working on 10.10.4! To do this start in single user mode (-s) and copy the following files from 10.11 to 10.10. The source/destination folder is listed for each set of files. DO NOT copy the entire directories. BACK UP THE FILES YOU'RE REPLACING. Folder: /System/Library/Extensions AMD2400Controller.kext AMD2600Controller.kext AMD3800Controller.kext AMD4600Controller.kext AMD4800Controller.kext AMD5000Controller.kext AMD6000Controller.kext AMD7000Controller.kext AMD8000Controller.kext AMD9000Controller.kext AMDFramebuffer.kext AMDMTLBronzeDriver.bundle AMDRadeonVADriver.bundle AMDRadeonX3000.kext AMDRadeonX3000GLDriver.bundle AMDRadeonX4000.kext AMDRadeonX4000GLDriver.bundle AMDShared.bundle AMDSupport.kext ATIRadeonX2000.kext ATIRadeonX2000GA.plugin ATIRadeonX2000GLDriver.bundle ATIRadeonX2000VADriver.bundle IOAccelerator2D.plugin IOAcceleratorFamily.kext IOAcceleratorFamily2.kext Folder: /System/Library/Frameworks IOSurface.framework OpenCL.framework OpenGL.framework Folder: /System/Library/PrivateFrameworks GPUCompiler.framework GPUSupport.framework IOAccelerator.framework Once you've finished copying, repair disk permissions and rebuild the cache: diskutil repairPermissions / touch /System/Library/Extensions kextcache -Boot -U Exmoor framebuffer is used for laptops not desktops, should be using Baladi framebuffer Link to comment Share on other sites More sharing options...
Recommended Posts