Jump to content

Asus G750JX: porting DSDT patches to SSDT or OC ACPI patches

osxfr33k

By osxfr33k
in Asus Systems

 Share

Recommended Posts

osxfr33k Advanced Member

osxfr33k

Posted
  • Author
Posted

 

@Jake Lo

I am trying right now to finish the 16 level FN key into SSDT and again compile error wondering if you an have a look maybe it will compile for you or you may see a mistake?

  

DefinitionBlock ("", "SSDT", 2, "hack", "fn 16 stage", 0x00000000)
{

    
    External (_SB_.PCI0, DeviceObj)
    External (_SB_.PCI0.LPCB, DeviceObj)
    External (_SB_.PCI0.LPCB.EC0_, DeviceObj)
    External (_SB_.PCI0.LPCB.EC0_.SKBL, MethodObj)    // 0 Arguments
    External (_SB_.PCI0.LPCB.EC0_.GKBL, MethodObj)    // 0 Arguments
    External (_SB_.PCI0.LPCB.ATKP, DeviceObj)
    External (_SB_.PCI0.LPCB.EC0.WRAM, DeviceObj)
    External (B0FF, IntObj)        
    External (KBLV, IntObj)        
    External (KBPW, IntObj)      
        
      Scope (_SB)
      {

         Name (BOFF, Zero)
         Method (SKBL, 1, NotSerialized)
         {
              If (((Arg0 == 0xED) | (Arg0 == 0xFD)))
              {
                 If (((Arg0 == 0xED) & (BOFF == 0xEA)))
                 {
                    Local0 = Zero
                    BOFF = Arg0
                 }
                 ElseIf (((Arg0 == 0xFD) & (BOFF == 0xFA)))
                 {
                    Local0 = Zero
                    BOFF = Arg0
                 }
                 Else
                 {
                  
                      Return (BOFF) /* \_SB_.ATKD.BOFF */                   
                 }                     
                ElseIf (((Arg0 == 0xEA) | (Arg0 == 0xFA)))
                {
                    Local0 = KBLV /* \_SB_.KBLV */
                    BOFF = Arg0
                }
                Else
                {
                    Local0 = Arg0
                    KBLV = Arg0
                }

                Local1 = DerefOf (KBPW [Local0])
                ^^PCI0.LPCB.EC0.WRAM (0x044B, Local1)
                Return (Local0)
            }

            Name (KBPW, Buffer (0x10)
            {
                /* 0000 */  0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77,  // .."3DUfw
                /* 0008 */  0x88, 0x99, 0xAA, 0xBB, 0xCC, 0xDD, 0xEE, 0xFF   // ........
            })
            Method (GKBL, 1, NotSerialized)
            {
                If ((Arg0 == 0xFF))
                {
                    Return (BOFF) /* \_SB_.ATKD.BOFF */
                }

                Return (KBLV) /* \_SB_.KBLV */
            }
            
         } 
      }

 

 

@Baio77 

Mine has only dedicated GTX 770M intel GPU is disabled.  Will this work with this condition?

I will give that a try only want to eliminate the DSDT and have the patches as SSDT, what I have left to work on the really hard one is Battery and another easy one is the WIfi/BT LEd wake thing.

Where are these kexts, actually I found AsusSMC.kext from a github site and the brightnesskeys.kext by searching here was in Jake Lo's thread.  Are you sure these are not for Integrated rather than discreet only graphics? Keep in mind EMlyDinesh made these custom DSDT patches a few years ago and they have worked for me from Yosemite all the way through Big Sur. I have 16 level brightness for the Keyboard Keys and 16 level Brightness for the LCD with Apple Animation.  Will those kexts enable this?

Link to comment
Share on other sites
  • Replies 44
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Jake Lo
Jake Lo

You can't just convert them from that. You need the vanilla DSDT and the patched DSDT (make sure it works) to compare the 2 to make the SSDT. Of course the vanilla DSDT must be without error, sav

Jake Lo
Jake Lo

Uncomment this line on the second code should fix it //External (_SB_.PCI0.LPCB.EC0_, DeviceObj)

Jake Lo
Jake Lo

I'm using the same version to compile without error. I set the compiler to "Stable", but no issue either with dev or legacy SSDT-fnKey.dsl.zip

Posted Images

osxfr33k Advanced Member

osxfr33k

Posted
  • Author
Posted

I will try and get this to you either before I head out to work or after by tonight.  I will edit this post, and include it, also thanks for helping, its hard to find tat kind of help these days.  I have attached them, using rehabmana's AppleBacklightFixup.kext but to get this to work I had to use these flags in nvram applbklbeta applbkl=0 this has basically worked for me from Mojave all the way through Big Sur.  Using VoodooHDA since I have the subwoofer they were never able to get this to work with AppleHDA and with the Midi setting I can now control front and rear speakers.  I also load AppleHDA to it can do its conversations like to HDEF for example.  I want to be completely DSDTless, OpenCore does not do well with loading a DSDT since it already loads a DSDT in firmware.  I see issues loading my own DSDT for example GFX0 rename to IGPU shows  no change when my DSDT is loaded but if I remove my DSDT the rename of GFX0 to IGPU shows up in MacIASL System DSDT.  I also have Clover EFI if you want to look at that as well, let me know.  I am trying to figure out how I will fix Mutex in OpenCore.

 

I have also attached all my patches as txt files if you want o have a look at them, Emly prepared for me back in 2014.

 

EFI.zip

osxfr33k’s MacBook Pro.ioreg.zip

Patches.zip

Link to comment
Share on other sites
osxfr33k Advanced Member

osxfr33k

Posted
  • Author
Posted

She would not boot I have a picture not sure if that will help.  Debug is on but no log in EFI to attach.  This really looks great placing all patches in one SSDT thanks so much for that. Can I load my own Usbports.kext and disable usbinjextall or you need it this way for now?   Let me know what you think and what should I try next.  Thanks!

 

Edited:

 

I ran this command at the terminal may have found something:

 

log show --predicate "processID == 0" --start 2021-03-17 --debug

 

I don't think this is the reason why thought it might be HPET don't think its that either.

  

Backtrace 0xffffff7fa0aa9b34 0xffffff7fa0a767bb 0xffffff7fa0a77464 0xffffff8000a4628e 0xffffff7fa0a869e2 0xffffff8000a5045b 0xffffff80003a8e51
2021-03-17 21:18:00.859159-0500 0x77e      Default     0x0                  0      0    kernel:       Kernel Extensions in backtrace:
2021-03-17 21:18:00.859170-0500 0x77e      Default     0x0                  0      0    kernel:          com.apple.iokit.IOGraphicsFamily(585.0)[EF8876FC-C6D6-3D53-9915-762EF4F12870]@0xffffff7fa0a62000->0xffffff7fa0a90fff
2021-03-17 21:18:00.859179-0500 0x77e      Default     0x0                  0      0    kernel:             dependency: com.apple.iokit.IOPCIFamily(2.9)[BF2C5E86-1E8F-3FD4-9874-7738178FA73B]@0xffffff8002c1f000->0xffffff8002c46fff
2021-03-17 21:18:00.859190-0500 0x77e      Default     0x0                  0      0    kernel:          com.apple.iokit.IONDRVSupport(585.0)[40BEBEA2-BBB5-3B09-B6AE-B4B372775FBD]@0xffffff7fa0aa7000->0xffffff7fa0aaffff
2021-03-17 21:18:00.859201-0500 0x77e      Default     0x0                  0      0    kernel:             dependency: com.apple.iokit.IOGraphicsFamily(585)[EF8876FC-C6D6-3D53-9915-762EF4F12870]@0xffffff7fa0a62000->0xffffff7fa0a90fff
2021-03-17 21:18:00.859214-0500 0x77e      Default     0x0                  0      0    kernel:             dependency: com.apple.iokit.IOPCIFamily(2.9)[BF2C5E86-1E8F-3FD4-9874-7738178FA73B]@0xffffff8002c1f000->0xffffff8002c46fff
2021-03-17 21:18:00.906254-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.906260-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.906264-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.906283-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.906295-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.906300-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908834-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908840-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908844-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908847-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908850-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908854-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>
2021-03-17 21:18:00.908858-0500 0xc8e      Default     0x0                  0      0    kernel: (kernel) <compose failure [UUID]>

 

 

 

8A878A95-A6BA-4672-AD2E-5429246D070E.jpeg

Link to comment
Share on other sites
Baio77 First Lieutenant

Baio77

Posted
Posted

in my opinion in this initial EFI you passed me there are too many things that actually do not serve, so I start from 0, see if it starts this EFI ...
SSDT Unique is the last thing I do, because it serves to insert necessary parts, consequently block in Verbose, as in your case
EFI.zip

  • Like 1
Link to comment
Share on other sites
osxfr33k Advanced Member

osxfr33k

Posted
  • Author
Posted

It only boots pre kernel message [EB] messages then stops never loads the kernel.   I tried as you have it now without HPET and with HPET.  My CFG lock is disabled, I have unhidden Advanced menus in Bios and disabled CFG lock but changing those options in Kernel Quirks to "no" made no difference.

 

edited:

 

I am going to try a few different things because I noticed on the first EFI you attached I did not get the GUI boot once I replaced the resource folder with my original which is what you had anyhow,  it boot back to the GUI.  Maybe there is some issue with syncing files after they are zipped and attached then unzipped on my end just a theory.  If you see one of my prior posts MacIASL was leaving blank lines when I was pasting code.  
 

Another thing I remember EmlyDinesh had a real hard time with some of those patches he made he told he had to make many changes many times some bug he mentioned not sure what but something in the code maybe a variable or spacing just theorizing I really have no idea.  
 

So what I can try is use my opencore core files and just make all the changes manually in the config re-compile all the ACPI files and give it another try both the original EFI and the latest one you sent.  Thanks for being patient with me.  We will get this figured out I am sure of it.  

 

Edited Again:

 

Made some changes in config more like my original, made Quirk Changes and Nvram flags removed syms flag.   At this point no Brightness control, brightness maxed out and for some reason no PS2 keyboard?  Find attached my Ioreg and OpenCOre config I made adjustments to.  I also noticed under ACPI Delete you enabled the CPU patches not sure if this was the cause or what now I have to enable one thing back at a time you had made adjustments to my original config to see what was causing the kernel not to load.  In the meantime over the weekend if you want to test a little more frequently I can if you will be able to? 

 

Sorry one more thing I tried the all in one ACPI patch with my adjusted config and that issue is the same as is was before the config modification did not change the boot process, it stops as I posted above and I have the keyboard working again.     

 

Now with the current EFI you provided and after adding PNLF I have brightness slider in System Preferences Display but the slider gives me just on/off slide all the way to the left black screen which is howit should work and sliding it partially or all the way does not change brightness.  The 16 key press comes later I am assuming.

 

Ioreg_Config.zip

Link to comment
Share on other sites
Baio77 First Lieutenant

Baio77

Posted
Posted

1) you must always attach Ioreg + full EFI

 

2) see the image posted, your DSDT.aml is certainly NOT loaded, to use DSDT with OpenCore you must check the 2 boxes in the picture below

 

1759664067_Schermata2021-03-19alle12_47_48.thumb.png.64bd88c07e3fe4b28eda2a191c41b69b.png

 

Set like this to load DSDT

1616281479_Schermata2021-03-19alle12_49_41.png.f66a58af36966d4538cb490c475fa4ad.png
 

I don't want to sound like a professor, I'm a normal user who has been doing Hackintosh for a few years.
Look This https://github.com/Baio1977?tab=repositories ,all EFI do feature SSDT Hack Full Patch, whether Laptop or Desktop

 

In Laptop need to patch battery use DSDT patch, because it is very complex to extrapolate the battery patch, but not impossible ...
Open Core is also fine with DSDT Patch, just set well the EFI

 

Example of EFI with DSDT Patch

 

555525148_Schermata2021-03-19alle13_00_21.thumb.png.b59cca832ca9f1d527ff6ad777e59d2e.png
Excuse my English, I use translator

 

Link to comment
Share on other sites
osxfr33k Advanced Member

osxfr33k

Posted
  • Author
Posted

Sorry I forgot to enable DSDT. I will do this in a few minutes and send it over.  Is the 16 level patch still in this DSDT?  Will we be able to create the SSDT battery patch later because this was the entire point I want to do away with DSDT and even though  you can load DSDT in opencore it does not like it.  I have tested and proved it causes issues with ACPI patch rename in Opencore, and possible other things as well.  I read this in the Dortania OpenCore Guide.  I will load it for now because without the battery patch its breaks ACPI and that can cause issues as well but eventually would you be able to help me create the SSDT battery patch? Thanks

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...