You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ALL and sorry if you find my question wrong placed.
I got a really tiny issue with the Backlight Register Fix: I'm running 13.7 and 15.3 on the same machine and according WEG FAQs at 13.4 and up the alternate blr fix is needed (I'm using the DevicePropertie "enable-backlight-registers-alternative-fix").
Against the FAQs the alternate fix isn't working on my Ventura but on all above (14.0 and up) - indeed I need to activate the "previous" enable-backlight-registers-fix to prevent the 3 minutes blackout even in the latest version of Ventura.
This is a bit annoying because I can't load the right fix depending on the kernel version (at least I don't know of any way to do that). So all I can do is change the DeviceProperty before loading the other macOS (which I of course regularly forget to do).
My idea / question is: would it be possible to "move" the blr fix from DP to the WEG Kext, e.g. info.plist? Because a Kext of course I can load in dependence of the kernel version.
Btw.: the issue is the same when using boot-args.
I guess I got this, because my laptop has a whiskey lake cpu (i7-8565U) which aren't natively supported by macOS (correct me if I'm wrong - a whiskey lake Mac was never released). Btw. another even tinier #issue is a weird blinking, when the display switches from UEFI driver to iGPU...
So again: this is not a bug report, because everything works - just not as well as it could.
The text was updated successfully, but these errors were encountered:
schrup21
changed the title
WhateverGreen tiny Issue regarding Backlight Registers Fix
project:green WhateverGreen tiny Issue regarding Backlight Registers Fix
Jan 27, 2025
schrup21
changed the title
project:green WhateverGreen tiny Issue regarding Backlight Registers Fix
WhateverGreen tiny Issue regarding Backlight Registers Fix
Jan 27, 2025
Please note this has been fixed by Apple in 13.5 and enable-backlight-registers-alternative-fix or -igfxblt is no longer required on macOS Ventura 13.5 and later
Please note this has been fixed by Apple in 13.5 and enable-backlight-registers-alternative-fix or -igfxblt is no longer required on macOS Ventura 13.5 and later
Thank you for your reply but I have to disagree.
If I deactivate the backlight register fixes, both OS (13.7.3 and 15.3) getting the "3 Minutes blackout". As I said above:
on 13.7.3 I have to activate the Property enable-backlight-registers-fix, to prevent the issue
on 14.0 and above (in the meantime I'm using 15.3) I have to activate enable-backlight-registers-alternative-fix
Hi @ALL and sorry if you find my question wrong placed.
I got a really tiny issue with the Backlight Register Fix: I'm running 13.7 and 15.3 on the same machine and according WEG FAQs at 13.4 and up the alternate blr fix is needed (I'm using the DevicePropertie "enable-backlight-registers-alternative-fix").
Against the FAQs the alternate fix isn't working on my Ventura but on all above (14.0 and up) - indeed I need to activate the "previous" enable-backlight-registers-fix to prevent the 3 minutes blackout even in the latest version of Ventura.
This is a bit annoying because I can't load the right fix depending on the kernel version (at least I don't know of any way to do that). So all I can do is change the DeviceProperty before loading the other macOS (which I of course regularly forget to do).
My idea / question is: would it be possible to "move" the blr fix from DP to the WEG Kext, e.g. info.plist? Because a Kext of course I can load in dependence of the kernel version.
Btw.: the issue is the same when using boot-args.
I guess I got this, because my laptop has a whiskey lake cpu (i7-8565U) which aren't natively supported by macOS (correct me if I'm wrong - a whiskey lake Mac was never released). Btw. another even tinier #issue is a weird blinking, when the display switches from UEFI driver to iGPU...
So again: this is not a bug report, because everything works - just not as well as it could.
The text was updated successfully, but these errors were encountered: