URL: https://github.com/5T33Z0/OC-Little-Translated/tree/main/E_Compatibility_Charts

On this repo there's a work-in-progress list of compatible PCI IDs organized in dedicated .md files for each kext that may attach to certain PCI IDs (e.g. AirportItlwm, IntelMausi ecc)

Heya, I was poking around in Hopper a couple of months ago, and found the pref key for this.

So you should be able to just run defaults write com.apple.ActivityMonitor ShowGPUTab -bool true, and get the tab. It worked out of the box on my hack, and my Apple hardware (even without dGPU).

Let me know if it works for you!

An update for the Synaptics PS2 driver was just merged for Acidanthera's VoodooPS2. This changes some of the properties which the driver looks for, and removes the need for the Clickpad/Trackpad SSDTs. These are still somewhat useful if you want to change trackpoint cursor and scroll speed, or want an example of setting properties for VoodooPS2.

Also, VoodooRMI is a stable driver for these SMBus trackpads. Some older thinkpad trackpads don't support Intertouch (Synaptic's term for operating over SMBus instead of PS/2), in which case VoodooPS2Trackpad is still useful.

I have been following your work for some time and I would like to suggest some changes:

https://github.com/Baio1977/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/AC%20Adapter%20FIX%20(SSDT-AC%5CAC0%5CADP0%5CADP1%5CACAD)

you can improve the information I add

Original Patch in Maciasl by RM

Hey, just wanted to provide some corrections (and give some background) for SMBus trackpads.

You group PS/2 and SMBus together, which is a bit weird. SMBus is really a derivative of I2C, which both have much higher data bandwidth compared to PS/2. The main benefit to SMBus (and I2C) is that they send all finger coordinates at once, which the PS/2 bus is not able to do. While 99% of SMBus trackpads I've seen so far do support PS/2 connectivity, this relationship does not hold true the other way around. Many Synaptics PS/2 trackpads (generally Skylake era and older) are not connected over SMBus. Use of SMBus over PS/2 is basically always preferred for Synaptics, especially since Acidanthera's VoodooPS2 has some bugs with how buttons are handled.

SMBus trackpads are not that easy to detect. Best way in Windows is to check the name of the SMBus Controller in Device Manager. Normally, it'll be named "Intel SMBus Controller". When renamed to "Elans SMBus Controller" or "Synaptics SMBus Controller", there is an SMBus trackpad. The HID devices will always be attached to the PS/2 interface due to how the drivers work, but they really are using the higher bandwidth SMBus. In macOS, Acidanthera's VoodooPS2Trackpad will put a property in IORegistry which mentions "Intertouch Support". In Linux, just search for "RMI4" or "Intertouch" in sudo dmesg. If RMI4 appears, then it's an SMBus trackpad. The Linux method though is not that accurate, as many trackpads have to be added manually to a list in the PS/2 Synaptics driver for SMBus support.

Many Thinkpads and HP ProBooks (Ivy Bridge and newer) will use SMBus, though this is not a rule. The Thinkpad 2-in-1s like to use I2C for example. My Thinkpad X1 Extreme (Gen 1 - Coffeelake) uses SMBus, and I believe that was the case for gen 2 as well.

VoodooElans is not complete. Elans SMBus trackpads should use VoodooSMBus from the VoodooSMBus repo. The VoodooSMBus that comes with VoodooRMI is built on a different branch and has different functionality.

Also, VoodooRMI works for Synaptics I2C trackpads. Probably best to replace VoodooI2CSynaptics with it, as VoodooRMI fixes some bugs and has more functionality in general. It also supports the F12 trackpads.

Edit:
If you've got extra questions, feel free to ask them. It can get confusing.

Hi,
I'm opening this issue just to make some suggestions:

1. Enable commit verification (https://docs.github.com/en/authentication/managing-commit-signature-verification)
2. Using better commit names. Way more readable than "Update README.md"

https://github.com/5T33Z0/OC-Little-Translated/tree/main/D_Updating_OpenCore#for-users-updating-from-opencore-065-or-lower

Should be "Updating Bootstrap"

Link: https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/Intel_I225-V_Fix_(SSDT-I225V)#user-content-fnref-3-52460499954034579036b340dcb4d433=

Issue: Combining Vt-D and DisableIOMapper makes no sense to me but that's what the user reported as working.

In case you need VT-d features on other OSs (e.g. Linux with KVM), it absolutely makes sense enabling both VT-d and DisableIOMapper

I2C Hackintosh: I'm adding two patches widely used in hacks, SSDT-USTP and SSDT-SPED.
I can't find the right information to attach, maybe you can find more info about it.
In some hacks I have had, I have used these patches to get the trackpad working , here (https://github.com/Baio1977/Acer-Aspire-E5-574G)

Example ACER ACPI DSDT analysis: I look for USTP and it looks like in the picture.
I could define USTP as a kind of Bus Sped for I2C

and here (https://github.com/Baio1977/DELL-Inspiron-5584)
in these two configurations SSDT-USTP + rename in ACER and on DELL SSDT-SPED is fundamental.

Work added :
I2C Other Fixes
SSDT-I2C0\I2C1_USPT :

When to use it ?? : Laptop from 6th to 10th(CometLake) Gen CPU , after analysis of the ACPI.
In combination with SSDT USTP it modifies the config.plist ACPI-Patch section integrates the Rename :

Find USTP: 55 53 54 50 08
Replace XSTP: 58 53 54 50 08

SSDT-I2C0\I2C1_SPED : Looking for information. DELL 5584 claims this SSDT, without non-working trackpad.It may happen that you read an error in verbose mode by starting the PC they concern SSCN FMCN this is hard to notice when everything is working fine.

Hi,
I was a little bit bored today and created a repository that explains how to reduce the weight of IntelBluetoothFirmware (from ~7.2MB to less than 1MB).
I know that it's not that useful, but at least you'll have a slim kext.

For more infos check my repo

Hi, and thank you so much for the shared knowledge over the months.
I actually came up to this page that explains how to disable unsupported GPUs but noticed a few errors:

1. Both -wegnoegpu and disable-external-gpu require WhateverGreen.kext injected
2. In case of multiple dGPUs systems (e.g. 4090+RX6800XT) the wisest way would be, after proper checking the definition of pci-bridges, use DeviceProperties and therefore use disable-gpu property.

I hope you will find this info useful somehow.
Have a nice day

--
dreamwhite

External (SB.SLPB._STA, MethodObj) returns compile error in .asl.
Solution:
External (SB.SLPB._STA, UnknownObj)

Thanks as always

Hi, I followed a topic on tonymacx86 to come this page, Thanks for your great job.

I have a Radeon VII 16G graphic card, but dont find its @0,name, could you help me with this?

Thank you so much!

Hi, Can you please help me to find the internal mic nodes.
Speaker, Headphone and Ext. input seems OK, but no int. mic.
I have attached the output and the codec dump, please suggest me the possible solutions.
Thank you
output.zip

SSDT-Navi-Vega56\64.aml.zip

Simplified SSDT so that you have fewer problems in OS.
Studying ACPI and Ioreg real Macs I noticed that Navi and Vega are named as in posted SSDT.
See ImacPro 1.1

Good evening. You have
11. Alternatively you can set AAPL,slot-name to build-in
and
ricoc90 and miliuco for for macOS 13 GPU Testing Utility
Excellent work, as usual.

https://github.com/5T33Z0/OC-Little-Translated/tree/main/01_Adding_missing_Devices_and_enabling_Features/Platform_Power_Management_(SSDT-PPMC)

Hello I'm back to breaking the boxes, this search section in screen is not correct

As in your case, the search is at ACPI level, the correct thing is to search IOService in order to see if the device is loaded correctly by the system.Not all devices in ACPI are loaded by the system, also thanks to the choices of SMBios etc. etc.

So it is correct

Thanks as always and sorry, I try to help you make this guide better

I'm specifically looking for a laptop ice lake 10th gen i3 CPU

OCLP detected Modern Wireless (BCM4360), installed root patches, rebooted.
Wifi/BT shows up now, but when I try to connect to wifi (after inputting password).
macOS crashes, panic and reboots.

panic(cpu 12 caller 0xffffff801d1878d3): Kernel trap at 0xffffff8020e35fa8, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000160, CR3: 0x0000000021d6c000, CR4: 0x00000000003406e0
RAX: 0x00000000fffffff2, RBX: 0xffffff86a5cdf400, RCX: 0x0000000000002aab, RDX: 0xffffffcc2d7c734c
RSP: 0xffffffcc2d7c7310, RBP: 0xffffffcc2d7c7310, RSI: 0xffffffcc2d7c7687, RDI: 0x0000000000000000
R8: 0xffffffcc2d7c72d8, R9: 0x0000000000000001, R10: 0x0000000000000002, R11: 0x000000000000000b
R12: 0xffffff950abaf000, R13: 0xffffff86a5a7b800, R14: 0xffffff86a5ce8400, R15: 0xffffffcc2d7c7687
RFL: 0x0000000000010246, RIP: 0xffffff8020e35fa8, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000160, Error code: 0x0000000000000000, Fault CPU: 0xc VMM, PL: 0, VF: 1

Panicked task 0xffffff86a5916218: 342 threads: pid 0: kernel_task
Backtrace (CPU 12), panicked thread: 0xffffff86a643c5a8, Frame : Return Address
0xffffffcc2d7c6c90 : 0xffffff801d03a211
0xffffffcc2d7c6ce0 : 0xffffff801d197ce0
0xffffffcc2d7c6d20 : 0xffffff801d18742c
0xffffffcc2d7c6da0 : 0xffffff801cfd6951
0xffffffcc2d7c6dc0 : 0xffffff801d03a4fd
0xffffffcc2d7c6eb0 : 0xffffff801d039ba3
0xffffffcc2d7c6f10 : 0xffffff801d7d91ab
0xffffffcc2d7c7000 : 0xffffff801d1878d3
0xffffffcc2d7c7180 : 0xffffff801d1875b7
0xffffffcc2d7c7200 : 0xffffff801cfd6951
0xffffffcc2d7c7220 : 0xffffff8020e35fa8
0xffffffcc2d7c7310 : 0xffffff8020bf102e
0xffffffcc2d7c76e0 : 0xffffff8020c9a86c
0xffffffcc2d7c78a0 : 0xffffff8020ca09bc
0xffffffcc2d7c7950 : 0xffffff8020cc6267
0xffffffcc2d7c7b00 : 0xffffff8020ca1caa
0xffffffcc2d7c7b50 : 0xffffff8020bb23d9
0xffffffcc2d7c7b80 : 0xffffff8020bc07d4
0xffffffcc2d7c7ca0 : 0xffffff8020bbe488
0xffffffcc2d7c7d40 : 0xffffff8020bd3813
0xffffffcc2d7c7da0 : 0xffffff8020a402ec
0xffffffcc2d7c7de0 : 0xffffff8020a4097d
0xffffffcc2d7c7e30 : 0xffffff8020a40a3d
0xffffffcc2d7c7e40 : 0xffffff801d710618
0xffffffcc2d7c7ea0 : 0xffffff801d093b28
0xffffffcc2d7c7ee0 : 0xffffff801d094bb8
0xffffffcc2d7c7fa0 : 0xffffff801cfd619e
Kernel Extensions in backtrace:
com.apple.iokit.IO80211FamilyLegacy(1200.12.2b1)[4C07538B-62EB-3D6D-AEF9-93BCDCF45FAB]com.apple.0xffffff8020970000-com.apple.driver.0xffffff8020b56fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[26773101-4F1A-339A-9597-EF2645721A3F]com.apple.0xffffff801e660000-com.apple.driver.0xffffff801e696fff
dependency: com.apple.driver.corecapture(1.0.4)[0DED4F91-AC29-379C-9A48-83E6009E40F0]com.apple.0xffffff801fb55000-com.apple.driver.0xffffff801fb77fff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[4A31F7E7-78EA-39E5-BD87-85AC3D4D3AE4]com.apple.0xffffff801ea3d000-com.apple.driver.0xffffff801ea46fff
dependency: com.apple.iokit.IONetworkingFamily(3.4)[7350A38C-B7AE-3627-867C-48504D02BA13]com.apple.0xffffff801f0af000-com.apple.driver.0xffffff801f0c6fff
dependency: com.apple.iokit.IOSkywalkFamily(1.0)[035A9AD9-6CDE-362F-8DEC-B664BC6431EC]com.apple.0xffffff80208a2000-com.apple.driver.0xffffff8020960fff
dependency: com.apple.kec.corecrypto(14.0)[9A9FD228-3123-32AE-9761-042B08D57A85]com.apple.0xffffff801fb86000-com.apple.driver.0xffffff801fc01fff
com.apple.driver.AirPort.BrcmNIC(1400.1.1)[E4678FEB-1DC1-35CC-9306-48021083D04A]com.apple.0xffffff8020b7a000-com.apple.driver.0xffffff80213f1fff
dependency: com.apple.driver.corecapture(1.0.4)[0DED4F91-AC29-379C-9A48-83E6009E40F0]com.apple.0xffffff801fb55000-com.apple.driver.0xffffff801fb77fff
dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[14410048-29B3-3126-BE24-D2A0BD5DFE52]com.apple.0xffffff801f309000-com.apple.driver.0xffffff801f30dfff
dependency: com.apple.iokit.IO80211FamilyLegacy(1200.12.2b1)[4C07538B-62EB-3D6D-AEF9-93BCDCF45FAB]com.apple.0xffffff8020970000-com.apple.driver.0xffffff8020b56fff
dependency: com.apple.iokit.IONetworkingFamily(3.4)[7350A38C-B7AE-3627-867C-48504D02BA13]com.apple.0xffffff801f0af000-com.apple.driver.0xffffff801f0c6fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6A0762A3-54A1-3652-932A-99F3B8E3D842]com.apple.0xffffff801f310000-com.apple.driver.0xffffff801f341fff
dependency: com.apple.iokit.IOSkywalkFamily(1.0)[035A9AD9-6CDE-362F-8DEC-B664BC6431EC]com.apple.0xffffff80208a2000-com.apple.driver.0xffffff8020960fff
[panic-2023-09-09-073334.txt]

(https://github.com/5T33Z0/OC-Little-Translated/files/12565242/panic-2023-09-09-073334.txt)

Hi,
Problem: real MacbookPro10,1 running Big Sur 11.7.9 setup via clean install using OCLP 0.6.8. all went well. Problem is in SystemPreferences under Software update, it not showing Ventura as an available Update.

I followed your guide: 09_Board-ID_VMM-Spoof and tried both Option 1 and Option 2 methods to get OTA listed but neither works.

Solution: (not ideal)
The only way I could get Ventura listed as an Update was to set Cpuid1Data and Cpuid1Mask = 0x00000000000000000000008000000000

OCLP 0.6.8 now uses AMFIPass.kext.
OCLP for this real rMBP10,1 sets revpatch=f16c which is suppose to fix a potential issue with iGPU. Anyway, I changed it to sbvmm but it did not help.

Any ideas ?
Could it be that the FirmwareFeatures needs to be setup in PlatformInfo ?
OCLP generated config.plist attached:
config-original.plist.zip

https://github.com/corpnewt/ACPIRename , It is used to generate Rename, after analysis of the DSDT origin.

I'm kinda lost into your guides, can you redirect where I can spoof mine as well?

Hi,
me and @1alessandro1 collected a few charts, collected from forums. Let me know if you wanna use them in your repo:

• SSD
• NVRAM
• Kexts

I followed the guide and added everything besides the amfipass kext since that requires macos to get, I installed Ventura successfully on my Ivy Bridge but after running OCLP and installing the root patch graphics don't initialize upon boot. Here is my config
https://drive.google.com/file/d/1aYWgFfmDa0-e1vwY7n-ENJhMu4gbK9Lf/view?usp=sharing

Hallo,

Du, ist das bei deinen Rechnern auch so oder hast du ähnliche Erfahrung mit dem AppleIGC.kext ?
Ich schildere zunächst mal das ganze ist situation.

Ich kann ohne den AppleIGC.kext problemlos den Lan Adapter Unter Monterey & Ventura starten.
Ohne den Modern Wifi patch vom OCLP unter Sonoma funktioniert die I225-V v3 auch.
Mit dem patch funktioniert die Wifi aber plötzlich kann die Intel I225-V v3 keine DHPC adresse vom Fritzbox beziehen.
Daraufhin kam ich von dir auf diese AppleIGC.kext, mit dem kext funktioniert die Intel I225-V v3 vom Catalina bis Sonoma sehr gut aber mit dem Kext kann der rechner nicht mehr in den Sleep rübergehen.
Es endet mit einem KP. Ohne Kext hab ich zwar mein Sleep wieder aber diesmal unter Sonoma kein DHCP.
Die Kext ist irgendwie mit SATA/AHCI (AppleAHCIDiskQueueManager) in konflikt.
Hab auch bemerkt das es mit dem Kext die Recovery Modus nicht startbar ist.
Irgend eine Idee dazu?

Gruss Coban

kernelPanicSleep MSIz590.txt

As Monterey 12.3 dropped Python2 pre-built binaries, users need to download Python 2.7.18 installer. Official download link

Hello great

All the repo is an excellent job but I've just read the AMFIPass chapter and I must say that it's amazing.
It's a confused topic yet for a lot of users but this text clarifies all in a very understandable way.
Congrats!!!

Is there any reason in this guide there are some useless SSDT that don't add any "feature" on macOS?
I'm talking about:

• SSDT-ARTC (see also this)
• SSDT-FWHD
• SSDT-XSPI

I'd rather drop them rather than clogging uselessly ACPI tables as o*****a does...

Please read this PR also: acidanthera/OpenCorePkg#121 (comment)

Not an issue, merely a report/suggestion:

After combining all my DSDT, I noticed that there was significant room for further improvements by reordering and cleaning up the various patches so they go down in descending order:

Example below

And therefore streamlining the execution, reduces the size of the file and eliminating a lot of Scope calls and simplifying device pathing.

I'm making the SSDT patch but ran into something:

While finding the name and path of my Graphics card in IORegistry Explorer, I see a value but also a bridge, which the guide says to watch out for, and the two Terminal commands return nothing, so there's multiple red flags according to the guide.

My IORegistry: https://ibb.co/P9M8tBm

But I have a Sapphire Vega 64 which is fairly common. Will this SSDT not work?

If it helps, here is the audio device in Hackintool: https://ibb.co/XCrJ6QY

Thanks!

Its always hang/stall on the second boot, should i do post insall patches then to my plist. Add amfipass kext then delete amfi getout of my way and amfi=80 then reboot?

Hi Guys and congratulations 5T33Z0 for the immense work you have done, it was very helpful to me to revive an old Haswell 2014 laptop. My question is: I am trying to integrate the SSDT-PTSWAKTTS, but the system does not create me the PCI9 Device for inserting patches (in IORegistryExplorer it is present only under: ACPIPlane but not in IOService). Do I forget or am I wrong something? Thanks in advance...!

Good morning,
in this section : https://github.com/5T33Z0/OC-Little-Translated/tree/main/04_Fixing_Sleep_and_Wake_Issues/060D_Instant_Wake_Fix/i%20Common%20060D%20Patch
It is suggested to rename 0x6D, 0x03/04 to 0x6D, 0x00 using a patch for those _PRW that are defined as a PackageObj.
It should also work a simple SSDT hotpatch without renames that could be eventually merged with SSDT-GPRW.

DefinitionBlock ("", "SSDT", 2, "OCLT", "GPRW", 0x00000000)
{
    External (_SB_.PCI0.XHC_._PRW, PkgObj) //Pathway of the _PRW of our interest

        If (_OSI ("Darwin"))
        {
            \_SB.PCI0.XHC._PRW [One] = 0x00
        }
       
}

Renames such as 0x6D, 0x03/04 to something else can create problems in other parts of the DSDT.

Hi there,
in my spare time I created a GitHub repository containing all the possible layout-ids per codec extracted directly from latest AppleALC source.

You can consult it here.
Let me know your thoughts

https://github.com/5T33Z0/OC-Little-Translated/blob/main/04_Fixing_Sleep_and_Wake_Issues/060D_Instant_Wake_Fix/i_Common_060D_Patch/SSDT-XPRW.dsl

"""
If (_OSI ("Darwin")){
"""

it must stand after the Method in this case.

Use standard GPRW or UPRW SSDT.

SSDT-GPRW.dsl.zip

SSDT-UPRW.dsl.zip

Link: https://github.com/5T33Z0/OC-Little-Translated/blob/main/01_Adding_missing_Devices_and_enabling_Features/System_Clock_(SSDT-AWAC)/SSDT-AWAC_STA0.dsl

As per ACPI 6.4. specs, _STA is a method, therefore you can't assign it as a local variable. I'd rather delete this SSDT as STAS variable patching is way cleaner and compliant.

Same speech with https://github.com/5T33Z0/OC-Little-Translated/blob/main/01_Adding_missing_Devices_and_enabling_Features/System_Clock_(SSDT-RTC0)/SSDT-RTC_STA0F.dsl

I have tested this change on various Hackintoshes and it works Opencore starts Windows regularly and everything works as it should
SSDT-PNLF GFX0
Archivio.zip

Hello!

Is there a possibility to disable a specific M.2 slot? I am assuming I should be using a custom SSDT (but don't know how)

With a friend of mine, I created a handy script to read in human-readable form the file generated by OpenCore SysReport PCIInfo.txt.
This saves a lot of time when having to deal with obtaining info about every PCI device connected on the motherboard.

You can read more here

Before I‘m using these patches to make macOS install and boot with unsupported SMBIOS:

But today I find the RestrictEvents have update with VMM support so I tried the new commit.

1. Delete all the vmm kernel patch but reserve the 2 boot patches.
2. Using the RestrictEvents with new commit.
3. Stay boot-arg: revpatch=sbvmm.
4. Reboot and it works.

I have tested in install and macOS have no problem.

But when into macOS the
kern.hv_vmm_present: 0

Do you think your guide works for this Graphics card AMD Radeon Pro W6400

Its a card base AMD RDNA2 Architecture, It is Navi 24 XL not 21 or 23

Thanks for the guide

Check my Fork, I have added alternative methods for SSDT-SLPB_STA0B.
Tested and modified addresses of some SSDTs, for example SSDT-ALSD before it was under _SB and INI method, now under \ removed INI method.
Besides these other minor changes.
Everything I have entered and edited has been tested.
Thanks as always.

EDIT: I have ioreg of the tests done, in case you want proof.

macOS 13 Sonoma ❌
macOS 14 Sonoma ✅

Link: https://github.com/5T33Z0/OC-Little-Translated/tree/main/10_Kexts_Loading_Sequence_Examples#kernel-support-table

If I use SSDT-AWAC-ARTC.asl, I need to delete the HPET table. Would the double system affect the Windows system.
Would the use of SSDT-AWAC-ARTC.asl affect the Windows system？

Hi,

After trying to apply a new Layout ID 18 for ALC 280 I am getting a Kernel Panic. I am able to successfully build and use a vanilla version of AppleALC, but with my changes it goes wrong. Do you have any ideas?

acidanthera/AppleALC@master...james090500:AppleALC:master

Hi 5T33Z0.

Thank you for your contribution to the community. you are wonderful. Wish you have a good day.

Last month i was install macos on my laptop Lenovo Thinkpad T470S. My Laptop Specs:

• Processor and Chipset: Intel Core i5 6300u
• Graphics: Intel HD 520
• Storage: SN530
• RAM: 12 GB DDR4
• 1 x Synaptics SMBUS Trackpad + Trackpoint
• 1 x PS/2 Keyboard
• 1 x USB 3.0 card reader
• 3 x USB 3.0 type a ports
• 1 x TB3/USB C port
• 1 x HDMI port
• 1 x 3.5mm mic/headphone jack
• Dual Battery

I have researched and learned that my Laptop has 2 batteries and I have learned a bit of ACPI code and patched SSDT-BATC. I use SSDT-BATC included with ECEnabler.kext and Battery works

I thought everything was fine but no. I realized that my battery is only taking half its capacity. My battery as far as I know it has ~4k4 mAh but the macos side only receives ~2k mAh. I have searched and patched a lot but the number still only stops at 1k8. With such a battery capacity, I cannot use it without a charger. help me please. I spent a month trying to fix my battery but failed. if not fix my battery is too low and can not be used without charging 24/24. I can't watch youtube (1920x1080) more than 30p, only about ~30p my laptop is out of battery.... i also used kext CPUFriend + CPUFriendFriend (with 800mhz ) because i think its CPU problem but NOT... I'm really helpless right now. please help me...thank you very much

Here is my DSDT and SSDT i use for Battery ( work but with very small capacity )

• i use SSDT-BATX.dsl without patch BAT0,1 to BATX because i just use it for fix battery 16,32 and 128 byte ( i dont use ECEnabler because its make my battery has been reported for maintenance - and still low capacity )
• SSDT-BATC for Notify BAT0 and BAT1 ( i also have rename Patch )
• SSDT-BATT.am. I found it on Oclittle github ( I don't know if it helpful or not )

DSDT and SSDTs.zip

And here is my EFI:

https://drive.google.com/file/d/19fNSEdeseKGWO_skEzErd6cl-MeoM6s6/view?usp=drive_link

THANK YOU VERY MUCH

Hi @5T33Z0

Extract AMFIPass-v1.2.1 without installing OCLP-AMFIPass

Simple bash script command
AMFIPass-v1.2.1-Extract.zip

• script command

#!/bin/bash
# Extract AMFIPass.kext
# By chris1111
rm -rf $HOME/Desktop/AMFIPass-v1.2.1-RELEASE.zip
# get AMFIPass path
if [ "$2" == "" ]; then

echo -n "Please move to terminal window ➤  \ OpenCore-Patcher.app \ 
Followed by ENTER: "

while [ -z "$AMFIPass" ]; do
read AMFIPass
done
if [ ! -d "$AMFIPass" ]; then echo "$AMFIPass not found"; exit; fi 
else
AMFIPass="$2"
fi
 
# open Installer.app
echo -n password | hdiutil attach -stdinpass -owners on -nobrowse -noverify -mountpoint /tmp/AMFI "$AMFIPass"/Contents/Resources/payloads.dmg

cp -Rp /tmp/AMFI/Kexts/Acidanthera/AMFIPass-v1.2.1-RELEASE.zip $HOME/Desktop
Sleep 1
Umount -f /tmp/AMFI

echo "Done ➤ $HOME/Desktop/AMFIPass-v1.2.1-RELEASE.zip"

Given that it's pretty useless and counter-productive when debugging, it would be nice to write a small guide that explains how to write a unified SSDT once you're done with your ACPI.

I'll try summing up things:

• first of all create a folder where you'll make your tests
• for each SSDT disassemble it in .dsl and remove DefinitionBlock (e.g. iasl SSDT*.aml)
• create a dummy SSDT that contains the following code:

DefinitionBlock("", "SSDT", 2, "AUTHOR", "HACKSSDT", 0)
{
    #include "SSDT-X.dsl"
    ...

}

• compile using iasl SSDT-FINAL.dsl and make sure you're not having errors

Make sure to change AUTHOR and HACKSSDT with your favourite names as well as adding an #include "SSDT-Y.dsl" directive for each SSDT. See the below example:

1. folder with disassembled SSDTs

2. removed DefinitionBlock for each SSDT. e.g.

3. SSDT with final stuff

Please note that in case you're having issue like Existing object has invalid type for Scope operator (_SB.PCI0 [Untyped]) add as an external reference in the final SSDT External (_SB.PCI0, DeviceObj) like below:

Currently, my machine only has 2 network adapters:

• Marvell AVASTAR 88W8897 Wi-Fi card
• HoRNDIS.kext for Android tethering

In the picture, you can see that only the USB (HoRNDIS) is shown in the list, with en0 marked as not built-in.

I have tried to make HoRNDIS built-in, iServices does not work however. I have also tried to make the incompatible Wi-Fi card as built-in, does not work either.

Is there any patches I can do to make iServices work?