AMD Radeon HD 7670m and El Capitan (no HD4000)

[RehabMan]

Interesting, corrected it, and even after the successful boot nothing happens, it's still unrecognized... Has onboard-1 something with for instance PCI1? Because my graphics is on PCI0, but onboard-1 is set in the file.

"onboard-1" has to do with HDMI audio.

 

[filigor94]

Alright, so do I have to change it to idk, onboard-2 for graphics or something else?

 

[RehabMan]

Alright, so do I have to change it to idk, onboard-2 for graphics or something else?

As long as it matches the injection on HDEF for "hda-gfx" that's all that matters.

You should look in your ioreg to see if you see the expected injections.

 

[filigor94]

Here it is. I can see only some radeon sensors and some and support, but nothing exact with 7670m...

 

[RehabMan]

Here it is. I can see only some radeon sensors and some and support, but nothing exact with 7670m...

I only see a single properly, "hda-gfx"="onboard-1" injected @PEG0.VGA@0 (you can look in device-properties in IOACPIPlane).

 

[filigor94]

Really, I see only hdau and I should see gfx too, right? But why didn't injected it, if it injected hdau?

 

[RehabMan]

Really, I see only hdau and I should see gfx too, right? But why didn't injected it, if it injected hdau?

You can use search to see where "hda-gfx" is injected at... (make sure you enable the appropriate options n Preferences).

But "hda-gfx" does not relate to enabling Radeon graphics... it is a secondary task to enable HDMI audio.

 

[filigor94]

Well, I did it in dsdt like this:

Spoiler

Device (GFX0)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            Store (Package (0x02)
                {
                    "hda-gfx",
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
        }
    }
    Device (HDAU)
    {
        Name (_ADR, One)
        Method (_DSM, 4, NotSerialized)
        {
            Store (Package (0x02)
                {
                    "hda-gfx",
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
        }
    }

Has it anything to do then with the graphics?

 

[RehabMan]

Well, I did it in dsdt like this:

Spoiler

Device (GFX0)
    {
        Name (_ADR, Zero)
        Method (_DSM, 4, NotSerialized)
        {
            Store (Package (0x02)
                {
                    "hda-gfx",
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
        }
    }
    Device (HDAU)
    {
        Name (_ADR, One)
        Method (_DSM, 4, NotSerialized)
        {
            Store (Package (0x02)
                {
                    "hda-gfx",
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                }, Local0)
            DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
            Return (Local0)
        }
    }

Has it anything to do then with the graphics?

That's fine, but it has nothing to do with enabling your graphics card. It has to do with HDMI-audio, which would be a task to accomplish *after* you get graphics working.

 

[filigor94]

I can't believe it. I completely changed the config.plist with a 100 years older configured clover and suddenly the graphics card is working!!! But for instance, I can't see now the patched dsdt's hdau that we discussed before, am I right? And can there be other side effects using a really old clover config file?