Contribute
Register

[Guide] Laptop backlight control using AppleBacklightFixup.kext

Hi, RehabMan, I had tried twice, but the brightness bar doesn't work. Can you help me find where the problem is?

Thanks!

Code:
kextstat|grep -y acpiplat
kextstat|grep -y appleintelcpu
kextstat|grep -y applelpc
kextstat|grep -y applehda

   13    2 0xffffff7f830c9000 0x60000    0x60000    com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>
   24    0 0xffffff7f82cd0000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (219.0.0) C2841490-D1F6-30D4-AC81-48D63A8FA04C <7 6 5 4 3 1>
   34    0 0xffffff7f82ccb000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (219.0.0) B802638B-251C-3602-BA8C-001F87228765 <7 6 5 4 3 1>
   98    0 0xffffff7f829a4000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <96 12 5 4 3>
  104    1 0xffffff7f82d7e000 0x1d000    0x1d000    com.apple.driver.AppleHDAController (279.48) ED51F180-19C8-3DE1-AF81-0E389D98ADDE <103 102 86 12 7 6 5 4 3 1>
  125    0 0xffffff7f82f00000 0xb5000    0xb5000    com.apple.driver.AppleHDA (279.48) 806B8C17-50CA-3C6B-90B3-195F38D8FB89 <124 107 104 103 102 86 6 5 4 3 1>


➜  sudo touch /System/Library/Extensions && sudo kextcache -u /

kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelCPUPowerManagement.kext
KernelCache ID: FFA127AFB61E4595B79774B0A513F3E8

No laptop hardware details in your profile (please fix as per FAQ).
But your laptop probably does not use the IGPU PWM registers for backlight control.
 
No laptop hardware details in your profile (please fix as per FAQ).
But your laptop probably does not use the IGPU PWM registers for backlight control.

My laptop is Clevo P151em

Code:
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
Intel HD Graphics 4000
Audio ALC892
WIFI/BT BCM94352

My laptop works fine with ACPIBacklight.kext in 10.12.3, it doesn't work with IntelBacklight.kext all the time.
As you said, I guess my laptop does not use the IGPU PWM registers for backlight control, but.. can this problem be solved?

Thanks again.
 
My laptop is Clevo P151em

Code:
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
Intel HD Graphics 4000
Audio ALC892
WIFI/BT BCM94352

My laptop works fine with ACPIBacklight.kext in 10.12.3, it doesn't work with IntelBacklight.kext all the time.
As you said, I guess my laptop does not use the IGPU PWM registers for backlight control, but.. can this problem be solved?

Thanks again.

ACPIBacklight.kext does not work on 10.12.4.
As your laptop requires it, you will need to wait until a fix is found for it, or go back to 10.12.3 (or 10.11.6).
 
ACPIBacklight.kext does not work on 10.12.4.
As your laptop requires it, you will need to wait until a fix is found for it, or go back to 10.12.3 (or 10.11.6).

Thank you very much !
 
It is likely your NVRAM is broken (keep in mind EmuVariableUefi-64.efi requires "RC scripts"... and keep in mind Skylake+ computers usually have incompatible UEFI NVRAM, so require EmuVariableUefi-64.efi + RC scripts).

You should check your NVRAM setup.

And read post #1, "Problem Reporting".
Thanks Rehabman. How can I check if my NVRAM is working? If not, how to add EmuVariableUefi-64.efi + RC scripts to fix this?
 
Thanks Rehabman. How can I check if my NVRAM is working? If not, how to add EmuVariableUefi-64.efi + RC scripts to fix this?

You can test NVRAM by setting an NVRAM variable, rebooting, then checking if the variable is still in NVRAM.
For example, in Terminal:
Code:
sudo nvram Test=4567
nvram Test #should print "Test 4567"
sudo reboot
# upon reboot...
nvram Test #should print "Test 4567"

EmuVariable and RC scripts are options in the Clover installer.
 
You can test NVRAM by setting an NVRAM variable, rebooting, then checking if the variable is still in NVRAM.
For example, in Terminal:
Code:
sudo nvram Test=4567
nvram Test #should print "Test 4567"
sudo reboot
# upon reboot...
nvram Test #should print "Test 4567"

EmuVariable and RC scripts are options in the Clover installer.
Thanks Rehabman. Looks like the value is retain in NVRAM after reboot. This means my NVRAM is working.

I see the below value for backlight level in NVRAM
<key>backlight-level</key>
<data>
9gA=
</data>
 
Thanks Rehabman. Looks like the value is retain in NVRAM after reboot. This means my NVRAM is working.

I see the below value for backlight level in NVRAM
<key>backlight-level</key>
<data>
9gA=
</data>

Code:
SPEEDY-NUC:Downloads rehabman$ pbpaste|base64 --decode|xxd
00000000: f600

You need to analyze what happens with that value... check your Clover bootlog.
And how it relates to the last setting of backlight-level before you rebooted.
 
Code:
SPEEDY-NUC:Downloads rehabman$ pbpaste|base64 --decode|xxd
00000000: f600

You need to analyze what happens with that value... check your Clover bootlog.
And how it relates to the last setting of backlight-level before you rebooted.


Thanks Rehabman finally got it working by removing default backlight value from config.plist
 
hello ! here are my files if someone can take a look. thanks!
 

Attachments

  • Archive.zip
    1.9 MB · Views: 91
Back
Top