[HOW TO] Modification of AMD FB + Clover injection

[vusun123]

Hi may i know this thread will make my lvds detect as a laptop monitor rather than a display? Because basically i have qe/ci working by editing the kext and injectati=yes but the lvds doesn't work. So i use customedid and injectedid and now my lvds works but it detects as a display rather than a laptop display. I need it to detect as a laptop display as i need to get sleep to work. Every time i click sleep, the screen just turn black with a cursor. Also clamshell doesn't work too despite having implemented pnlf in my dsdt. Thank you very much. My laptop is compaq cq42-277tx, ATI 5430m.

Use Rehabman's generic PNLF patch. It will detect your laptop's lvds as a backlight display

[Sen]

Use Rehabman's generic PNLF patch. It will detect your laptop's lvds as a backlight display

 

Thanks for the reply! I tried. But it still the same. Detect as a display with no brightness slider, sleep and clamshell.

 

I think yes. Just try.

 

Thanks slice for the reply! Btw i have some question to ask sorry for my incompetence:

1. Im abit lost at this part:

 

 

Constructed FB is made this way, mostly due to the fact that Apple monitors are using DP as the primary connection and then we have beneath in order all others.

 

In the vast majority of cases there, you will need to change only the last 4 digits, which are also the most important for proper connector injection, or eventually you will need to assign further a DVI-I (SL) connection for your monitor. In this case, it is basically a mandatory thing mostly because the original code does not have it. Therefore, we will need to change the second row from DP into DVI-SL.  The initial input of first four pairs of digits we will need to change from 00 04 00 00 to 00 02 00 00, which is the proper input for DVI-SL.

 

00 02 00 00

 

Then follows the explanation of the second set of digits:

 

0×0002 : LVDS               ControlFlag : 0×0040 and 0×0100

0×0004 : DVI                  ControlFlag : 0×0016, 0×0014, and 0×214

0×0010 : VGA                ControlFlag : 0×0010

0×0080 : S-Video           ControlFlag : 0×0002

0×0200 : DVI                  ControlFlag : 0×0014, 0×0214, and 0×0204

0×0400 : DisplayPort     ControlFlag : 0×0100, 0×0104, 0×0304, 0×0604, and 0×0400

0×0800 : HDMI               ControlFlag : 0×0200 

0×1000 : DVI                   ControlFlag : 0×0016

 

Translated in to:

 

Connector Type DP 04 03 00 00

Connector Type DP 04 03 00 00

Connector Type HDMI 00 02 00 00

Connector Type DVIDL 14 02 00 00

Connector Type_DVISL C 04 02 00 00

Connector Type_DVISL 04 02 00 00

 

From this example it is clear that in the modified row we should add further 04 02 00 00 according to the matched connector name. So after first 00 02 00 00 we will need to add the following 4 pair of digits 04 02 00 00 and all together it looks like this:

 

00 02 00 00 04 02 00 00

Is it true that 0x0040 and 0x0100 after encoding them is = 40 00 00 01? But why is there a need to put the 00 01? Cant i just put 00 00 instead? Because i seen a config.plist belong to a guy whose laptop is acer and his graphic is ati 5000 series, he put 40 00 00 00 rather than 40 00 00 01. Also, step 1 thread starter says that we need to dump/extract the rom from our graphic card using either dpcimanager from OS X or gpu-z. I choose the latter but i was prompted with an error saying that bios reading is not supported from this device. So i use aida64 instead. But the file extension is dmp rather than rom. So i changed it to rom. Will it have an effect or something? Thank you very much

[vusun123]

The problem might be in your patch. LVDS use 0901 as Output Feature, not 0001 as other connectors

[Sen]

The problem might be in your patch. LVDS use 0901 as Output Feature, not 0001 as other connectors

I haven't actually created the patch. Still reading the thread to further understand. Im having some troubles understanding the second set of digit. The control flag part.

[vusun123]

I haven't actually created the patch. Still reading the thread to further understand. Im having some troubles understanding the second set of digit. The control flag part.

I don't have any trouble at that part. Just pick one

[Sen]

I don't have any trouble at that part. Just pick one

Ok, i just followed the guide. Now my laptop whenever i clicked sleep, the screen turn black without any backlight! Unlike last time the screen turn black with a cursor and backlight. But my laptop does not sleep completely though I can hear the fan running at full throttle and the power button still have light. And the display preference doesn't have any slider or so. Oh and clamshell doesn't work too despite pnlf is implemented in my dsdt. Do you think something wrong with my patch? Thank you very much.

 

**Edit** Success! I just applied rehab man pnlf and it works! Now i have brightness slider and clamshell working! Im wondering can i create another two patch for my vga and hdmi alongside with the lvds patch at clover? I haven't tested my hdmi and vga but i still they don't work because the frame buffer I'm using is langur. Will it cause friction between each other Thank you very much.

[vusun123]

Ok, i just followed the guide. Now my laptop whenever i clicked sleep, the screen turn black without any backlight! Unlike last time the screen turn black with a cursor and backlight. But my laptop does not sleep completely though I can hear the fan running at full throttle and the power button still have light. And the display preference doesn't have any slider or so. Oh and clamshell doesn't work too despite pnlf is implemented in my dsdt. Do you think something wrong with my patch? Thank you very much.

 

**Edit** Success! I just applied rehab man pnlf and it works! Now i have brightness slider and clamshell working! Im wondering can i create another two patch for my vga and hdmi alongside with the lvds patch at clover? I haven't tested my hdmi and vga but i still they don't work because the frame buffer I'm using is langur. Will it cause friction between each other Thank you very much.

Yes you can, but you must patch your own framebuffer for them.

[Mork vom Ork]

Just a litle update for all of you:

 

recently i switched to ASUS X99-E WS motherboard and Intel I7 5820k cpu. And this board and cpu is a hassle for a hackintosh. Took me a whole weekend to make OS X 10.10.5 and OS X 10.11.1 running on this board. GFX-card still the same ASUS R9 380 STRIX with 2GB RAM running in PCI Slot #3 (have to move it to that slot, cause Thunderbolt card needs to be plugged into Slot #2 for best results). BIOS is the latest 1302 for this board and i still use my ASUS ThunderboltII EX card in PCI slot #2. First i got memory allocation error when trying to boot. Gladly i found a working "OsxAptioFixDrv-64.efi" driver, so now i am able to boot with latest CLOVER 3305.

 

Now here is the problem:

 

tried almost every framebuffer with this card. Under YOSEMITE no problem: all of my injected fb-patches work like a charm: OS X will boot in verbose mode, when booting to desktop, all connected monitors (1 DP, 1 HDMI and 1 DVI) stop responding for about 90 seconds. After that period of time they will come back and all monitors are showing the desktop (with full acceleration). So i can live with that amount of delay when booting to desktop.

 

But no chance to make it working with latest EL CAPITAN 10.11.1 - same effect: booting verbose mode is ok, than all monitors turn black and... no response anymore! But machine still seems to be working, cause i could connect to filesharing of EL CAPITAN machine (i enabled it to test, if machine still is responding) and also responds to ping requests. Using Apple Remote Desktop Admin client, i can see also, that EL CAPITAN machine ist still alive, but it says "ARD not ready" and when i try to connect via ARD i will get a timeout message: "EL CAPITAN not responding. Verrify, if Firewall is blocking the ports" or something similar like that.

 

When i delete the "AMDRadeonX4000.kext" from System/Extensions, i could boot into desktop, but without acceleration. IORegistryExplorer shows me correct patched framebuffer with all 4 ports connected and correctly assigned to their order (port 4 still has no monitor connected). You can see in attached Screenshot. Also DPCIManager shows, that RADEON has the Framebuffer accepted successfully.

 

In my example i choose to modify GREYHOUND framebuffer from

 

Greyhound original:

00040000040300000001010710000103
00040000040300000001020720010204
00040000040300000001030711020301
00040000040300000001040721030402
00040000040300000001050712040505
00040000040300000001060722050606

000400000403000000010107100001030004000004030000000102072001020400040000040300000001030711020301000400000403000000010407210304020004000004030000000105071204050500040000040300000001060722050606

Greyhound patched:

00040000040300000001000711020401
00080000040200000001000021030403
00020000140200000001000010000405
04000000140000000001000012040406
00040000040300000001000010000402
00020000140200000001000010000404

 

000400000403000000010007110204010008000004020000000100002103040300020000140200000001000010000405040000001400000000010000120404060004000004030000000100001000040200020000140200000001000010000404

 

And now for the strange thin in üatching the framebuffers: the only work, when i set "04" for the HotPlugID to all defined connectors! If i set the HotPlugID in a normal order like 01 for DP, 02 for HDMI, 03 for DVI-I and 04 for DVI-D (05 and 06 for the last defined connectors) i will allways get errors on reboot, when system tries to show desktop on the connected monitors (w/o connector #4, which is still working correctly). Then, when i try to connect remotly to desktop with ARD from my Macbook, i can see in IORegistryExplorer, that the connectors are still in the right order, but still have no monitor connected (w/o defined port #4).

 

So when i change the HotPlugID of patched framebuffer all to "04", all Monitors will be correctly recognized and are showing their desktops. VERRY WEIRED !!!

 

Could anyone explain this to me? Also i found out, that i could define the order of connectors by switching the following entries in framebufferpatch:

 

00040000040300000001001711020401
00080000040200000001002021030403
00020000140200000001003010000405
04000000140000000001004012040406
00040000040300000001005010000402
00020000140200000001006010000404

 

Changing these values in thier order, will change the connectors order in IORegistryExploer as well. JUST TESTED AND CONFIRMED. So why do i have to change these values instead of the HotPlugID values?

And why does changing the HotPlugID makes my setup broke?

 

Any explanations to this are welcome.

 

So far... regards. Hope this will help all the other owners of a RADEON R9 380 gfx-card.

 

 

PS: all AMD9000.kext framebuffers could be patched with the above patch. BASSET still get the first 4 rows patched, cause this is a 4 connectors framebuffer. All the others use 6 connectors. When i try to use patched BALADI or EXMOOR, they will change to default RADEONFRAMEBUFFER after boot. All the others got accepted: BASSET, GREYHOUND, OPM, LABRADOR (only in 10.11.1, cause it isnt availlable in 10.10.5)

CLOVER Config.txt

[Vlada.]

Did anyone figure out blackout issue after wake from sleep under El Capitan?

 

That’s the problem that troubling me lately. The anomaly is typical for AMD graphics which considers display blackout and there is no operational USB.

 

And, hm... that USB anomaly is interesting. It’s pointing that the problem might be related to something else too, but not with graphics only.

 

As far as I can see FB code is the same, so there are no changes in that part, but I was notice that sensor-properties line is removed by Apple in info.plist file inside the AMDRadeonX4000.kext under Capitan, so that could be something… However, I’m not sure about that, because some people reporting that they don’t have any problem!? Anyway, I didn’t manage to find proper solution for now, so any help or suggestion will be more than welcome!

[winlog]

Trying to extract some info, but...

 

Kext /System/Library/Extensions/AMD7000Controller.kext/Contents/MacOS/AMD7000Controller

Personality: Ramen

ConnectorInfo count in decimal: 0

Disk offset in decimal 1884704

Personality: Tako

ConnectorInfo count in decimal: 0

Disk offset in decimal 1884912

Personality: Namako

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885008

Personality: Aji

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885168

Personality: Buri

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885232

Personality: Chutoro

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885296

Personality: Dashimaki

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885376

Personality: Ebi

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885440

Personality: Gari

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885520

Personality: Futomaki

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885648

Personality: Hamachi

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885712

Personality: OPM

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885840

Personality: Ikura

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885936

Personality: IkuraS

ConnectorInfo count in decimal: 0

Disk offset in decimal 1885952

Personality: Junsai

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886048

Personality: Kani

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886144

Personality: KaniS

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886160

Personality: DashimakiS

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886256

Personality: Maguro

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886320

Personality: MaguroS

ConnectorInfo count in decimal: 0

Disk offset in decimal 1886336

 

El Capitan, 10.11.1. Can't get what is wrong. Script version 0.15

[polyzargone]

@winlog

 

Look here .

[winlog]

The second pair of numbers:

 

Use Internal * 0 × 01 = 01

Use RGB YUV On 0 × 04 = 04

Use Backlight * 0 × 08 = 08

Backlight Inverted 0 × 10 = 10

Use Clamshell 0 × 20 = 20

 

Could you explain what does it mean, for example, Use RGB YUV On or Use Clamshell?

[Vlada.]

Could you explain what does it mean, for example, Use RGB YUV On or Use Clamshell?

 

 

Well, you could use google for that.

 

Use RGB YUV On is the color space which you could enable by using those inputs... And if I'm correct, Use Clamshell means that the display should turn off when you close your laptop;  *(Clamshell = Any of various devices that consist of two parts attached by a hinge and that open and close like a clamshell).

[Ciro82]

@Vlada

 

I write here my experience with the HD 7970 (Reference).

I had problems with this card, as in OSX 10.10 and 10.11 the FB was not loaded, "AMD Radeon FrameBuffer" loaded, instead of "Aji" (DSDT inject).

Following a tip from @Pjalm (Thanks PJ) , i've modified the GFX card's firmware by adding "GOP" in it.

After the FW flashing (with modified FW) and enabling "Super Fast Boot" on mobo's FW, the FB "Aji" is loaded correctly (I inject "Aji" through DSDT) in both 10.10 and 10.11.

I hope that will be a solution for someone.

[winlog]

Well, you could use google for that.

 

Use RGB YUV On is the color space which you could enable by using those inputs... And if I'm correct, Use Clamshell means that the display should turn off when you close your laptop;  *(Clamshell = Any of various devices that consist of two parts attached by a hinge and that open and close like a clamshell).

Anyone can use Google to find out some info. But there is forum, related to. Also, if you wrote that, you have to know what does it mean.

 

I was asked that because of now after patching connectors, I see CGSThirtyBitColor as color depth in profiler for my 4K monitor, and also Television: Yes. Now I'm searching for solution, how to enable 30 bit color depth and remove Television: Yes as my monitor is not TV

[twisterchoc]

Don´t work for me under 10.11  I´ve one Gigabyte R9 270x with two displays, one primary connected via display port and the other via hdmi but only the hdmi turns on. This is clover patch i made with this tutorial:

 

<key>Graphics</key>

<dict>

<key>FBName</key>

<string>Futomaki</string>

<key>Inject</key>

<dict>

<key>ATI</key>

<true/>

<key>Intel</key>

<false/>

<key>NVidia</key>

<false/>

</dict>

</dict>

<key>KernelAndKextPatches</key>

<dict>

<key>ATIConnectorsController</key>

<string>7000</string>

<key>ATIConnectorsData</key>

<string>00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103</string>

<key>ATIConnectorsPatch</key>

<string>00040000040300000001010112040101000800000402000000010201220502030002000004020000000100001000030604000000140200000001000011020505</string>

Please can anyone help me with this?

[winlog]

 

Don´t work for me under 10.11  I´ve one Gigabyte R9 270x with two displays, one primary connected via display port and the other via hdmi but only the hdmi turns on. This is clover patch i made with this tutorial:

 

<key>Graphics</key>

<dict>

<key>FBName</key>

<string>Futomaki</string>

<key>Inject</key>

<dict>

<key>ATI</key>

<true/>

<key>Intel</key>

<false/>

<key>NVidia</key>

<false/>

</dict>

</dict>

<key>KernelAndKextPatches</key>

<dict>

<key>ATIConnectorsController</key>

<string>7000</string>

<key>ATIConnectorsData</key>

<string>00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103</string>

<key>ATIConnectorsPatch</key>

<string>00040000040300000001010112040101000800000402000000010201220502030002000004020000000100001000030604000000140200000001000011020505</string>

Please can anyone help me with this?

 

<string>Labrador_Patch</string>

<key>Find</key>

<data>

AgAAAAABAAAAAQEDIQMCBAIAAAAAAQAAAAECAxECAQMA

BAAABAMAAAABAwcQAAMBAAQAAAABAAAAAQQDIAEFBQAE

AAAEAwAAAAEFBxIEBAIABAAAAAEAAAABBgMiBQUF

</data>

<key>Name</key>

<string>AMD9000Controller</string>

<key>Replace</key>

<data>

AAQAAAQDAAAAAQAHEQIEAQAIAAAEAgAAAAEAACEDBAMA

AgAAFAIAAAABAAAQAAQFBAAAABQAAAAAAQAAEgQEBgAE

AAAEAwAAAAEAABAABAIAAgAAFAIAAAABAAAQAAQE

 

</data>

 

 

[twisterchoc]

winlog thanks for your help

[giacomoleopardo]

@Vlada

 

I write here my experience with the HD 7970 (Reference).

I had problems with this card, as in OSX 10.10 and 10.11 the FB was not loaded, "AMD Radeon FrameBuffer" loaded, instead of "Aji" (DSDT inject).

Following a tip from @Pjalm (Thanks PJ) , i've modified the GFX card's firmware by adding "GOP" in it.

After the FW flashing (with modified FW) and enabling "Super Fast Boot" on mobo's FW, the FB "Aji" is loaded correctly (I inject "Aji" through DSDT) in both 10.10 and 10.11.

I hope that will be a solution for someone.

Would you mind to be more specific about the patching job? that's quite interesting. Thanks

[Ciro82]

Would you mind to be more specific about the patching job? that's quite interesting. Thanks

 

Download this: https://www.dropbox.com/s/5bphx05ma8z9n13/AMD-UEFI-GOP-MAKER.zip ;

Extract AMD card's Vbios with DPCImanager, rename it to "original.rom";

Put the .rom file into AMD-UEFI-GOP-MAKER folder;

Run "UEFI_ROM.command" and after that you will find a new .rom file named "uefi.rom";

Run ATIWinFlash on Windows OS, following this guide: http://www.overclock.net/t/1353325/tutorial-atiwinflash-how-to-flash-the-bios-of-your-ati-cards.

 

Credits to: @STLVNUB

[chiefsalami]

Guys, how do I "force" the computer to use a particular framebuffer? I am using an unsupported video card (AMD FirePro W7100), and patching kexts in order to have it work. I have added the device ID to AMD9000Controller, and am injecting connector info with Clover. I am starting with the Basset framebuffer and editing the connector data using this guide, and also injecting with Clover. I can see that when I make changes to the connector info in the personality, it affects my output to the monitor. In other words, I can get different displays (I have two connected via DP), but not both, to work based on what I use for the connector info, but no matter what, when I run ioreg I don't see the Basset framebuffer being used. If I don't inject a framebuffer, OS X properly detects my two connected displays, but with all kinds of artifacts and stuttering. No matter what, whether I inject the framebuffer or not, whether the displays work correctly or not, I only see AMDFramebuffer being used. Never Basset or anything else. Can anyone tell me how to force the framebuffer to be used, instead of the default?

 

I'm on El Capitan 10.11.1, latest Clover, running either MacPro6,1 or iMac15,1 SMBIOS (doesn't appear to make a difference)

[TheRacerMaster]

Are you injecting it with Clover? Set the FBName key in config.plist/Graphics.

[chiefsalami]

Yes, that is how I am injecting. The default injection through Clover (Baladi) works better, but whether I inject the default FB or my modified one, nothing ever shows on ioreg besides AMDFramebuffer.

[Multisaft]

Hi Guys,

 

I need your help. Every tipp is highly welcome. 

 

I like to update from 10.9.5 to Yosemite. After all, this is my first use of clover, but I've used Chameleon since 10.7, therefore, I wouldn't suggest myself as a total beginner.

 

My PC is as follows: ASUS P6T-SE with the 0908 BIOS (no UEFI boot), Xeon X5660, 12Gig RAM, Powercolor PC+ R9 270x (absolutly the same as Vlada is using)

 

At the moment, I'm using 10.9.5 with Vladas DMG Patch-Package (works even that the system manager does not show the correct name - just Radeon 7xxx)

 

USB Installer / Clover Configuration / FB Injection:

 

I'm following this guide to create a usb installer: http://www.insanelymac.com/forum/topic/298521-easy-yosemite-1010-final-usb-installer-updated-10162014/

 

I'm using the actual/newest version of clover (r3220), I've loaded the newest FakeSMC provided from insanelymac and put it into the kext folder for 10.10 in the clover installation path /EFI/CLOVER/kexts/10.10/ no problem so far.

 

But now I'm stucked with my graphics, Until now, I'm running a 40" Philips 4k Monitor through 4k 60fps (DP 1.2) under 10.9.5 - it works like a charm.

 

I've followed Vladas Guide to Extracting my ROM File, I've used the BIOS decoders to find the correct connectors output, I've compared my results with Vladas (as mentioned above, we are using the SAME graphics card) and found out that the connectors outputs are the same, therefore I've created my HEX-Values to patch my AMD7000Controller with Clover injection. Its still the same result as Vladas.

 

Radeon Bios Decode:

ATOM BIOS Rom: 
	SubsystemVendorID: 0x148c SubsystemID: 0x2336
	IOBaseAddress: 0x0000
	Filename: E8B11LCC.HHW
	BIOS Bootup Message: 
C63101 CURACAO XT GDDR5 64Mx32 2GB E8B11LCC.HHW 2013                        

PCI ID: 1002:6810
Connector at index 0
	Type [@offset 43522]: DisplayPort (10)
	Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43632]: 0x90, OSX senseid: 0x1
Connector at index 1
	Type [@offset 43532]: HDMI-A (11)
	Encoder [@offset 43536]: INTERNAL_UNIPHY2 (0x21)
	i2cid [@offset 43659]: 0x92, OSX senseid: 0x3
Connector at index 2
	Type [@offset 43542]: DVI-I (2)
	Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e)
	i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
Connector at index 3
	Type [@offset 43552]: DVI-I (2)
	Encoder [@offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15)
	i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
Connector at index 4
	Type [@offset 43562]: DVI-D (3)
	Encoder [@offset 43566]: INTERNAL_UNIPHY1 (0x20)
	i2cid [@offset 43723]: 0x94, OSX senseid: 0x5

Redsock Bios Decode:

E8B11LCC.HHW:

C63101 CURACAO XT GDDR5 64Mx32 2GB E8B11LCC.HHW 2013                        

Subsystem Vendor ID: 148c
       Subsystem ID: 2336
Object Header Structure Size: 355
Connector Object Table Offset: 48
Router Object Table Offset: 0
Encoder Object Table Offset: fd
Display Path Table Offset: 12
Connector Object Id [19] which is [DISPLAY_PORT]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false
Connector Object Id [12] which is [HDMI_TYPE_A]
	encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true
Connector Object Id [2] which is [DVI_I]
	encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false
Connector Object Id [2] which is [DVI_I]
	encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 enc 0x10?)] linkb: false
Connector Object Id [4] which is [DVI_D]
	encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false

Then I've opened the Clover Config EDITOR and used these setting: Under Graphics: Inject ATI (I've learned that this must be done to use any graphics injection), Load VBios, added the FrameBuffer Name: "Futomaki" - as this is the FB I'm patching in the next Kernel and Kext Patches tab, and "Inject EDID".

 

In the Kernel and Kext Patches tap, I've followed Vladas description most closely, adding

the "AMD7000Controller" Name,

the HEX Values for Find*:

00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103

and Replace*: 

00040000040300000001020112040101000200000402000000010101100003060400000014020000000103001102050500080000000200000001040022050203

and some description.

 

This is exactly!! the same routine, Vlada is describing on the first page:

 

Original code:
00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 - DP
00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 - DP
04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 - DVI-DL
00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 - HDMI
 
Modified code:
 

00 04 00 00 04 03 00 00 00 01 02 01 12 04 01 01 - DP
00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06 - DVI-I
04 00 00 00 14 02 00 00 00 01 03 00 11 02 05 05 - DVI-D
00 08 00 00 00 02 00 00 00 01 04 00 22 05 02 03 - HDMI

 

The rest of the clover configurator is standard. It boots with flags: kext-dev-mode=1, and rootless=0

 

Booting and Installing 10.10:

 

Booting into the Clover USB Installer works but not as described in the installation guide  "without caches", It just loades with caches, but then I'm stucked with the "white screen" problem (using the display port 1.2). 

OK when I'm using a dvi to hdmi, or a hdmi connection - and with the ATI Injection still set to true, I'm stucked at the "black screen" issue, therefore, something must be wrong with applying the frame-buffer injection, isn't it?

 

First question (or the second): is it correct, that the Clover Config Editor is changing the HEX Values into some DATA fields in the config.plist ?

 

I've seen some config.plist posted, where the guys have used string values to change FB, therefore my next step: In addition to the added injection, I've added my connector information into the top fields in the Clover Config EDITOR in the tap "Kernel Patches" - fields named "ATI Connectors Data" (the old original Futomaki FrameBuffer), and my own (or Vladas) Framebuffer in the "ATI Connectors Path". Now my config file does contain both configurations. That doesn't worked, same problem: with DP connected, white screen, with HDMI/DVI connected, black screen, without ATI Injection (so without my framebuffer injection), the Installation Screen is visible.

 

What am I doing wrong? 

 

Next idea: I'm installing 10.10. without ATI Injection, and try it again on the SSD and Clover Configuration and not on the usb installer. Next Problem to be solved, the 10.10.4 setup ends at the end, the PC restarts, but the CLOVER USB Installer does not find the installed 10.10 on my SSD - just my 10.9.5 installation and the usb Installer itself. 

 

Any advice?

 

Here is a part of my config.plist:

<key>Graphics</key>
	<dict>
		<key>FBName</key>
		<string>Futomaki</string>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<true/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>InjectEDID</key>
		<true/>
		<key>LoadVBios</key>
		<true/>
		<key>NvidiaSingle</key>
		<false/>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>ATIConnectorsData</key>
		<string>00040000040300000001010112040401000400000403000000010201220505020400000014020000000103000000060600080000040200000001040011020103</string>
		<key>ATIConnectorsPatch</key>
		<string>00040000040300000001020112040101000200000402000000010101100003060400000014020000000103001102050500080000000200000001040022050203</string>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<false/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelHaswellE</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Connectors Patch</string>
				<key>Find</key>
				<data>
				AAQAAAQDAAAAAQEBEgQEAQAEAAAEAwAAAAECASIFBQIE
				AAAAFAIAAAABAwAAAAYGAAgAAAQCAAAAAQQAEQIBAw==
				</data>
				<key>Name</key>
				<string>AMD7000Controller</string>
				<key>Replace</key>
				<data>
				AAQAAAQDAAAAAQIBEgQBAQACAAAEAgAAAAEBARAAAwYE
				AAAAFAIAAAABAwARAgUFAAgAAAACAAAAAQQAIgUCAw==
				</data>
			</dict>
		</array>
	</dict>

[Allan]

@Multisaft, stop bumping now!

 

Read our Rules: 

# Bumping of posts is not permitted. Other than being less annoying it also keeps the posts more informative.

# Only post your post once (1). This keeps the forum cleaner and makes it easier to find what you are looking for.

Your other posts in "Clover General discussion" and "Easy Yosemite 10.10 Final USB Installer" will be deleted.