Contribute
Register

Guide How to Patch AMD Framebuffers for High Sierra using Clover

Status
Not open for further replies.
Tested your templates and they work fine on my card VisionTek AMD Radeon HD 7970 updated guide. The real trick is the code construction.
The problem remains in Post #1, specifically
Now we can simplify this process by using this set based on your connectors.
LVDS 02000000 40000000 08010000 00000000 + (add your code construction) 00000000
VGA 10000000 10000000 00010000 00000000 + (add your code construction) 00000000
DP 00040000 04030000 00010000 00000000 + (add your code construction) 00000000
DVI-SL 00020000 04020000 00010000 00000000 + (add your code construction) 00000000
DVI-DL 04000000 14020000 00010000 00000000 + (add your code construction) 00000000
HDMI 00080000 00020000 00010000 00000000 + (add your code construction) 00000000

The above connector control flags change
AMD60000Controller and newer:
hdmi: 00080000 04020000 ... (i.e., Duckweed)

AMD70000Controller and newer:
lvds: 02000000 00010000 ... (i.e., Exmoor)
 
Last edited:
Sorry could have sworn I fixed that it’s fixed now thanks again
 
The problem remains in Post #1, specifically


The above connector control flags change
AMD60000Controller and newer:
hdmi: 00080000 04020000 ... (i.e., Duckweed)

AMD70000Controller and newer:
lvds: 02000000 00010000 ... (i.e., Exmoor)
Could have sworn I fixed that this morning anyhow thanks again it’s fixed now
 
Oh god, this is too much work lol. I'll just pray that clvoer devs will automate this in future clover builds. In the meantime I can boot from a clover which doesnt use UEFI...
 
Oh god, this is too much work lol.

Too much work? How? I made a template that can be used for simple patch construction in the guide. If you prefer a need to do nothing approach Apple sells Macs everyday.

I'll just pray that clvoer devs will automate this in future clover builds. In the meantime I can boot from a clover which doesnt use UEFI...

Not likely this will happen too many graphics configurations to have to test. Now I have been thinking about writing a script that will generate the patch for you, I would likely need to employ the help of folks like @toleda and @RehabMan, but time is always a struggle to find. I hardly had time to write the guide.
 
I have Intel i3-2100 built on z68 chipset with Asus 7750 from AMD.
I am running on High Sierra.

I have tried Lilu+WhateverGreen, which seems to be working, but performance is limited when it comes to games.
I noticed that I am not able to see my GPU in HWmonitor, so I decided to try the framebuffer guide.

Is this possible for HDMI connectivity?
I have tried some framebuffers from AMD7000Controller (Aji, Namako) but all of them resulted in black screen with monitor off.

These are the codes I have constructed, are they correct?
Code:
DISPLAY_PORT
12040102

HDMI-A
22050205

DVI-DL
10000304

DVI-SL
00100404
ATOM BIOS Rom:
SubsystemVendorID: 0x1043 SubsystemID: 0x0427
IOBaseAddress: 0x0000
Filename: AsusC445PI2.
BIOS Bootup Message:
683F.15.14.0.4.AS08

PCI ID: 1002:683f
Connector at index 0
Type [@offset 45600]: DisplayPort (10)
Encoder [@offset 45604]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 45684]: 0x91, OSX senseid: 0x2
Connector at index 1
Type [@offset 45610]: HDMI-A (11)
Encoder [@offset 45614]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 45711]: 0x94, OSX senseid: 0x5
Connector at index 2
Type [@offset 45620]: DVI-I (2)
Encoder [@offset 45624]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 45748]: 0x93, OSX senseid: 0x4
Connector at index 3
Type [@offset 45630]: DVI-I (2)
Encoder [@offset 45634]: INTERNAL_KLDSCP_DAC1 (0x15)
i2cid [@offset 45748]: 0x93, OSX senseid: 0x4
AsusC445PI2.:

683F.15.14.0.4.AS08

Subsystem Vendor ID: 1043
Subsystem ID: 427
Object Header Structure Size: 246
Connector Object Table Offset: 3e
Router Object Table Offset: 0
Encoder Object Table Offset: b5
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
 
I have Intel i3-2100 built on z68 chipset with Asus 7750 from AMD.
I am running on High Sierra.

I have tried Lilu+WhateverGreen, which seems to be working, but performance is limited when it comes to games.
I noticed that I am not able to see my GPU in HWmonitor, so I decided to try the framebuffer guide.

Is this possible for HDMI connectivity?
I have tried some framebuffers from AMD7000Controller (Aji, Namako) but all of them resulted in black screen with monitor off.

These are the codes I have constructed, are they correct?
Code:
DISPLAY_PORT
12040102

HDMI-A
22050205

DVI-DL
10000304

DVI-SL
00100404
ATOM BIOS Rom:
SubsystemVendorID: 0x1043 SubsystemID: 0x0427
IOBaseAddress: 0x0000
Filename: AsusC445PI2.
BIOS Bootup Message:
683F.15.14.0.4.AS08

PCI ID: 1002:683f
Connector at index 0
Type [@offset 45600]: DisplayPort (10)
Encoder [@offset 45604]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 45684]: 0x91, OSX senseid: 0x2
Connector at index 1
Type [@offset 45610]: HDMI-A (11)
Encoder [@offset 45614]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 45711]: 0x94, OSX senseid: 0x5
Connector at index 2
Type [@offset 45620]: DVI-I (2)
Encoder [@offset 45624]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 45748]: 0x93, OSX senseid: 0x4
Connector at index 3
Type [@offset 45630]: DVI-I (2)
Encoder [@offset 45634]: INTERNAL_KLDSCP_DAC1 (0x15)
i2cid [@offset 45748]: 0x93, OSX senseid: 0x4
AsusC445PI2.:

683F.15.14.0.4.AS08

Subsystem Vendor ID: 1043
Subsystem ID: 427
Object Header Structure Size: 246
Connector Object Table Offset: 3e
Router Object Table Offset: 0
Encoder Object Table Offset: b5
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
I need problem reporting files mentioned in the guide right before the credits to help you
 
If you prefer a need to do nothing approach Apple sells Macs everyday.

lol, they dont offer a product which would fit my needs. they only have all-in-ones and a ridicuously overpriced macpro... Also, there is an easy DSDT patch on the other forum, which fixes the blackscreen issue and deprecates whatevergreen, and I'm hopeful they'll add it to clover soon.

Also, DPCIManager is tagged as malware on sourceforge, so I dont have the tools to do it..
 
Last edited:
lol, they dont offer a product which would fit my needs. they only have all-in-ones and a ridicuously overpriced macpro... Also, there is an easy DSDT patch on the other forum, which fixes the blackscreen issue and deprecates whatevergreen, and I'm hopeful they'll add it to clover soon.

Also, DPCIManager is tagged as malware on sourceforge, so I dont have the tools to do it..

Yeah I've read the post you mentioned and plan on adding it to my guide, Mieze's work on that BAR2 vs BAR5 is outstanding work. I can assure you DPCIManager isn't malware it was developed by one of the Mods here at @tonymacx86 named @SJ_UnderWater who also developed MaciASL the program we use to compile our DSDTs, who also developed IOJones. Besides you get obtain your rom file from windows with GPUZ and a google search. Now I doubt Slice will be adding the DSDT patch to clover. But hey he might. The idea here isn't to be looking for quick fixes. But to learn about the OS, and how it can function on regular PC hardware. Now I ask you please don't spam my thread with nonsense. If you need help there are plenty of folks here willing to help you with this method. But we don't need to be wasting time on nonsense. All replies to this thread need to either asking for help or providing feedback with findings to improve the guide for others.
 
Status
Not open for further replies.
Back
Top