Asus Laptop G51JX Aptio Legacy Bios won't complete boot into Ventura

[deeveedee]

@Middleman I see that you have more experience with AirportBrcmFixup than I do, so I'm going to let you and @oSxFr33k work together to figure this out.  Wi-Fi and Bluetooth works well for me in Big Sur with the EFI that I have posted in my thread and I don't need -v.  I have been experimenting with Bluetooth changes for Monterey and Ventura (all documented in my thread) that are not yet posted in the EFI in my thread.  The changes that I made (all documented in my thread) make Bluetooth and Wi-Fi work well in Monterey and Ventura.

 

I'll leave the two of you with my observations:

• If in fact -v is required (verbose boot), then it means that a delay is needed during communication with the brcm card.  Look at the boot-args that I use in my EFI. -v should NOT be required.
• I didn't find it necessary to use brcmfx-aspm=258 or brcmfx-aspm=259 with my BCM 94352HMB.  Maybe I didn't need them on my Dell Latitude E6410 and they are required on other laptops or for other Brcm cards?  If you look at my config.plist, you'll see that I added the following DeviceProperty.  I never confirmed that it was necessary.
  Spoiler

  

   

• @oSxFr33k I think you need to boot Catalina again (with DosDude patcher) and make sure everything still works.  If you look at my thread, you will see that I made sure everything was working perfectly in HighSierra before I attempted to boot Big Sur.  Only after I was certain that HighSierra worked perfectly did I attempt Big Sur.  Whenever I had a problem, I would go back to High Sierra to make sure that High Sierra still worked.  I think you are introducing too many variables at once (new CPU, different Brcm Cards, changing ACPI patching from DSDT to SSDT, ...).  I think you should simplify your approach and minimize the changes after you confirm that older versions of macOS are working.
• USB mapping is very important for properly working Bluetooth.  If you look at my thread, you'll see that I spent quite a bit of time refining my USB map for the Dell Latitude E6410.  The USB map will be different for other laptops.

 

EDIT: Also, you should make sure that you can boot older versions of macOS (I prefer High Sierra, since it's the last macOS that natively supports NVidia Tesla) with Open Core.  If you are trying to learn Open Core and you are trying to learn NVRAM Emulation at the same time that you are trying to upgrade to Big Sur or Montery or Ventura, you are making the problem too hard for yourself.  You will see that my first step was getting High Sierra to boot with Open Core.  That is my recommendation.

 

Edited July 1, 2023 by deeveedee

[oSxFr33k]

@deeveedee

 

So true never installed OC for Hi-Sierra or Catalina on this G51JX Laptop both work so good with Clover and flawless in Hi Sierra and Catalina.   The only exception is Shutdown, sleep/wake broke from Hi Sierra to Catalina, I also tried Rehabman’s DSDT Debug technique and even with his help could never figure out the cause seems like you have mastered the fix for this which I will look at once I can get to the Desktop with GPU acceleration. 

 

My only true baby is the Asus G750JX, a huge huge history on this laptop.  Actually if you ever look on eBay for one I recommend you buy one you will be in heaven.  Make sure it’s the G750JX model with the GTX 770M dedicated only graphics, I know what your most likely thinking, its a Haswell Laptop what’s the big deal, you get one you will have everything you need from me OC wise to get this running in perfection at least up to Ventura. A quick Google search G750JX Mavericks brings up a Asus Rog thread started by Bozzified then kinda continued by me near the end and G750JX Github search brings up my stuff for the G750JX.  Everything you need is on Github all patches etc to do it from scratch if one wanted to and learn.

 

I still have all the DSDT patching text files from EmiyDinesh, we spent months perfecting those DSDT patches, which I converted the GPU patch to SSDT starting in Catalina.  Maybe Clover made things to easy for me but OC was a real chalenge.  Emily also help me perfect the G750JX DSDT patches.  All of those now I have converted to SSDT/OC, except one,  I cannot get for the life of me and with the help of some great people over on OSXLatitide forums, the WIFI Led on the front base of the Laptop to convert to SSDT, it just cannot be done. I just have to live without an LED indicator or go back to DSDT and we know it’s not recommended in OC.  Even the Battery patch which I believe you have done the same thing taken what would have been Rehabman’s battery patch guide for DSDT and converted to OC ACPI patching/renaming/SSDT one of Rehabman’s last incredible journey’s, he knew the huge significance of the OC team look what they have done.

 

BTW that extra code I have in the GPU SSDT is for preparing it for under/over scan for LCD monitors connected externally to the HDMI port.  I have to check my Real MacBookPro6,2  to see if this exists in Ioreg but it does for the G750JX.  I honestly don’t remember why it is there.  

 

You can see from my signature I have a huge list of hardware I am updating slowly to Ventura, one is rather famous here the Dell XPS M1530 which Fusion71au perfected to work beyond Catalina.

 

I know I have been here for a long time you would think and I am sure many others may think the same, by now I would have this all down but I don’t that is unfortunate for me. 

 

We are very similar in some way perfection wise, but you go way out of your way to lay it down, your entire process step by step troubleshooting and still somehow not sure how find time to help others, have not seen anyone ever do anything like what you have done, documenting every single phase as you move along this is invaluable information don’t ever give up on your journey.

 

Again thanks for the help!!

Edited July 1, 2023 by oSxFr33k

[oSxFr33k]

@Middleman

Tried the ASPM but in DeviceProperties no luck.   The Nvram flags that you posted a while back I have most of them except instead of vsmcbeta I have vsmcgen=1 nieither one make any difference.  What is smcgen=1 which I tried didn't have any luck, nor did any of the NCPI flags 2000 or 3000.  Even tried Darkwake no difference.

 

Thanks for the help.

 

@deeveedee

 

I was able to boot with GPU acceleration into Catalina using the same OC settings I have for Ventura with one huge difference.   It boots with acceleration using the graphics DeviceProperties in OC and won't boot my GPU SSDT so that tells me something there.  I don't know why Ventura boots to dark screen with only using DeviceProperties in OC while Catalina no issues.  Both Catalina and Ventura behave exactly the same with the GPU SSDT it stalls and does not even boot ever to screen just stalls.

 

Do you have a guide for creating the GPU SSDT?   Did you start with SSDTTime?  I did notice you include many sections you find in the original DSDT, was not quite sure why there are Multiple OperationsRegions, Multiple Scopes and Methods, most of which had to come from your native DSDT.  Is all of it really needed or you had to bring in all the code to get it to boot with acceleration and to get Sleep/Wake and shutdown to work?

 

Thanks for the help.

Edited July 1, 2023 by oSxFr33k

[oSxFr33k]

12 hours ago, Middleman said:

I believe as well as the kext you have to enable ASPM in the BIOS as well as use the following boot-args:

 

-v brcmfx-aspm=259

or

-v brcmfx-aspm=258

 

The -v is mandatory (otherwise it won’t work)

 

The plug-ins are not needed (ie.kext only required) if your card is Apple native as they are for non Apple-native cards.

I don’t have that setting in Legacy Bios.  I loaded the Bios in Aptio tools and a very interesting feature I can actually enable UEFI but will make a rom backup of the Bios before I change that setting. I don’t see how it can just magically become UEFI Bios without all the modules drivers and as complex as it is it can’t be that simple. 

Edited July 1, 2023 by oSxFr33k

[oSxFr33k]

@deeveedee

 

Good news after looking over your SSDT and the _DSM you pasted as well as carefully looking over my GPU SSDT I entered what I think is most important into DeviceProperties in OC and guess what, it booted as accelerated graphics finally in Ventura.  I don't see anything with Underscan on the real but that is a hot swappable so it may not show up in Ioregistry until after a connection is made, I still left that data out of DeviceProperties.  Where do I view in Ioregistry if the GPU is spoofed correctly and what should it look like?  I will have to look through your thread on GPU injection I think you have some Ioreg screenshots.

 

You are correct with OC the CPU is unknown but not when I boot Clover.  Have to spoof CPU.   Last few things to work on is Wifi and sleep/wake/shutdown which is in your guides.

 

Screenshot of OC DeviceProperties and Ioreg attached.

 

Thanks Again!

 

G51JX_VENTURA.IOREG.zip

Edited July 2, 2023 by oSxFr33k

[deeveedee]

@oSxFr33k I see that you are defining 3 graphics ports (@0, @1 and @2).  You'll see in my SSDT-GFX0 that I define only 2 ports (@0, @1).  I only use my built-in LCD and external VGA port on a regular basis (I don't use my DP port), so this works for me and means that I only need to adjust 2 displays in my display settings.  Just curious - are you using all 3 displays?

 

EDIT: I added a 3rd graphics port (@2) to my SSDT so that I'm running with a configuration similar to yours.  The only settings change I needed to make was to Arrange displays (the addition of the 3rd port changed my graphics display arrangement).

Edited July 3, 2023 by deeveedee

[oSxFr33k]

12 hours ago, deeveedee said:

@oSxFr33k I see that you are defining 3 graphics ports (@0, @1 and @2).  You'll see in my SSDT-GFX0 that I define only 2 ports (@0, @1).  I only use my built-in LCD and external VGA port on a regular basis (I don't use my DP port), so this works for me and means that I only need to adjust 2 displays in my display settings.  Just curious - are you using all 3 displays?

 

EDIT: I added a 3rd graphics port (@2) to my SSDT so that I'm running with a configuration similar to yours.  The only settings change I needed to make was to Arrange displays (the addition of the 3rd port changed my graphics display arrangement).

 

-I have not tested the VGA nor the HDMI ports yet.  Will VGA work in MacOS BigSur+

-Successful install of Big Sur, WIFI working might re-install Ventura 13.2.1 or maybe update to see if I can get the WIFI to work

-I cannot get the SSDT to inject the graphics investigating but DeviceProperties takes care of it, I am using WhateverGreen.

-I tried to Fake CPU with CPU Mask , still says unknown processor but also seems to be running fine, you will see the edit in OC config attached files.

-I am unsure if the deviceProperty Nvidia Spoof is working or not, Ioreg attached, where/what am I looking for if Spoofing is working or not?

-Assuming from my readings that if AGPM is enabled it will show up under CPU1?

-DSDT just reboots with Big Sur and I made sure RebaseRegions was enabled.

-Does AppleACPIEC really need to be present in Ioreg?  I thought that was what needed to be prevented in a hack.  I see EC and ECO with _STA in Ioreg and I am fairly sure the SSDT is correct.

-My USB ports kext is correct but for some odd reason it won't let me rename EHC0 but the important one to rename is EHCI or EHC1 correct?

-The Kext created from SSDTTime 'SSDT-USB-Reset.aml' I believe is the one that does the EHC renaming and without it, none of the USB ports will work.

-Still a lot of work left for PS2 devices, using USB keyboard and USB mouse for now.

-Need to get Sleep/Wake/shutdown to work.  This actually broke in Catalina and never was able to figure out how to fix it.

-Have to work on getting LCD brightness to function, No slider present in Display in settings.

-I have a real MacBookPro6,2 with the GT330M I can supply Ioreg if you want to see it for reference?

-Can I get a copy of your Ioreg?

-Please find EFI and my Ioreg from Big Sur attached fairly sure its the same as what I already attached from previous post where I finally booted with GPU acceleration with attached files.

 

 

EFI and Ioreg Big Sur.zip

 

Edited July 4, 2023 by oSxFr33k

[deeveedee]

@oSxFr33k You should be using IORegistry Explorer dump from your real MBP6,2 as your reference.  Your DSDT should work with Open Core and allow you to boot Big Sur (and Monterey and Ventura). I wonder if you have to drop the original DSDT in OC?  I'm not sure.   I'll review your last posted EFI when I get more time.  
Depending on your original unpatched ACPI, renaming both EH01 and EH02 may be required.  It can't hurt to have both renamed and the renames should work.

 

Here are IORegistry screenshots from my hack

 

CPU

Spoiler

 

EC

Spoiler

 

LPCB / MCHC (Note that my LPCB is equivalent to your SBRG)

Spoiler

 

EH01 / EH02

Spoiler

 

Edited July 4, 2023 by deeveedee

[deeveedee]

@oSxFr33k I reviewed your config.plist and have the following comments:

• Why are you still injecting SSDT-PMC?
• I don't define @x,connector-type and @x,can-hot-plug in my NVidia patches.  Did you find that you need these?
• If your NVidia patches are correct, you shouldn't need WhateverGreen.kext
• Depending on your Brcm card, you may need BluetoothSpoof.kext enabled in your config.plist in order to have working Bluetooth
• Depending on your Brcm card, you may need BluetoolFixup.kext enabled for working Bluetooth
• Depending on your Brcm card, you may need BrcmPatchRAM3 and BrcmFirmwareData kexts enabled for working Bluetooth
• You have Kernel patches in your config.plist that I don't recognize

 

There are a lot of things that I can't help with because I don't have your laptop.  I still think that your best approach is to boot High Sierra with Open Core and to confirm that everything is working properly in High Sierra (with Open Core) before attempting Big Sur.

 

Yes, VGA works with Big Sur, Monterey and Ventura.

[deeveedee]

@oSxFr33k In an older hack, I used Open Core with a DSDT.  It's frowned upon to reference TonyMacx86 from this forum, but I'm not sure how else to direct you to my old material.  See here.

[deeveedee]

@oSxFr33k You may want to monitor this thread to see if anyone answers my questions about using DSDT with Open Core.

[oSxFr33k]

1 hour ago, deeveedee said:

@oSxFr33k In an older hack, I used Open Core with a DSDT.  It's frowned upon to reference TonyMacx86 from this forum, but I'm not sure how else to direct you to my old material.  See here.

-The AGPMenabler is how you know your GPU was spoofed, if not where in ioreg tells you?

-Have to review kernel patches might have left a few things in there I have to remove. 
-I might put the i7-720M back in but it’s the same Device-ID as the i7-940XM. 
-Not sure what else I have to do to fake CPU tried also in Platform Generic CPU device. 
-I keep forgetting to remove PMC SSDT

-I just now noticed a pre boot message OCCPU: failed to get FSBFrequecy data using Apple Platform Info - Not Found. I thought I had the 3 kexts loaded for CPU I will double check the ASP one but thought for sure I was loading it. 

Edited July 4, 2023 by oSxFr33k

[deeveedee]

@oSxFr33k If anyone is telling you that you can't or shouldn't use edited DSDT with Open Core, they are wrong.  Look at the Sample.plist that is included with Open Core 0.9.3:

Spoiler

 

There has been heated and emotional debate about editing DSDT vs. patching with SSDTs.  I think both methods are valid and I enjoyed a lot of success on older rigs with edited DSDTs.  If you are comfortable with using your edited DSDT, I would recommend that you stick with your edited DSDT until you get everything working with Open Core and High Sierra.

[deeveedee]

9 minutes ago, oSxFr33k said:

-The AGPMenabler is how you know your GPU was spoofed, if not where in ioreg tells you?

 

The presence of AGPM in your IORegistry tells you that macOS has recognized your CPU and GPU

 

My GPU

Spoiler

 

 

My CPU

Spoiler

 

[deeveedee]

@oSxFr33k This may be a dumb question, but when you are attempting to run Big Sur or later macOS, you are installing the OCLP post-install patches, correct?  You don't need OCLP with High Sierra (which is why I am suggesting that you get High Sierra booting/running with Open Core before you attempt Big Sur or later).

[oSxFr33k]

9 minutes ago, deeveedee said:

@oSxFr33k This may be a dumb question, but when you are attempting to run Big Sur or later macOS, you are installing the OCLP post-install patches, correct?  You don't need OCLP with High Sierra (which is why I am suggesting that you get High Sierra booting/running with Open Core before you attempt Big Sur or later).

Correct. 

[deeveedee]

@oSxFr33k Slice mentioned something in another thread that reminded me ... you may need Vt-x enabled in BIOS.  If your BIOS has any options to enable virtual machine support, this should be enabled (but not Vt-d).

Edited July 7, 2023 by deeveedee

[oSxFr33k]

@deeveedee

 

Having a real hard time with this SSDT experimenting around it partially works EHC0 remains as EHC0 and EHC1 gets renamed as EH01.  Trying to figure out how to rename EHC0 to EH02 for example here is my before and after and EHC0 just does not rename.   If I try Rename EHC0 and EHC1 to EH01 and EH02 within the Opencore Config ACPI/Patch, it kills all the USB ports.  I believe my USBports.kext is correct I spent a lot of time with that my EFI was posted up a few.  Still working on APGM.   I had to do more research on Device (EC0) I don't think I really understood how the patching should be done.  My Ioreg now looks like yours for EC.

 

This was only renames EHC1 as EH01.

DefinitionBlock ("", "SSDT", 2, "CORP", "UsbReset", 0x00001000)
{
    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.EHC0.RHUB, DeviceObj)
    External (_SB_.PCI0.EHC1, DeviceObj)

    Scope (\_SB.PCI0.EHC0.RHUB)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

    Scope (\_SB.PCI0.EHC1)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

    Scope (\_SB.PCI0)
    {
        Device (EH01)
        {
            Name (_ADR, 0x001A0000)  // _ADR: Address
            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                If (_OSI ("Darwin"))
                {
                    Return (0x0F)
                }
                Else
                {
                    Return (Zero)
                }
            }
        }
    }
}

 

Edited the script to also rename ECH1 to EH02

 

DefinitionBlock ("", "SSDT", 2, "CORP", "UsbReset", 0x00001000)
{
    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.EHC0.RHUB, DeviceObj)
	External (_SB_.PCI0.EHC1.RHUB, DeviceObj)
    External (_SB_.PCI0.EHC0, DeviceObj)
	External (_SB_.PCI0.EHC1, DeviceObj)

    Scope (\_SB.PCI0.EHC0.RHUB)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

    Scope (\_SB.PCI0.EHC1.RHUB)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }

    Scope (\_SB.PCI0.EHC1)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }


    Scope (\_SB.PCI0.EHC0)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (Zero)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }


    Scope (\_SB.PCI0)
    {
        Device (EH01)
        {
            Name (_ADR, 0x001A0000)  // _ADR: Address
            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                If (_OSI ("Darwin"))
                {
                    Return (0x0F)
                }
                Else
                {
                    Return (Zero)
                }
            }
        }
    }

    Scope (\_SB.PCI0)
    {
        Device (EH02)
        {
            Name (_ADR, 0x001D0000)  // _ADR: Address
            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                If (_OSI ("Darwin"))
                {
                    Return (0x0F)
                }
                Else
                {
                    Return (Zero)
                }
            }
        }
    }
}

 

 

 

[deeveedee]

@oSxFr33k I'm confused.  Does your DSDT not work?  I inspected it only enough to see that your DSDT includes EH01 and EH02.  If you're abandoning the DSDT that worked for you and you want to pursue an SSDT hot-patching approach, look at the EFI in my thread to see how I renamed / patched USB.  In my opinion, if you abandon the DSDT without first using it to get Open Core booting High Sierra, you're making this harder than it should be.

Edited July 7, 2023 by deeveedee

[oSxFr33k]

10 minutes ago, deeveedee said:

@oSxFr33k I'm confused.  Does your DSDT not work?  I inspected it only enough to see that your DSDT includes EH01 and EH02.  If you're abandoning the DSDT that worked for you and you want to pursue an SSDT hot-patching approach, look at the EFI in my thread to see how I renamed / patched USB.  In my opinion, if you abandon the DSDT without first using it to get Open Core booting High Sierra, you're making this harder than it should be.

 

DSDT does not boot BigSur/Monterey nor Ventura only Catalina.  I will have a look at yours.  I used SSDTTime to generate the SSDTs and the USB reset partially works.

[deeveedee]

@oSxFr33k Just to clarify, you are booting Catalina with Open Core and your DSDT?

[oSxFr33k]

35 minutes ago, deeveedee said:

@oSxFr33k Just to clarify, you are booting Catalina with Open Core and your DSDT?

 

Yes, when I get home let me boot one more time just to verify.

Edited July 7, 2023 by oSxFr33k

[deeveedee]

@oSxFr33k Please post your Open Core EFI that boots Catalina with your DSDT.  Also post the IORegistryExplorer captured after you boot Catalina with your Open Core / DSDT EFI.

[oSxFr33k]

19 hours ago, deeveedee said:

@oSxFr33k Please post your Open Core EFI that boots Catalina with your DSDT.  Also post the IORegistryExplorer captured after you boot Catalina with your Open Core / DSDT EFI.

 

-Apologies I spoke to soon, I have made all necessary changes as was discussed to boot Opencore config with DSDT boot, in Catalina unfortunately I get waiting for root device FD8884C1-A5C6-4B2F-A117-E23A453708C5 just assuming the root device is SATA rather than the USB, working on a fix, if I can get past this point I think she will boot. 

 

- I will try to boot Hi-Sierra eventually with OC but rather start with Catalina at this point since Clover boots Catalina perfectly with AGPM and all devices properly set. 

 

-I don't think I ever posted my Ioreg from Clover boot with DSDT boot, so I have posted it maybe you can see if something is not patched properly in my DSDT for Clover.  Everything is loading properly, I have AGPM with the newer processor i7-940QM, AppleACPIEC is under EC.  SBRG is renamed as LPCB.  EH01/EH02 showing PR ports numbers just as your ioreg screenshot shows.

 

-The only thing broken and have not fixed in Catalina is Shutdown/Sleep/Wake which I think was working in Hi-Sierra I don't remember?

 

-You mentioned a couple times about Bluetooth I am purposely not loading those kexts right now just the WIFI in Opencore until I finally get OC to boot in older MacOS's as you have.

 

-One question should I be loading RestrictAgents.kext, FeatureUnlock.kext and RSRHelper.kext under Catalina with OpenCore, I believe you load them in your latest OC v0.8.8, I am using v0.9.3.  Will the more current versions of OC boot your system?

Catalina CLover boot Ioreg also includes OC Config.zip

Edited July 8, 2023 by oSxFr33k

[deeveedee]

With OCLP as your solution for Big Sur and later versions of macOS, I think it will be better to first get High Sierra booting with Open Core (without any legacy NVidia graphics patching).  In my opinion, the reason that my hack is working so well with OCLP patches is that my hack behaves exactly like a real MBP6,2.  I made sure that it was as perfect as it could be in High Sierra.  You said you have a real MBP6,2 (unless I misunderstood), so you have more than I do.  You can dump ACPI and IOReg on the real MBP6,2 to make your own comparisons.

 

OCLP is designed for real Macs (including a real MBP6,2) and real MBP6,2s start with High Sierra when being upgraded to Big Sur with OCLP.  There can't be any traces of DosDude's patcher when performing the Big Sur install.  It just makes sense to me to do the same with our hacks. You can look at my High Sierra EFI (OC 0.8.8) and my new Big Sur/Monterey/Ventura/Sonoma EFI (OC0.9.3) and compare the differences.  When I made the decision to attempt Big Sur, I did not revisit my Catalina solution (with DosDude patcher) except to move my ACPI patches from CLOVER to Open Core.

 

You may need to read through my entire thread multiple times to see exactly how I debugged my own issues and solved them.  It's all there.

Edited July 8, 2023 by deeveedee