Issues with High Sierra Supplemental Update (Jan 8, 2018) and Intel Integrated UHD 630

[His_Tudness]

That's odd... Doesn't work for me. I get very laggy, unusable graphics with spinning beachball.

 

[Roen]

That's odd... Doesn't work for me. I get very laggy, unusable graphics with spinning beachball.

BIOS settings?

What's your fail condition?

 

[His_Tudness]

What do you mean by fail condition?

BIOS settings:

Advanced > Chipset Config > Primary Graphics Adapter > Onboard/iGPU
Advanced > Chipset Config > Vt-d > disabled
Advanced > Chipset Config > Restore on AC Power Loss > Enabled [Not required, but very useful an automated media center.]
Advanced > USB Configuration > XHCI Handoff > Enabled
H.W. Monitor > CPU_OPT / W_Pump Switch > Water Pump
H.W. Monitor > CPU Optional Fan Control Mode > PWM

And I think I've also changed IGPU memory to 128mb as suggested somewhere.

 

[Roen]

What do you mean by fail condition?

BIOS settings:

Advanced > Chipset Config > Primary Graphics Adapter > Onboard/iGPU
Advanced > Chipset Config > Vt-d > disabled
Advanced > Chipset Config > Restore on AC Power Loss > Enabled [Not required, but very useful an automated media center.]
Advanced > USB Configuration > XHCI Handoff > Enabled
H.W. Monitor > CPU_OPT / W_Pump Switch > Water Pump
H.W. Monitor > CPU Optional Fan Control Mode > PWM

And I think I've also changed IGPU memory to 128mb as suggested somewhere.

Essentially, describe the issue. Is it just sleep? Can you start and shut down without issue?

 

[His_Tudness]

If I use the multibeast method, I get almost perfectly working graphics. Only waking from sleep causes weird graphic tearing and glitching. System is basically unusable. But I can restart and shutdown with no problems.

If I use only graphics fixup kext and fake ID, I get really slow, dimmed graphics with the spinning beach ball, system is unusable, but I can still restart and shutdown if I'm patient.

If I use no kext, no fake ID or anything in Clover, I get VESA graphics with tearing and glitches, but at least it somewhat works. No restart/shutdown issues.

 

[Roen]

If I use the multibeast method, I get almost perfectly working graphics. Only waking from sleep causes weird graphic tearing and glitching. System is basically unusable. But I can restart and shutdown with no problems.

If I use only graphics fixup kext and fake ID, I get really slow, dimmed graphics with the spinning beach ball, system is unusable, but I can still restart and shutdown if I'm patient.

If I use no kext, no fake ID or anything in Clover, I get VESA graphics with tearing and glitches, but at least it somewhat works. No restart/shutdown issues.

You have latest Lilu.kext?

 

[His_Tudness]

Yeah I had the latest kexts. I'm going to re check everything, reset everything and then try one more time, before settling for multibeast graphics.

So best configuration should be: native GFX ID (0x59128086 or is it actually 0x3e928086?) in Clover Config under Devices and GraphicsFixup.kext + Lilu.kext?

 

[Roen]

59128086 worked for me for FakeID.

But for platform id, I used 0x59120000.

You can experiment based on my posts and see how it turns out.

 

[His_Tudness]

59128086 worked for me for FakeID.

But for platform id, I used 0x59120000.

You can experiment based on my posts and see how it turns out.

This works for me too now. For some reason. Still need to test does acceleration work after waking from sleep.

Edit: HDMI still not working. Can't wait to get a proper graphics card.

 

[Roen]

Good to hear, keep testing and keep reporting.