• OS

  • Disable dithering on M1/M2 devices

mirza Let's try to make booting more verbose by adding the -v parameter

Please, try to input

sudo nvram boot-args="-v enableDither=0 PE_i_can_has_debugger=1 iomfb_RuntimeProperty_enableDither=0"

Then make sure the boot-args was accepted:

nvram -p | grep "boot-args"

The output must be the same as the previous input.

Reboot your laptop.

run the command

log show --process 0 | grep "IOMobileFramebufferLegacy"

    Same issues unfortunately. And, just to be on a clear side, I'm pluggin my external monitor back and forth with PC and MBA, while closing MBA, just to make sure. For hours I'm using my Benq without any issues, in fact feels relaxing on the eyes, I plug it to MBA, wait 5 mins or so, eyes start to burn a bit, light headache, and whole nine yards. But please, do keep trying 🙂 Maybe you will be the one to solve hundreds or thousands of people's issues. I mean, it has to be software issue, otherwise it doesn't make sense from this I wrote above…

      mirza Did log show --process 0 | grep "IOMobileFramebufferLegacy" print something?

          mirza In this case, direct kernel debugging can only help. Not sure it is possible on the Apple silicon devices.

          But before, it still worth to check more drivers. Maybe I missed something.

            mirza But the shared solution would definitely work in the case if the IOMobileFramebufferLegacy class is used. It is unclear why its debug messages are missed in the log. This class is initialized in the kext's global constructor.

              I read somewhere (I think macroumors) that temporal dithering is not used at all on macbook air m1… Is that a possibllity? Then what is generating this problem?

                mirza It is difficult to say right now as I never have M1/M2 based devices. I will get such device on Monday so I will have more flexibility.

                  mirza To speed up the process, could you share the output of the 'kextstat' command?

                  And it would be very useful to get all kexts itself. You can do it by zipping the folder /System/Library/Extensions

                    mirza …and, please, the output of the "kextstat" command.

                      mirza just type 'kextstat' in the terminal. This command gives you the output of currently loaded kernel extensions. Copy the output and share it here or somewhere else.

                        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.

                            dev