RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,058
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Guide To Install Mavericks with Clover Bootloader
If it were me, I'd probably edit the _WAK/_PTS methods such that they don't access that SSDT...
Ok, I did as you told me and added some debug statements at the beginning and the end of those 2 methods accessing the External variable declared on the DSDT. After some testing I discovered that dropping SSDT-1 (Cpu0Ist) made these to abort before finishing. So right now I am dropping all SSDTs and using only Pike's SSDT + SSDT-1 in the Clover's patched folder.
But I don't know if this was an optimal solution. Maybe I should have dropped Cpu0Ist to avoid conflicts with Pike's SSDT, or copy "what matters" so that I avoid the DSDT methods abortion. Another possibility might be to erase on the DSDT whatever involves that external variable.
What do you think?
Attaching here original SSDT-1 and custom SSDT, just in case.
If it were me, I'd probably edit the _WAK/_PTS methods such that they don't access that SSDT...