WhatEverGreen Support Topic

ross232 · August 17, 2017

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

Hutch71 · August 17, 2017

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?

vandroiy2012 · August 17, 2017

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

Yes

Jofkos · August 18, 2017

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?

MattsCreative · August 18, 2017

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

Jofkos · August 18, 2017

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

mark-san · August 18, 2017

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

MattsCreative · August 18, 2017

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

TombaFI · August 18, 2017

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?

MattsCreative · August 18, 2017

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

TombaFI · August 18, 2017

-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.

vandroiy2012 · August 18, 2017

-radbeta -lilubeta -liluforce add that to config

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

MattsCreative · August 18, 2017

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

vandroiy2012 · August 18, 2017

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!

TombaFI · August 18, 2017

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... 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!

MattsCreative · August 18, 2017

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... 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

stehor · August 18, 2017

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

MattsCreative · August 18, 2017

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

TombaFI · August 19, 2017

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... 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!

vandroiy2012 · August 19, 2017

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).

TombaFI · August 19, 2017

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?

mark-san · August 19, 2017

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.

MattsCreative · August 19, 2017

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

TombaFI · August 19, 2017

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

If any help with this?

Cheers!

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

surfinchina · August 20, 2017

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.

WhatEverGreen Support Topic

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites