Jump to content

Surface Book 2: UHD 620 Graphic Acceleration/Framebuffer Issue


Recommended Posts

CPU - Intel i7-8650U

GPU - Intel UHD 620 / Disabled dGPU in bios

RAM - SK Hynix 16GB 1867MHz

Network - 88W8897 Avastar 802.11ac Wireless

Audio - ALC298

Input - HID Keyboard/Mouse

SMBIOS - MacBookPro15,2

OS - Monterey 12.5

 

When the device-id is '16900000' dummy number. Graphics showing as 'Intel UHD 620 26 MB'

 

Cannot boot into macOS when using '16590000' from Dortania Guide.

 

I have also tried AAPL,ig-platform-ids 00001B59 (current), 00001659, 0000C087 without success.

 

Tackling the graphics issue first but there are other issues such as wifi, bluetooth, sound, dual battery which I'll create another post for unless I manage to figure it out first. Any help would be much appreciated. Thanks

 

 

SB15.IOREG EFI.zip

Link to comment
Share on other sites

  • Administrators

@Hack.intosh The OC config and IOReg you attached in post #1 show that you were:

  1. injecting KBL framebuffer layout 0x591B0000
  2. faking iGPU device 0x9016
  3. using SMBIOS MBP15,2
  4. using boot args -igfxlspcon -igfxmlr -igfxdvmt -disablegfxfirmware

I believe only #3 to be correct, 1 and #2 being totally wrong with #4 most likely unnecessary. If you look at my old Latitude 7490 guide (i7-8650U CPU with UHD 620 graphics) or other Latitude 7x90/5x90 guides, you would see that the expected properties to inject are:

  • KBL framebuffer layout 0x59160000 or 0x87C00000
  • iGPU device id 0x5916 (not sure about 0x87C0)

 

As such, your injected properties should look like this:

AAPL,ig-platform-id         00001659    DATA
device-id                   16590000    DATA
framebuffer-patch-enable    1           NUMBER
framebuffer-fbmem           00009000    DATA
framebuffer-stolenmem       00003001    DATA

or

AAPL,ig-platform-id         0000C087    DATA
device-id                   16590000    DATA
framebuffer-patch-enable    1           NUMBER
framebuffer-fbmem           00009000    DATA
framebuffer-stolenmem       00003001    DATA

or possibly

AAPL,ig-platform-id         0000C087    DATA
device-id                   C0870000    DATA
framebuffer-patch-enable    1           NUMBER
framebuffer-fbmem           00009000    DATA
framebuffer-stolenmem       00003001    DATA

but framebuffer layout 0x87C00000 and device id 0x87C0 usually are for Amber Lake platforms.

 

Did you try such settings combination without your -igfx---- boot args at all?

Link to comment
Share on other sites

I have tried all three with -igfxdvmt (can't set dvmt in bios) and without igfx---- args. All three do not boot, with results in a restart loop. 

 

initially faking iGPU device 0x9016 was a typo when editing device-id but that resulted in the Surface Book actually booting in macOS (to my surprise). I'm under the impression, the issue lays in either the device-id, frame buffers or args? I've tried many combinations prior to posting but with device-id removed - it will boot without graphics acceleration.

Link to comment
Share on other sites

  • Administrators

It's perfectly normal that you booted without acceleration when injecting an incorrect iGPU id such as 0x9016. You'd have experienced the same result with id 0x1234 or 0x5678. When such parameters are invalid (same applies to framebuffer layout), macOS boots in VESA mode, i.e. a very basic graphics mode without graphics driver that you could compare to Windows safe mode.

 

Try booting with only -disablegfxfirmware boot arg alongside the revised properties injection.

 

You stated that the dGPU was disabled in BIOS so I assume this is an option for this Surface Book 2 which is presumably fitted with nVidia Optimus technology. Usually, disabling Optimus limits the laptop to its dGPU only, voiding dual GPU operation. If you want to run on the UHD 620 for Hackintosh purposes, you probably need to re-enable Optimus but disable the dGPU through patched SSDT. To prove this, do try to re-enable dGPU in BIOS but boot with boot arg -wegnoegpu.

Link to comment
Share on other sites

  • Administrators

This IOReg shows you're faking iGPU id 0x5917 so it's never going to work... If you have another macOS system, you could try to access this Surface Book 2 remotely but you'd have to setup screen sharing to begin with. You can do that when you boot with one of those invalid ids. You may need to inject your screen EDID if screen goes black when graphics initialize.

Link to comment
Share on other sites

I’ve set up screen sharing using an invalid fake gpu as suggested, tested and working with the fake gpu then had device-id removed altogether afterwards. I do have another MacBook to remote into the surface book but the it won’t connect as you would’ve guess. Not familiar with injecting my screen’s EDID. I’ve googled but came up with unrelated results. Do you have a link of sorts? Also, is this method going to resolved this issue?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...