Jump to content
87 posts in this topic

Recommended Posts

Having an issue with brightness on this machine. Using the usual AppleBacklightInjector.kext and Kexts to patch and SSDT-PNLF method and still no control. Ive tried patching my DSDT with the brightness fix also. Still no go. Ive noticed my kextcache seems correct. But if i clear my kextcache, then reboot. The machine always crashes on the first reboot and boots normal on the second. No Brightness controls though. Attached is my current debug. Thanks guys. 

debug_25771.zip

For me, brightness worked OOB once I added a PNLF device to my DSDT.  I added the most basic device info possible and not the PNLF patches by RehabMan.  However, when I switched from FakeSMC to VirtualSMC, I started using the SMCLightSensor.kext.  It makes brightness change automatically based on ambient light (which I often override when I want full brightness.)

On 10/5/2018 at 4:52 PM, mnfesq said:

For me, brightness worked OOB once I added a PNLF device to my DSDT.  I added the most basic device info possible and not the PNLF patches by RehabMan.  However, when I switched from FakeSMC to VirtualSMC, I started using the SMCLightSensor.kext.  It makes brightness change automatically based on ambient light (which I often override when I want full brightness.)

So im not sure how to "add a PNLF device to my DSDT?" Im using the typical SSDT-PNLF method with applebacklightinjector kext and kexts to patch. But still its a no go. Sorry for my ignorance on this process.. lol. 

17 hours ago, tikizondo94 said:

So im not sure how to "add a PNLF device to my DSDT?" Im using the typical SSDT-PNLF method with applebacklightinjector kext and kexts to patch. But still its a no go. Sorry for my ignorance on this process.. lol. 

 

OK, let's do this the easiest way.  Using Clover Configurator, check the box for add PNLF in ACPI (it's in group 2 of fixes).  Don't use the SSDT-PNLF and don't use any brightness injector kext and don't use any brightness kext patch and see if it works OOB for you like it does for me.

1 hour ago, mnfesq said:

 

OK, let's do this the easiest way.  Using Clover Configurator, check the box for add PNLF in ACPI (it's in group 2 of fixes).  Don't use the SSDT-PNLF and don't use any brightness injector kext and don't use any brightness kext patch and see if it works OOB for you like it does for me.

Ok, Removed SSDT-PNLF, removed AppleBacklightInjector.kext and also kexts to patch method. Added "AddPNLF" in ACPI section. Now during boot it loads to a black screen. I have sound, but no image.

 

Another strange thing is no matter what, anytime i boot my system, the first boot always crashes, then usually the next boot it loads up normally. "no brightness controls of course". 

Edited by tikizondo94
4 hours ago, tikizondo94 said:

Ok, Removed SSDT-PNLF, removed AppleBacklightInjector.kext and also kexts to patch method. Added "AddPNLF" in ACPI section. Now during boot it loads to a black screen. I have sound, but no image.

 

Another strange thing is no matter what, anytime i boot my system, the first boot always crashes, then usually the next boot it loads up normally. "no brightness controls of course". 

 

Did you try rebuilding the kernel cache? Do you know if you have any other settings in your SSDT-PNLF beside the PNLF device?  If you get a black screen, it usually means that you don't have the correct ig-platform-id.  Is that in your SSDT-PNLF?  Do you have a Graphics Device ID in your config.plist?  What about an ig-platform-id?

55 minutes ago, mnfesq said:

 

Did you try rebuilding the kernel cache? Do you know if you have any other settings in your SSDT-PNLF beside the PNLF device?  If you get a black screen, it usually means that you don't have the correct ig-platform-id.  Is that in your SSDT-PNLF?  Do you have a Graphics Device ID in your config.plist?  What about an ig-platform-id?

Im currently using the new whatevergreen method for my graphics injection. Using FBpatcher app to setup my config for Device/Properties. Im not sure how my SSDT-PNLF is setup. I just used rehabs method for fixing backlight. So far i have not had any luck with that method. Also i did rebuild cache before rebooting. Attached is my "current" Clover so you can see what im working with. 

CLOVER.zip

I noticed Rehab just released a new method for backlight, using the AppleBacklightFixup kext and new SSDT-PNLF. Also removing the old method. I tried this new method this morning and ended up with the same result. Boots still to a black screen. The method im currently using seems to make the screen atleast "work". But having brightness controls would be nice, especially when on battery power. I also tried changing my platform IDs in Devices/Properties. Currently im using 191E0000 and swithed to 191B0000. So far its made no difference. I can leave the properties blank and whatevergreen seems to still inject a correct property to get QE/CI working.  

6 hours ago, tikizondo94 said:

I noticed Rehab just released a new method for backlight, using the AppleBacklightFixup kext and new SSDT-PNLF. Also removing the old method. I tried this new method this morning and ended up with the same result. Boots still to a black screen. The method im currently using seems to make the screen atleast "work". But having brightness controls would be nice, especially when on battery power. I also tried changing my platform IDs in Devices/Properties. Currently im using 191E0000 and swithed to 191B0000. So far its made no difference. I can leave the properties blank and whatevergreen seems to still inject a correct property to get QE/CI working.  

 

I'm wondering why your SMBIOS is MBP11,1 instead of MBP13,3.  I read that the Dell Inspiron 7559 has the i7 6700HQ processor.  There is a MBP that has the identical cpu and it uses the 13,3 SMBIOS.  

 

https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6-15-late-2016-retina-display-touch-bar-specs.html

 

Brightness control should work OOB for you since that model of MBP has the Intel HD530 gpu.

 

I really think you need to make sure your system is set up correctly in order to troubleshoot specific problems.  I also noticed that you have a custom DSDT but also use DSDT patches in your clover config.plist.  You should choose one or the other unless you are just trying out DSDT patches temporarily in your config.plist. If you ever want to chat in order to troubleshoot your problems in real time, just send a PM with time and contact info.

Edited by mnfesq
1 hour ago, mnfesq said:

 

I'm wondering why your SMBIOS is MBP11,1 instead of MBP13,3.  I read that the Dell Inspiron 7559 has the i7 6700HQ processor.  There is a MBP that has the identical cpu and it uses the 13,3 SMBIOS.  

 

https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6-15-late-2016-retina-display-touch-bar-specs.html

 

Brightness control should work OOB for you since that model of MBP has the Intel HD530 gpu.

 

I really think you need to make sure your system is set up correctly in order to troubleshoot specific problems.  I also noticed that you have a custom DSDT but also use DSDT patches in your clover config.plist.  You should choose one or the other unless you are just trying out DSDT patches temporarily in your config.plist. If you ever want to chat in order to troubleshoot your problems in real time, just send a PM with time and contact info.

Agreed with the SmBIOS. There's a few guides going around for the Dell 7559 and in each guide there using the MBP11,1 or 11,2. Both seem to boot fine for me. Ive not yet tried the 13,3 yet. But will shortly. I have 2 drives on this laptop so i keep a semi normal stable OS then i have a test OS i can try things with. The only real time chat i use is discord. But i could really use your help at this point. Im slowly gaining ground with hack laptops, But you seem to be way more advanced. :)

12 hours ago, mnfesq said:

 

I'm wondering why your SMBIOS is MBP11,1 instead of MBP13,3.  I read that the Dell Inspiron 7559 has the i7 6700HQ processor.  There is a MBP that has the identical cpu and it uses the 13,3 SMBIOS.  

 

https://everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.6-15-late-2016-retina-display-touch-bar-specs.html

 

Brightness control should work OOB for you since that model of MBP has the Intel HD530 gpu.

 

I really think you need to make sure your system is set up correctly in order to troubleshoot specific problems.  I also noticed that you have a custom DSDT but also use DSDT patches in your clover config.plist.  You should choose one or the other unless you are just trying out DSDT patches temporarily in your config.plist. If you ever want to chat in order to troubleshoot your problems in real time, just send a PM with time and contact info.

Ok, Switched to MPB 13.3 SMbios. 

1st tried with new AppleBacklightfixup kext and new SSDT-PNLF. Boots to black screen.

2nd Removed Kext and PNLF, tried adding "AddPNLF" in ACPI/Patches - boots to black screen

3rd Removed "AddPNLF" and just tried with No Fixes - Boots to black screen. 

 

Strange i know.. 

10 hours ago, tikizondo94 said:

Ok, Switched to MPB 13.3 SMbios. 

1st tried with new AppleBacklightfixup kext and new SSDT-PNLF. Boots to black screen.

2nd Removed Kext and PNLF, tried adding "AddPNLF" in ACPI/Patches - boots to black screen

3rd Removed "AddPNLF" and just tried with No Fixes - Boots to black screen. 

 

Strange i know.. 

 

What about the kext patch?  Did you disable that?

4 minutes ago, mnfesq said:

 

What about the kext patch?  Did you disable that?

Yes sir. I disabled it when using the AddPNLF method in ACPI/Patches and also disabled it when using the new AppleBacklightFixup method. Also when trying with no fixes. Its disabled in general. Only when using AppleBacklightInjector.kext method is it enabled. 

On 10/15/2018 at 1:16 PM, tikizondo94 said:

Yes sir. I disabled it when using the AddPNLF method in ACPI/Patches and also disabled it when using the new AppleBacklightFixup method. Also when trying with no fixes. Its disabled in general. Only when using AppleBacklightInjector.kext method is it enabled. 

 

I didn't see AppleBacklightInjector in your Clover kexts.  Do you keep in in L/E?  I don't understand why you would use that kext.  What is it that you want injected?  Device ID?  Ig-Platform-id?  What is your native VID/PID for your IGPU?

6 hours ago, mnfesq said:

 

I didn't see AppleBacklightInjector in your Clover kexts.  Do you keep in in L/E?  I don't understand why you would use that kext.  What is it that you want injected?  Device ID?  Ig-Platform-id?  What is your native VID/PID for your IGPU?

I was originally following this guide "https://www.tonymacx86.com/threads/guide-laptop-backlight-control-using-applebacklightfixup-kext.218222/" to try and get backlight working. After my install of Mojave i had QE/CI but no brightness controls, first i tried adding PNLF to my DSDT, which didnt work. I tried the brightness patch in my DSDT it also didnt work. So currently ive tried the linked method to try and get backlight/brightness working. I seem to have native NVRAM working with AptioMemoryFix driver. Backlight shows as "backlight-level=<6c05>. But i have no controls for it. Sometimes the slider is there sometimes its not. And if i try to adjust brightness the screen goes out. if i adjust brightness to come back up the screen comes back on. "im using Fn-F11 and F12 keys to adjust brightness". This has been my experience with Mojave and now Sierra. I have a Sierra Partition also on my laptop and am having the same brightness issues. Ive attached my latest debug with screenshots that will hopefully help. I really appreciate you taking the time to help. 

Debug 19470.zip

8 hours ago, tikizondo94 said:

I was originally following this guide "https://www.tonymacx86.com/threads/guide-laptop-backlight-control-using-applebacklightfixup-kext.218222/" to try and get backlight working. After my install of Mojave i had QE/CI but no brightness controls, first i tried adding PNLF to my DSDT, which didnt work. I tried the brightness patch in my DSDT it also didnt work. So currently ive tried the linked method to try and get backlight/brightness working. I seem to have native NVRAM working with AptioMemoryFix driver. Backlight shows as "backlight-level=<6c05>. But i have no controls for it. Sometimes the slider is there sometimes its not. And if i try to adjust brightness the screen goes out. if i adjust brightness to come back up the screen comes back on. "im using Fn-F11 and F12 keys to adjust brightness". This has been my experience with Mojave and now Sierra. I have a Sierra Partition also on my laptop and am having the same brightness issues. Ive attached my latest debug with screenshots that will hopefully help. I really appreciate you taking the time to help. 

Debug 19470.zip

 

OK, I made some changes to your custom DSDT and tried to clean up your SSDT-3.  I lack the skill to clean up your SSDT-1 but it is messed up.  Unfortunately, it is an important SSDT as it controls your laptop's sensors, likely including your backlight sensor.  I added a PNLF device to your DSDT and made name changes that were needed but changing _DSM to XDSM causes a ton of errors and I don't recommend doing so.  The reason is that you already have some XDSM's and some _DSM's and when you change them all to XDSM, it causes conflicts.  I think that doing so generated over 200 errors.  Because I couldn't fix your SSDT-1, I added a line in config.plist to disable it.  If that causes problems, you can always delete that in config.plist and your OEM SSDT-1 will be restored in all of its erroneous glory.  BTW, SSDT-3 controls your fans.  Have you had any issues with your fans or cooling?  If you start having them, you can delete the SSDT-3 from ACPI/patched and your system will go back to using the OEM version of SSDT-3.

 

Use the attached files in their usual places and remove your AppleBacklightInjector.kext.  I already disabled your backlight patch in config.plist.  I also noticed that you have lots of stuff in your config.plist that you probably don't need.  When you use someone's tutorial to set up your system, I recommend that you go through most of the config.plist settings and custom kexts and remove them and see if, in fact, you ever really needed them.  If your system works just as well without the items, don't use them.  Less is definitely more when it comes to setting up your system perfectly.  The less variables the better.

 

Archive.zip

  • Thanks 1
3 hours ago, mnfesq said:

 

OK, I made some changes to your custom DSDT and tried to clean up your SSDT-3.  I lack the skill to clean up your SSDT-1 but it is messed up.  Unfortunately, it is an important SSDT as it controls your laptop's sensors, likely including your backlight sensor.  I added a PNLF device to your DSDT and made name changes that were needed but changing _DSM to XDSM causes a ton of errors and I don't recommend doing so.  The reason is that you already have some XDSM's and some _DSM's and when you change them all to XDSM, it causes conflicts.  I think that doing so generated over 200 errors.  Because I couldn't fix your SSDT-1, I added a line in config.plist to disable it.  If that causes problems, you can always delete that in config.plist and your OEM SSDT-1 will be restored in all of its erroneous glory.  BTW, SSDT-3 controls your fans.  Have you had any issues with your fans or cooling?  If you start having them, you can delete the SSDT-3 from ACPI/patched and your system will go back to using the OEM version of SSDT-3.

 

Use the attached files in their usual places and remove your AppleBacklightInjector.kext.  I already disabled your backlight patch in config.plist.  I also noticed that you have lots of stuff in your config.plist that you probably don't need.  When you use someone's tutorial to set up your system, I recommend that you go through most of the config.plist settings and custom kexts and remove them and see if, in fact, you ever really needed them.  If your system works just as well without the items, don't use them.  Less is definitely more when it comes to setting up your system perfectly.  The less variables the better.

 

Archive.zip

Well good news :) So far Sierra boots. Brightness slider shows in preferences now. But the screen goes black if i try to dim it. Comes back when i brighten the screen. Always 100% though. SmBios 13,3 seems to work. Fans seem to be working ok. Temps staying around 38-47c. I see what you mean with SSDT-1. Wow. Error city. I tried to smooth it out. But if you cant do it. I sure as heck cant at this point lol. Anyways Ive attached my latest debug. Ill give my Mojave partition a shot in a bit. Thanks for this. I really do appreciate your help :)

debug_5099.zip

 

ok, Cleared caches a few more times and reboots and now brightness is working! Im running on battery power currently and everything seems to be working correctly with your latest files. Thanks for this @mnfesq!!

 

Edited by tikizondo94
Well good news  So far Sierra boots. Brightness slider shows in preferences now. But the screen goes black if i try to dim it. Comes back when i brighten the screen. Always 100% though. SmBios 13,3 seems to work. Fans seem to be working ok. Temps staying around 38-47c. I see what you mean with SSDT-1. Wow. Error city. I tried to smooth it out. But if you cant do it. I sure as heck cant at this point lol. Anyways Ive attached my latest debug. Ill give my Mojave partition a shot in a bit. Thanks for this. I really do appreciate your help
debug_5099.zip
Press F4 at CLOVER GUI, then upload here your CLOVER FOLDER. I will make good configuration for you

Sent from my Mi Note 2 using Tapatalk

9 minutes ago, Andres ZeroCross said:

Press F4 at CLOVER GUI, then upload here your CLOVER FOLDER. I will make good configuration for you

Sent from my Mi Note 2 using Tapatalk
 

This is my latest extract. 

debug_5099.zip

BrcmPatchRAM2.kext
BrcmFirmwareRepo.kext
AppleBacklightInjector.kext
FakePCIID.kext
FakePCIID_Broadcom_WiFi.kext
Sinetek-rtsx.kext
USBInjectAll.kext

Remove all this kext at your Library/extensions,, DON"T FORGET

 

 

And i forget to copy this USBInjectAll.kext to EFI/CLOVER/Kexts/Other,, just add it. Then boot

USBInjectAll.kext.zip

Edited by Andres ZeroCross
56 minutes ago, Andres ZeroCross said:

Backup then delete your entire CLOVER folder,, and paste this. Try to reboot. Let me know for the result

CLOVER.zip

Cant DL your clover folder attachment. 

2 hours ago, tikizondo94 said:

ok, Cleared caches a few more times and reboots and now brightness is working! Im running on battery power currently and everything seems to be working correctly with your latest files. Thanks for this @mnfesq!!

 

Yay!

 

I'm curious to know if, by disabling that SSDT-1, you no longer have any sensors working at all.  Do you use temp or other sensors with FakeSMC?  Do they work?

Edited by mnfesq
  • Thanks 1
×
×
  • Create New...