Contribute
Register

Skylake Intel HD 530 Graphics Glitch Fix

Status
Not open for further replies.
nkmacuser said:
Thanks for the point in fixing my BIOS Settings!

History:
I had working Sierra on HDD with HD530 glitch (i.e. Reference A). I recently bought SSD (i.e. Reference B) which I used CCC to copy the entire HDD and prepare identical EFI Partition. Obviously, both are suffering HD530 glitch but other than that everything else works perfectly; able to boot own its own and function.

Progress:
I am playing with B's EFI config.plist using latest Clover Configurator. After trying variety of fixes through Clover configurator, now the B drive is not able to boot itself. I tried copying back the A's entire EFI partition to B's EFI to return to prior state, but still the drive is completely unbootable where verbose mode tells me this line
>>> "[IGPU] Failed to initialize graphics firmware."

When I get home, I will try changing BIOS setting to a) primary graphic as IGPU b) DVMT to 64MB and see if any of drive A or B is able to address HD530 glitch.

I really want to make Drive B work, but what would you suggest I do? :( should I try clean re-installl ? Thanks for your time and help!
Click to expand...

Rather then copying clover bootloader to new drive, remove what you copied and install fresh clover bootloader. After its loaded you can open the EFI partition and remove and replace config.plist, and add fakeSMCkext to kext folders 10.12 and other. This is what I do when Carbon Copying to a new disk. Just replace with old plist and add the kexts.
Google Clover Bootloader and get the latest copy.
 
Pentium G3258 w/RX 480
GA-H97-D3H |  Pentium G3258 |  Radeon Other
iMac 17.1 w/RX480
GA-Z170M-D3H |  i5 6500 |  Radeon Other
Bladeknight said:
Work like a charm for me. Thanks you! 2K monitor

fJQ2EPy.png
Click to expand...

Can I get you config and other files? I'm so having problems..
 
ATX Home 16GB DDR4
Z170-A |  i5 6600K |  HD 530
Gigamaxx said:
Rather then copying clover bootloader to new drive, remove what you copied and install fresh clover bootloader. After its loaded you can open the EFI partition and remove and replace config.plist, and add fakeSMCkext to kext folders 10.12 and other. This is what I do when Carbon Copying to a new disk. Just replace with old plist and add the kexts.
Google Clover Bootloader and get the latest copy.
Click to expand...

I followed these steps but the drive is unbootable, should I just try clean reinstall of Sierra to this new SSD drive.. ? :(

1. Deleted everything under the EFI folder of the new drive.
2. Installed fresh clover bootloader to new drive.
3. Opened the EFI partition in the new drive, replaced the config.plist by the one from backup drive (functional/bootable)
4. only added fakeSMCkext to kext folders 10.12 and other, I grabbed fakeSMCkext from the backup drive (functional/bootable)
5. Cannot boot itself alone, neither boot via the working drive or USB drive. the loading bar stops when it reaches 75% of bar, verbose mode stops at "[IGPU] Failed to initialize graphics firmware."
 
NK Skylake Build
Z170-A |  i5 6600K |  HD 530
tonymacx86 said:
The full patch (for further testing) is as specified here:

Code: 
<key>Devices</key>
    <dict>
        <key>AddProperties</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL,Gfx324</string>
                <key>Value</key>
                <data>
                AQAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL,GfxYTile</string>
                <key>Value</key>
                <data>
                AQAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL00,PanelPowerUp</string>
                <key>Value</key>
                <data>
                MAAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL00,PanelPowerOn</string>
                <key>Value</key>
                <data>
                GQEAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL00,PanelPowerOff</string>
                <key>Value</key>
                <data>
                EQAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL00,PanelPowerDown</string>
                <key>Value</key>
                <data>
                PAAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>AAPL00,PanelCycleDelay</string>
                <key>Value</key>
                <data>
                +gAAAA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>Skylake glitch fix © Apple</string>
                <key>Device</key>
                <string>IntelGFX</string>
                <key>Key</key>
                <string>device-colors</string>
                <key>Value</key>
                <data>
                AAIAAKCdnQAAAAAAAAAAAA==
                </data>
            </dict>
        </array>
    </dict>
Click to expand...

This fixed the flickering in the corner for me. Along with Inject/Intel = true and ig-platform-id = 0x19120000 I now have hw acceleration and 2560x1440 @ 60Hz via the motherboard's DisplayPort!
 
pgriss said:
This fixed the flickering in the corner for me. Along with Inject/Intel = true and ig-platform-id = 0x19120000 I now have hw acceleration and 2560x1440 @ 60Hz via the motherboard's DisplayPort!
Click to expand...
Can you try something?
Close your monitor for 1 minute and turn it on again. Do you still have signal?
When i closing my monitor or change input source I’m losing the signal with Displayport
 
What value DVMT parameter set?
 
Last edited:
teosard said:
Can you try something?
Close your monitor for 1 minute and turn it on again. Do you still have signal?
When i closing my monitor or change input source I’m losing the signal with Displayport
Click to expand...

If I turn my monitor off, I can't get signal afterward. Also, if I put the computer to sleep, when it wakes up I can't get signal. [UPDATE: After sleep/wake, it's not just the video signal that doesn't work! Because of this, I now think these are two different issues.] My understanding is that both of these are generic problems with HD530 that nobody has a solution for. Please do let me know if I am mistaken.

I set DVMT to 64MB in BIOS. It was 32MB by default and that was causing a kernel panic at boot.
 
Last edited:
pgriss said:
If I turn my monitor off, I can't get signal afterward. Also, if I put the computer to sleep, when it wakes up I can't get signal. My understanding is that both of these are generic problems with HD530 that nobody has a solution for. Please do let me know if I am mistaken.

I set DVMT to 64MB in BIOS. It was 32MB by default and that was causing a kernel panic at boot.
Click to expand...
Yes i have the same problems.I am using LG 27UD68 (4k) monitor connected with displayport.
 
Status
Not open for further replies.
Copyright © 2010 - 2023 tonymacx86 LLC
Back
Top