Contribute
Register

[Guide] Patching LAPTOP DSDT/SSDTs

okay I don't rename anything is same like you wrote about this all good new but about _dsm mode what I need to do in dsdt leave that mode what I change manual or replace it original in _XDSM?

The VoodooI2C.kext expects to call _DSM methods in the related part of DSDT...
So don't rename those _DSM methods.
I suggested a change to the kext to allow both _DSM and XDSM, but I don't think the developer ever made my suggested change...
 
and I got same panic :( I dont understand whats wrong now :(
 

Attachments

  • RehabMantautvispanic.zip
    2.7 MB · Views: 77
and I got same panic :( I dont understand whats wrong now :(

No image provided of panic.
One of your I2C _DSM methods is renamed XDSM.

Your SSDT.aml is a duplicate of SSDT-0.aml.
SSDT.aml should be from ssdtPRgen.sh.
 
No image provided of panic.
One of your I2C _DSM methods is renamed XDSM.

Your SSDT.aml is a duplicate of SSDT-0.aml.
SSDT.aml should be from ssdtPRgen.sh.
but I look in my dsdt and I see all i2c is xdsm so all change to _DSM ?
 

Attachments

  • not running 2.zip
    625.6 KB · Views: 63
Look in your nvram.plist. You can see backlight-level is invalid (0xffff).
Maybe you did not install "RC scripts" or your rc scripts are not up-to-date.
Your Clover revision is old.

And further discussion here about NVRAM is off-topic, as it has nothing to do with ACPI.
Okay Sorry!! Can i update so for fixing? Thanks
 
but I look in my dsdt and I see all i2c is xdsm so all change to _DSM ?

You will need to understand which _DSM methods the VoodooI2C.kext expects to call.
And then avoid renaming those to XDSM.
 
You will need to understand which _DSM methods the VoodooI2C.kext expects to call.
And then avoid renaming those to XDSM.
I as blankman who help me with my touch pad and say everything with I2c all good and I dont get were Im done mistake for this issue :(
 
I as blankman who help me with my touch pad and say everything with I2c all good and I dont get were Im done mistake for this issue :(

You will need to understand which _DSM method the kext expects to call...
You should look at your ACPI for the case that VoodooI2C.kext wasn't patched.
For myself, I would just fix the kext.
 
mmm.. please, need help
first, thanks to the moderator for pulling me to this thread, now.. how do i take control of my processor frequency so it's gonna be stay still at the lowest freq but not that always stays at lowest.. eg for editing some videos or some apps taht need high frequency
 
Back
Top