Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

R9 nano released

danboyy

could you try to add your device id (7300) to < key>AMDTongaGraphicsAccelerator</key> section of AMDRadeonX4000.kext?

since fiji and tonga are bpth gcn 1.2, might help to get acceleration
 
Sorry for my ignorance, only really ever edited the AHCIBlockStorage kext to enable TRIM support.

I assume the information would need to be added to info.plist?

The section you refer to is this part;

Code: 
<key>AMDTongaGraphicsAccelerator</key>
        <dict>
            <key>ATIEnableWideBlitSupport</key>
            <true/>
            <key>ATIUseTearingWideBlit</key>
            <false/>
            <key>CFBundleIdentifier</key>
            <string>com.apple.AMDRadeonX4000</string>
            <key>GpuDebugPolicy</key>
            <integer>0</integer>
            <key>IOClass</key>
            <string>AMDTongaGraphicsAccelerator</string>
            <key>IODVDBundleName</key>
            <string>AMDRadeonVADriver</string>
            <key>IOKitDebug</key>
            <integer>0</integer>
            <key>IOMatchCategory</key>
            <string>IOAccelerator</string>
            <key>IOPCIMatch</key>
            <string>0x69201002 0x69211002 0x69301002 0x69381002 0x69391002</string>
            <key>IOProbeScore</key>
            <integer>200</integer>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
            <key>IOSourceVersion</key>
            <string>0.0.0.0.0</string>
            <key>IOVARendererID</key>
            <integer>16908288</integer>
            <key>cail_properties</key>
            <dict>
                <key>CAIL_DisableAcpPowerGating</key>
                <integer>0</integer>
                <key>CAIL_DisableJpegEngine</key>
                <integer>1</integer>
                <key>CAIL_DisableSAMUPowerGating</key>
                <integer>0</integer>
                <key>CAIL_DisableSysClockGating</key>
                <integer>1</integer>
                <key>CAIL_DisableUVDPowerGating</key>
                <integer>0</integer>
                <key>CAIL_DisableVCEPowerGating</key>
                <integer>0</integer>
            </dict>
        </dict>

Where about would you add the Device ID?
 
Add 0x73001002 to the lits of device IDs below <key>IOPCIMatch</key>.

This can only be done if SIP is disabled, otherwise you can't write to /System. You'll might also have to repair the file permissions after doing the modification as the kext won't load with broken permissions. Can be done manually with "chown root:wheel" and "chmod 755".
 
My friend might be ordering one in a couple of weeks, asked if I could borrow it briefly before he installs it :)

I've added that information into the appropriate kernel extension, I'll let you guys know what the result is, if someone doesn't beat me to it.
 
Last edited:
  • Like
Reactions: Chung123
Fl0r!an said:
Add 0x73001002 to the lits of device IDs below <key>IOPCIMatch</key>.

This can only be done if SIP is disabled, otherwise you can't write to /System. You'll might also have to repair the file permissions after doing the modification as the kext won't load with broken permissions. Can be done manually with "chown root:wheel" and "chmod 755".
Click to expand...

Sorry, I seem to be getting an issue after modifying this kernel extension.

I already had SIP disabled, and enabled kext-dev-mode=1 in my NVRAM. I added 0x73001002 to the devices listed under the relevant <key>IOPCIMatch</key> entry.

I then did chown root:wheel and chmod 755 on info.plist and restarted.

Unfortunately, even with kext-dev-mode=1, this kernel extension still isn't loadable according to System Information;

Loadable: No
Signature Validation Errors: Kext signature validation error code -67030
Dependencies: Satisfied
Signed by: Unknown

EDIT

Just read that kext-dev-mode=1 in NVRAM now does nothing.. hmm. Unsure why this kext doesn't load with SIP disabled then.
 
Loadable=NO doesn't mean it didn't load, just that it isn't loadable via Apple's rules.

I have a Nano, I don't get screen output at all in 10.11.3, no idea how a few have reported even partial function.
 
Hello to all. I took the plunge and I've bought, 2 x R9 NANO graphics cards.

*I've considered the 2 x Fury X option, but, the idea of two radiators inside the case, releasing water vapor and the water leaks possibility, worried me alot! Also, the 275+275 TDP, didn't look a safe option...

I've also done the "Pixlas Mac Pro mod". One cable from PSU to 2 x 8-pin connectors.

Graphics card 1: Motherboard 2 x 6-pin to 1 8-pin conector cable (175 TDP) (PCIe x16)
Graphics card 2: PSU 1 8-pin conector cable (175 TDP) (PCIe x4)


Here are my results:

Windows 8.1 - All perfect / Crossfire working
Windows 10 TH2 - All perfect / Crossfire working

OS X Mavericks - No picture
- redundant

OS X Yosemite - picture working
- no acceleration (kext edit)

OS X EL Capitan - picture working
- no acceleration (kext edit)

Windows / Origin / Crysis 3 - 2560 x 1440 60Hz
- All settings on Ultra / max
- Consistent 60 fps

- 4K 60 Hz (displayport to hdmi 2.0 adapter)
- All settings on Ultra / max
- Consistent 45 fps

Regards to all,
Xanix
 
Last edited:
  • Like
Reactions: kiopoptr877, JimmyPainter and Chung123
Thanks for the info––really too bad the R9 Nano doesn't work with acceleration! Would love to pick up two of those for OS X as well.
 
Xanix said:
Hello to all. I took the plunge and I've bought, 2 x R9 NANO graphics cards.

*I've considered the 2 x Fury X option, but, the idea of two radiators inside the case, releasing water vapor and the water leaks possibility, worried me alot! Also, the 275+275 TDP, didn't look a safe option...

I've also done the "Pixlas Mac Pro mod". One cable from PSU to 2 x 8-pin connectors.

Graphics card 1: Motherboard 2 x 6-pin to 1 8-pin conector cable (175 TDP) (PCIe x16)
Graphics card 2: PSU 1 8-pin conector cable (175 TDP) (PCIe x4)


Here are my results:

Windows 8.1 - All perfect / Crossfire working
Windows 10 TH2 - All perfect / Crossfire working

OS X Mavericks - No picture
- redundant

OS X Yosemite - picture working
- no acceleration (kext edit)

OS X EL Capitan - picture working
- no acceleration (kext edit)

Windows / Origin / Crysis 3 - 2560 x 1440 60Hz
- All settings on Ultra / max
- Consistent 60 fps

- 4K 60 Hz (displayport to hdmi 2.0 adapter)
- All settings on Ultra / max
- Consistent 45 fps

Regards to all,
Xanix
Click to expand...

Interesting you got a non-accelerated picture when MVC reported he didn't even get that, any screenshots of it in action?
 
Anyone played around with this some more? You'd think that AMD would have better driver support in OS X considering Apple is AMD only on GPUs now.
 
jonisign said:
Anyone played around with this some more? You'd think that AMD would have better driver support in OS X considering Apple is AMD only on GPUs now.
Click to expand...

The only AMD drivers in OS X are written by Apple (I believe) for existing cards in their hardware lineup. No current Macs use Fiji, so OS X doesn't support them. Unfortunately, AMD just don't seem interested in writing their own drivers for OS X.
 
Draeconis said:
The only AMD drivers in OS X are written by Apple (I believe) for existing cards in their hardware lineup. No current Macs use Fiji, so OS X doesn't support them. Unfortunately, AMD just don't seem interested in writing their own drivers for OS X.
Click to expand...

Are they written by Apple, or does AMD provide them to Apple?

And yes, I'm aware no current Macs use Fiji–– it's too bad AMD doesn't write their own drivers for OS X as Nvidia does.
 
jonisign said:
Are they written by Apple, or does AMD provide them to Apple?

And yes, I'm aware no current Macs use Fiji–– it's too bad AMD doesn't write their own drivers for OS X as Nvidia does.
Click to expand...

I thinks that's one of the reason why AMD won the contract, but not Nvidia. Apple love to keep everything in their hand, and no second source for their customer. Nvidia keep providing the web driver to us. Of course it's good for us, but I don't think Apple will like it.
 
jonisign said:
Are they written by Apple, or does AMD provide them to Apple?

And yes, I'm aware no current Macs use Fiji–– it's too bad AMD doesn't write their own drivers for OS X as Nvidia does.
Click to expand...

Unfortunately this isn't a question I know the answer to. I can see Apple writing them themselves though as more likely; they like the 'it just works' integrated approach; web drivers probably look messy to them. If novice users can't work it, out it's too complicated.

Of course for us that's an issue as once it's working it's unclear how much work is done to ensure optimal performance through driver improvements. Most OS X betas have advised checking for graphics performance improvements, but that could mean driver refinements, OpenGL improvements, or any number of other low-level things.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back