Jump to content

AppleALC — dynamic AppleHDA patching

vit9696

By vit9696,
in AppleALC

 Share
5,390 posts in this topic

Recommended Posts

twsps
twsps
Posted
Posted
3 minutes ago, ammoune78 said:

Ok, now check the following:

 

  Hide contents

1078810168_ScreenShot2018-07-09at3_41_18PM.png.bf4e283ab361df05eb0afeedec181438.png

1331213593_ScreenShot2018-07-09at3_44_33PM.png.116778443a43c5917ea0aa7b1291a73c.png

1860648962_ScreenShot2018-07-09at3_47_56PM.png.3e9659834d4b373b7a10d0fa586bd59d.png 938242677_ScreenShot2018-07-09at3_52_55PM.png.7b4c18f5b25c11fff92ab997de93832b.png   1633524478_ScreenShot2018-07-09at3_57_16PM.png.4b5081a11e29fe7a2c5cf83227614c29.png

 

Now because of the DSDT already contain Layout ID 28 which was proposed by @pepito1, i added it into screenshot. And because of CpuSsdt already contain the required things for CPUPM, you can uncheck AppleIntelCPUPM like the screenshot. Then, you can go to KernelAndKextPatches, and under KernelToPatch add the following:

 

  Hide contents 


		<key>KernelToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>MSR 0xE2 _xcpm_idle instant reboot(c) Pike R. Alpha</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ILniAAAADzA=
				</data>
				<key>Replace</key>
				<data>
				ILniAAAAkJA=
				</data>
			</dict>
		</array>

 

 

Reboot, and see if you can boot with the these options

Just curious, why would I need SAT0 to SATA? I'm using NVMe and there's no SATA disk in my laptop. But beside all this, would SATA matter with audio?

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)
10 minutes ago, twsps said:

Just curious, why would I need SAT0 to SATA? I'm using NVMe and there's no SATA disk in my laptop. But beside all this, would SATA matter with audio?

 

You can leave it as is or use it, now because Apple names SATA to SATA in ACPI I follow them in each step, some devices MUST be renamed in order to have full support, like Device EC=Embedded Controller, ALS0, but in our case DELL uses ECDV and we cannot rename them otherwise KP. And NO, SATA wouldn't matter audio, as i said it's just a tweak to follow Macs attitude, i do that in every hack i own. What i did here is not just for audio as you can see, but in order to have the things between the minimum and the maximum, so the system have to be free of errors during the boot process

Edited by ammoune78
  • Like 1
Link to comment
Share on other sites
twsps
twsps
Posted
Posted
Just now, ammoune78 said:

 

You can leave it as is or use it, now because Apple names SATA to SATA in ACPI I follow them in each step, some devices MUST be renamed in order to have full support, like Device EC=Embedded Controller, ALS0, but in our case DELL uses ECDV and we cannot rename them otherwise KP. And NO, SATA wouldn't matter audio, as i said it's just a tweak to follow Macs attitude, i do that in every hack i own. What i did here is not just for audio as you can see, but in order to have the things between the minimum and the maximum, so the system have to be free of errors during the boot process

For disable drivers, I can't do that... I believe I need the code to do that. For the second section, I believe you mean KextsToPatch not KernelToPatch..

 

Thanks

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)
3 minutes ago, twsps said:

For disable drivers, I can't do that... I believe I need the code to do that.

 

If you disable VBoxHfs you'll have KP? What code do you need?

 

For the second section, I believe you mean KextsToPatch not KernelToPatch

 

No, under KernelToPatch

 

Edited by ammoune78
Link to comment
Share on other sites
twsps
twsps
Posted
Posted
6 minutes ago, ammoune78 said:

 

If you disable VBoxHfs you'll have KP? What code do you need?

 

For the second section, I believe you mean KextsToPatch not KernelToPatch

 

No, under KernelToPatch

 

If I add under disable driver "VBoxHfs-64", clover will not see any disks. I'll retry KernelToPatch now

9 minutes ago, ammoune78 said:

 

If you disable VBoxHfs you'll have KP? What code do you need?

 

For the second section, I believe you mean KextsToPatch not KernelToPatch

 

No, under KernelToPatch

 

There's no section called KernelToPatch

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
12 minutes ago, ammoune78 said:

 

If you disable VBoxHfs you'll have KP? What code do you need?

 

For the second section, I believe you mean KextsToPatch not KernelToPatch

 

No, under KernelToPatch

 

Ok, I added KernelToPatch section my own. The issue still exists. Here I've attached files for you to check.

Note: I didn't add disable driver because I won't be able to see any disks in clover if I add that.

 

Thanks

Step 3.zip

step 3 intel power gadget.png

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
Just now, twsps said:

If I add under disable driver "VBoxHfs-64", clover will not see any disks. I'll retry KernelToPatch now

 

Sure, because you don't have HFSPlus.efi, here's under the following:

 

Spoiler

918815070_ScreenShot2018-07-09at4_44_13PM.thumb.png.418d2f733fe2d11bbe34fa32ca629f7b.png

 

Link to comment
Share on other sites
twsps
twsps
Posted
Posted
5 minutes ago, ammoune78 said:

 

Sure, because you don't have HFSPlus.efi, here's under the following:

 

  Hide contents

918815070_ScreenShot2018-07-09at4_44_13PM.thumb.png.418d2f733fe2d11bbe34fa32ca629f7b.png

 

Sorry, I don't have those options in my clover configurator. Here I have HFSPlus under UEFI section.

Btw, would this matter to cpu management related to AppleALC?

 

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
2 minutes ago, twsps said:

Sorry, I don't have those options in my clover configurator. Here I have HFSPlus under UEFI section.

Btw, would this matter to cpu management related to AppleALC?

 

 

You can download the latest version by clicking on clover configurator in the menubar and then check for updates

Do you still have the problem? Why you keep checked DellSMBIOSPatch, without it you can't boot? Now do you have the same problem on all macOS versions or only Mojave? Have you tried the latest build of AppleALC and Lilu?

Link to comment
Share on other sites
twsps
twsps
Posted
Posted



 
You can download the latest version by clicking on clover configurator in the menubar and then check for updates
Do you still have the problem? Why you keep checked DellSMBIOSPatch, without it you can't boot? Now do you have the same problem on all macOS versions or only Mojave? Have you tried the latest build of AppleALC and Lilu?


I'm using macOS High Sierra, for Mojave, it stuck at ++++++++. And when wake up today, my High Sierra also stuck at ++++++++. For DellSMBiosPatch, I need this to make usb injection work. Right now I need to solve why it stuck at ++++++++

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted





I'm using macOS High Sierra, for Mojave, it stuck at ++++++++. And when wake up today, my High Sierra also stuck at ++++++++. For DellSMBiosPatch, I need this to make usb injection work. Right now I need to solve why it stuck at ++++++++

Sent from my MHA-AL00 using Tapatalk



Why you can’t boot , last time you was able! Did you changed something after my previous post, before posting the latest kexts? I need some time of rest now because it’s a night in my country, so i can help you from iphone and not from the laptop right now!
You only have to remember what the last change you did before shutting down the laptop. Check again that config for any mistake


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
twsps
twsps
Posted
Posted





Why you can’t boot , last time you was able! Did you changed something after my previous post, before posting the latest kexts? I need some time of rest now because it’s a night in my country, so i can help you from iphone and not from the laptop right now!
You only have to remember what the last change you did before shutting down the laptop. Check again that config for any mistake


Sent from my iPhone using Tapatalk


I'll try to solve it myself, but I would like to know are all those settings necessary? I'll try to use latest Lilu and AppleALC you've provided after I can boot into OS.
Ps. I never understand when ++++++++ would occur

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted





I'll try to solve it myself, but I would like to know are all those settings necessary?



I never said i can’t help you!
Yes, because you’re last post confirmed that it worked, except for that driver, and after that i suggested that you download hfsplus from clover configurator drivers menu, and you said that you don’t have the latest build.

Each set in your config have a sense, uncheck things doesn’t mean that your config is good and checking too much things doesn’t mean by the same way it’s good each hack will have some of same sets but not all completely. I let you check the things that need to be for a proper boot process, and let you uncheck things that doesn’t make sense for your hack like: uncheck xmp because of laptop memory, RTC because i already patched it in DSDT, AppleIntelCPUPM because we added CpuSsdt with new way plugin-type in the case of your hardware, xosi because i added Darwin in \_OSI for OS check by@RehabMan in the DSDT.

You just have to know why to do, not complicated, these problems you had and have with your hack will help you to know more, like every one here!

May i ask you what you did before shutting down your laptop, this will help us to go directly to the problem


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment
Share on other sites
twsps
twsps
Posted
Posted


I never said i can’t help you!
Yes, because you’re last post confirmed that it worked, except for that driver, and after that i suggested that you download hfsplus from clover configurator drivers menu, and you said that you don’t have the latest build.

Each set in your config have a sense, uncheck things doesn’t mean that your config is good and checking too much things doesn’t mean by the same way it’s good each hack will have some of same sets but not all completely. I let you check the things that need to be for a proper boot process, and let you uncheck things that doesn’t make sense for your hack like: uncheck xmp because of laptop memory, RTC because i already patched it in DSDT, AppleIntelCPUPM because we added CpuSsdt with new way plugin-type in the case of your hardware, xosi because i added Darwin in \_OSI for OS check by[mention=1031260]RehabMan[/mention] in the DSDT.

You just have to know why to do, not complicated, these problems you had and have with your hack will help you to know more, like every one here!

May i ask you what you did before shutting down your laptop, this will help us to go directly to the problem


Sent from my iPhone using Tapatalk
Actually I didn't do any settings tbh. Sometimes my Dell will go into kp but it won't when I boot up the second time. I'll reinstall again and do everything again

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted
Actually I didn't do any settings tbh. Sometimes my Dell will go into kp but it won't when I boot up the second time. I'll reinstall again and do everything again

Sent from my MHA-AL00 using Tapatalk



Have you updated the bios to the latest one? Another thing is maybe you need an nvme patch, and maybe a fresh download of the latest macOS with fresh usb media and clover, and i need you to post a IOREG and video or screenshot of the verbose!


Sent from my iPhone using Tapatalk
Link to comment
Share on other sites
twsps
twsps
Posted
Posted





Have you updated the bios to the latest one? Another thing is maybe you need an nvme patch, and maybe a fresh download of the latest macOS with fresh usb media and clover, and i need you to post a IOREG and video or screenshot of the verbose!


Sent from my iPhone using Tapatalk


Nvme patch is already included since macOS 10.12.5. 10.13.6 just released today, but I'll still stick with 13.5 right now. After the new installation with my own DSDT and SSDT, I'll give you my ioreg with latest Lilu and AppleALC you've provided

Sent from my MHA-AL00 using Tapatalk

Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted





Nvme patch is already included since macOS 10.12.5. 10.13.6 just released today, but I'll still stick with 13.5 right now. After the new installation with my own DSDT and SSDT, I'll give you my ioreg with latest Lilu and AppleALC you've provided

Sent from my MHA-AL00 using Tapatalk


A verbose also is needed, but i’ve seen strange thing in the original DSDT you can see it from the origin folder after pressing F4, the OEM Revision of that DSDT is 0x01072009, similar thing for other SSDT’s that have 0x00003000, and this means that the tables had been updated more than one time, knowing that your laptop is a new generation! Mine is only haswell 2013 but have 0x00000012, sensrhub-ssdt have 0x00000000 other have 0x00002000, this mean that it had no much updates, which means that he haven’t had much bugs, errors and such things that need really to do for it an update.

IMHO, rollback to previous bios versions and see if you’ll have same problem!


Sent from my iPhone using Tapatalk

Or update it if it’s not the case


Sent from my iPhone using Tapatalk

Link to comment
Share on other sites
twsps
twsps
Posted
Posted

A verbose also is needed, but i’ve seen strange thing in the original DSDT you can see it from the origin folder after pressing F4, the OEM Revision of that DSDT is 0x01072009, similar thing for other SSDT’s that have 0x00003000, and this means that the tables had been updated more than one time, knowing that your laptop is a new generation! Mine is only haswell 2013 but have 0x00000012, sensrhub-ssdt have 0x00000000 other have 0x00002000, this mean that it had no much updates, which means that he haven’t had much bugs, errors and such things that need really to do for it an update.

IMHO, rollback to previous bios versions and see if you’ll have same problem!


Sent from my iPhone using TapatalkOr update it if it’s not the case


Sent from my iPhone using Tapatalk

I didn't update my bios for a while. But even if I remove all dsdt and ssdt with clean clover, I would also have the same issue. So would it relate to my current dsdt or ssdt?


Sent from my iPad using Tapatalk Pro
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted

I didn't update my bios for a while. But even if I remove all dsdt and ssdt with clean clover, I would also have the same issue. So would it relate to my current dsdt or ssdt?


Sent from my iPad using Tapatalk Pro

Yes i know, but best thing is to try bios versions one by one and see, we all know that the latest versions is the one that have to be, but sometimes it’s not the case, some problems appear or disappear from bios version to another!
You’ll experiment that by yourself. This also is to try, yes do it to have mind free.


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)
7 minutes ago, twsps said:

What's the point of removing VBoxHfs? I'm curious

Sent from my MHA-AL00 using Tapatalk
 

 

 

Use what the whole community use is preferable instead of some investigation by yourself. HFSPlus is a driver owned by Apple this is why you'll not see it in the clover installer, to don't warm fire for Hackintosh community, so you'll have to put it by yourself, this is the meaning why you'll not see it. And it's the best, it's also used in other bootloaders.

Edited by ammoune78
Link to comment
Share on other sites
ammoune78
ammoune78
Posted
Posted (edited)
13 hours ago, twsps said:

Note: SSDT-XOSI is for brightness key fix

 

No, it's not for, contrariwise it's for:

 

Spoiler 

// Override for host defined _OSI to handle "Darwin"...

#ifndef NO_DEFINITIONBLOCK
DefinitionBlock("", "SSDT", 2, "hack", "_XOSI", 0)
{
#endif
    // All _OSI calls in DSDT are routed to XOSI...
    // As written, this XOSI simulates "Windows 2015" (which is Windows 10)
    // Note: According to ACPI spec, _OSI("Windows") must also return true
    //  Also, it should return true for all previous versions of Windows.
    Method(XOSI, 1)
    {
        // simulation targets
        // source: (google 'Microsoft Windows _OSI')
        //  https://docs.microsoft.com/en-us/windows-hardware/drivers/acpi/winacpi-osi
        Local0 = Package()
        {
            "Windows",              // generic Windows query
            "Windows 2001",         // Windows XP
            "Windows 2001 SP2",     // Windows XP SP2
            //"Windows 2001.1",     // Windows Server 2003
            //"Windows 2001.1 SP1", // Windows Server 2003 SP1
            "Windows 2006",         // Windows Vista
            "Windows 2006 SP1",     // Windows Vista SP1
            "Windows 2006.1",       // Windows Server 2008
            "Windows 2009",         // Windows 7/Windows Server 2008 R2
            "Windows 2012",         // Windows 8/Windows Server 2012
            "Windows 2013",         // Windows 8.1/Windows Server 2012 R2
            "Windows 2015",         // Windows 10/Windows Server TP
            //"Windows 2016",       // Windows 10, version 1607
            //"Windows 2017",       // Windows 10, version 1703
            //"Windows 2017.2",     // Windows 10, version 1709
            //"Windows 2018",       // Windows 10, version 1803
        }
        Return (Ones != Match(Local0, MEQ, Arg0, MTR, 0, 0))
    }
#ifndef NO_DEFINITIONBLOCK
}
#endif
//EOF

 

 

@RehabMan hotpatch from GitHub source for config plists

 

"_OSI abbreviation and meaning is: Open Systems Interconnection, it's used to facilitate to the computers the communication for different protocols or OSs protocole code. This is why you'll see Windows 2001 and up, in particular cases you'll have for each OS build it's own protocol under some methods and devices, briefly, how this windows build will work under some devices and methods"

 

@RehabMan give the choice for users and in some particular builds, to use OSI Windows 7 and ups with Darwin or XOSI_SSDT to tell to macOS this is the protocol that you have to follow and the one that you have to deal with.

 

 

This is why i told you, you have to know what thing you did and for what reason. The reason for me i deleted it, simply because you already used DSDT, logically if so, why removing OEM _OSI if we have DSDT in the hand, and by the way why not inserting all the things in DSDT instead of using multiple SSDT. So you have to decide to use DSDT and one CpuSsdt at all or multiple SSDT's for multiple reasons.

I personally opt for DSDT and SSDT at all, because I don't like too much things.

 

4 hours ago, twsps said:

For DellSMBiosPatch, I need this to make usb injection work.

 

 

Here also you only need a patch for USB XHC in order to work, an MBP14,1 ACPI is in our hand for that, so better inspiring from for your Inspiron ^_^ :

 

Spoiler

1521610583_ScreenShot2018-07-10at4_12_54AM.thumb.png.10fad4c28eeb498f3401731c503eae3c.png

 

This part of PNLF is Apple specific and will not help Hacki for backlight.

Related or not for your Audio or not! So better to solve other things or not my friend :D ?

Edited by ammoune78
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...