NoobsPlanet

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics, posts and unlimited download to our resources, as well as connect with other members through your own private inbox!

Mojave Brightness Control Stops Working

mossy

New member
Hi, originally the Mojave Backlight fix (https://noobsplanet.com/index.php?threads/enable-and-control-brightness-backlight-for-mojave.72/) worked perfectly for me! At some point today it stopped working though. I was able to solve it temporarily by deleting and re-adding the 4 files cited above and running the lines of code you provided.

Immediately after "sudo touch /System/Library/Extensions && sudo touch /Library/Extensions && sudo kextcache -u /" , brightness slider and key commands were working perfectly. After rebooting it will only register backlight on (100%) or off (0%). Any ideas? Very much appreciated, this site is incredible! I've attached my CLOVER folder, let me know if you need anything else, thanks :)
 

Attachments

Last edited:

mossy

New member
Update: I noticed that after letting my laptop time out and go to sleep that normal brightness functionality returned upon waking. But upon rebooting it is back to the same situation as above. I was able to repeat this success once by going into Sleep from the Apple menu, (ie. normal brightness functionality upon reawakening), but it's not a convenient or reliable fix since it doesn't work every time. Thoughts? Cheers!
 

mossy

New member
Also, when I run ;
sudo touch /System/Library/Extensions && sudo touch /Library/Extensions && sudo kextcache -u /

I get ;
Warning: /AppleInternal/Library/Extensions: No such file or directory (although it does continue from there and runs the process)

this was also the case when it was originally working for me but figured i should mention!
 

mossy

New member
I recovered my system and am up and running again! Brightness Control even works perfectly now after revisiting the tutorial mentioned above. If anything happens like last time where it stops working, will report back! Thanks again for everyone who makes this site amazing!
 

mossy

New member
Sorry for the long winded journey but yes, after all is said and done, I end up at the same point- in Mojave, everything running super smooth except for Brightness control. As I suspected, the fix in the tutorial cited above only works until after reboot, at which point brightness control stops working. Fn-S and Fn-B still bring up the brightness indicator visual but the brightness of the screen only changes if either 0% or 100%. My hypothesis would be that something (DSDT / SSDT problem?) is interfering during the boot process but I've tried everything I can think of and don't know exactly what I'm looking for so any advice would be greatly appreciated!

I've attached my clover folder, please let me know if anything else is needed!
 

Attachments

mossy

New member
Latest update is that it that Brightness Control now works again, but only after sleep, similar to how I described earlier in the thread.

If i click sleep from menu and reawaken too quickly it doesn't work, but if it sits for about 20 seconds it seems to reach a deeper state of rest (lol) , at which point I can re-awaken with working brightness. This feels very beyond my grip so any help is still appreciated! Here's my current clover folder as well since it is probably slightly different now than previous uploads.
 

Attachments

noobsplanet

Well-known member
Staff member
Administrator
Moderator
Welcome to NoobsPlanet @mossy & Happy New Year 2021.

The first thing your profile is incomplete, complete it first.

Hi, originally the Mojave Backlight fix (https://noobsplanet.com/index.php?threads/enable-and-control-brightness-backlight-for-mojave.72/) worked perfectly for me! At some point today it stopped working though. I was able to solve it temporarily by deleting and re-adding the 4 files cited above and running the lines of code you provided.

Immediately after "sudo touch /System/Library/Extensions && sudo touch /Library/Extensions && sudo kextcache -u /" , brightness slider and key commands were working perfectly. After rebooting it will only register backlight on (100%) or off (0%). Any ideas? Very much appreciated, this site is incredible! I've attached my CLOVER folder, let me know if you need anything else, thanks :)
Before answering your question I would like to know how you have installed Hackintosh in the system? It is recommended that you use RehabMan os x config (If you're using a laptop).

Sounds like the brightness value isn't stored in NVRAM. you may try the following post && rest NVRAM with command sudo nvram -c

attach the screenshot of output
Code:
sudo kextcache -u /
 

mossy

New member
Thanks for getting back to me :) I freshly installed from an osx Recovery boot usb as per : https://internet-install.gitbook.io/macos-internet-install/

Prior to that, I had used the following guide : https://osxlatitude.com/forums/topic/8506-dell-latitude-inspiron-precision-vostro-xps-clover-guide/ (Mojave section near the bottom of the page). I had the exact same results using that method, and in the process of trying to solve brightness, messed up my library/extensions folder (accidentally had FakeSMC in there while VirtualSMC was in EFI partition) and couldn't boot, hence why this time i used the ethernet osx recovery tool.

Re: brightness reset to max at start--- AptioMemoryFix.efi is already in drivers/uefi. This is the equivalent of drivers64UEFI/aptiomemoryfix-64.efi right? So should be all good?

Oh! Maybe this is something? running sudo nvram -c prints:
nvram: Error clearing firmware variables: (iokit/common) not permitted
 

mossy

New member
kextcache prints:
Bash:
Kext with invalid signatured (-67062) allowed: <OSKext 0x7fd3f1b0bf20 [0x7fff8c2738e0]> { URL = "file:///System/Library/Extensions/BrcmBluetoothInjector.kext/", ID = "org.rehabman.injector.BrcmBluetoothInjector" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7fd3f18899a0 [0x7fff8c2738e0]> { URL = "file:///System/Library/Extensions/CodecCommander.kext/", ID = "org.tw.CodecCommander" }


KernelCache ID: 4B0A132C00043AC70FC4FD1D5AD3F03A


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f8e008b1800 [0x7fff8c2738e0]> { URL = "file:///System/Library/Extensions/CodecCommander.kext/", ID = "org.tw.CodecCommander" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f8e00a3af20 [0x7fff8c2738e0]> { URL = "file:///System/Library/Extensions/BrcmBluetoothInjector.kext/", ID = "org.rehabman.injector.BrcmBluetoothInjector" }


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f8e00d43810 [0x7fff8c2738e0]> { URL = "file:///System/Library/Extensions/BrcmPatchRAM3.kext/", ID = "com.no-one.BrcmPatchRAM3" }
 
Last edited by a moderator:

mossy

New member
I will try to play with the RehabMan osx config by the way, but it's barely in my comfort zone so may take a minute for me to figure out!
 

mossy

New member
Minor update: though I'm not really familiar with hot patching, I tried the SSDT-PNLF from the Rehabman config folder in acpi/patches (i just renamed the .dsl to .aml which I read somewhere, not sure if that's proper) as well as a few different config.plists (HD 520 , HD4000 1600x900 6 series, and a couple others). Still no luck, brightness slider disappears in system preferences even when I try these.
 

noobsplanet

Well-known member
Staff member
Administrator
Moderator
Minor update: though I'm not really familiar with hot patching, I tried the SSDT-PNLF from the Rehabman config folder in acpi/patches (i just renamed the .dsl to .aml which I read somewhere, not sure if that's proper) as well as a few different config.plists (HD 520 , HD4000 1600x900 6 series, and a couple others). Still no luck, brightness slider disappears in system preferences even when I try these.
It is recommended that you use all the kext in Clover/Kext/Other folder so that you don't mess with permission issues and kext duplication. Renaming .dsl to .aml is a bad idea and recommend you to use the MaciASL tool which can be found in the download section. Also, are you using other DSDT patches? If yes, then how you manage to do it? Please attach the clover folder because you might be using some clover boot args which might be affecting brightness. If you are new to the DSDT patch read the following guide first.
 

mossy

New member
Yes, I have learned some more about the kext locations since I made that error! And yes, I assumed simply renaming would not really work but it was the best I could find from my knowledge / immediate research. Any DSDT patching would have been done through the Clover / config files I downloaded via my install method. I previously tried the AppleBacklightFixup + SSDT-PNLF patch which did not work. I have also already attempted to make my way through the "Disable NVIDIA / AMD" tutorial you linked there, but was never able to get Clover to boot with the F4 mode. I also did the Piker Alpha SSDT.aml generating tutorial before. At the moment I don't have my laptop charger so I can not try anything new. But at least wanted to report back and attach my clover folder. Thank you again and I will follow up tomorrow once I have my charger!
 

Attachments

mossy

New member
Latest update: I generated the SSDT.aml (with Pike R. Alpha method) in ACPI/patched. Unfortunately neither F4 nor any combination of Fn / Ctrl / Alt / Windows key /Shift with F4 have any effect in the Clover boot window so I'm not sure how to proceed with the DSDT patch. One thing I noticed is that brightness keys were actually working in the Clover menu with Fn-F11 and Fn-F12 upon booting. But after booting into Mojave, again the key commands revert to Fn-S and Fn-B, while not actually controlling the brightness despite showing the mac brightness graphic.

I've attached my Clover folder again, any suggestions appreciated! :)
 

Attachments

noobsplanet

Well-known member
Staff member
Administrator
Moderator
Latest update: I generated the SSDT.aml (with Pike R. Alpha method) in ACPI/patched. Unfortunately neither F4 nor any combination of Fn / Ctrl / Alt / Windows key /Shift with F4 have any effect in the Clover boot window so I'm not sure how to proceed with the DSDT patch. One thing I noticed is that brightness keys were actually working in the Clover menu with Fn-F11 and Fn-F12 upon booting. But after booting into Mojave, again the key commands revert to Fn-S and Fn-B, while not actually controlling the brightness despite showing the mac brightness graphic.

I've attached my Clover folder again, any suggestions appreciated! :)

The problem is here in your boot args, dart=0 debug=0x100 darkwake=no bpr_probedelay=200 bpr_initialdelay=400 bpr_postresetdelay=400 nvram -c you are clearing nvram in every boot so the brightness values is always cleared. The other problem of brightness might be due to dart=0 and darkwake=no args. I recommend you try booting removing all and if suceed, try removing from config.plist
 

mossy

New member
I've removed all boot args. The good news is that it didn't seem to introduce any issues so i guess I will leave it like that. The bad news as that it didn't solve the brightness issue. Any other ideas?
 

mossy

New member
I'm sure it's nothing but wondered if any of these intel graphics kexts in System/Library/Extensions could be interfering?
Screen Shot 2021-01-04 at 3.40.05 PM.png
 

mossy

New member
Small progress! Using the following config.plist actually sheds some light on the situation maybe! Now, brightness actually works immediately upon loading Mojave. The main problem now is that boot times are significantly slower and overall performance drops significantly. Also, the Mac OS brightness graphic does not appear (though it's not the end of the world for me). But I do need performance to be smooth so any help is appreciated either fine tuning this config file or my previous one to get the best of both worlds. I will try comparing the two and experiment with some different settings in the meantime!
 

Attachments

noobsplanet

Well-known member
Staff member
Administrator
Moderator
Small progress! Using the following config.plist actually sheds some light on the situation maybe! Now, brightness actually works immediately upon loading Mojave. The main problem now is that boot times are significantly slower and overall performance drops significantly. Also, the Mac OS brightness graphic does not appear (though it's not the end of the world for me). But I do need performance to be smooth so any help is appreciated either fine tuning this config file or my previous one to get the best of both worlds. I will try comparing the two and experiment with some different settings in the meantime!
That config may give you unexpected results now or later on because that is made for different IGPU. so per your signature, you should use the config already prepared by Rehabman. please try it out. If you get K.P. then don't panic just keep solving issues after that because this is the correct path to move with. (y)(y)
 

mossy

New member
I already tried the Intel 520 config file, it runs similar to my previous config except still no brightness and no audio output devices found either. This is why I tried the HD4000 1600x900 6series (I had read somewhere that choosing one of the configs with the 1600x900 could resolve display issues on certain machines...I forgot where or why I read that but it's not really relevant since using that file actually does cause brightness control to work). My troubleshooting today has led to notice that brightness control only works immediately after booting if I copy over certain settings from the HD4000 config, particularly the Devices / Properties tab:
Screen Shot 2021-01-06 at 7.21.47 AM.png


I don't understand nearly enough about what's going on here, but this also appears to be where the performance is dropping. (ie. all other factors remaining constant except this properties tab, things run faster and smoother but with no brightness.) I know there are many other variables but hopefully this is a clue in the right direction? Please let me know if you have any other ideas, thanks so much :)
 
Top