Contribute
Register

[Guide] Laptop backlight control using AppleBacklightFixup.kext

i placed SSDT-PNLF.aml in acpi/patch when i look in boot clover log sort order not found.
 
chill2x said:
i placed SSDT-PNLF.aml in acpi/patch when i look in boot clover log sort order not found.
Click to expand...

If you have an issue, describe it in detail and attach "Problem Reporting" files as per post #1.
 
I tried to find a similar error on the forum, maybe is a simple question you can tell me what is wrong.
After follow the guide, I got sttucked on the "make" script. It aborts compiler and shows the following results (thanks a lot!):

iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-ALS0.aml hotpatch/SSDT-ALS0.dsl
ASL Input: hotpatch/SSDT-ALS0.dsl - 20 lines, 258 bytes, 5 keywords
AML Output: build/SSDT-ALS0.aml - 101 bytes, 5 named objects, 0 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 1 Optimizations
iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-Config.aml hotpatch/SSDT-Config.dsl
ASL Input: hotpatch/SSDT-Config.dsl - 72 lines, 1104 bytes, 19 keywords
AML Output: build/SSDT-Config.aml - 687 bytes, 11 named objects, 8 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 7 Optimizations
iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-Debug.aml hotpatch/SSDT-Debug.dsl
Compiler aborting due to parser-detected syntax error(s)
hotpatch/SSDT-Debug.dsl(26) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(26) : error 6126 - syntax error, unexpected PARSEOP_NAMESEG
hotpatch/SSDT-Debug.dsl(26) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(40) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(40) : error 6126 - syntax error, unexpected PARSEOP_NAMESEG
hotpatch/SSDT-Debug.dsl(40) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(62) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(62) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(62) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(63) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(63) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(69) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(69) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(69) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(70) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(70) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(71) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(71) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(77) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(77) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(77) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(78) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(78) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(79) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(79) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(80) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(80) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(86) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(86) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(86) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(87) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(87) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(88) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(88) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(89) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(89) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(90) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(90) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(96) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(96) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(96) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(97) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(97) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(98) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(98) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(99) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(99) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(100) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(100) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(101) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(101) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(107) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(107) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(107) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(108) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(108) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(109) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(109) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(110) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(110) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(111) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(111) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(112) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(112) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(113) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(113) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(118) : error 6126 - syntax error, unexpected $end and premature End-Of-File
ASL Input: hotpatch/SSDT-Debug.dsl - 118 lines, 2576 bytes, 84 keywords

Compilation complete. 67 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
make: *** [build/SSDT-Debug.aml] Error 255
 

Attachments

  • biscate data.zip
    2.3 MB · Views: 57
iMac 19,1
Z390 AORUS ULTRA |  i9 9900K |  HD 630
biscate said:
I tried to find a similar error on the forum, maybe is a simple question you can tell me what is wrong.
After follow the guide, I got sttucked on the "make" script. It aborts compiler and shows the following results (thanks a lot!):

iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-ALS0.aml hotpatch/SSDT-ALS0.dsl
ASL Input: hotpatch/SSDT-ALS0.dsl - 20 lines, 258 bytes, 5 keywords
AML Output: build/SSDT-ALS0.aml - 101 bytes, 5 named objects, 0 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 1 Optimizations
iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-Config.aml hotpatch/SSDT-Config.dsl
ASL Input: hotpatch/SSDT-Config.dsl - 72 lines, 1104 bytes, 19 keywords
AML Output: build/SSDT-Config.aml - 687 bytes, 11 named objects, 8 executable opcodes

Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 7 Optimizations
iasl -vw 2095 -vw 2008 -vi -vs -p build/SSDT-Debug.aml hotpatch/SSDT-Debug.dsl
Compiler aborting due to parser-detected syntax error(s)
hotpatch/SSDT-Debug.dsl(26) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(26) : error 6126 - syntax error, unexpected PARSEOP_NAMESEG
hotpatch/SSDT-Debug.dsl(26) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(40) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(40) : error 6126 - syntax error, unexpected PARSEOP_NAMESEG
hotpatch/SSDT-Debug.dsl(40) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(62) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(62) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(62) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(63) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(63) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(69) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(69) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(69) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(70) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(70) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(71) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(71) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(77) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(77) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(77) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(78) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(78) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(79) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(79) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(80) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(80) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(86) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(86) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(86) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(87) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(87) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(88) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(88) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(89) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(89) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(90) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(90) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(96) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(96) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(96) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(97) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(97) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(98) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(98) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(99) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(99) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(100) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(100) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(101) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(101) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(107) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(107) : error 6126 - syntax error, unexpected PARSEOP_INTEGER
hotpatch/SSDT-Debug.dsl(107) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(108) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(108) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(109) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(109) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(110) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(110) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(111) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(111) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(112) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(112) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(113) : error 6126 - Invalid character (0x5B), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(113) : error 6126 - Invalid character (0x5D), expecting ASL keyword or name
hotpatch/SSDT-Debug.dsl(118) : error 6126 - syntax error, unexpected $end and premature End-Of-File
ASL Input: hotpatch/SSDT-Debug.dsl - 118 lines, 2576 bytes, 84 keywords

Compilation complete. 67 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
make: *** [build/SSDT-Debug.aml] Error 255
Click to expand...

You must be using the wrong version of iasl.
See guide for correct version:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/
 
RehabMan said:
You must be using the wrong version of iasl.
See guide for correct version:
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/
Click to expand...

I was already using the version from the guide. Just to ensure, reinstalled it (with terminal) on "/usr/bin" but same problem.

Terminal "iasl" says:

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20141107-64 [Jan 2 2015]
Copyright (c) 2000 - 2014 Intel Corporation

Supports ACPI Specification Revision 5.1
 
iMac 19,1
Z390 AORUS ULTRA |  i9 9900K |  HD 630
biscate said:
I was already using the version from the guide. Just to ensure, reinstalled it (with terminal) on "/usr/bin" but same problem.

Terminal "iasl" says:

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20141107-64 [Jan 2 2015]
Copyright (c) 2000 - 2014 Intel Corporation

Supports ACPI Specification Revision 5.1
Click to expand...

I think you have to use iasl.zip not iasl51.zip
 
I try this method but when I try to shutdown and open it up again or restart still the brightness range is not saving on nvram, its always on 75%.when boot up or restart..before on 10.12.3 I did not use emu variable and my brightness range is saving on nvram.i will upload my files, please see the attachment below.

Code: 
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AirPortAtheros40.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HD_Graphics.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_BCM57XX_as_BCM57765.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext IOHDAFamily.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleHDAController.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 8E5FED24F4D1B2CB66A1A034C2214E11

btw applebacklightinjector.kext id in L/E not in S/L/E.
 

Attachments

  • EFI.zip
    15.5 MB · Views: 75
  • Alexis-Sofia’s MacBook Pro.ioreg
    7.2 MB · Views: 67
Last edited:
biscate said:
I was already using the version from the guide. Just to ensure, reinstalled it (with terminal) on "/usr/bin" but same problem.

Terminal "iasl" says:

Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20141107-64 [Jan 2 2015]
Copyright (c) 2000 - 2014 Intel Corporation

Supports ACPI Specification Revision 5.1
Click to expand...

You have the wrong version.
 
chill2x said:
I try this method but when I try to shutdown and open it up again or restart still the brightness range is not saving on nvram, its always on 75%.when boot up or restart..before on 10.12.3 I did not use emu variable and my brightness range is saving on nvram.i will upload my files, please see the attachment below.

Code: 
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AirPortAtheros40.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HD_Graphics.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_BCM57XX_as_BCM57765.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext IOHDAFamily.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleHDAController.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 8E5FED24F4D1B2CB66A1A034C2214E11

btw applebacklightinjector.kext id in L/E not in S/L/E.
Click to expand...

Read post #1 regarding NVRAM implementation and see link for fake ALS device.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top