[solved] Can't boot to installer on XPS 15 9570 4K

[Raymonf]

Dell XPS 15 9570, 4K model
CPU: i7-8750H
BIOS version: 1.4.1
Graphics: Intel UHD Graphics 630

I can't boot to the installer. The system crashes (reboots) about a second after this shows:

DSMOS has arrived
GTrace synchronization point 3
Unsupported PCH
IOConsoleUsers: time(0) 0->0, lin 0, lik 1,
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0

If I select keepsyms=1 and debug=0x100, there is no stack trace and the system does not reboot. It just hangs at that line.

Without verbose mode, the progress bar goes to the middle and then hangs there.

Taking a look around, I noticed some people trying fake ig-platform-ids. Unfortunately, that only causes a black screen after booting. Then, it restarts.

My Clover configuration is based on this: https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/config_UHD630.plist
The only change I made is changing DellSMBIOSPatch to true.
-cdfon is set, and I do have WhateverGreen in my 10.14 kexts folder.

Kexts:
FakeSMC 2018-0915 from RehabMan
FakePCIID/FakePCIID_Intel_HD_Graphics 2018-0919 from RehabMan
VoodooPS2Controller 2018-0506 from RehabMan
USBInjectAll 2018-0716 from RehabMan
Lilu 1.2.7
WhateverGreen 1.2.3
VoodooI2C

Clover drivers:

Referenced guides:
https://www.tonymacx86.com/threads/...k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/
https://www.tonymacx86.com/threads/wip-xps-9570-hackintosh-guide.259844/
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

 

[RehabMan]

Dell XPS 15 9570, 4K model
CPU: i7-8750H
BIOS version: 1.4.1
Graphics: Intel UHD Graphics 630

I can't boot to the installer. The system crashes (reboots) about a second after this shows:

DSMOS has arrived
GTrace synchronization point 3
Unsupported PCH
IOConsoleUsers: time(0) 0->0, lin 0, lik 1,
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0

If I select keepsyms=1 and debug=0x100, there is no stack trace and the system does not reboot. It just hangs at that line.

Without verbose mode, the progress bar goes to the middle and then hangs there.

Taking a look around, I noticed some people trying fake ig-platform-ids. Unfortunately, that only causes a black screen after booting. Then, it restarts.

My Clover configuration is based on this: https://github.com/RehabMan/OS-X-Clover-Laptop-Config/blob/master/config_UHD630.plist
The only change I made is changing DellSMBIOSPatch to true.
-cdfon is set, and I do have WhateverGreen in my 10.14 kexts folder.

Kexts:
FakeSMC 2018-0915 from RehabMan
FakePCIID/FakePCIID_Intel_HD_Graphics 2018-0919 from RehabMan
VoodooPS2Controller 2018-0506 from RehabMan
USBInjectAll 2018-0716 from RehabMan
Lilu 1.2.7
WhateverGreen 1.2.3

Clover drivers:
View attachment 352812

Referenced guides:
https://www.tonymacx86.com/threads/...k-touch-1tb-ssd-32gb-ram-100-adobergb.224486/
https://www.tonymacx86.com/threads/wip-xps-9570-hackintosh-guide.259844/
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[Raymonf]

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

Sorry, I've attached them in the main post.

Due to the nature of the screen being 4K (and me not being able to figure out how to get HiDPI console logging working, if that's even possible) it's a little hard to read.

Edit: Oops, I think CLOVER 2 is what you want.

 

[RehabMan]

Sorry, I've attached them in the main post.

Due to the nature of the screen being 4K (and me not being able to figure out how to get HiDPI console logging working, if that's even possible) it's a little hard to read.

Edit: Oops, I think CLOVER 2 is what you want.

A 4k display might be a bit of a trick with only 32mb DVMT-prealloc.
Can you set DVMT-prealloc to 64mb (or 128mb) and remove the 32mb related patching in config.plist/Devices/Properties(cursormem/stolenmem)?
What about booting with invalid ig-platform-id?

You have a bit of a mess in drivers64UEFI (why two AptioMemoryFix*.efi for example??)
EmuVariable should not be used with AptioMemoryFix..

 

[Raymonf]

Can you set DVMT-prealloc to 64mb

The BIOS doesn't have an option to change it. After looking around, I read that changing DVMT-prealloc might brick. Is there any other method?
I noticed something called "IntelGraphicsDVMTFixup", which was integrated into WhateverGreen. I'm assuming the stolenmem/cursormem is exactly that...

What about booting with invalid ig-platform-id?

This causes a black screen and then a restart after a few seconds of darkness.

You have a bit of a mess in drivers64UEFI (why two AptioMemoryFix*.efi for example??)
EmuVariable should not be used with AptioMemoryFix..

I think I've cleaned it up.

 

[RehabMan]

The BIOS doesn't have an option to change it. After looking around, I read that changing DVMT-prealloc might brick. Is there any other method?
I noticed something called "IntelGraphicsDVMTFixup", which was integrated into WhateverGreen. I'm assuming the stolenmem/cursormem is exactly that...

Those patches change the kext to assume 32mb instead of 64mb, but that may be an issue with the 4k screen (it may require larger memory spaces).

This causes a black screen and then a restart after a few seconds of darkness.

Attach PR files that represent this configuration. Make sure you're setting the ig-platform-id inside the config.plist, not trying to use the Clover GUI.

I think I've cleaned it up.
View attachment 352835

Why do you still have EmuVariableUefi-64.efi.
I already said it is not needed with AptioMemoryFix.efi.

 

[Raymonf]

Attach PR files that represent this configuration. Make sure you're setting the ig-platform-id inside the config.plist, not trying to use the Clover GUI.

Ah, that might be the issue. I was setting it in the GUI.

Like this, it gets to the exact spot as in the main post (IOConsoleUsers hang).

Why do you still have EmuVariableUefi-64.efi.
I already said it is not needed with AptioMemoryFix.efi.

Whoops. Just removed it.

 

[RehabMan]

Like this, it gets to the exact spot as in the main post (IOConsoleUsers hang).

Because you have "#ig-platform-id" instead of "AAPL,ig-platform-id", your property has no effect.

Also, <string> is not a valid type for AAPL,ig-platform-id, must be 4-byte <data>.

 

[Raymonf]

Because you have "#ig-platform-id" instead of "AAPL,ig-platform-id", your property has no effect.

Oh, #ig-platform-id is under Graphics.

I now changed Devices>Properties>PciRoot(0)/Pci(0x02,0)>AAPL,ig-platform-id to eFY0Eg== which should be 0x12345678.

What this currently looks like:

Like this, it actually boots to the installer UI and I can interact with the UI. There isn't any acceleration, though.

 

[RehabMan]

Oh, #ig-platform-id is under Graphics.

I now changed Devices>Properties>PciRoot(0)/Pci(0x02,0)>AAPL,ig-platform-id to eFY0Eg== which should be 0x12345678.

What this currently looks like:

View attachment 353031

Use a plist editor (Xcode or PlistEditPro) so you don't have to do base64 conversion manually.

Like this, it actually boots to the installer UI and I can interact with the UI. There isn't any acceleration, though.

The installer does not use QE.