BRCM4360 and Sierra 10.12.6 Issues

[fallen00sniper]

It is extremely unlikely your native DSDT has references to "Darwin", therefore they are patched (likely by you).
Delete all files from ACPI/origin.
The extract fresh with F4.

I did exactly that before posting the files for you, the only ones that are patched are in the patched directory, is it possible clover is reading the patched files on my other ssd containing my Yosemite install or my config is causing clover to do patches?

I'll remove those possibilities and extract again.

 

[RehabMan]

I did exactly that before posting the files for you, the only ones that are patched are in the patched directory, is it possible clover is reading the patched files on my other ssd containing my Yosemite install or my config is causing clover to do patches?

I'll remove those possibilities and extract again.

Clover does not patch ACPI/origin/DSDT.aml. It should be a pure extract of native.

It is always possible the OEM put some direct macOS/OS X support in, but I've never seen it.
(or you have patched BIOS with such support?).
I'm referring to this code in DSDT.aml:

                    }
                    Else
                    {
                        If (CondRefOf (\_OSI, Local0))
                        {
                            If (\_OSI ("Linux"))
                            {
                                Store (0x01, LINX)
                            }

                            If (\_OSI ("Darwin"))
                            {
                                Store (0x01, AMAC)
                            }
                       }

 

[fallen00sniper]

Clover does not patch ACPI/origin/DSDT.aml. It should be a pure extract of native.

I'm not sure whats going on, after I did all of the things listed below, my bios reset itself to default again and prior to that set itself a password, Sierra is a odd little beast.

Removed:
Yosemite ssd
DSDT & HDMI aml files
created new config with clover and unchecked a few things I thought could be a problem

rebooted and extracted
hardly had time to put things back in place before Sierra decided to panic and reboot.

Attaching ACPI folder with origin folder and config used at that point in time, does not reflect putting my settings back as they were.

 

[RehabMan]

Attaching ACPI folder with origin folder

It might be some half-assed attempt at native macOS/OS X support in your BIOS.

 

[fallen00sniper]

Clover does not patch ACPI/origin/DSDT.aml. It should be a pure extract of native.

It is always possible the OEM put some direct macOS/OS X support in, but I've never seen it.
(or you have patched BIOS with such support?).
I'm referring to this code in DSDT.aml:

                    }
                    Else
                    {
                        If (CondRefOf (\_OSI, Local0))
                        {
                            If (\_OSI ("Linux"))
                            {
                                Store (0x01, LINX)
                            }

                            If (\_OSI ("Darwin"))
                            {
                                Store (0x01, AMAC)
                            }
                       }

The BIOS are direct from Gigabyte website, I noticed in the config at boot clover was setting Drop _OEM enabled for everything, or _DSM.

Would removing those lines from my DSDT fix the issue if they are present?

It might be some half-assed attempt at native macOS/OS X support in your BIOS.

Should I try the oldest BIOS revision, F9 I believe it was that also has a DSDT and see if the issue is removed?

Seems to go to F4, F8 is the lowest DSDT supported in the database.
https://www.gigabyte.com/Motherboard/GA-P55A-UD3-rev-10#support-dl

 

[RehabMan]

Would removing those lines from my DSDT fix the issue if they are present?

Not likely.
Did you test your hardware on Windows?

 

[fallen00sniper]

Not likely.
Did you test your hardware on Windows?

Everything works great on Windows 10, Wireless card does not cause a BSOD anymore since I have changed to a different driver directly from Broadcom, Yosemite everything works as well only needed to use the kext patches to get it working properly.

Sierra is the only area that I am having issues and the only noticeable issue is with wifi, I did have an issue with the SMBIOS setting being 11,3 until I used clover to patch the USB ports from EHC01 to EH01.

 

[fallen00sniper]

I haven't looked myself yet, but this is from my Yosemite install.

I don't know if it will help you to help me any, but I thought it might?

Also this is with clover 4077, Sierra was using 4099 and I found the reference to Darwin in the DSDT I got from the database as well, is it possible that isn't what is causing the problem and just an oddity?

 

[RehabMan]

Everything works great on Windows 10, Wireless card does not cause a BSOD anymore since I have changed to a different driver directly from Broadcom, Yosemite everything works as well only needed to use the kext patches to get it working properly.

Sierra is the only area that I am having issues and the only noticeable issue is with wifi, I did have an issue with the SMBIOS setting being 11,3 until I used clover to patch the USB ports from EHC01 to EH01.

You should try adding an appropriate ACPI identity for the WiFi card.
eg. add a Device node (_ADR=0) at _SB.PCI0.PEX3, name PXSX.
Something like:

DefinitionBlock ("", "SSDT", 1, "hack", "WiFi", 0)
{
    Device(_SB.PCI0.PEX3.PXSX) 
    {
        Name(_ADR, 0)
    }
}

 

[fallen00sniper]

You should try adding an appropriate ACPI identity for the WiFi card.
eg. add a Device node (_ADR=0) at _SB.PCI0.PEX3, name PXSX.
Something like:

DefinitionBlock ("", "SSDT", 1, "hack", "WiFi", 0)
{
    Device(_SB.PCI0.PEX3.PXSX)
    {
        Name(_ADR, 0)
    }
}

I'll try that, anywhere specific in the DSDT or insert at the end of the file?

I've been trying to compare the only other DefinitionBlock and how it is laid out in the code, I also have looked at _SB and the contents of PEX3, should I add this code before or after the code in PEX3, before PEX3, before _SB or at the end?

Nevermind I get it now, this is meant to be SSDT.aml.