Contribute
Register

Laptop Compatibility - Sager Np8278-s

Status
Not open for further replies.
No problem. Post your DSDT.
i attached the original DSDT without the 2 patches and the 5 errors lines removed (the previous one that I had)and the one with 2 patches and i got 5 errors so i removed the lines that caused them(they are compressed in a .zip file) i think it was the same as yesterday errors so here is a picture of the errors that I got yesterday
 

Attachments

  • DSDT-2.zip
    39.8 KB · Views: 58
  • image.jpg
    image.jpg
    999.7 KB · Views: 79
i attached the original DSDT without the 2 patches and the 5 errors lines removed (the previous one that I had)and the one with 2 patches and i got 5 errors so i removed the lines that caused them(they are compressed in a .zip file) i think it was the same as yesterday errors so here is a picture of the errors that I got yesterday

You will not need to keep fixing the same errors if you keep/save your patched DSDT.dsl so adding new patches is easier.

Add to _Q12:
Code:
            Method (_Q12, 0, NotSerialized)
            {
                \RMDT.P1 ("EC _Q12 enter")
           [B]     \rmdt.p5 ("WINF/OSYS/OEMF/OEM2", WINF, OSYS, OEMF, OEM2)[/B]
...

Then do the same test. We need to find a way to disambiguate between the two keys. The secret is likely in OEM2.
 
You will not need to keep fixing the same errors if you keep/save your patched DSDT.dsl so adding new patches is easier.

Add to _Q12:
Code:
            Method (_Q12, 0, NotSerialized)
            {
                \RMDT.P1 ("EC _Q12 enter")
           [B]     \rmdt.p5 ("WINF/OSYS/OEMF/OEM2", WINF, OSYS, OEMF, OEM2)[/B]
...

Then do the same test. We need to find a way to disambiguate between the two keys. The secret is likely in OEM2.
so do i just apply this patch to DSDT and try using Console.app again ?
Note: i think its missing }
 
so do i just apply this patch to DSDT and try using Console.app again ?

It is is not a patch. It is a single line of code to be added to your existing DSDT.

You will need to reboot, then collect new output in system.log as you press the keys.
 
It is is not a patch. It is a single line of code to be added to your existing DSDT.

You will need to reboot, then collect new output in system.log as you press the keys.

this happens when i press Fn + F9
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x7, }

and this happens when i press Fn + F8 (press and hold the last digit keeps decreasing until it reaches 0x0)

Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x6, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x5, }

Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x4, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x3, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x2, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x1, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }

note: i wrote this output changes manually here beause i couldn't really find what i was looking at in console.app in system.log but here it is
 

Attachments

  • system.log.zip
    298.3 KB · Views: 41
this happens when i press Fn + F9
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x7, }

and this happens when i press Fn + F8 (press and hold the last digit keeps decreasing until it reaches 0x0)

Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x6, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x5, }

Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x4, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x3, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x2, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x1, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }

note: i wrote this output changes manually here beause i couldn't really find what i was looking at in console.app in system.log but here it is

Press each key only once. Record the associated output with each key. Also, indicate which key is up vs. down.

Also, you should add an additional patch: "OS Check Fix" https://github.com/RehabMan/Laptop-DSDT-Patch

Looking at DSDT, it seems like _Q11 should be one brigthness function, and _Q12 the other. But the system may not be initialized correctly since OSYS=0x7d0.
 
Press each key only once. Record the associated output with each key. Also, indicate which key is up vs. down.
this is up:
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x7, }

this is down:
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x6, }
Note: down starts from 0x6 and keeps decreasing if i hold until 0x0 and then keeps outputting
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }
 
this is up:
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x7, }

this is down:
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x6, }
Note: down starts from 0x6 and keeps decreasing if i hold until 0x0 and then keeps outputting
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: "EC _Q12 enter"
Nov 23 02:26:46 waleeds-MacBook-Pro kernel[0]: ACPIDebug: { "WINF/OSYS/OEMF/OEM2", 0x4, 0x7d0, 0x89c5, 0x0, }

Don't worry about repeats. Just press & release. And do each multiple times, but alternating.
 
Don't worry about repeats. Just press & release. And do each multiple times, but alternating.

alright :) but i can't seem to find that patch that you told me to apply (OS check fix)
 
Status
Not open for further replies.
Back
Top