devilgrove But with this tweak, can you now use that MB? Is it something related with the dithering?
OSX dithering - Help wanted
Lauda89 i was able to use it before, but still with a decent amount of headaches and eyestrain. However after the fix it's practically as good as Safe Boot (I'm actively trying to find a way to make it 100% equal).
I'd be willing to share, but NewDwarf is technically the reason I was able to figure it out in the first place, so I would want to hear from him first before doing anything.
And yes, it's directly related to dithering.
devilgrove This would be a huge finding! If you share how to do it and several users experience benefits it is something you can bring to apple's attention to put an accessibility setting that would disable that feature.
Is something that can work only with intel GPU or also M1/2 SOC?
Lauda89 to be honest this issue has been around for so long that I don't think Apple cares at this point, but it would be good to get out to the masses so that they don't have to deal with this problem.
I tried looking up if the command would be available on Silicon, but couldn't find anything online. I'd need to get my hands on a Silicon laptop and do some testing on Terminal to figure it out.
devilgrove You can simply verify the result by the command
log show --predicate "processID == 0" | grep Dither
If you entered the correct command, you can see such kernel log
Default 0x0 0 0 kernel: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG ][MODESET ] Dither is disabled in pipe misc
if it will print out
Default 0x0 0 0 kernel: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG ][MODESET ] Dither is enabled in pipe misc
the command, you entered, was incorrect.
NewDwarf oh wow, when I entered the command, it actually says my dithering is still enabled. Wonder what I did wrong
- Edited
Since my solution seems to be a unique one (and could possibly be incorrect) I'll post it here.
In Terminal, write:
sudo nvram boot-args="dither=1"
Reboot.
Also, you can check if it's there by entering nvram boot-args
afterwards. It should write out boot-args dither-1
Edit: this is actually incorrect, it should be sudo nvram boot-args="dither=0"
, thanks to NewDwarf for the fix.
devilgrove Yay! You found it!
…But, you cannot enter this command in normal mode! You must enter the recovery mode first and then run that command.
To disable dithering you have to enter
nvram boot-args="dither=0"
Not sure why you put dither=1. 1 is incorrect parameter here.
devilgrove I'd be super keen to hear if you still find an improvement given the correct argument being used. I have found a 2020 to try it on but would appreciate hearing about your experience. Having seen your other threads our issue appears very very similar.
- Edited
NewDwarf well, the reason I thought it was dither=1 is because I read that the default was 0, so my assumption was 0=true and 1=false. And the output did change for me, so maybe I got lucky.
Also, I actually inputted your command into Terminal during recovery, but when I input log show --predicate "processID == 0" | grep Dither
, it still loops "Dither is enabled in pipe misc" every time. See picture below:
If you have any advice on that I'd appreciate it as well, I'm a bit confused now since my eyestrain has undoubtedly relieved.
devilgrove What exactly laptop you use?
CRoebuck Let us know how it goes! I'll keep you posted if I find anything else.
- Edited
devilgrove You must reboot your laptop in the normal mode. Check the logs in the normal mode!
NewDwarf it's a MacBookPro16,2
devilgrove Reboot to the normal mode. You have to add the nvram parameter only once. This parameter is passed to the kernel on booting.
NewDwarf the logs were actually in normal mode!
devilgrove Hmm. Interesting…
Could you share the output of below command, please?
nvram -p | grep dither
NewDwarf it outputted boot-args dither=0
devilgrove One more advice. Wait when the command
log show --predicate "processID == 0" | grep Dither
is finished. More likely, you see the old logs. The last string have to report you about disabled dithering.
NewDwarf Wow, you're right! It does say disabled at the end. I didn't even realize that I was looking at log history, I thought the command was constantly checking for some reason. Thank you!
Looks like OSX dithering has finally been solved