Contribute
Register

[Guide] Patching LAPTOP DSDT/SSDTs

telepati said:
@RehabMan

Hi, I added my all patched SSDT to my new DSDT 'cause I want to clear my ACPI/patched folder. Now inside my ACPI/patched folder one SSDT for power management, one DSDT I created and USB port SSDT.

I added all @toleda sound SSDT patched, LPC SSDT, @goodwin_c HD530 patched, Pike's sleep codes to my DSDT without no error, remark and warnings.

But I can't boot with just DSDT?

I remove DSDT and add all SSDTs to ACPI/patched folder this time I can boot without any problem.

Could you please check my DSDT what is it wrong?
Click to expand...

I really can't tell from that text what exactly you're doing.
If you have an issue booting...
Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).

And also, I don't know why you're using desktop solutions on your laptop...
 
Move to this thread.
I am follow your guide strictly. The disassembled dsl code can compile without error.
May be "_OS" is predefined object?
 
livacore said:
Move to this thread.
I am follow your guide strictly. The disassembled dsl code can compile without error.
May be "_OS" is predefined object?
Click to expand...

Not possible to answer your questions without the files...
Attach native ACPI files as extracted with Clover F4 (ACPI/origin).
 
livacore said:
Here it is:
https://www.tonymacx86.com/attachments/rehabman-zip.226778/
Click to expand...

There are no errors in the resulting DSDT.dsl if you disassemble correctly:
iasl -da -dl -fe refs.txt DSDT.aml SSDT*.aml

Must use the correct tools. They are linked from post #1.

Another question: Which code calls L62 GPE method? I only see WNIC._PRW calls L69. Does L62 called by implicit grammar?
Click to expand...

_L62 is a "general purpose event". It is called by the GPE driver when the corresponding event is generated by the hardware.
Read about it in the ACPI spec.
 
RehabMan said:
It is called by the GPE driver when the corresponding event is generated by the hardware.
Click to expand...
Could you spend time to explain? Which event trigger _L62? Thx.
From my opinion, and reading ACPI spec, there may be a method object in a device scope to call it:
Code: 
Method(_TST, ...) // TEST DEMO
{
  return package(0x2) { 0x62, 0x?? }
}
Maybe my understanding is wrong..
 
livacore said:
Could you spend time to explain? Which event trigger _L62? Thx.
From my opinion, and reading ACPI spec, there may be a method object in a device scope to call it:
Code: 
Method(_TST, ...) // TEST DEMO
{
  return package(0x2) { 0x62, 0x?? }
}
Maybe my understanding is wrong..
Click to expand...

Looking at the code in _L62 leads me to believe it has something to do with the wireless button/key on your laptop.
 
RehabMan said:
Looking at the code in _L62 leads me to believe it has something to do with the wireless button/key on your laptop.
Click to expand...
Yup :)
I collected dmesg with debug info from my laptop running Yosemite (DW1820A works fine in 10.10) and another box (ECS liva core, DW1820A works fine in 10.11 on this device).
Then disassemble Airport Brcm4360 to compare what works, what not works. And read ACPI code to figure out why DW1820A cannot working in10.11on my laptop.
Any help info?
 
livacore said:
Yup :)
I collected dmesg with debug info from my laptop running Yosemite (DW1820A works fine in 10.10) and another box (ECS liva core, DW1820A works fine in 10.11 on this device).
Then disassemble Airport Brcm4360 to compare what works, what not works. And read ACPI code to figure out why DW1820A cannot working in10.11on my laptop.
Any help info?
Click to expand...

What is not working?
 
RehabMan said:
What is not working?
Click to expand...
DW820A WIFI not working in 10.11.x on my laptop, but works in 10.10.
Same card works fine in both 10.10 and 10.11 on another device ( ECS liva core).

So I think this a device-specific problem, and I am trying to figure out the problem in which part. Guess ACPI related.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top