Contribute
Register

Dell e6230 fn keys for brightness messed HELP please

Status
Not open for further replies.
edgarrosandy

edgarrosandy

Joined
Nov 11, 2015
Messages
40
Motherboard
GA-H110M-A
CPU
i3-6100
Graphics
HD 530
Mobile Phone
  1. Android
  2. iOS
Hi i have Dell Latitude E6230 Running 10.11.6 Clover UEFI
Ive got everything working but didn't get brightness keys to work correctly, my brightness key supposed to be fn+up & fn+down
but now its fn+insert=brightness up & fn+f3 is brightness down.
help please, I've tried to follow rehab mans methods to patch dsdt for backlight control but i can't seem to get any results on Console for my brightness keys.

Help please, thanks.
 
edgarrosandy said:
Hi i have Dell Latitude E6230 Running 10.11.6 Clover UEFI
Ive got everything working but didn't get brightness keys to work correctly, my brightness key supposed to be fn+up & fn+down
but now its fn+insert=brightness up & fn+f3 is brightness down.
help please, I've tried to follow rehab mans methods to patch dsdt for backlight control but i can't seem to get any results on Console for my brightness keys.

Help please, thanks.
Click to expand...

https://www.tonymacx86.com/threads/guide-patching-dsdt-ssdt-for-laptop-backlight-control.152659/
 
edgarrosandy said:
Hi thanks rehabman, ive managed to get the EC query methode for my brightness key, but it only shows one code for both up and down brightness key which is Q_66.. how do i patch that into my dsdt ? i have tried to copy your code from the tutorial fro hp envy but my dsdt shows an error say "objectHKNO does not exist"
Click to expand...

Analyze the code in _Q66. Use ACPIDebug.kext to trace the execution path and variables in an effort to determine what conditions result from brightness keys.

You cannot expect that code from an HP Envy will apply directly to your Dell.
 
RehabMan said:
Analyze the code in _Q66. Use ACPIDebug.kext to trace the execution path and variables in an effort to determine what conditions result from brightness keys.

You cannot expect that code from an HP Envy will apply directly to your Dell.
Click to expand...

Still cant get it to work properly. my brightness keys are still the insert key=brightness up & f3=brightness down :(
 
edgarrosandy said:
Still cant get it to work properly. my brightness keys are still the insert key=brightness up & f3=brightness down :(
Click to expand...

Read guide, post #1, "Problem Reporting".
 
RehabMan said:
Read guide, post #1, "Problem Reporting".
Click to expand...
Code: 
Brilliants-MBP:~ zerocool$ kextstat|grep -y acpiplat
   13    2 0xffffff7f8250d000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (4.0) A29C7512-D3A8-3AED-9721-3A5FF1A32EB2 <12 11 7 6 5 4 3 1>
Brilliants-MBP:~ zerocool$ kextstat|grep -y appleintelcpu
Brilliants-MBP:~ zerocool$ kextstat|grep -y applelpc
   94    0 0xffffff7f8203b000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) 32BDCF9F-0473-32D4-9DAE-F523EFB2D244 <93 12 5 4 3>
Brilliants-MBP:~ zerocool$

Code: 
Brilliants-MBP:~ zerocool$ sudo touch /System/Library/Extensions && sudo kextcache -u /
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBXHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBEHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOGraphicsFamily.kext
kext-dev-mode allowing invalid signature -67050 0xFFFFFFFFFFFEFA16 for kext GenericUSBXHCI.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelFramebufferCapri.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIDebug.kext
 

Attachments

  • RehabMan.zip
    4.4 MB · Views: 132
edgarrosandy said:
Code: 
Brilliants-MBP:~ zerocool$ kextstat|grep -y acpiplat
   13    2 0xffffff7f8250d000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (4.0) A29C7512-D3A8-3AED-9721-3A5FF1A32EB2 <12 11 7 6 5 4 3 1>
Brilliants-MBP:~ zerocool$ kextstat|grep -y appleintelcpu
Brilliants-MBP:~ zerocool$ kextstat|grep -y applelpc
   94    0 0xffffff7f8203b000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) 32BDCF9F-0473-32D4-9DAE-F523EFB2D244 <93 12 5 4 3>
Brilliants-MBP:~ zerocool$

Code: 
Brilliants-MBP:~ zerocool$ sudo touch /System/Library/Extensions && sudo kextcache -u /
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBXHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleUSBEHCIPCI.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext IOUSBHostFamily.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext IOGraphicsFamily.kext
kext-dev-mode allowing invalid signature -67050 0xFFFFFFFFFFFEFA16 for kext GenericUSBXHCI.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleIntelFramebufferCapri.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleHDAHardwareConfigDriver.kext
kext-dev-mode allowing invalid signature -67061 0xFFFFFFFFFFFEFA0B for kext AppleHDA.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIDebug.kext
Click to expand...

If you look carefully at _Q66, you will find it eventually calls (or intends to call) BRT6, which is where the brightness keys are handled. That is likely the method you must patch.

The patch you made to _Q66 is nonsense.
 
RehabMan said:
If you look carefully at _Q66, you will find it eventually calls (or intends to call) BRT6, which is where the brightness keys are handled. That is likely the method you must patch.

The patch you made to _Q66 is nonsense.
Click to expand...
i still dont get how to patch the method. can i use the hp envy patch ?
 
edgarrosandy said:
i still dont get how to patch the method.
Click to expand...

First you need to instrument the method so you know:
1) that it is called
2) which path is taken for brightness up vs. brightness down

Then change the code to send the required Notifies to the keyboard driver.

can i use the hp envy patch ?
Click to expand...

Of course not.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top