sorry lost it, how to write it?
Disable dithering on M1/M2 devices
- Edited
mirza If you really use macOS ventura, it explains the weird things I noticed (you don't have any mentions of 'IOMobileFramebufferLegacy' in the kernel log).
The macOS Ventura changed concept of using of the kernel extensions. I don't familiar with the technical details.
The folder you dropped just doesn't have the drivers which existed on the previous macOS versions.
Which OS should I install? I will try to revert to older one.
ok I will do it now.
mirza I guess the already entered commands are still active. You can verify it by the "nvram -p | grep boot-args" command.
If it will return the parameters you passed to the command, please, run the
log show --process 0 | grep "IOMobileFramebufferLegacy"
command.
Also, please do zipping of the /System/Library/Extensions folder and share it.
I've got an M2 Macbook air coming today- let me know what you need to help with testing. Assume it will come out of the box with Monterey, I will hold off upgrading til there is a solution.
Just out of curiosity, do we have a solution for setting lower color depth? This is something that has helped me in the past. On windows laptops, easily accessed through integrated graphics settings. 6 bit is also very easy to determine dithering vs. no dithering using test patterns.
dirtydenim yes please! Would be incredible if this solution actually works for eye strain
dirtydenim Could you please check the results of the command
sudo nvram boot-args="enableDither=0 PE_i_can_has_debugger=1 iomfb_RuntimeProperty_enableDither=0"
whether it will have any effect.
Also, it would be useful to see the output of the command
log show --process 0 | grep "IOMobileFramebufferLegacy"
To clarify- do you want me to run in normal desktop mode or recovery mode?
dirtydenim On M1/M2 devices this command should be executed in normal mode only.
- Edited
I was able to successfully execute the command. I do not see any changes in my test image but sometimes it requires lowering the color depth as I mentioned to show the steps instead of a smooth gradient.
Note, I first had to use the "csrutil disable" command in recovery mode.
Difficult to tell if there is a comfort improvement yet, I will report back after some time and try some other objective tests- images, etc. to validate dithering is indeed disabled.
Also @NewDwarf there was no result from the log show --process 0 | grep "IOMobileFramebufferLegacy" command.
Is there a log I need to review?