Dell 7559 No brightness/backlight controls

[Andres ZeroCross]

6 minutes ago, tikizondo94 said:

Wierd, I dont know why smclightsensor showed. I removed my other OSX drive this time just to make sure. Cleared all NVRAM values again, I deleted and readded your clover folder again. This is a new verbose lock point. 

 

Before get to sleep,,, use this. If problem still persist, i will check it tommorow morning. I can't concentrate while sleepy 

 

CLOVER.zip

[tikizondo94]

Just now, Andres ZeroCross said:

 

Before get to sleep,,, use this. If problem still persist, i will check it tommorow morning. I can't concentrate while sleepy 

 

CLOVER.zip

No problem. I really appreciate your help on this. Get some sleep

[tikizondo94]

54 minutes ago, mnfesq said:

 

Thanks for the info.  I decided to make/use the CPUFriendDataProvider.kext instead of making an SSDT.  It worked and it added some P-States at the low-end of my cpu's capacity.  Now, I will play with it to get the max frequencies as well.

 

 

Sorry for all of the off-topic posts.

Ive not been able to find much documentation to instructions on this method.. What process did you use? 

[mnfesq]

1 hour ago, tikizondo94 said:

Ive not been able to find much documentation to instructions on this method.. What process did you use? 

 

OK, I downloaded CPUFriend.kext here:

 

https://github.com/acidanthera/CPUFriend/releases

 

I copied ResourceConverter.sh from here and pasted it into a plain text document and named it ResourceConverter.sh:

 

https://raw.githubusercontent.com/acidanthera/CPUFriend/master/ResourceConverter/ResourceConverter.sh

 

Then, I looked at my SMBIOS and took the board-id listed in the SMBIOS and looked for it in this folder:

 

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources

 

I then copied the board-id.plst to my desktop, where I also had saved my ResourceConverter.sh.  I then opened Terminal and entered the following command (which you will need to edit to have it go to your user folder and correct board-id):

 

bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist

 

This created the kext, CPUFriendProvider.kext in my /Users/mnfesq folder (not Desktop for some reason). Now, you have to modify that kext by opening it and going to the info.plist.  Under IOKitPersonalities/CPUFriendDataProvider/cf-frequency-data, make a data entry on the right side: 0800.  Save the info.plist and close up the kext.  Then add the kext and CPUFriend.kext to Clover/kexts/Other (or 10.14, whichever you use.). Then reboot and test with CPU-S.

 

I should mention that CPU-S is not perfect and is limited as to the number of P-States that it will report.  In subsequent tests, I have seen P-States from 800 MHz to 4 GHz.  Those are the lowest and highest frequencies my CPU supports.

 

 

 

 

[tikizondo94]

2 minutes ago, mnfesq said:

 

OK, I downloaded CPUFriend.kext here:

 

https://github.com/acidanthera/CPUFriend/releases

 

I copied ResourceConverter.sh from here and pasted it into a plain text document and named it ResourceConverter.sh:

 

https://raw.githubusercontent.com/acidanthera/CPUFriend/master/ResourceConverter/ResourceConverter.sh

 

Then, I looked at my SMBIOS and took the board-id listed in the SMBIOS and looked for it in this folder:

 

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources

 

I then copied the board-id.plst to my desktop, where I also had saved my ResourceConverter.sh.  I then opened Terminal and entered the following command (which you will need to edit to have it go to your user folder and correct board-id):

 

bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist

 

This created the kext, CPUFriendProvider.kext in my /Users/mnfesq folder (not Desktop for some reason). Now, you have to modify that kext by opening it and going to the info.plist.  Under IOKitPersonalities/CPUFriendDataProvider/cf-frequency-data, make a data entry on the right side: 0800.  Save the info.plist and close up the kext.  Then add the kext and CPUFriend.kext to Clover/kexts/Other (or 10.14, whichever you use.). Then reboot and test with CPU-S.

 

I should mention that CPU-S is not perfect and is limited as to the number of P-States that it will report.  In subsequent tests, I have seen P-States from 800 MHz to 4 GHz.  Those are the lowest and highest frequencies my CPU supports.

 

 

 

 

Well written! Thank you for this. Ill give it a shot in the morning. Ive noticed speedstep isnt working correctly with my 4790K using SmBios 14,2 in Mojave. I using the Plugin-Type=1 and its worked flawless in High Sierra, But im guessing some things have changed in Mojave. Ive noticed other users having the same issue with the same configuration. So hopefully this will correct that!

[mnfesq]

6 minutes ago, tikizondo94 said:

Well written! Thank you for this. Ill give it a shot in the morning. Ive noticed speedstep isnt working correctly with my 4790K using SmBios 14,2 in Mojave. I using the Plugin-Type=1 and its worked flawless in High Sierra, But im guessing some things have changed in Mojave. Ive noticed other users having the same issue with the same configuration. So hopefully this will correct that!

 

You should be using MBP13,3 with your Dell, not MBP14,2.  You have the 6700HQ cpu, as does the Apple MacBook Pro "Core i7" 2.6 15" Touch/Late 2016, which uses the MBP13,3 SMBIOS.  As for the AsRocks desktop, the closest is probably the Apple MacBook Pro "Core i7" 2.2 15" Mid-2014, which has the i7 4770HQ cpu, and it uses the MBP11,2 SMBIOS.  I always use the everyman.com website to compare my specs with actual Mac computers in order to determine which SMBIOS to use.  SMBIOS has a big impact on power management and the right SMBIOS might improve speed stepping for your ASRocks.  However, why do you care if it's a desktop. Speedstepping is designed to save battery life and most desktop computers run at full power at all times, particularly if you have your power settings in high performance mode.

[Andres ZeroCross]

6 hours ago, mnfesq said:

 

OK, I downloaded CPUFriend.kext here:

 

https://github.com/acidanthera/CPUFriend/releases

 

I copied ResourceConverter.sh from here and pasted it into a plain text document and named it ResourceConverter.sh:

 

https://raw.githubusercontent.com/acidanthera/CPUFriend/master/ResourceConverter/ResourceConverter.sh

 

Then, I looked at my SMBIOS and took the board-id listed in the SMBIOS and looked for it in this folder:

 

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources

 

I then copied the board-id.plst to my desktop, where I also had saved my ResourceConverter.sh.  I then opened Terminal and entered the following command (which you will need to edit to have it go to your user folder and correct board-id):

 

bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist

 

This created the kext, CPUFriendProvider.kext in my /Users/mnfesq folder (not Desktop for some reason). Now, you have to modify that kext by opening it and going to the info.plist.  Under IOKitPersonalities/CPUFriendDataProvider/cf-frequency-data, make a data entry on the right side: 0800.  Save the info.plist and close up the kext.  Then add the kext and CPUFriend.kext to Clover/kexts/Other (or 10.14, whichever you use.). Then reboot and test with CPU-S.

 

I should mention that CPU-S is not perfect and is limited as to the number of P-States that it will report.  In subsequent tests, I have seen P-States from 800 MHz to 4 GHz.  Those are the lowest and highest frequencies my CPU supports.

 

 

 

 

 

 

Are you sure with this command??? "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist"

it should be "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist". There is no CPUFriendProvider.kext yet before you run the command (ResourceConverter.sh is made to build it)

[tikizondo94]

9 hours ago, mnfesq said:

 

You should be using MBP13,3 with your Dell, not MBP14,2.  You have the 6700HQ cpu, as does the Apple MacBook Pro "Core i7" 2.6 15" Touch/Late 2016, which uses the MBP13,3 SMBIOS.  As for the AsRocks desktop, the closest is probably the Apple MacBook Pro "Core i7" 2.2 15" Mid-2014, which has the i7 4770HQ cpu, and it uses the MBP11,2 SMBIOS.  I always use the everyman.com website to compare my specs with actual Mac computers in order to determine which SMBIOS to use.  SMBIOS has a big impact on power management and the right SMBIOS might improve speed stepping for your ASRocks.  However, why do you care if it's a desktop. Speedstepping is designed to save battery life and most desktop computers run at full power at all times, particularly if you have your power settings in high performance mode.

Im talking about one of my other systems. My 4790k desktop, I use the iMac 14,2 for it. Sorry for the confusion. Im using the MBP 13,3 for my Dell 7559 laptop currently. What i have noticed though is with the change of smbios from 11,1 to 13,3 Speedstep and bluetooth have disappeared. When using the MPB 11,1 i had speedstep and bluetooth working out of the box. With 13,3 i have to use CPUfriend and DataProvider to get speedstep working. And currently i have not been able to get bluetooth back. Work in progress lol. 

[tikizondo94]

4 hours ago, Andres ZeroCross said:

 

 

Are you sure with this command??? "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist"

it should be "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist". There is no CPUFriendProvider.kext yet before you run the command (ResourceConverter.sh is made to build it)

You are correct. This command adds cf-frequency-data into the plist. 

[mnfesq]

12 hours ago, Andres ZeroCross said:

 

 

Are you sure with this command??? "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop CPUFriendProvider.kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist"

it should be "bash /Users/mnfesq/Desktop/ResourceConverter.sh --kext /Users/mnfesq/Desktop/Mac-551B86E5744E2388.plist". There is no CPUFriendProvider.kext yet before you run the command (ResourceConverter.sh is made to build it)

 

I see how your command adds all of the info from the board-id plist.  However, I lost the 800 MHz speedstep.  That means that I need to add that frequency to the board-id plist.  Any idea how to do that? 

 

EDIT:  Never mind.  I found the answer here:  

Quote

For X86PlatformPlugin.kext:
Step 1: Browse into the kext’s resource folder at:

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext/Contents/Resources

You will see a bunch of plist files here, which are power profiles for new Mac models.

Step 2:

• Open the plist file corresponding with the Board-id you are using.
  • For example, if you are using MacBookPro12,1 SMBIOS configuration, you should open Mac-E43C1C25D4880AD6.plist.
• Navigate into IOPlatformPowerProfile -> FrequencyVectors property.
• Change the second word of the data in FrequencyVectors from 0D000000 to 0800000, and make sure the value of CPUFloor property is 800. This will enable CPU to run at 800MHz at idle.

 

 

Edited October 19, 2018 by mnfesq

[Andres ZeroCross]

1 hour ago, mnfesq said:

 

I see how your command adds all of the info from the board-id plist.  However, I lost the 800 MHz speedstep.  That means that I need to add that frequency to the board-id plist.  Any idea how to do that? 

 

EDIT:  Never mind.  I found the answer here:  

 

 

You always talk about frequency,, but forget about HWP

[mnfesq]

2 minutes ago, Andres ZeroCross said:

You always talk about frequency,, but forget about HWP

 

I haven't forgotten, I just haven't learned about it yet.  That's on my to-do list.  I downloaded the HWPEnabler.kext but still don't know how to use it.

[Andres ZeroCross]

6 minutes ago, mnfesq said:

 

I haven't forgotten, I just haven't learned about it yet.  That's on my to-do list.  I downloaded the HWPEnabler.kext but still don't know how to use it.

 

You said that you haven't forget  But you choose wrong SMBIOS. There is no HWP Profile with MacbookPro12,1, HWP Profile is written at board-id.plist inside X86PlatformPlugin.kext/Content/Resources

 

 

My iMac17,1 (PC Hackintosh) with HWP Profiler from MacbookPro 14,2

Edited October 19, 2018 by Andres ZeroCross

[mnfesq]

47 minutes ago, Andres ZeroCross said:

 

You said that you haven't forget  But you choose wrong SMBIOS. There is no HWP Profile with MacbookPro12,1, HWP Profile is written at board-id.plist inside X86PlatformPlugin.kext/Content/Resources

 

My iMac17,1 (PC Hackintosh) with HWP Profiler from MacbookPro 14,2

 

I remember that PMHeart had an injector that would allow you to take power management from one board-id.plist and use it in another.  I am using MacBookPro14,3 SMBIOS but I don't know how to set up HWP.

[tikizondo94]

Doesn't this script ultimately do the same thing? 

https://github.com/Piker-Alpha/freqVectorsEdit.sh 

[mnfesq]

1 hour ago, tikizondo94 said:

Doesn't this script ultimately do the same thing? 

https://github.com/Piker-Alpha/freqVectorsEdit.sh 

 

Yes.  The kext I was thinking about takes the information generated by Pike's script and puts it into an injector kext so that you don't have to repatch the Apple kext with every update.  It was clearly the forerunner of CPUFriend.

[tikizondo94]

4 hours ago, Andres ZeroCross said:

 

You said that you haven't forget  But you choose wrong SMBIOS. There is no HWP Profile with MacbookPro12,1, HWP Profile is written at board-id.plist inside X86PlatformPlugin.kext/Content/Resources

 

 

My iMac17,1 (PC Hackintosh) with HWP Profiler from MacbookPro 14,2

Can HMP profiles be used with "pre" Skylake model Intel CPUs? Are Haswell Cpus able to utilize HMP profiles?

[tikizondo94]

14 hours ago, mnfesq said:

 

Yes.  The kext I was thinking about takes the information generated by Pike's script and puts it into an injector kext so that you don't have to repatch the Apple kext with every update.  It was clearly the forerunner of CPUFriend.

 

X86PlatformPluginInjector.kext.zip

[mnfesq]

2 hours ago, tikizondo94 said:

 

X86PlatformPluginInjector.kext.zip

 

Yeah, that's the one.  Being an old guy with failing memory and more than 10 years of hackingtoshing, stuff I learn here pours out of my brain way too fast.

[tikizondo94]

Well i got HMP PM working successfully on my machine. I got it work using CPUFriend and or the FrequencyVectors.sh script. Both work the same ive found. Just depends on if you want to load through bootloader or L/E. Anyways Still i cannot get Bluetooth to work on my Sierra Partition using the 13,3 smbios. Im using brcmFirmwareRepo and BrcmPatchRAM2 and i just cant get them to load. Very strange. Even if i install them into L/E i cant get them to load into kextcache. Any Ideas? Ive attached my latest debug. 

debug_22106.zip

Dell 7559 AppleIntelInfo.txt

Edited October 21, 2018 by tikizondo94

[Andres ZeroCross]

Well i got HMP PM working successfully on my machine. I got it work using CPUFriend and or the FrequencyVectors.sh script. Both work the same ive found. Just depends on if you want to load through bootloader or L/E. Anyways Still i cannot get Bluetooth to work on my Sierra Partition using the 13,3 smbios. Im using brcmFirmwareRepo and BrcmPatchRAM2 and i just cant get them to load. Very strange. Even if i install them into L/E i cant get them to load into kextcache. Any Ideas? Ive attached my latest debug. 

debug_22106.zip

Dell 7559 AppleIntelInfo.txt

Bluetooth is related to XHCI, you need to use XHCI Limit patch or make UIAC of DSDT / SSDT for your XHCI.

 

TOTAL ports of XHCI for every smbios is different

 

Sent from my Mi Note 2 using Tapatalk

 

 

 

[tikizondo94]

10 minutes ago, Andres ZeroCross said:

Bluetooth is related to XHCI, you need to use XHCI Limit patch or make UIAC of DSDT / SSDT for your XHCI.

 

TOTAL ports of XHCI for every smbios is different

 

Sent from my Mi Note 2 using Tapatalk

 

 

 

Our minds think alike. lol. Ive been currently looking for the latest 10.12 USB port limit patch...lol

[tikizondo94]

Well Ive added the 10.12 USB port limit patch in kexts to patch, But for some reason brcm kexts are still not loading. Ive tried in L/E and in Clover/Other they dont show in Kextstat. Could you look at my SSDT-UIAC and see if its correct?

SSDT-UIAC.aml

config.plist

[tikizondo94]

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.)

Ok, sorry to have gone so far off topic. Your help has been awesome..Anyways, with the orginial problem of backlight. Backlight/Brightness seems to work with sierra. It has it moments where it wont work correctly but on battery power it seems to work correctly. And it also autodims when switching to battery. Now with Mojave i have not been able to get brightness controls at all. Its Odd. I have 2 drives in my machine. One with Mojave on it and the other with Sierra. I have CloverUEFI installed on each drive. So Im able to keep a "stable" drive when testing the other. Anyways, The only things noticed with the Sierra install have been the Battery will randomly not show its plugged in, or it will read 100% all the time. The other is No Bluetooth. Now this is with your clover and ACPI patched files. And SmBIOS of 13,3. On the Mojave drive I use 11,1 smbios and Battery and bluetooth work fine. But with no backlight controls. Confusing i know. Anyways, if i could get bluetooth rolling id be set. Port limit patch does seem to change anything. Any ideas? 

Debugging Files.zip

[mnfesq]

22 hours ago, tikizondo94 said:

Ok, sorry to have gone so far off topic. Your help has been awesome..Anyways, with the orginial problem of backlight. Backlight/Brightness seems to work with sierra. It has it moments where it wont work correctly but on battery power it seems to work correctly. And it also autodims when switching to battery. Now with Mojave i have not been able to get brightness controls at all. Its Odd. I have 2 drives in my machine. One with Mojave on it and the other with Sierra. I have CloverUEFI installed on each drive. So Im able to keep a "stable" drive when testing the other. Anyways, The only things noticed with the Sierra install have been the Battery will randomly not show its plugged in, or it will read 100% all the time. The other is No Bluetooth. Now this is with your clover and ACPI patched files. And SmBIOS of 13,3. On the Mojave drive I use 11,1 smbios and Battery and bluetooth work fine. But with no backlight controls. Confusing i know. Anyways, if i could get bluetooth rolling id be set. Port limit patch does seem to change anything. Any ideas? 

Debugging Files.zip

 

First question:  What are you doing in your UEFI firmware to make sure that when you want to boot Mojave, you are using the CloverX64.efi in the EFI partition on your Mojave drive.  Typically, UEFI firmware is not set up to have 2 EFI partitions from which to boot.  I have encountered this issue when I want to boot from Windows Boot Manager for my Windows 10 installation rather than booting from Clover.  The reason this is important is that you are assuming that all of the changes you make to your Clover folder in the EFI partition of your Mojave drive are being implemented when you boot to Mojave.  That may not be 100% true.

 

Second question:  Have you tried using SMCBatteryManager.kext since you are already using VirtualSMC.kext?  For me, it works much better than ACPIBatteryManager.kext. Also, I believe I made some DSDT patches to get battery power to display correctly.  That may be necessary for you but wait to do that until you have tried SMCBatteryManager.

 

Third question:  When you say that you have no brightness controls in Mojave, are you saying that you don't even have the slider bar? or just that the slider bar doesn't do anything?  I highly doubt that you would have no slider bar if the DSDT I edited for you is loading at boot.

 

Fourth question:  Did you try re-enabling that SSDT with all the errors?  You may need it and those errors may not be preventing your laptop from using the sensors it controls.  Just delete the SSDT entry from the disable SSDT section in your config.plist.