Contribute
Register

[Guide] Laptop backlight control using AppleBacklightFixup.kext

how about now? patched DSDT without brightness patch. Is there still conflict?
DSDT attached.
 

Attachments

  • DSDT.aml
    40.5 KB · Views: 208
Also, it is possible you're not reading the debug output correctly, and it is actually being patched...
In that case, try the attached injector (remove AppleBacklightInjector.kext when using it). Reply with "Problem Reporting" files.
The slider is now present with partial brightness controls
 

Attachments

  • backlightt300la.zip
    2.6 MB · Views: 126
The slider is now present with partial brightness controls

You can see that AppleBacklight is using "F%uP%04x" instead of "F%uT%04x".
I don't know exactly what causes AppleBacklight.kext to use the different format specifiers.
I have added the necessary patch to config_patches.plist, and the necessary entries to AppleBacklightInjector.kext.

I don't know what you mean by "partial"...

Note: You should keep the name SSDT-PNLF.aml... (I see you renamed it to SSDT-14.aml which is just confusing).
 
I don't know what you mean by "partial"...
the display is very dark
bklt value 0x54
brightness max 0x400
the lowest brightness i get 0x160
 
the display is very dark
bklt value 0x54
brightness max 0x400
the lowest brightness i get 0x160

May be because of your ig-platform-id choice.
Use 0xa260006 instead.
 
May be because of your ig-platform-id choice.
Use 0xa260006 instead.

0x0a160000 uses 0xad9 too
i switched over to 0x0a260006
still says 0x54
 
0x0a160000 uses 0xad9 too
i switched over to 0x0a260006
still says 0x54

I realize it uses 0xad9.
But you're mapping to a different AppleBacklight format (FxxPxxxx instead of FxxTxxxx).
There are no FxxPxxxx profiles in AppleBacklight that appear to be for 0xad9/Haswell.
You may need to determine why.
It might have to do with your SMBIOS setup.
 
Back
Top