Search results

All works here after the update, except the backlight control. I had it installed via the guide of rehabman and all worked fine, but after the update the backlight control was gone and the backlight is again full on. Graphics used is an Intel HD630.

Sorry I have to reply like this, but the read carefully does apply to more people! I was not directly reporting a problem, I was just asking if more people have issues with the latest Mojave 10.14.3 update. I wanted to determine first if the change in behaviour is more a general OS update thing...

I had no backlight control and the backlight was full on, so I installed the stuff as described in this guide and all worked fine! However after the Mojave update to 10.14.3 the backlight control has been broken. Are there any other users with the same issue?

I had a working backlight path, but the backlight control stopped working with the update from 10.14.2 to 10.14.3. Thus certainly something changed in the graphic department with the latest update.

Device-id to "0x591B" did not make a difference. Anyhow thanks for your help and suggestions. Any idea why Hackintool doesn't work properly, while FB-patcher does? Both behave the same on the hackintosh as on a real mac. Is is depending on a certain kext that isn't there?

Sorry pressed post button instead of the attached files, here picture of boot screen.

No luck, during boot only apple logo but no bar and it hangs. I'm glad it is an installation on an external drive. Just plug it in my other laptop swap out the config.plist and I'm back ;-).

I disabled the settings: Change HECI to IMEI Change PCI0.VID to IGPU #1 Change PCI0.VID to IGPU #2 Change GFX0 to IGPU I also removed the UseIntelHDMI flag, so it is disabled. The functionality remains the same, no noticeable loss or gain in functionality. I tested all HDMI index bus id...

When I remove "Change GFX0 to IGPU" from the ACPI settings, then irrespective of how the "UseIntelHDMI" flag is set the LVDS line will always be red. The other change settings do not have influence on the behavior of the UseIntelHDMI flag. After reboot the LVDS is either reported as internal or...

I will remove the ACPI entries you mention and test first if it boots and have at least the same functionality as I have now. As for the Inject ATI and NVIDIA, I already had them removed. When I noticed the UseIntelHDMI, I went through the whole config.plist and saw the inject statements and...

When working on the config.plist file because of the devece id I noticed an entry: UseIntelHDMI Which was set at NO. So I altered to YES and rebooted and now I have a green line for the internal display. This gave me hope, so I start to try the index and bus id combinations, but no success to...

I tried the suggested platform and device id, but at the moment during boot that I normally see that the apple logo becomes smaller and less stretched, the machine now hangs. Just a black screen thats all. Thus at the moment otherwize the more advanced display settings becomes active it now goes...

I use MacBookPro14.3, since that seems the best match ijn CPU and screen size (not resolution). It is a mobile platform (laptop), so that seemed normal to me. I shall try the other platform ID and device Id and see what happens. I also noticed that the coloring of the lines was not as expected...

I tested as far as I know all Index 3 options and no luck. Any hint bout controlling the backlight, it seems that the app Brighter slider is not controlling the backlight, but just makes the pixels darker or lighter. Further I searched were the entries came from you asked about and the are from...

Just tested with my usb-c to HDMI converter. Under windows after login all ports work both USB-C and the HDMI and for all ports I can either mirror or extend the display under windows. Will now try the index 3 variants under macOS.

Just a thought what about framebuffer size? What I've read is that apple assumes a minimum of 64MB, while on most windows systems it is 32MB. I was able to set it in the bios to 64MB and removed the framebuffer lines from the config.plist file related to fix this to get it to 64MB.

Yes I do see the changes, after the reboot if "Apply Current Patches" is enabled. But I can only see them in FB Patcher and not in Hackintool. For some reason Hackintool v1.8.2 does not work, the dropdown boxes are not populated after "Framebuffer->macOS 10.14". Hacktool has the same behavior on...

I've tested the following combinations, all in vain. The last item always goes to -1, it seems it is not possible to define more then 3 indices. I can define them in FB patcher and put it in the config.plist file, but after a reboot the last one will be at index -1 and the other altered settings...

What about my indices? They go 0, 2, 3, -1. Thus Framebuffer_con0 is now Index 0, Framebuffer_con1 is index 2, Framebuffer_con2 is index 3 and Framebuffer_con4 is -1 and thus now disabled I assume.

I just wonder which pipe value to use for enabling Index 3 and what the impact of that value is. Why is the one that works 8 and the other two entries 10, does it hint to how it is connected, to the Intel or the NVIDIA?