Jump to content
WarDoc

WhatEverGreen Support Topic

1,088 posts in this topic

Recommended Posts

Hey guys I managed to get my ryzen 10.12.6 working without helper card on my Msi rx 480(thanks go Gigamaxx) my only issue is that I have no acceleration (I'm not Injecting anything in graphics settings in clover) I tried different fb and when I get to the home screen it shows correct card number but only with a couple mb of VRAM. Any help I would appreciate it

Gigamaxx mentioned in a different thread that for him 10.12.6 only works if you use the AMD9510Controller and RadeonX4100 kexts from 10.12.5 with IOPCIMatch patches. I haven't tried yet so am not sure :/

 

 

Sent from my HUAWEI RIO-L02 using Tapatalk

Share this post


Link to post
Share on other sites
Advertisement

With the release of mid-2017 iMacs, Apple has used Polaris Ellesmere GPUs in its lineup.

10.12.6 include drivers for RX 470, 480, 570, and 580.

This means starting with 10.12.6 version, we don’t need to perform these kext modifications anymore?

Share this post


Link to post
Share on other sites

I've updated my Hackintosh from El Capitan to Sierra today and now I'm trying to get that dual monitor back to work.
On El Capitan I used @Vlada.'s framebuffer patching method and now I've only got little success with WhatEverGreen (one screen).
(My setup is in my signature)
 
Two screen results in loading up the os until a certain point and than black screen on both screens.
 
Here is the data I worked on for the FB patch back on El Capitan:


01 [DISPLAY_PORT]
redsock:
enc obj 0x21 txmit 0x12 duallink 0x2 enc 0x4
radeon:
Type [@offset 42556]: DisplayPort (10)
Encoder [@offset 42560]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 42648]: 0x90, OSX senseid: 0x1
 
Code construction: 12 04 01 01
 
02 [HDMI_TYPE_A]
redsock:
enc obj 0x21 txmit 0x22 duallink 0x2 enc 0x5
radeon:
Type [@offset 42566]: HDMI-A (11)
Encoder [@offset 42570]: INTERNAL_UNIPHY2 (0x21)
i2cid [@offset 42675]: 0x92, OSX senseid: 0x3
 
Code construction: 22 05 02 03
 
03 [DVI_D]
redsock:
eng obj 0x20 txmit 0x11 duallink 0x1 enc 0x2
radeon:
Type [@offset 42576]: DVI-D (3)
Encoder [@offset 42580]: INTERNAL_UNIPHY1 (0x20)
i2cid [@offset 42702]: 0x93, OSX senseid: 0x4
 
 
Code construction: 11 02 03 04
 
04 [DVI_D]
redsock:
eng obj 0x1e txmit 0x10 duallink 0x0 enc 0x0
 
radeon:
Type [@offset 42586]: DVI-D (3)
Encoder [@offset 42590]: INTERNAL_UNIPHY (0x1e)
i2cid [@offset 42729]: 0x95, OSX senseid: 0x6
 
 
Code construction: 10 00 04 06


 
Here is WhatEverGreen's debug output:


(kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo found 4 connectors
 (kernel) WhateverGreen: (DEBUG) con @ 0 is type 00000400 (DP  ) flags 00000304 feat 0100 pri 0000 txmit 12 enc 04 hotplug 02 sense 01
 (kernel) WhateverGreen: (DEBUG) con @ 1 is type 00000800 (HDMI) flags 00000204 feat 0100 pri 0000 txmit 22 enc 05 hotplug 03 sense 03
 (kernel) WhateverGreen: (DEBUG) con @ 2 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 01 enc 02 hotplug 01 sense 04
 (kernel) WhateverGreen: (DEBUG) con @ 3 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 00 enc 00 hotplug 06 sense 06
 (kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo attempting to autofix connectors
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 12 enc 04 sense 01 for 0 connector
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector found unsupported connector type 13
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 22 enc 05 sense 03 for 1 connector
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector found unsupported connector type 0C
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 11 enc 02 sense 04 for 2 connector
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector replacing txmit 01 with 11 for 2 connector sense 04
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 10 enc 00 sense 06 for 3 connector
 (kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector replacing txmit 00 with 10 for 3 connector sense 06
 (kernel) WhateverGreen: (DEBUG) rad @ getConnectorInfo leaving unchaged priority
 (kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo resulting 4 connectors follow
 (kernel) WhateverGreen: (DEBUG) con @ 0 is type 00000400 (DP  ) flags 00000304 feat 0100 pri 0000 txmit 12 enc 04 hotplug 02 sense 01
 (kernel) WhateverGreen: (DEBUG) con @ 1 is type 00000800 (HDMI) flags 00000204 feat 0100 pri 0000 txmit 22 enc 05 hotplug 03 sense 03
 (kernel) WhateverGreen: (DEBUG) con @ 2 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 11 enc 02 hotplug 01 sense 04
 (kernel) WhateverGreen: (DEBUG) con @ 3 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 10 enc 00 hotplug 06 sense 06
 (kernel) WhateverGreen: (DEBUG) rad @ SetProperty caught model 19 (AMD Radeon HD 8xxx)
 (kernel) WhateverGreen: (DEBUG) util @ getOSData vendor-id has 1002 value
 (kernel) WhateverGreen: (DEBUG) util @ getOSData device-id has 67B0 value
 (kernel) WhateverGreen: (DEBUG) util @ getOSData revision-id has 80 value
 (kernel) WhateverGreen: (DEBUG) util @ getOSData subsystem-vendor-id has 1462 value
 (kernel) WhateverGreen: (DEBUG) util @ getOSData subsystem-id has 2015 value
 (kernel) WhateverGreen: (DEBUG) rad @ SetProperty autodetect found for 1002:67B0:0080 1462:2015
 (kernel) WhateverGreen: (DEBUG) rad @ SetProperty autodetect found AMD Radeon R9 390X


 
The result:
 

                               DP                      HDMI                  DVI_D                 DVI_D    
Data read               12 04 02 01        22 05 03 03        01 02 01 04        00 00 06 06
Data corrected        12 04 02 01        22 05 03 03        11 02 01 04        10 00 06 06
Data worked out     12 04 01 01        22 05 02 03        11 02 03 04        10 00 04 06
 

As it's only the hot plug id that changed it could depend on that. Has anyone an idea how to get my R9 390x to work with both screens? (both on DVI)

Any help would be appreciated :)

 

EDIT: is there a way to inject the proper connector data via clover?

Share this post


Link to post
Share on other sites

I've updated my Hackintosh from El Capitan to Sierra today and now I'm trying to get that dual monitor back to work.

On El Capitan I used @Vlada.'s framebuffer patching method and now I've only got little success with WhatEverGreen (one screen).

(My setup is in my signature)

 

Two screen results in loading up the os until a certain point and than black screen on both screens.

 

Here is the data I worked on for the FB patch back on El Capitan:

 

 

01 [DISPLAY_PORT]

redsock:

enc obj 0x21 txmit 0x12 duallink 0x2 enc 0x4

radeon:

Type [@offset 42556]: DisplayPort (10)

Encoder [@offset 42560]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 42648]: 0x90, OSX senseid: 0x1

 

Code construction: 12 04 01 01

 

02 [HDMI_TYPE_A]

redsock:

enc obj 0x21 txmit 0x22 duallink 0x2 enc 0x5

radeon:

Type [@offset 42566]: HDMI-A (11)

Encoder [@offset 42570]: INTERNAL_UNIPHY2 (0x21)

i2cid [@offset 42675]: 0x92, OSX senseid: 0x3

 

Code construction: 22 05 02 03

 

03 [DVI_D]

redsock:

eng obj 0x20 txmit 0x11 duallink 0x1 enc 0x2

radeon:

Type [@offset 42576]: DVI-D (3)

Encoder [@offset 42580]: INTERNAL_UNIPHY1 (0x20)

i2cid [@offset 42702]: 0x93, OSX senseid: 0x4

 

 

Code construction: 11 02 03 04

 

04 [DVI_D]

redsock:

eng obj 0x1e txmit 0x10 duallink 0x0 enc 0x0

 

radeon:

Type [@offset 42586]: DVI-D (3)

Encoder [@offset 42590]: INTERNAL_UNIPHY (0x1e)

i2cid [@offset 42729]: 0x95, OSX senseid: 0x6

 

 

Code construction: 10 00 04 06

 

 

 

Here is WhatEverGreen's debug output:

 

 

(kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo found 4 connectors

(kernel) WhateverGreen: (DEBUG) con @ 0 is type 00000400 (DP ) flags 00000304 feat 0100 pri 0000 txmit 12 enc 04 hotplug 02 sense 01

(kernel) WhateverGreen: (DEBUG) con @ 1 is type 00000800 (HDMI) flags 00000204 feat 0100 pri 0000 txmit 22 enc 05 hotplug 03 sense 03

(kernel) WhateverGreen: (DEBUG) con @ 2 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 01 enc 02 hotplug 01 sense 04

(kernel) WhateverGreen: (DEBUG) con @ 3 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 00 enc 00 hotplug 06 sense 06

(kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo attempting to autofix connectors

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 12 enc 04 sense 01 for 0 connector

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector found unsupported connector type 13

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 22 enc 05 sense 03 for 1 connector

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector found unsupported connector type 0C

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 11 enc 02 sense 04 for 2 connector

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector replacing txmit 01 with 11 for 2 connector sense 04

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnectors found txmit 10 enc 00 sense 06 for 3 connector

(kernel) WhateverGreen: (DEBUG) rad @ autocorrectConnector replacing txmit 00 with 10 for 3 connector sense 06

(kernel) WhateverGreen: (DEBUG) rad @ getConnectorInfo leaving unchaged priority

(kernel) WhateverGreen: (DEBUG) rad @ getConnectorsInfo resulting 4 connectors follow

(kernel) WhateverGreen: (DEBUG) con @ 0 is type 00000400 (DP ) flags 00000304 feat 0100 pri 0000 txmit 12 enc 04 hotplug 02 sense 01

(kernel) WhateverGreen: (DEBUG) con @ 1 is type 00000800 (HDMI) flags 00000204 feat 0100 pri 0000 txmit 22 enc 05 hotplug 03 sense 03

(kernel) WhateverGreen: (DEBUG) con @ 2 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 11 enc 02 hotplug 01 sense 04

(kernel) WhateverGreen: (DEBUG) con @ 3 is type 00000004 (DVI ) flags 00000004 feat 0100 pri 0000 txmit 10 enc 00 hotplug 06 sense 06

(kernel) WhateverGreen: (DEBUG) rad @ SetProperty caught model 19 (AMD Radeon HD 8xxx)

(kernel) WhateverGreen: (DEBUG) util @ getOSData vendor-id has 1002 value

(kernel) WhateverGreen: (DEBUG) util @ getOSData device-id has 67B0 value

(kernel) WhateverGreen: (DEBUG) util @ getOSData revision-id has 80 value

(kernel) WhateverGreen: (DEBUG) util @ getOSData subsystem-vendor-id has 1462 value

(kernel) WhateverGreen: (DEBUG) util @ getOSData subsystem-id has 2015 value

(kernel) WhateverGreen: (DEBUG) rad @ SetProperty autodetect found for 1002:67B0:0080 1462:2015

(kernel) WhateverGreen: (DEBUG) rad @ SetProperty autodetect found AMD Radeon R9 390X

 

 

 

The result:

 

 

DP HDMI DVI_D DVI_D

Data read 12 04 02 01 22 05 03 03 01 02 01 04 00 00 06 06

Data corrected 12 04 02 01 22 05 03 03 11 02 01 04 10 00 06 06

Data worked out 12 04 01 01 22 05 02 03 11 02 03 04 10 00 04 06

 

 

As it's only the hot plug id that changed it could depend on that. Has anyone an idea how to get my R9 390x to work with both screens? (both on DVI)

Any help would be appreciated :)

 

EDIT: is there a way to inject the proper connector data via clover?

inject via 48bit hex with a ssdt

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

What has the hex to look like? How do I get to 48 byte?

And for the ssdt injection, can I work with the sample on the WhateverGreen Github project? (There are 64 bytes in the connector thing)

How do I compile and "use" that ssdt?

 

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20140926-64 [Oct 24 2014]
 * Copyright (c) 2000 - 2014 Intel Corporation
 * 
 * Disassembly of iASLfBeIhA.aml, Fri Aug 18 14:40:51 2017
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x0000011E (286)
 *     Revision         0x02
 *     Checksum         0x9F
 *     OEM ID           "APPLE "
 *     OEM Table ID     "SSDTAMDG"
 *     OEM Revision     0x00001000 (4096)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20140926 (538183974)
 */
DefinitionBlock ("iASLfBeIhA.aml", "SSDT", 2, "APPLE ", "SSDTAMDG", 0x00001000)
{

    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.PEG0, DeviceObj)
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB.PCI0)
    {
        Scope (PEG0)
        {
            Scope (PEGP)
            {
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x06)
                        {
                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "connectors", 
                            Buffer (0x40)
                            {
                                0x00, 0x08, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x02, 0x03,
                                0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00,
                                0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x01, 0x01,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x03, 0x00, 0x11, 0x02, 0x03, 0x04,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x04, 0x01, 0x10, 0x00, 0x04, 0x06
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
        }

        Method (DTGP, 5, NotSerialized)
        {
            If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")))
            {
                If (LEqual (Arg1, One))
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Store (Buffer (One)
                            {
                                 0x03
                            }, Arg4)
                        Return (One)
                    }

                    If (LEqual (Arg2, One))
                    {
                        Return (One)
                    }
                }
            }

            Store (Buffer (One)
                {
                     0x00
                }, Arg4)
            Return (Zero)
        }
    }
}

00 08 00 00 00 02 00 00 00 01 02 00 22 05 02 03

00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01

04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 04

04 00 00 00 14 02 00 00 00 01 04 01 10 00 04 06

 

For whatever reason one and three screens (DP, DVI, DVI) work, but two don't.

 

EDIT: I figured out everything and the ssdt patch from above works with two screens :)

Share this post


Link to post
Share on other sites

Hi,

 

Can you please post the compiled SSDT so i can try with my card? It has the exact same connectors (R9 290).

 

What has the hex to look like? How do I get to 48 byte?
And for the ssdt injection, can I work with the sample on the WhateverGreen Github project? (There are 64 bytes in the connector thing)
How do I compile and "use" that ssdt?
 

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20140926-64 [Oct 24 2014]
 * Copyright (c) 2000 - 2014 Intel Corporation
 * 
 * Disassembly of iASLfBeIhA.aml, Fri Aug 18 14:40:51 2017
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x0000011E (286)
 *     Revision         0x02
 *     Checksum         0x9F
 *     OEM ID           "APPLE "
 *     OEM Table ID     "SSDTAMDG"
 *     OEM Revision     0x00001000 (4096)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20140926 (538183974)
 */
DefinitionBlock ("iASLfBeIhA.aml", "SSDT", 2, "APPLE ", "SSDTAMDG", 0x00001000)
{

    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.PEG0, DeviceObj)
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB.PCI0)
    {
        Scope (PEG0)
        {
            Scope (PEGP)
            {
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x06)
                        {
                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "connectors", 
                            Buffer (0x40)
                            {
                                0x00, 0x08, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x02, 0x03,
                                0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00,
                                0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x01, 0x01,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x03, 0x00, 0x11, 0x02, 0x03, 0x04,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x04, 0x01, 0x10, 0x00, 0x04, 0x06
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
        }

        Method (DTGP, 5, NotSerialized)
        {
            If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")))
            {
                If (LEqual (Arg1, One))
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Store (Buffer (One)
                            {
                                 0x03
                            }, Arg4)
                        Return (One)
                    }

                    If (LEqual (Arg2, One))
                    {
                        Return (One)
                    }
                }
            }

            Store (Buffer (One)
                {
                     0x00
                }, Arg4)
            Return (Zero)
        }
    }
}

00 08 00 00 00 02 00 00 00 01 02 00 22 05 02 03
00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01
04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 04
04 00 00 00 14 02 00 00 00 01 04 01 10 00 04 06

For whatever reason one and three screens (DP, DVI, DVI) work, but two don't.

EDIT: I figured out everything and the ssdt patch from above works with two screens :)

 

Share this post


Link to post
Share on other sites

What has the hex to look like? How do I get to 48 byte?

And for the ssdt injection, can I work with the sample on the WhateverGreen Github project? (There are 64 bytes in the connector thing)

How do I compile and "use" that ssdt?

 

 

/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20140926-64 [Oct 24 2014]
 * Copyright (c) 2000 - 2014 Intel Corporation
 * 
 * Disassembly of iASLfBeIhA.aml, Fri Aug 18 14:40:51 2017
 *
 * Original Table Header:
 *     Signature        "SSDT"
 *     Length           0x0000011E (286)
 *     Revision         0x02
 *     Checksum         0x9F
 *     OEM ID           "APPLE "
 *     OEM Table ID     "SSDTAMDG"
 *     OEM Revision     0x00001000 (4096)
 *     Compiler ID      "INTL"
 *     Compiler Version 0x20140926 (538183974)
 */
DefinitionBlock ("iASLfBeIhA.aml", "SSDT", 2, "APPLE ", "SSDTAMDG", 0x00001000)
{

    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.PEG0, DeviceObj)
    External (_SB_.PCI0.PEG0.PEGP, DeviceObj)

    Scope (\_SB.PCI0)
    {
        Scope (PEG0)
        {
            Scope (PEGP)
            {
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x06)
                        {
                            "AAPL,slot-name", 
                            Buffer (0x07)
                            {
                                "Slot-1"
                            }, 

                            "@0,AAPL,boot-display", 
                            Buffer (Zero) {}, 
                            "connectors", 
                            Buffer (0x40)
                            {
                                0x00, 0x08, 0x00, 0x00, 0x00, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x02, 0x00, 0x22, 0x05, 0x02, 0x03,
                                0x00, 0x04, 0x00, 0x00, 0x04, 0x03, 0x00, 0x00,
                                0x00, 0x01, 0x01, 0x01, 0x12, 0x04, 0x01, 0x01,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x03, 0x00, 0x11, 0x02, 0x03, 0x04,
                                0x04, 0x00, 0x00, 0x00, 0x14, 0x02, 0x00, 0x00,
                                0x00, 0x01, 0x04, 0x01, 0x10, 0x00, 0x04, 0x06
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }
        }

        Method (DTGP, 5, NotSerialized)
        {
            If (LEqual (Arg0, ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b")))
            {
                If (LEqual (Arg1, One))
                {
                    If (LEqual (Arg2, Zero))
                    {
                        Store (Buffer (One)
                            {
                                 0x03
                            }, Arg4)
                        Return (One)
                    }

                    If (LEqual (Arg2, One))
                    {
                        Return (One)
                    }
                }
            }

            Store (Buffer (One)
                {
                     0x00
                }, Arg4)
            Return (Zero)
        }
    }
}

00 08 00 00 00 02 00 00 00 01 02 00 22 05 02 03

00 04 00 00 04 03 00 00 00 01 01 01 12 04 01 01

04 00 00 00 14 02 00 00 00 01 03 00 11 02 03 04

04 00 00 00 14 02 00 00 00 01 04 01 10 00 04 06

 

For whatever reason one and three screens (DP, DVI, DVI) work, but two don't.

 

EDIT: I figured out everything and the ssdt patch from above works with two screens :)

please post he ssdt I will add it to the first post for 390x users

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Once again a big hand for everyone who has been involved, and made this fantastic hack available!! 

macOS Sierra 10.12.6 AMD Fury STILL working fine.

I have been using since the beginning of WhatEverGreen.Kext when it was released!

Sleep mode, and everything else is working as it should be,Yeah!

 

However, any word about And Fury support for High Sierra?

Its booting fine, but there is no metal support and acceleration.

it's very strange that  AMD9300Controller.kext (which have all ready Fury support 0x73001002) is loading, but actually do nothing to act!

Have tried all ready ForceKextsToLoad 9300.kext and also AMDRadeonX4150.kext, AMDRadeonX4200.kext and AMDRadeonX4250.kext 7300 buffin modification with no luck!

 

Any clue to start digging at!

 

Or whether we have to wait for future HS releases for any support Fury?

Share this post


Link to post
Share on other sites

Once again a big hand for everyone who has been involved, and made this fantastic hack available!! I

macOS Sierra 10.12.6 AMD Fury STILL working fine.

I have been using since the beginning of WhatEverGreen.Kext when it was released!

Sleep mode, and everything else is working as it should be,Yeah!

 

However, any word about And Fury support for High Sierra?

Its booting fine, but there is no metal support and acceleration.

it's very strange that AMD9300Controller.kext (which have all ready Fury support 0x73001002) is loading, but actually do nothing to act!

Have tried all ready ForceKextsToLoad 9300.kext and also AMDRadeonX4150.kext, AMDRadeonX4200.kext and AMDRadeonX4250.kext 7300 buffin modification with no luck!

Any clue to start digging at!

-radbeta -lilubeta -liluforce add that to config

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

-radbeta -lilubeta -liluforce add that to config

 

 

Sent from my iPhone using Tapatalk

Thanks a lot WarDoc, for a quick reply!! 

I get back to you tomorrow when i'm back to machine.

Share this post


Link to post
Share on other sites

Useless bootargs. Lilu and plugins already have HS support...

weird then why does it not work on b6 without those flags

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

weird then why does it not work on b6 without those flags

 

I don't know. For me Lilu and Plugins in 10.13b6 works fine without any bootargs! Maybe it's because you place those kexts in S/L/E or L/E instead of placing them in EFI/Clover/Kexts/Other where they HAVE TO BE? Stable work of Lilu and plugins guaranteed ONLY if you inject them with bootloader. If lilu and plugins are in kernel cache they behaviour become unpredictable. And if you have Lilu and plugins in S/L/E or L/E and in EFI/Clover/Kexts/Other in the same time...  :drool:  :hysterical: Well... it could be anything in this case. Placing kexts in S/L/E or L/E is obsolete ton*mac legacy. Especially on systems with SIP!

Share this post


Link to post
Share on other sites

I don't know. For me Lilu and Plugins in 10.13b6 works fine without any bootargs! Maybe it's because you place those kexts in S/L/E or L/E instead of placing them in EFI/Clover/Kexts/Other where they HAVE TO BE? Stable work of Lilu and plugins guaranteed ONLY if you inject them with bootloader. If lilu and plugins are in kernel cache they behaviour become unpredictable. And if you have Lilu and plugins in S/L/E or L/E and in EFI/Clover/Kexts/Other in the same time...  :drool:  :hysterical: Well... it could be anything in this case. Placing kexts in S/L/E or L/E is obsolete ton*mac legacy. Especially on systems with SIP!

Thanks for good tips! In fact everything you mention here, is in the 'read me section' Right? 

Anyway will get back tomorrow and report how it goes.

Thanks in advance!

You guys rock!

Share this post


Link to post
Share on other sites

I don't know. For me Lilu and Plugins in 10.13b6 works fine without any bootargs! Maybe it's because you place those kexts in S/L/E or L/E instead of placing them in EFI/Clover/Kexts/Other where they HAVE TO BE? Stable work of Lilu and plugins guaranteed ONLY if you inject them with bootloader. If lilu and plugins are in kernel cache they behaviour become unpredictable. And if you have Lilu and plugins in S/L/E or L/E and in EFI/Clover/Kexts/Other in the same time... :drool::hysterical: Well... it could be anything in this case. Placing kexts in S/L/E or L/E is obsolete ton*mac legacy. Especially on systems with SIP!

no one uses s/l/e lol crazy to even think it haha

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

lets not argue with the dev please we all know that some users will always use s/l/e

Share this post


Link to post
Share on other sites

lets not argue with the dev please we all know that some users will always use s/l/e

those are not users those are tonymac people

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

I don't know. For me Lilu and Plugins in 10.13b6 works fine without any bootargs! Maybe it's because you place those kexts in S/L/E or L/E instead of placing them in EFI/Clover/Kexts/Other where they HAVE TO BE? Stable work of Lilu and plugins guaranteed ONLY if you inject them with bootloader. If lilu and plugins are in kernel cache they behaviour become unpredictable. And if you have Lilu and plugins in S/L/E or L/E and in EFI/Clover/Kexts/Other in the same time...  :drool:  :hysterical: Well... it could be anything in this case. Placing kexts in S/L/E or L/E is obsolete ton*mac legacy. Especially on systems with SIP!

Hi,

Sorry still missing AMD Fury Metal acceleration HS 10.13 b6. 

I also checked that I was not accidentally but Lilu or WhatEverGreen kext to S/L/E or S/L. So everything is as it should be at E/C/K/O

 

Also check boot arguments!

No go!

Any suggestions?

Thanks!

Share this post


Link to post
Share on other sites

 

Hi,

Sorry still missing AMD Fury Metal acceleration HS 10.13 b6. 

I also checked that I was not accidentally but Lilu or WhatEverGreen kext to S/L/E or S/L. So everything is as it should be at E/C/K/O

 

Also check boot arguments!

No go!

Any suggestions?

Thanks!

 

 

Sorry. No suggestions for beta macOS versions. Try to get acceleration without WhateverGreen and with helper card (IGFX primary and CSM enabled).

Share this post


Link to post
Share on other sites

Sorry. No suggestions for beta macOS versions. Try to get acceleration without WhateverGreen and with helper card (IGFX primary and CSM enabled).

I forgot to mention that my IGP IntelHD 530 Is working without problems, ever since HS b1 was release.

 

Just wondering how it may be possible that Fury ’driver’ exists, but no not recognize acceleration?

Share this post


Link to post
Share on other sites

The AMD driver crashes and spits a backtrace to the system message buffer if i have more than one monitor plugged in while booting. I can get two monitors (three doesn't work) if i boot with one connected to DVI then plug another one to DP or HDMI. Hopefully High Sierra works better.

 

Ps.: I have a Hawaii card.

Share this post


Link to post
Share on other sites

The AMD driver crashes and spits a backtrace to the system message buffer if i have more than one monitor plugged in while booting. I can get two monitors (three doesn't work) if i boot with one connected to DVI then plug another one to DP or HDMI. Hopefully High Sierra works better.

 

Ps.: I have a Hawaii card.

according to the devs that’s how everything should work but sadly most of us have the same issue 3 monitors don’t work period and we need 1 screen to boot and to plug another In after

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

If any help with this?

Cheers!

https://www.sendspace.com/file/ec6cl6

In HS it's that 9300 controller that prevents the kext patches we used in Sierra. And they still haven't included the kexts similar to the Vega for the fury / nano.

In the end I gave up and bought a Vega. Works great.

I tried deleting the 9300 controller kext and using the old patches. Might have promise for someone less noob than me.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By MaLd0n
      ---TUTORIAL---

      https://olarila.com/forum/viewtopic.php?f=50&t=8685
       
      --Original Post--
       
      https://olarila.com/forum/viewtopic.php?f=97&t=11237
       
      --Bios/UEFI Settings--
       
      *Update bios/uefi to F7+*
      1- Go to M.I.T./Advanced Frequency Settings tab
       
      Extreme Memory Profile (X.M.P.) - Profile 1
       
      2- Go to BIOS tab
       
      CSM Support - Disabled
       
      3- Go to Peripherals/Thunderbolt(TM) Configuration tab
       
      Security Level - No Security
      Thunderbolt USB Support - Enabled
      GPIO3 Force Pwr - Enabled
       
      4- Go to Chipset tab
       
      Internal Graphics - Enable
       
      ---CLOVER FOLDER---
      https://olarila.com/forum/download/file.php?id=25033
      *Use this folder with FULL DSDT PATCHED
       
      ---OPENCORE FOLDER---
      https://olarila.com/forum/download/file.php?id=24376
      *Use this folder with FULL DSDT PATCHED
       
       
      ---Extract one Full dump for DSDT edits, post files---
       
      RunMe.app
       
       
       
      ---HARDWARE---
       
      --MOBO

      GIGABYTE Z390 DESIGNARE
      -Link
      https://www.amazon.com/Z390-DESIGNARE-Gigabyte-Thunderbolt-Motherboard/dp/B07K8RJZRG/ref=sr_1_1?keywords=Z390+DESIGNARE&qid=1565492390&s=electronics&sr=1-1

      --PROCESSOR

      Intel Core i9-9900K
      -Link
      https://www.amazon.com/Intel-i9-9900K-Desktop-Processor-Unlocked/dp/B005404P9I/ref=sr_1_1_sspa?keywords=Intel+Core+i9-9900K&qid=1553358099&s=gateway&sr=8-1-spons&psc=1

      --COOLER

      CORSAIR H100i RGB PLATINUM AIO Liquid CPU Cooler
      -Link
      https://www.amazon.com/CORSAIR-H100i-PLATINUM-Liquid-Cooler/dp/B07JWB5BSN/ref=sr_1_4?keywords=WATER+COOLER+CPU&qid=1565492509&s=gateway&sr=8-4

      --MEMORY

      Corsair CMW32GX4M2C3200C16 Vengeance RGB PRO 32GB (2x16GB) DDR4 3200 (PC4-25600)
      -Link
      https://www.amazon.com/Corsair-CMW32GX4M2C3200C16-Vengeance-PC4-25600-Desktop/dp/B07GTG2T7L/ref=sr_1_15?keywords=memory+ddr4+32&qid=1553358238&s=gateway&sr=8-15

      --GPU

      MSI RX Vega 64 AIR Boost 8G OC
      -Link
      https://www.amazon.com/MSI-RX-64-AIR-8G/dp/B07DH7S1X1/ref=sr_1_2?keywords=vega+64+gigabyte&qid=1565492819&s=electronics&sr=1-2

      --SSD

      Samsung 970 EVO 1TB SSD (MZ-V7E1T0BW) NVMe M.2 V-NAND
      -Link
      https://www.amazon.com/Samsung-970-EVO-1TB-MZ-V7E1T0BW/dp/B07BN217QG/ref=sr_1_1?keywords=s+samsung+970+evo+1tb&qid=1565493002&s=electronics&sr=1-1

      --POWER SUPPLY

      EVGA Supernova 1000 P2 80+ Platinum, 1000W ECO Mode Fully Modular 
      -Link
      https://www.amazon.com/EVGA-Supernova-Platinum-Crossfire-220-P2-1000-XR/dp/B00EKJQM5E/ref=sr_1_3?keywords=power+supply+1000w&qid=1565493196&s=gateway&sr=8-3

      --WIRELESS

      TP-Link Archer T9E
      -Link
      https://www.amazon.com/TP-Link-Archer-T9E-Beamforming-Technology/dp/B00TQEX7AQ/ref=sr_1_1?keywords=TP-Link+Archer+T9E&qid=1553358397&s=gateway&sr=8-1

      --CASE

      Thermaltake Core P5 Tempered Glass Black Edition ATX Open Frame Panoramic Viewing
      -Link
      https://www.amazon.com/Thermaltake-Tempered-Panoramic-Certified-CA-1E7-00M1WN-03/dp/B01N4IGVSC/ref=sr_1_2?keywords=Thermaltake+Core+P5&qid=1565493567&s=gateway&sr=8-2

      --DSDT Patches--
      -FIX ACPI ERRORS -FIX OEM SSDTs to AVOID ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA -DMAC -REMOVE PROBLEMATIC AND UNUSED DEVICES -FIX K.P in REBOOT -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -FWHD -USBX -PMCR -PPMC -XSPI -CNVW -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES ---SCREENSHOTs---




















      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Thanks to KGP for SSDT Thunderbolt
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By ludufre
      Installing macOS Mojave 10.14.6 on Gigabyte Z370N WIFI + i7 8700K + UHD 630



      Changelog:
       
      09/01/2019 15:57h GMT-0
      - Updated to 10.14.6.
       
      06/10/2019 00:44h GMT-0
      - Completely rewritten.
       
      10/17/2018 08:12h GMT-0
      - Fix Kexts permissions commands adjusted.
      - Removed FrameBuffer patch that is not needed.
      - Added audio solution and HDMI.
      - Unfortunately DisplayPort does not work.
      - Replaced Wifi/BT with DW1560 (BCM94352Z)
       
      10/11/2018 04:15h GMT-0
      - Added USB 3.0 patch.
      - Adjusted some steps.
      - Changed text formatting.
       
      10/11/2018 03:42h GMT-0
      - Added missing UEFI configuration.
       
      10/07/2018 00:36h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i7-8700K ->  Work. All SpeedStep stages.
      - Video Card: Intel UHD 630 ->  Work. QE/CI and Metal.
      - Chipset: Intel Z370 ->  Work.
      - HDMI 2.0 (1st) ->  Work.
      - HDMI (2nd) ->  Work.
      - DP ->  Not tested yet.
      - Audio: ALC1220 ->  Work.
      - HDMI Audio ->  Work.
      - WiFi/Bluetooth ->  Not work. Replaced with BCM94360CS2.
      - Ethernet (1st) ->  Work.
      - Ethernet (2nd) ->  Work.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Todo
       
      - Make audio work.
      - Make HDMI audio work.
      - Test DisplayPort.
      - Make second ethernet work.
      - Replace Wifi/Bluetooth.
      - Test DP.
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover Configurator
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes. / 8 minutes with USB 3.0
       
       

      Install bootloader

      Download the CloverEFI (used 5058, from Automated Clover Builds) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - Recommended drivers (check all)
      - UEFI Drivers - Human Interface Devices (check all)
      - UEFI Drivers - FileVault 2 UEFI Drivers (check all, If you are going to use FileVault)
      - UEFI Drivers - Additional drivers - NvmExpressDxe (if you are going to use NVMe)


       
       
      Make things works
       
      We'll make a full working flash drive, so follow these instructions:
       
      Will be mounted the EFI partition of the flash drive.
       
      Open the the /Volumes/EFI/CLOVER/config.plist inside this new partition with Clover Configurator (used 5.5.0.0)
       
      Important modifications
       
      config.plist
       
      ACPI Page
       
      - Check: SSDT - PluginType
       
      BOOT Page
       
      - Add: Arguments - darkwake=2
      - Check: Legacy - XMPDetection=Yes
       
      KERNEL AND KEXT PATCHES Page
       
      - Check: KernelPm
       
      RT VARIABLES Page
       
      - Change: CsrActiveConfig - 0x3E7
       
      SMBIOS Page
       
      - Change: Macmini8,1 - Mac mini (Late 2018) | Intel Core i7-8700B @ 3.20 GHz

       
      - Click: Generate New (few times in the two buttons)

       
       
      Need some Kexts in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext, ITEIT87x.kext and IntelCPUMonitor.kext inside of DMG version r240.
      - Download the Lilu.kext from here. I used the version 1.3.8.

       
      Intel UHD 630
       
      ACPI Page
      - Uncheck: Fixes - AddHDMI
      - Uncheck: Fixes - FixDisplay
      - Uncheck: Fixes - FixHDA
       
      GUI Page
      - Change: Screen Resolution - 3840x2160 (My monitor is 4K)

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the WhateverGreen.kext from here. I used the version 1.3.1.

       
      Audio ALC 1220 and HDMI audio

      BOOT Page
      - Add: Arguments - alcid=11

      DEVICES Page
      - Change: Audio - Inject - 11
      - Uncheck: Audio - AFGLowPowerState
      - Uncheck: Audio - ResetHDA

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the AppleALC.kext from here. I used the version 1.4.0.

       
      All USBs (2.0, 3.0, Type-C, internal)
       
      KERNEL AND KEXT PATCHES Page - KextsToPatch
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 1 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 2 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 3 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FF0F0F
      - Replace* [HEX]: 83FF3F0F
      - Comment: USB Port Limit Patch 4 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
       
      Need SSDT patch in the folder /EFI/CLOVER/ACPI/patched/
       
      - Download the SSDT-EC.aml, SSDT-UIAC.aml and SSDT-USBX attached bellow.
       
      Wifi and Bluetooth (BCM94360CS)
       
      Works out of box (plug 'n' play).
       
       
      LAN Cards
       
      Need a Kext for feach card in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the IntelMausiEthrenet.kext from here. I used the version 2018-1031.
      - Download the SmallTreeIntel82576.kext attached bellow. I do not remember where I found it.

       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      - Shutdown and insert the flash.
      - Power on with DEL pressed to enter BIOS setup.
      - Change value: Periphelrals - Initial Display to IGP
      - Change value: Periphelrals - USB Configuration - XHCI Hand-off to ENABLE
      - Change value: Chipset - VT-d to DISABLE
      - Change value: Chipset - Internal Graphics to ENABLE
      - Change value: Chipset - DVMT Pre-Allocated to 128M
      - Save & Exit Setup
       
      - Now, hold the F12
      - In the list, select your flash drive.
      - It will show twice. One with UEFI prefix and another without.
      - Select with UEFI prefix. Ie.: "UEFI: Sandisk Cruzer"
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "HD".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.6
       
      - Download and open latest CloverConfigurator
      - Open Mount EFI and click in Mount Partition in EFI Partitions list
      - Click in Open Partition that appears
      - Go to EFI -> CLOVER
      - Backup config.plist and ACPI folder to desktop
      - Go back and delete CLOVER folder
      (If you restart now you can't boot in macOS - DON'T RESTART)
      - Download latest Clover and install (link and config above)
      - Replace config.plist and ACPI folder from your desktop
       
      - Update Lilu.kext, AppleALC.kext, WhateverGreen.kext, HWSensors kexts (FakeSMC, ACPIMonitor, IntelCPUMonitor, ITEIT87x) in /Library/Extensions/
      - Run:
       
      sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i /  
       
      - Install macOS Update 10.14.6 and restart
       

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
       
       
       
      Z370N-WIFI v2.zip
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil IGPU = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Adjusting the brightness on a laptop
      1. Method 1
      Enable Clover DSDT fix AddPNLF. Enable SetIntelBacklight and SetIntelMaxBacklight. A specific value is not necessary - it will be automatically injected according to the processor installed.
      2. Method 2
      Use this ACPI table: SSDT-PNLF.dsl SSDT-PNLF.aml
      Do not use both methods at the same time!
       
      Digital Audio (HDMI / DVI / DP)
      To enable digital audio it is necessary to set the necessary properties and, usually, patch the connectors.
      To enable audio in general and HDMI in particular use WEG along with AppleALC.kext.
      On 10.10.5 and above, WEG automatically changes the connector-type of DP (00040000) to HDMI (00080000) if no custom patches are used.
      The actual connection may be of any type (HDMI / DVI / DP), but for the digital audio to function the connector-type must explicitly be HDMI.
       
      VGA support
      In most cases with Intel Skylake and newer it works by default.
      For Ivy Bridge and possibly other generations there are the options to patch your connectors with the following:
      06020000 02000000 30000000 // Option 1
      06020000 01000000 30000000 // Option 2
      On OS X 10.8.2 and newer it is impossible to have VGA on Ivy Bridge systems.
      Hot-plugging VGA usually does not work.
      In case this doesn't help - there are no other known solutions at this time.
       
      EDID
      EDID is usually correctly identified, so no actions are required. In rare cases, EDID needs to be injected manually.
      An EDID dump can be obtained, for example, with Linux. The correct EDID must be put into *AAPL00,override-no-connect* property for IGPU, where the second 0 stands for the display number.
      In some cases the EDID dump may be incompatible with macOS and leads to distortions. For some EDID in such cases you can use this script, which corrects a provided EDID and saves it to your desktop.
       
      HDMI in UHD resolution with 60 fps
      Add the enable-hdmi20 property to IGPU, otherwise you will get a black screen. Or instead of this property use the boot-arg -cdfon
       
      Disablng a discrete graphics card
      Add the disable-external-gpu property to IGPU. Or instead of this property, use the boot-arg -wegnoegpu
       
      Fix the invalid maximum link rate issue on some laptops (Dell XPS 15 9570, etc.)
      Add the enable-dpcd-max-link-rate-fix property to IGPU, otherwise a kernel panic would happen due to a division-by-zero. Or instead of this property, use the boot-arg -igfxmlr.
      You could also manually specify a maximum link rate value via the dpcd-max-link-rate for the builtin display.
      Typically use 0x14 for 4K display and 0x0A for 1080p display. All possible values are 0x06 (RBR), 0x0A (HBR), 0x14 (HBR2) and 0x1E (HBR3). If an invalid value is specified, the default value 0x14 will be used instead. If this property is not specified, same as above.  
      Fix the infinite loop on establishing Intel HDMI connections with a higher pixel clock rate on Skylake, Kaby Lake and Coffee Lake platforms
      Add the enable-hdmi-dividers-fix property to IGPU or use the -igfxhdmidivs boot argument instead to fix the infinite loop when the graphics driver tries to establish a HDMI connection with a higher pixel clock rate, for example connecting to a 2K/4K display with HDMI 1.4, otherwise the system just hangs (and your builtin laptop display remains black) when you plug in the HDMI cable.  
      1. General Notes
      For those who want to have "limited" 2K/4K experience (i.e. 2K@59Hz or 4K@30Hz) with their HDMI 1.4 port, you might find this fix helpful. For those who have a laptop or PC with HDMI 2.0 routed to IGPU and have HDMI output issues, please note that this fix is now succeeded by the LSPCON driver solution, and it is still recommended to enable the LSPCON driver support to have full HDMI 2.0 experience.  
      (You might still need this fix temporarily to figure out the connector index of your HDMI port. See the LSPCON section below.)
      LSPCON driver support to enable DisplayPort to HDMI 2.0 output on IGPU
      1. Brief Introduction
      Recent laptops (Kaby Lake/Coffee Lake-based) are typically equipped with a HDMI 2.0 port. This port could be either routed to IGPU or DGPU, and you can have a confirmation on Windows 10. Intel (U)HD Graphics, however, does not provide native HDMI 2.0 output, so in order to solve this issue OEMs add an additional hardware named LSPCON on the motherboard to convert DisplayPort into HDMI 2.0.
      LSPCON works in either Level Shifter (LS) or Protocol Converter (PCON) mode. When the adapter works in LS mode, it is capable of producing HDMI 1.4 signals from DisplayPort, while in PCON mode, it could provide HDMI 2.0 output. Some onboard LSPCON adapters (e.g. the one on Dell XPS 15 9570) have been configured in the firmware to work in LS mode by default, resulting a black screen on handling HDMI 2.0 connections.
      Starting from version 1.3.0, WhateverGreen now provides driver support for the onboard LSPCON by automatically configuring the adapter to run in PCON mode on new HDMI connections, and hence solves the black screen issue on some platforms.
       
      2. Before you start
      LSPCON driver is only applicable for laptops and PCs with HDMI 2.0 routed to IGPU. LSPCON driver is necessary for all newer platforms unless the new IGPU starts to provide native HDMI 2.0 output. Supported Intel Platform: Skylake, Kaby Lake, Coffee Lake and later.
      Skylake Case: Intel NUC Skull Canyon; Iris Pro 580 + HDMI 2.0 with Parade PS175 LSPCON.
      Coffee Lake Case: Some laptops, e.g. Dell XPS 15 9570, are equipped with HDMI 2.0 and Parade PS175 LSPCON. If you have confirmed that your HDMI 2.0 is routed to IGPU and is working properly right now, you don't need to enable this driver, because your onboard LSPCON might already be configured in the firmware to work in PCON mode.
      3. Instructions
      Dump your kernel log and you should also be able to see something simillar to lines below.
       
      // When you insert the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] Found the LSPCON adapter: Parade PS1750. igfx @ (DBG) SC:   LSPCON::probe() DInfo: [FB2] The current adapter mode is Level Shifter (DP++ to HDMI 1.4). igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has detected the onboard chip successfully. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver has been initialized successfully. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x00. igfx @ (DBG) SC: LSPCON::getMode() DInfo: [FB2] The current mode value is 0x01. igfx @ (DBG) SC: LSPCON::setMode() DInfo: [FB2] The new mode is now effective. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] The adapter is running in preferred mode [Protocol Converter (DP++ to HDMI 2.0)]. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. // When you remove the HDMI 2.0 cable igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a868c000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] No LSPCON chip associated with this framebuffer. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB0] Returns 0x0. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] called with controller at 0xffffff81a8680000 and framebuffer at 0xffffff81a869a000. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] LSPCON driver (at 0xffffff802ba3afe0) has already been initialized for this framebuffer. igfx @ (DBG) SC: LSPCON::setModeIfNecessary() DInfo: [FB2] The adapter is already running in Protocol Converter (DP++ to HDMI 2.0) mode. No need to update. igfx @ (DBG) SC: LSPCON::wakeUpNativeAUX() DInfo: [FB2] The native AUX channel is up. DPCD Rev = 0x12. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Will call the original method. igfx @ (DBG) SC:     GetDPCDInfo() DInfo: [FB2] Returns 0x0. Additionally, you can find these properties injected by the driver under the corresponding framebuffer.
      (Only available in DEBUG version)
       
      fw-framebuffer-has-lspcon indicates whether the onboard LSPCON adapter exists or not.
      fw-framebuffer-preferred-lspcon-mode indicates the preferred adapter mode. 1 is PCON, and 0 is LS.
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By Slice
      I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
      I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
       
      Hardware
      Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
      Chipset Intel 7 series, no patches needed
      Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
      LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
      Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
      SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
      USB3.0 works natively if not disabled in DSDT
      PS2 keyboard and touchpad works with VoodooPS2.
      WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
      LCD Screen 1366x768
      BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
      For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
       
      WiFi
      It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
      I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
      As well a patch for channels.
      I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
       
      VideoCards
      In Bios we can set Optimus = Enable/Disable
      If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
      If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
      But here there is contradiction with WiFi with required Board-ID from MacBookAir.
      So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
      Set BoardID like iMac13,2 to make Nvidia working.
      Patch BoardID in Brcm4360 to make WiFi working.
      Now I have
      Inject->
      ->Intel=YES
      ->Nvidia=YES
      and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
      For Intel graphics there is a patch against 8 apples at start.
      This Nvidia 5200 is Fermi and works in ElCapitan.
       
      Brightness
      No special kexts.
      The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here  #72 
       
      DSDT and SSDT
      This is very long story and finally I have working sleep in both cases Intel or Nvidia.
       
      Sensors
      I use my HWSensors3 with FakeSMC 3.5.2.
      I got monitoring:
      CPU temperature
      GPU temperature
      GPU main frequency
      GPU shader frequency
      Battery state % full, time to charged or time to empty.
      Battery voltage dinamically.
      Battery amperage dynamically. I can see it changes on heavy games.
      HDD temperature.

       
      Audio
      I like VoodooHDA and have no problems with it.
      The sound is clear, loud, and switchable between internal speaker and headphone.
      Mic is working.
       
      Bluetooth
      Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
      For 10.13.6 there is other kext BRCMInjector.
       
      Keyboard, Touchpad and Touchstick
      Post #14
      I made my fork of the VoodooPS2 driver, take here sources and release version
      https://github.com/SergeySlice/VoodooPS2-for-ALPS
       
      My config, ACPI files and kexts are in attachment.
      05.12.2017
      EFI.7z
       
      EDITED:
      Better DSDT in the post #6.
      Sleep working even when AC inserted.
       
      EDITED 06.12.2018
      Now I have HighSierra and this is my EFI folder. Note, HighSierra is possible only with Intel graphics (Optimus is enabled in BIOS)
       

       
       
      Welcome to discussion!
      EFI-E6430.7z
      BRCMInjector.kext.zip
×