<< Solved >> [HELP]: Working system won't boot with OC 0.7.7

[aylamrin]

Hi, I have a working system with OC 0.7.6 running Catalina (10.15.7).

But I am getting:

AAPL: [EB|#LOG:EXITBS:START]

with OC 0.7.7

My specs are:

CPU	i5 3470
Board	Gigabyte H77-DS3H
Memory	2X4GB (Corsair XMS3 1333MHz)
GPU	MSi NVIDIA GTX 650 (1GB)

Attached my EFI and OC debug log.

Could someone kind help me with this issue?

 

[aylamrin]

Resolved. Issue may be marked as closed.

 

[miliuco]

Resolved. Issue may be marked as closed.

But how did you solve it? If you only say solved, we can't learn anything about it.

 

[deeveedee]

ocvalidate reveals the following error for the config.plist in Post #1:

Booter->Quirks->EnableSafeModeSlide is enabled, but ProvideCustomSlide is not enabled altogether!

CheckBooter returns 1 error!

@aylamrin Just curious and probably a naive question - you have an SSDT that spoofs Wi-Fi Brcm device 14e4:43a0 and you don't have any Brcm kexts. It seems that your Brcm Wi-Fi is natively supported. Why do you need to rename PXSX->ARPT and spoof the device-id? Maybe you're using Dell DW1820A? If so, do you also need pci-aspm-default = 0? If so, why do you rename PXSX? Just cosmetic?

        Scope (\_SB.PCI0.RP02)
        {
            Scope (PXSX)
            {
                Name (_STA, Zero)  // _STA: Status
            }

            Device (ARPT)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                {
                    0x09,
                    0x04
                })
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If ((Arg2 == Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                             // .
                        })
                    }

                    Return (Package (0x02)
                    {
                        "compatible",
                        "pci14e4,43a0"
                    })
                }
            }
        }

 

[aylamrin]

Resolved. Issue may be marked as closed.

I tinkered with values in the Booter->Quirks and Kernel->Quirks a lot. TBH I do not know what exactly fixed the issue, but my guess is it could be "ProvideCurrentCpuInfo", which I DISABLED to make the system boot.

 

[aylamrin]

ocvalidate reveals the following error for the config.plist in Post #1:

Booter->Quirks->EnableSafeModeSlide is enabled, but ProvideCustomSlide is not enabled altogether!

CheckBooter returns 1 error!

@aylamrin Just curious and probably a naive question - you have an SSDT that spoofs Wi-Fi Brcm device 14e4:43a0 and you don't have any Brcm kexts. It seems that your Brcm Wi-Fi is natively supported. Why do you need to rename PXSX->ARPT and spoof the device-id? Maybe you're using Dell DW1820A? If so, do you also need pci-aspm-default = 0? If so, why do you rename PXSX? Just cosmetic?

        Scope (\_SB.PCI0.RP02)
        {
            Scope (PXSX)
            {
                Name (_STA, Zero)  // _STA: Status
            }

            Device (ARPT)
            {
                Name (_ADR, Zero)  // _ADR: Address
                Name (_PRW, Package (0x02)  // _PRW: Power Resources for Wake
                {
                    0x09,
                    0x04
                })
                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    If ((Arg2 == Zero))
                    {
                        Return (Buffer (One)
                        {
                             0x03                                             // .
                        })
                    }

                    Return (Package (0x02)
                    {
                        "compatible",
                        "pci14e4,43a0"
                    })
                }
            }
        }

You are right, the rename is more for cosmetic reasons.
Also, the EFI that I had posted may be one of the variations, while I was tinkering with the Booter->Quirks, and it is not every time that I validated with with "ocvalidate". Apologies! But I eventually managed to get the system running.

 

[deeveedee]

@aylamrin I'm impressed with your EFI - clearly you've done a lot of work to refine it. Maybe you could post your final/working EFI so that others can benefit from the working version (even if the exact fix is not known).

EDIT:
@aylamrin I saw your question (and answer from @Henry.M) in "the other forum." Based on that exchange, it does appear that ProvideCurrentCpuInfo was the culprit.