AMD r9 270 problem

yoda · March 5, 2014

Hi daniesy,

I've done some more tests and it seems that without ATYinjector.kext it is also working, just a few % of difference.

For other kext files, I've only add id card like iFire show you.

The only thing I've noticed is that kext files (AMDController7000.kext and AMDRadeonX4000.kext) should be the ones from 10.9.2

If you use modified kext files from 10.9.1 in system 10.9.2, it will not work.

Even if I have ATY,AMD,RadeonFramebuffer@0 ..., the boards are working correctly.

I will do some more tests to see if I can change the framebuffer and let you know.

BTW, what r9 270 do you have ? I use XFX R9-270A-CDFC.

daniesy · March 5, 2014

Hey yoda! Thanks for the reply!

Mine is Saphire Dual-X R9 270 and i'm using Clover as the boot loader. The problem might be that i've first used this patcher http://www.osx86.net/files/file/3711-amd-radeon-r9-270-series/ and only later tried to fix things. I think it isn't compatible with 10.9.2 because ATYinjector.kext didn't even load.

With iFire technique, it did work on 10.9.1 but games like Starcraft 2 were very laggy (~ 5FPS) for this card.

yoda · March 5, 2014

Well, I'm not an expert with Hackintosch seup as I use a regular MacPro.

The only thing I've tried is to be able to use those boards with FCPX. It is not possible if we don't modify some (2) kext files.

If I found something else I will let you know.

daniesy · March 5, 2014

Danke!

pokenguyen · March 6, 2014

If you're using Clover, you can use Clover Injection to force those 2 kexts loaded. Here are the supported ids:

AMD7000: 0x26001002 0x22001002 0x67901002 0x67981002 0x679A1002 0x679E1002 0x67801002 0x68201002 0x68211002 0x68231002 0x68251002 0x68271002 0x682D1002 0x682F1002 0x68391002 0x683B1002 0x683D1002 0x683F1002 0x68001002 0x68011002 0x68061002 0x68081002 0x68101002 0x68181002
AMDX4000 Pitcairn: 0x68001002 0x68011002 0x68061002 0x68081002 0x68101002 0x68181002

As you see, those ids are supported by both kexts, so we set these in Clover:

FakeID > ATI: 0x68001002

OS X will think our card id is 0x68001002 and load them, voila!

You also have to set FB Name for this card (I assume Futomaki).

Graphics > FB Name: Futomaki
Graphics > Inject ATI: check
Graphics > Dual Link: 0 for low resolution, 1 for high
Graphics > Load VBIOS: check (or not)
Graphics > Patch VBIOS: check (or not)

the final config.plist should be this, and don't forget to use vanilla kexts too.

    <key>Devices</key>
    <dict>
        <key>FakeID</key>
        <dict>
            <key>ATI</key>
            <string>0x68001002</string>
        </dict>
    </dict>
    <key>Graphics</key>
    <dict>
        <key>DualLink</key>
        <integer>1</integer>
        <key>FBName</key>
        <string>Futomaki</string>
        <key>Inject</key>
        <dict>
            <key>ATI</key>
            <true/>
            <key>Intel</key>
            <false/>
            <key>NVidia</key>
            <false/>
        </dict>
        <key>LoadVBios</key>
        <true/>
        <key>PatchVBios</key>
        <true/>
    </dict>

daniesy · March 6, 2014

I think i already tried this but didn't work. I'll try it again and restore if it doesn't work...

daniesy · March 6, 2014

Oh yeah!!! 75fps in Cinebench! Thank you sir!

Electric_Sheep · March 6, 2014

I also have a Saphire Dual-X R9 270 however i'm not using [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] as a boot loader.

Any help would be much appreciated!

TechGuru · March 7, 2014

can someone upload whats inside new 10.9.3 graphics kext's to see if r7 250 is in it now and 290x will work thanks

daniesy · March 7, 2014

I also have a Saphire Dual-X R9 270 however i'm not using ##### as a boot loader.

Any help would be much appreciated!

Try clover as the boot loader. It did work for me.

VirusX · March 11, 2014

pokenguyen,

I have tried your method for my MSI 270X. But my problem is now, that only 8MB of my video RAM is recognized! (see attached screenshot)

Do you have any idea what could be the mistake? Thank you!

I used

and

	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<true/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
        	<key>DualLink</key>
        	<integer>1</integer>
        	<key>FBName</key>
        	<string>Futomaki</string>
		<key>PatchVBios</key>
		<false/>
	</dict>

here's my complete clover config file: (using the newest clover 2636): http://pastebin.com/BapNtnGt

in the boot log it says:

12:361  0:000  ATI card POSTed, 
12:361  0:000  Set VRAM for Cedar=2048Mb
12:361  0:000  ATI: get_vram_size returned 0x80000000
12:361  0:000  ATI Radeon EVERGREEN family
12:361  0:000  Users config name Futomaki
12:361  0:000  (AtiPorts) Nr of ports set to: 5
12:361  0:000  ATI Tahiti AMD Radeon R9 270X 2048MB (Futomaki) [1002:6810] (subsys [1462:3030]):: PcieRoot(0x0)\Pci(0x3,0x0)\Pci(0x0,0x0)

pokenguyen · March 12, 2014

Do you have QE/CI working? Is your benchmark score normal? If they are fine, "8MB" is just a cosmetic error, open config.plist and add your desired VRAM.

VirusX · March 12, 2014

thank you for your quick answer. I should have stated it clearly: no, I don't have QE/CI working (it lags like hell when I switch desktops etc) so I didn't even try benchmarks. Adding the VRAM in my config probably won't help to get QE/CI, right?

The strange thing is that it got recognized correctly before I added all those things like FakeID etc. I tried to get HDMI working with http://www.insanelymac.com/forum/topic/294315-radeon-r9-270x-framebuffer-issue/page-4 but did not succeed. So I put the AMD7000controller.kext back in S/L/E and am trying the all-clover approach.

Problem is that I cannot do a fresh install because my screen goes black/standby when I enter the installation. So I have only 2 installations of mavericks left to get that thing to work -.-

I hope you can still help me out. I can provide any information you need.

Thanks!

pokenguyen · March 12, 2014

This FakeID is only usable on R9 270, it means no native QE/CI at install, while your R9 270X is already working well without any injection. You should try to patch your port to get HDMI, I don't have experience though.

VirusX · March 12, 2014

I did use the FakeID for my card though but you're right: I deleted the FakeID and nothing has changed.

The problem is that my card does NOT work well out of the box. I don't know what's wrong with my config. I don't even now where to start because it feels that I have tried everything.

I theory, my 270X _should_ work with only Inject>ATI>true?

edit: I went back and started off at the beginning again: my report here

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-208?do=findComment&comment=2003420

Ed57 · July 30, 2014

Asrock 970 Extreme r2.0 + Gigabyte R9 290 + Niresh's Maverick 10.9 + Netkas kexts= fully working.

A big TY to Netkas who made this possible you're the best man.

p.s: of course i had to edit both kexts with hardware ids (0x67b1).

aizensosuke64 · August 6, 2014

I tried following the method here to inject into clover my GIGABYTE R9 270 OC .

But I just get a Graphics card with a total of 8mb of Vram and QE/CI doesn't seem to be active.

Pic

What I did, I inserted my deviced ID into both AMD7000Controller.kext and AMDX4000.kext which is 0x68111002 right under "IOPCIMatch". Then used kext utility to-reinsert the two edited .kext files.

Clover config.plist here:



<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

	<key>ACPI</key>

	<dict>

		<key>DSDT</key>

		<dict>

			<key>Debug</key>

			<false/>

			<key>Fixes</key>

			<dict>

				<key>AddDTGP_0001</key>

				<true/>

				<key>AddHDMI_8000000</key>

				<true/>

				<key>AddIMEI_80000</key>

				<true/>

				<key>AddMCHC_0008</key>

				<false/>

				<key>AddPNLF_1000000</key>

				<true/>

				<key>DeleteUnused_400000</key>

				<true/>

				<key>FIX_ACST_4000000</key>

				<true/>

				<key>FIX_ADP1_800000</key>

				<true/>

				<key>FIX_INTELGFX_100000</key>

				<false/>

				<key>FIX_RTC_20000</key>

				<true/>

				<key>FIX_S3D_2000000</key>

				<true/>

				<key>FIX_TMR_40000</key>

				<true/>

				<key>FIX_WAK_200000</key>

				<true/>

				<key>FakeLPC_0020</key>

				<false/>

				<key>FixAirport_4000</key>

				<true/>

				<key>FixDarwin_0002</key>

				<false/>

				<key>FixDisplay_0100</key>

				<true/>

				<key>FixFirewire_0800</key>

				<true/>

				<key>FixHDA_8000</key>

				<true/>

				<key>FixHPET_0010</key>

				<true/>

				<key>FixIDE_0200</key>

				<false/>

				<key>FixIPIC_0040</key>

				<true/>

				<key>FixLAN_2000</key>

				<true/>

				<key>FixRegions_10000000</key>

				<true/>

				<key>FixSATA_0400</key>

				<false/>

				<key>FixSBUS_0080</key>

				<false/>

				<key>FixShutdown_0004</key>

				<true/>

				<key>FixUSB_1000</key>

				<false/>

				<key>NewWay_80000000</key>

				<true/>

			</dict>

			<key>Name</key>

			<string>DSDT.aml</string>

		</dict>

		<key>DropTables</key>

		<array>

			<dict>

				<key>Signature</key>

				<string>DMAR</string>

			</dict>

			<dict>

				<key>Signature</key>

				<string>SSDT</string>

				<key>TableId</key>

				<string>CpuPm</string>

			</dict>

			<dict>

				<key>Signature</key>

				<string>SSDT</string>

				<key>TableId</key>

				<string>Cpu0Ist</string>

			</dict>

		</array>

		<key>HaltEnabler</key>

		<true/>

		<key>SSDT</key>

		<dict>

			<key>EnableC2</key>

			<false/>

			<key>EnableC4</key>

			<false/>

			<key>EnableC6</key>

			<true/>

			<key>EnableC7</key>

			<false/>

			<key>Generate</key>

			<dict>

				<key>CStates</key>

				<true/>

				<key>PStates</key>

				<true/>

			</dict>

		</dict>

	</dict>

	<key>Boot</key>

	<dict>

		<key>Arguments</key>

		<string>-v</string>

		<key>DefaultVolume</key>

		<string>MacHDD</string>

		<key>Fast</key>

		<false/>

		<key>Legacy</key>

		<string>PBR</string>

		<key>Log</key>

		<false/>

		<key>Timeout</key>

		<integer>10</integer>

		<key>XMPDetection</key>

		<string>-1</string>

	</dict>

	<key>Devices</key>

	<dict>

		<key>Audio</key>

		<dict>

			<key>Inject</key>

			<string>No</string>

		</dict>

		<key>FakeID</key>

		<dict>

			<key>ATI</key>

			<string>0x68111002</string>

			<key>IMEI</key>

			<string>0x0</string>

			<key>IntelGFX</key>

			<string>0x0</string>

			<key>LAN</key>

			<string>0x0</string>

			<key>NVidia</key>

			<string>0x0</string>

			<key>SATA</key>

			<string>0x0</string>

			<key>WIFI</key>

			<string>0x0</string>

			<key>XHCI</key>

			<string>0x0</string>

		</dict>

		<key>Inject</key>

		<false/>

		<key>USB</key>

		<dict>

			<key>AddClockID</key>

			<true/>

			<key>FixOwnership</key>

			<true/>

			<key>Inject</key>

			<true/>

		</dict>

	</dict>

	<key>DisableDrivers</key>

	<array>

		<string>Nothing</string>

	</array>

	<key>GUI</key>

	<dict>

		<key>Hide</key>

		<array>

			<string>Windows</string>

			<string>BOOTX64.EFI</string>

		</array>

		<key>Language</key>

		<string>en:0</string>

		<key>Mouse</key>

		<dict>

			<key>Enabled</key>

			<true/>

			<key>Speed</key>

			<integer>14</integer>

		</dict>

		<key>Scan</key>

		<dict>

			<key>Entries</key>

			<true/>

			<key>Legacy</key>

			<true/>

			<key>Tool</key>

			<true/>

		</dict>

		<key>TextOnly</key>

		<false/>

		<key>Theme</key>

		<string>bootcamp</string>

	</dict>

	<key>Graphics</key>

	<dict>

        <key>DualLink</key>

        <integer>1</integer>

        <key>FBName</key>

        <string>Futomaki</string>

		<key>Inject</key>

		<dict>

			<key>ATI</key>

			<true/>

			<key>Intel</key>

			<false/>

			<key>NVidia</key>

			<false/>

		</dict>

		<key>VRAM</key>

		<integer>2048</integer>

        <key>LoadVBios</key>

        <false/>

        <key>PatchVBios</key>

        <false/>

	</dict>

	<key>KernelAndKextPatches</key>

	<dict>

		<key>AppleRTC</key>

		<true/>

		<key>AsusAICPUPM</key>

		<true/>

		<key>Debug</key>

		<false/>

		<key>KernelCpu</key>

		<false/>

		<key>KextsToPatch</key>

		<array>

			<dict>

				<key>Comment</key>

				<string>External icons patch</string>

				<key>Find</key>

				<data>

				RXh0ZXJuYWw=

				</data>

				<key>Name</key>

				<string>AppleAHCIPort</string>

				<key>Replace</key>

				<data>

				SW50ZXJuYWw=

				</data>

			</dict>

		</array>

	</dict>

	<key>RtVariables</key>

	<dict>

		<key>LogEveryBoot</key>

		<string>10</string>

		<key>LogLineCount</key>

		<integer>3000</integer>

		<key>MountEFI</key>

		<true/>

	</dict>

	<key>SystemParameters</key>

	<dict>

		<key>InjectKexts</key>

		<string>Detect</string>

		<key>InjectSystemID</key>

		<true/>

	</dict>

</dict>

</plist>

Clover is currently installed to the EFI partition, not sure if that matters.

Any help appreciated.

terrorgen · May 20, 2015

Hi I have a XFX Double D R9 270 with 1x DP, 1x HDMI and 2x DVI-Dual Link. I have (3) Monoprice WQHD monitors, two of which is connected directly to the graphics card through DVI-Dual Link. The third is connected via an active DP to DVI-Dual Link adapter. I was using a HD 5850 before the upgrade so I know that this configuration works.

Here's what I have done so far:

1. I modified the kexts with the correct device ID: 0x6811.

2. In Clover I have InjectATI enabled.

3. I also set the FrameBuffer to Hamachi, replaced the framebuffer with the following:

00 04 00 00 04 03 00 00 00 01 00 00 22 05 01 02 DP

04 00 00 00 14 02 00 00 00 01 00 00 11 02 05 05 DVI-DL

04 00 00 00 14 02 00 00 00 01 00 00 10 00 03 06 DVI-DL

00 08 00 00 00 02 00 00 00 01 00 00 12 04 02 03 HDMI

The values are based on Vlada's tutorial and the attached ROM file downloaded from https://www.techpowerup.com/vgabios/151666/xfx-r9270-2048-131119.html

So far, only the monitor connected to the DP works. For the ones connected to the Dual-Link DVI ports, one does not receive a signal at all and went into sleep, the other one displays a black screen. However, all three monitors show up in System Information.

Wonder if anyone has the same graphics card and is able to help?

Thanks.

AMD r9 270 problem

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites