Jump to content
intruder16

Intel HD4600 banding/gradient/16-bit colors issue Y510p

127 posts in this topic

Recommended Posts

@intruder16
 

There is one thing that gets broken when this glitch appears, the restart functionality. Meaning, after restart the screen stays blank with cpu, fans etc still running. Not even the BIOS (pre-boot logo) shows up (coz of which i think it's a serious issue).


Actually, I found there is not a problem with the restart functionality. Previously we thought -- at least I did -- that the laptop would halt once we go for display off/on sequence and choose to reboot with the symptoms you mentioned. However, the reboot process works as usual but the graphics does not work correctly. I made myself sure of that using couple of simple procedures:

  • Boot OS X
  • Reproduce the graphics issue (set display off then on)
  • Restart, wait for a few moments (that are usually enough to get you in Clover again)
  • Use keyboard to choose and boot into Windows
  • Wait a few moments (that are usually enough to get logged into Windows desktop)
  • Use keyboard keystrokes that would shut down the PC (or actually make any feedback like logging a text file)
  • Windows will shutdown (or the feedback text file will be created)

Another thing I tried, which is interesting BTW:

  • Boot OS X, set the system to auto login, and set one of the hot corners to perform display sleep.
  • Reproduce the graphics issue (set display off then on)
  • Restart, wait for a few moments (that are usually enough to get you in Clover again)
  • Use keyboard to choose and boot into OS X
  • Wait a few moments (that are usually enough to get logged into OS X desktop)
  • Move the mouse cursor to the predefined corner then move it away
  • Display will wake up and you have a usable desktop as usual (but of course with the gradients as expected)

So basically no problem with restart itself after graphic re-initialization but the problem is with the wrongly configured graphics and how to display while restarting. Therefore, I believe if we are able to force OS X to initialize (and be able to re-initialize) the graphics in the correct way, the graphics data will be handled correctly across OS's and POST too. Currently, only the graphics is the problem.

Share this post


Link to post
Share on other sites
Advertisement
While I was searching around I came across these slides of AMD presentation on graphics with UEFI, and I quote that to allow dual boot (booting in UEFI or Legacy):
 
The industry needs to provide both legacy VGA BIOS and GOP for a transition period.

 

And of course this is the case and Intel provides both since Windows works flawlessly in either mode. However, the problem is to find the driver for OS X that can work with both. Especially since there is one major disadvantage of using Graphics Output Protocol (GOP) with UEFI:

 

OS or OS applications lose capability of changing display resolution and configuration if OS high performance display driver is not installed or functional.

 

In light of this, I strongly think the problem is with the the driver and nothing to do with anything else. The following is a diagram summarising the problem and I hope it make the whole situation clearer:

 

graphics.png

 

For now, Mobile HD4600 works in Yosemite disguised as Desktop HD4600. We need to check if people with actual Desktop HD4600 are having the same issue or not. If so, then Desktop HD4600 is not fully supported out of the box as thought of. Otherwise, Mobile HD4600 may need some more work (on driver) than just dressing it like its Desktop brother.

 

Just my two cents ...

Share this post


Link to post
Share on other sites

If you haven't solve the 16bits color problem yet, EDID edit might save you here. Comparision between a real Mac's EDID and many laptops shows that common laptops's EDID version is 0103 or lower, while real Mac uses 0104. Also the 1st value of basic param on real Mac is 90, while on common laptops are 80. Try edit those out, and recalculate the checksum. Fix yellow gradient issues on laptops with AMD GPUs and Nvidia GPUs's 16bit color issue, like this one

Share this post


Link to post
Share on other sites

If you haven't solve the 16bits color problem yet, EDID edit might save you here. Comparision between a real Mac's EDID and many laptops shows that common laptops's EDID version is 0103 or lower, while real Mac uses 0104. Also the 1st value of basic param on real Mac is 90, while on common laptops are 80. Try edit those out, and recalculate the checksum. Fix yellow gradient issues on laptops with AMD GPUs and Nvidia GPUs's 16bit color issue, like this one

 

Thanks for this. Although the OP stated he tried custom EDID and I was about to say that it is tried and proven not to work. however, I thought to give it a try myself and it worked like a charm and the gradients are all gone now.

 

With that said, still there is a problem with driver I guess. The re-initialized graphics after display off/on are still not correct and render BIOS without display after restart.

 

But this a good advance I must say, thanks!

Share this post


Link to post
Share on other sites

Thanks for this. Although the OP stated he tried custom EDID and I was about to say that it is tried and proven not to work. however, I thought to give it a try myself and it worked like a charm and the gradients are all gone now.

 

With that said, still there is a problem with driver I guess. The re-initialized graphics after display off/on are still not correct and render BIOS without display after restart.

 

But this a good advance I must say, thanks!

Glad to hear it work. Hope OP update the 1st post

Share this post


Link to post
Share on other sites

Glad to hear it work. Hope OP update the 1st post

 

Yea really thanks. I sent him a PM, he is away for sometime I believe. 

 

Anyway, I see that custom EDID fixed one of the registers related to 16-bit color behaviour. The register PIPE_DDI_FUNC_CTL_EDP used to change from 0x82000002 (this is normal colours) to 0x82200002 (this appears as 16-bit colours) once display is set off then on (and driver initialise). Now that register does not change upon driver re-initialisation which is good. There are other registers that still does change though and I think they are related and I will start investigating them. Any more tricks you know about? Thanks.

Share this post


Link to post
Share on other sites

Yea really thanks. I sent him a PM, he is away for sometime I believe. 

 

Anyway, I see that custom EDID fixed one of the registers related to 16-bit color behaviour. The register PIPE_DDI_FUNC_CTL_EDP used to change from 0x82000002 (this is normal colours) to 0x82200002 (this appears as 16-bit colours) once display is set off then on (and driver initialise). Now that register does not change upon driver re-initialisation which is good. There are other registers that still does change though and I think they are related and I will start investigating them. Any more tricks you know about? Thanks.

 

Oh wow, I'll have to give this a shot. Thanks for all the work, ahmed, and for the EDID suggestion vusun.

 

So if I'm understanding, the EDID injection will solve the gradients problem, but upon reboot what happens?

Share this post


Link to post
Share on other sites

First of all, sorry for being away for so long. Now onto topic.

 

@vusun123,

 

I did try custom EDID injection before but didn't notice anything. More specifically here. Maybe i was just looking for the end result i.e. 16-bit color fix.

 

@ahmed_ais,

 

Great Work!

 

Did you set the basic parameters frm 80 -> 90 and recalculated checksum? Anything else you changed? I'll try to reproduce it.

 

EDIT : My source : here.

Share this post


Link to post
Share on other sites

@intruder16

 

Using a custom EDID fixed the value of the register PIPE_DDI_FUNC_CTL_EDP and it does not change its value after display off/on. This resulted in fixing the 16-bit colour problem. The customisations made are based on vusun123 advice:
  • Change EDID version from 0103 to 0104
  • Change first value of basic param from 80 to 90
  • Fixing EDID checksum (last value from 7d to 6c)
 
The custom EDID is converted to Base64 and injected in Clover so this have to be added to Graphics section.
<key>Graphics</key>
<dict>
<key>InjectEDID</key>
<true/>
<key>CustomEDID</key>
<data>
AP///////wAw5BYEAAAAAAAXAQSQIxN4ChXVnllQmCYOUFQAAAABAQEBAQEB
AQEBAQEBAQEBGjaAoHA4H0AwIDUAWcIQAAAZAAAAAAAAAAAAAAAAAAAAAAAA
AAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDE1NldGMS1UTEMyAGw=
</data>


.. .. .. .. .. 
</dict>

 

 

EDIT:

 

This fixed the 16-bit color issue so now changing resolutions, connecting external display, display sleep, system sleep, are all hypothetically works in acceptable mode. The restart functionality is working as I previously found although without display as there are more to be fixed. However, I believe we can skip restart and go for shutdown for the time being until we know for sure what is the problem with the driver.

Share this post


Link to post
Share on other sites

If you haven't solve the 16bits color problem yet, EDID edit might save you here. Comparision between a real Mac's EDID and many laptops shows that common laptops's EDID version is 0103 or lower, while real Mac uses 0104. Also the 1st value of basic param on real Mac is 90, while on common laptops are 80. Try edit those out, and recalculate the checksum. Fix yellow gradient issues on laptops with AMD GPUs and Nvidia GPUs's 16bit color issue, like this one

 

Funny...

 

I have this in my hackintosh notes...

 

investigate:

 

changing Basic Param in EDID from 90 to 80 to fix gradient issues?

Share this post


Link to post
Share on other sites

Funny...

 

I have this in my hackintosh notes...

 

 

Yea and I followed a conversation between you, intruder16, and the-darkvoid on the other forum and this fix was suggested. However, I think changing Basic Param in EDID alone was not enough here, I also changed EDID version to 0104. (I assumed it was not enough as I read that the OP already tried changing Basic Param only and it did not work).

 

BTW, when I edited my EDID I changed from 80 to 90 not the other way around.

 

Thanks for your help

Share this post


Link to post
Share on other sites

Funny...

 

I have this in my hackintosh notes...

 

 

I know. Right. I linked our conversation about this in post #83. 

 

Didn't work for me then. I'll check if it works now.

Share this post


Link to post
Share on other sites

I think I used the wrong checksum, I need to fix that ... I hope it does not affect anything!

EDIT1: even the native EDID has invalid checksum according to http://www.edidreader.com/

 

EDIT2: It turn out the mentioned website is buggy and the checksum is correct actually. I checked with this script https://github.com/mochikun/EDID_checksum after converting the code to work with text file instead of binary and the checksum matched. All good!

Share this post


Link to post
Share on other sites

Oh wow, I'll have to give this a shot. Thanks for all the work, ahmed, and for the EDID suggestion vusun.

I believe you have G510 right? If so, I advice you to extract your own EDID and customise it as in post #84. This because I am not sure Y510p and G510 displays are having the same EDID.

Share this post


Link to post
Share on other sites

Holy fcking {censored} !!!! It fcking worked !!!!

 

Can't believe it ! No more 16-bit {censored} !

 

@RehabMan,

 

All we had to do is change EDID version from 1.3 to 1.4 and basic parameter from 80 to 90 and fix the checksum. We did all that before except changing EDID version.

 

@vusun123,

 

Thanks a lot for the heads up mate! 

 

@ahmed_ais,

 

Thanks for all the hard work. Great!

 

 

I don't know how i overlooked this crucial info, but in my source of info linked in post #83, he also changed the EDID version. I tried without this.

 

 

Anyway, thanks all very very much. Time for me to update OP.


@mattcurtis,

 

Please try the suggestions as @ahmed_ais suggested. I'm sure it'll work. If any problems post here.

Share this post


Link to post
Share on other sites

Holy fcking {censored} !!!! It fcking worked !!!!

 

Can't believe it ! No more 16-bit {censored} !

 

@RehabMan,

 

All we had to do is change EDID version from 1.3 to 1.4 and basic parameter from 80 to 90 and fix the checksum. We did all that before except changing EDID version.

 

@vusun123,

 

Thanks a lot for the heads up mate! 

 

@ahmed_ais,

 

Thanks for all the hard work. Great!

 

 

I don't know how i overlooked this crucial info, but in my source of info linked in post #83, he also changed the EDID version. I tried without this.

 

 

Anyway, thanks all very very much. Time for me to update OP.

@mattcurtis,

 

Please try the suggestions as @ahmed_ais suggested. I'm sure it'll work. If any problems post here.

Glad that worked out mate

@Rehabman change both EDID version and basic param, and you are writing the fix in the wrong order

Share this post


Link to post
Share on other sites

Glad that worked out mate

@Rehabman change both EDID version and basic param, and you are writing the fix in the wrong order

I'll add it to my notes. But since I don't have this issue on any of my machines, I never investigated further.

 

I suppose 80->90 or 90->80 depends on what you find in your existing EDID.

 

My notes now read:

investigate:

 

changing Basic Param in EDID from 90 to 80 to fix gradient issues?

or changing Basic Param in EDID from 80 to 90?

Depends on what you find in your native EDID?

 

also update version from 1.3 to 1.4.

Share this post


Link to post
Share on other sites

I'll add it to my notes. But since I don't have this issue on any of my machines, I never investigated further.

 

I suppose 80->90 or 90->80 depends on what you find in your existing EDID.

 

My notes now read:

That would be 80 to 90, since 90 is from real Macs. But trust me on that one

Share this post


Link to post
Share on other sites

That would be 80 to 90, since 90 is from real Macs. But trust me on that one

I'll leave my notes as-is. Obviously, if you already have one value it can't hurt to try the other one (hackintosh requires using your brain)...

 

What would be neat here is a DSDT patch that could automatically inject the modified EDID. I did a little bit of work on it in the past, but haven't found a reliable way to retrieve the panel EDID from DSDT code at _INI. I'm sure it is possible though, but will require more reading of the PRMs.

Share this post


Link to post
Share on other sites

....What would be neat here is a DSDT patch that could automatically inject the modified EDID. I did a little bit of work on it in the past, but haven't found a reliable way to retrieve the panel EDID from DSDT code at _INI. I'm sure it is possible though, but will require more reading of the PRMs.

 

That would be great indeed!

Share this post


Link to post
Share on other sites

Holy fcking {censored} !!!! It fcking worked !!!!

 

Can't believe it ! No more 16-bit {censored} !

 

 

@ahmed_ais,

 

Thanks for all the hard work. Great!

 

 

I don't know how i overlooked this crucial info, but in my source of info linked in post #83, he also changed the EDID version. I tried without this.

 

 

Anyway, thanks all very very much. Time for me to update OP.

 

...

LOOL .. yeah it feels so good without that $hit!

 

Thanks for your words, everyone did his best.

 

That said, I think you should also edit this part of the OP:

There is one thing that gets broken when this glitch appears, the restart functionality. Meaning, after restart the screen stays blank with cpu, fans etc still running. Not even the BIOS (pre-boot logo) shows up (coz of which i think it's a serious issue).

 

Because as I mentioned earlier, the restart functionality is all fine but with no display. This is related to another graphics driver issue that is yet to be fixed if someone is interested. I would prefer if you remove this part all together so we can start a new thread dedicated for that issue only using the diagram I made in post #77 for example. 

Share this post


Link to post
Share on other sites

Sure. I'll do it right away.

 

EDIT: Done.

 

Good. And just for the record I want to add this:

 

Once display is set OFF then ON and something change in IGPU memory. Upon restart in this case the system loses the display until further instruction but proceeds from POST to Clover in darkness.

  1. If we blindly choose OS X and hit Enter, we can get the display back on with ease. By pressing Fn+F2 to turn off display via hardware then pressing them again (immediately) the display will return.
  2. If we blindly choose Windows and hit Enter, we can get the display back on with ease too. Once Windows is loaded in the dark, pressing Fn+F1 will set Windows to sleep, then pressing any key will wake up the machine and display will be back on.

These are just some workarounds but of course the problem have to be solved from the root.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By mpe
      Hi,
       
      After wakeup my system is slow, console input show some duplicate character when I type some commands. Intel Power Gadget is shows no more statistics.
      I am looking for solution several days, but I can't find.
       
      Maybe some one have the same system or tips for me?
       
      I have already attach the Runme.app zip
       
      Best regards,
       
      mpe
      Send me mpe.zip
    • By gk12345
      Hi everyone, after lots of attempts i managed to install Mojave 14.4 on my asus zenbook ux303ub and get almost averything working, except i wasnt able to make wifi work with sleep, i replaced the intel wifi with dw1560/bcm94352z which i made to work by installing the kexts.The problem is that when i install it sleep gets affected, when i press sleep it takes 1 minute to go to sleep and when i press the power button it wakes to a black screen that is showing only the cursor and i have to force shut down by holding power button , so in order to fix sleep the only way i have found is to select "fixregions" in config.plist acpi section but then wifi stops working, it shows "hardware not installed" when i click the icon and only bluetooth works.I have tried clover config changes, patching ssdt and dsdt, usb ssdt, installing kexts in different locations but none of them seem to work , can someone help me with this?
      I attach the files below , thanks.
      debug_25741.zip
    • By BauerMac
      Hey guys,
      I hope you can help me solve a mystery.
      Even the amazing Mald0n has been working hard to help me find a solution, but now were are both stuck.
      Creative thinking or maybe just help to see the forest for the trees would be highly appreciated.
       
      PROBLEM:
      Mac will not sleep.
      Monitors sleep fine, and come back on with touch of keyboard.
      GPU and CPU coolers are constantly running on idle to low load and will not go on standby no matter what we have tried.
      Even when using full “Shut down” via apple menu the lights from the MoBo or GPU are pulsing slowly, which they normally dont as far as I recall.
      (This specific issue could possibly be solved by using ErP Ready in BIOS. Haven´t tested this since that´s a smaller issue ATM)
       
      Everything else seems to be working fine.
      This problem started appr a week ago, and I have no idea why.
      No major installs, updates or changes that I can think of.
       
      GOALS:
      • To be able to activate sleep via apple menu.
      • To have it sleep within 15-30 secs and wake up quickly (like it did before) via push on Power button

      TECH SPEC:
      • Running 10.13.6
      • Asus Maximus X Hero Wifi
      • Gtx 1080 Ti
      • 32 GB Corsair RAM
      • Intel i7 8700K
      • 2 monitors via Displayport
      • 6 internal disks (2 HDD, 4 SSD)
      • 1 external backup
      • 1 internal USB hub/SD reader
      • 3rd party Bluetooth and Wifi (Asus MB not compatible)
      • No Blutooth mouse, KB etc

      WHAT I HAVE DONE SO FAR:
      • Used Mald0n’s custom DSDT with latest config
      • IUpdated to latest Security Update
      • Updated to latest BIOS
      • Updated NVIDIA webdriver and CUDA to latest
      • Disconnected LED monitors and tested with old Mac monitor via DVI to see if Displayports were the issue
      • Disabled Adobe CC Sync
      • Run CleanMyMac
      • No start-up apps or extensions in System Prefs
      • Disk Utility: checked all disks
      • Terminal: no info on wake reason at all. (Possibly because it doesn´t sleep, hence nothing is interrupting it).
      • Blutooth allowed to wake sleep: set to OFF
      • Power manager: only setting is “never switch off monitors”. The rest are off/unchecked
      • BIOS: Tested by setting "ErP ready" to S5 > no difference
      • DSDT and EFI folder screenshot attached.

      I think that’s it - otherwise just ask
      I have read a lot of articles on this type of issue, but none with a clear answer.
      So if anyone can solve this mystery, it would be amazing!
      Thank you in advance!
       
      Bauermac DSDT.aml.zip



      UPDATE:
      Of course it was something seemingly insignificant and stupid that prevented sleep: An unfinished PRINTER job.... 
      After clearing the printer queue, it went to sleep but woke up immediately after due to a USB power issue. Possibly an internal USB/SD hub.
      Mald0n used his magic and made a new DSDT file to fix that, and now the machine is running almost perfectly apart from a fickle Bluetooth (fingers crossed).

      Hope this can help others out there with issues.

       
    • By vlgngrbrdmn
      Hey all,
       
      This is my first time posting to this forum.
       
      Here is my problem: My main issue is random freezing of my display (i.e. cannot move my mouse) and nothing being displayed after my monitors go to sleep (i.e. lock my screen, wait a few minutes, try to move mouse/type on keyboard. My displays wake up but display "no signal"). I have to reboot in order to use my Hackintosh again.

      Another issue that I am experiencing is that, every time I reboot my system and login initially, my right and left vertical displays do not display correctly until I turn one of them off and back on again. It is kind of hard to describe what is wrong, but basically the dimensions of the display and the orientation (horizontal vs. vertical) is wrong, and my mouse does not display in the correct place on the screen.

      Either way, after some research it looks like this all may be due to my Framebuffer being incorrect. However, I am having a hard time trying to determine whether that is the case and, if so, how to fix it.

      I did manually try to add a Framebuffer ("Kamarang") into my config.plist below, however that did not seem to make a difference.

      Any help with this would be much appreciated! Also, please let me know if I should upload anymore information.

      Currently, My setup consists of 1 Dell U3415w and 2 Dell 2415 monitors in an "H" configuration (both 2415s setup vertically on either side of the U3415W).

      This is all being powered by a SAPPHIRE Radeon RX Vega 64 (https://www.newegg.com/Product/Product.aspx?Item=N82E16814202326) with each monitor plugged via a DisplayPort.

      I am currently running the latest version of macOS Mojave, 10.14.4.

      I am also using the latest version of the Clover boot loader (4920) with the following kexts located in kexts\Other:
      AppleALC.kext AtherosE2200Ethernet.kext Lilu.kext USBInjectAll.kext VegaTab_64.kext VirtualSMC.kext WhateverGreen.kext My config.plist file contains the following:
      ?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>#DisableDrivers</key> <array> <string>CsmVideoDxe</string> <string>VBoxExt4</string> </array> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Fixes</key> <dict> <key>FixHPET</key> <true/> <key>FixIPIC</key> <true/> <key>FixRTC</key> <true/> <key>FixShutdown</key> <true/> <key>FixTMR</key> <true/> </dict> <key>Patches</key> <array> <dict> <key>Comment</key> <string>change XHCI to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDSQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change XHC1 to XHC</string> <key>Disabled</key> <false/> <key>Find</key> <data> WEhDMQ== </data> <key>Replace</key> <data> WEhDXw== </data> </dict> <dict> <key>Comment</key> <string>change SAT0 to SATA</string> <key>Disabled</key> <false/> <key>Find</key> <data> U0FUMA== </data> <key>Replace</key> <data> U0FUQQ== </data> </dict> </array> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>MATS</string> </dict> </array> <key>FixHeaders</key> <true/> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>PluginType</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>keepsyms=1 dart=0 debug=0x100 shikigva=40</string> <key>DefaultVolume</key> <string>LastBootedVolume</string> <key>Timeout</key> <integer>5</integer> </dict> <key>BootGraphics</key> <dict> <key>#DefaultBackgroundColor</key> <string>0xF0F0F0</string> <key>EFILoginHiDPI</key> <integer>1</integer> <key>UIScale</key> <integer>1</integer> </dict> <key>CPU</key> <dict> <key>#BusSpeedkHz</key> <integer>133330</integer> <key>#FrequencyMHz</key> <integer>3140</integer> <key>#HWPEnable</key> <true/> <key>#HWPValue</key> <string>0x30002a01</string> <key>#QPI</key> <integer>4800</integer> <key>#SavingMode</key> <integer>7</integer> <key>#TDP</key> <integer>95</integer> <key>#TurboDisable</key> <true/> <key>#Type</key> <string>0x0201</string> <key>#UseARTFrequency</key> <true/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> AAASGQ== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> </dict> </dict> <key>USB</key> <dict> <key>FixOwnership</key> <true/> </dict> </dict> <key>GUI</key> <dict> <key>Hide</key> <array> <string>PREBOOT</string> </array> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Linux</key> <true/> <key>Tool</key> <true/> </dict> </dict> <key>Graphics</key> <dict> <key>FBName</key> <string>Kamarang</string> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>RadeonDeInit</key> <true/> </dict> <key>KernelAndKextPatches</key> <dict> <key>KernelPm</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>Port limit increase</string> <key>Disabled</key> <false/> <key>Find</key> <data> g710////EA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.12.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g710////Gw== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (RehabMan)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g32IDw+DpwQAAA== </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.13.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g32ID5CQkJCQkA== </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (PMHeart)</string> <key>Disabled</key> <true/> <key>Find</key> <data> g/sPD4MDBQAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.0</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>Port limit increase (Ricky)</string> <key>Disabled</key> <false/> <key>Find</key> <data> g/sPD4OPBAAA </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14.x</string> <key>Name</key> <string>com.apple.driver.usb.AppleUSBXHCI</string> <key>Replace</key> <data> g/sPkJCQkJCQ </data> </dict> <dict> <key>Comment</key> <string>External Icons Patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> RXh0ZXJuYWw= </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AppleAHCIPort</string> <key>Replace</key> <data> SW50ZXJuYWw= </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>BooterConfig</key> <string>0x28</string> <key>CsrActiveConfig</key> <string>0x67</string> <key>MLB</key> <string>C02601270QXGPF7FB</string> <key>ROM</key> <string>UseMacAddr0</string> </dict> <key>SMBIOS</key> <dict> <key>BoardSerialNumber</key> <string>C02601270QXGPF7FB</string> <key>ProductName</key> <string>iMac17,1</string> <key>SerialNumber</key> <string>C02R2HZDGG7L</string> <key>SmUUID</key> <string>91E0E343-A938-4117-BBC7-234EA3ED265E</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> Also, for what it is worth, sleep is disabled on my system:

      Again, thank you all for taking time out of your day to help a fellow hackintosher out!
    • By Ade866
      Hi everyone, I have been optimizing my Asus x54h for some time. But now I find myself with sierra 10.12.6 installed with the problem of sleep, well: as soon as I put the PC to sleep the fans keep running, after a while they stop for a second and then start to turn again waking up the PC. What do you think the problem is? The notebook is equipped with: Amd 6470M CPU intel core i3 2330m. 4gb Ram DDR3 SDRAM. Clover legacy bootloader.
      config.plist
      SSDT.aml
      DSDT.aml
      Andrea’s iMac.zip
×