Google Pixelbook: unable to obtain graphics acceleration on KBL HD 615 under macOS

[olm3ca]

I've been able to get Mac OS 10.15.7 on the Google Pixelbook. (Typing this from it now.) It is the i5 Kaby Lake with Intel 615 graphics. Intel wifi is working great!

 

The main problem at this time is that the Intel HD615 graphics chip isn't playing nice - no graphics acceleration at the moment. I could use any ideas on what to try. I've saved my progress so far on GitHub, including the config.plist and setup notes: https://github.com/olm3ca/PixelbookOSX

 

What is odd is that the ig-platform-id only works when set to 16590000 which is incorrectly hexswapped, and I believe is a spoof which allows it to boot with minimal graphics support. I've tried all of the possible combinations on the OpenCore install guide and none work (00001B59, 00001659, 01001E59, 00001E59). I've also tried using Hackintool to generate others and those aren't working for this chip either. When I use any these, the system always hangs after IGPU Render Compression for IOSurface is Enabled, or a kernel panic.

 

My question to this group is... the spoofed ID I'm using above is allowing the OS to boot. What other variations of ig-platform-id should I try for the HD615? It seems like such a common graphics card. Thanks in advance! 

[Hervé]

Unless I'm mistaken, I saw iMac18,1 SMBIOS in your config file.  That would obviously be quite wrong given that this was a Kaby Lake desktop Mac (granted it was fitted with i5-7360U mobile CPU) with Intel Iris Plus 640 graphics. What you really ought to use is MacBook10,1 SMBIOS, i.e. the profile of those mid-2017 last little MacBooks fitted with similar CPUs (i5-7Y54 & i7-7Y75) and Intel HD615 graphics.

 

Regarding graphics, I believe you should use KBL framebuffer id 0x591e0000 or 0x591e0001, specified in reverse byte order. In your OC (or Clover) config, you'd therefore inject these as follows:

AAPL,ig-platform-id    00001E59    DATA

or

AAPL,ig-platform-id    01001E59    DATA

 

This is what is recommended as per Clover's and WEG's own documentation:

 

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

 

ID: 591E0000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes)
Model name: Intel HD Graphics KBL CRB
Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 87010000
02040A00 00040000 87010000

ID: 591E0001, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x002B0702
TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes)
Model name: Intel HD Graphics 615
Camellia: CamelliaV2 (2), Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000181 - ConnectorDP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000181 - ConnectorDP
00000800 02000000 98000000
01050900 00040000 81010000
02040A00 00040000 81010000

 

If not, well, you'd have to experiment with other KBL framebuffer ids.

[olm3ca]

Yep - I've since changed the SMBIOS to MacBook10,1. That was an error from initial setup I neglected to fix but it's in now. 

 

Thanks so much for these suggestions. I'll try them now and will report back. I just found on Intel's specs page for this processor that my device ID is 0x591E. That would give me a framebuffer of 0x591E0001, right? So in this case, I should use 01001E59... But I've tried that before and it didn't work. 

Ok here's something promising: the 01001659 entry is the first one that didn't fail! This is a good sign. Unfortunately I'm still stuck with 8mb VRAM. I was thinking of trying next the suggestions on the OC Install guide for VRAM:

 

framebuffer-patch-enable Data 01000000

framebuffer-stolenmem Data 00003001

framebuffer-fbmem Data 00009000

 

Thank you! One step closer I think...

[Hervé]

iGPU device-id and framebuffer platform-id are 2 x seperate things and you do not derive latter from former. See WEG's manual.

[olm3ca]

Noted. Thanks. Still have only 8mb VRAM. Is there any other way to specify the amount of VRAM to be used in config.plist? Thanks so much for your suggestions.

[Hervé]

You're only seeing 8MB VRAM because you still do not have full graphics acceleration. Once you've sussed out the correct settings, VRAM will be automatically set to something like 1536MB.

 

Post a zipped copy of your EFI folder.

[olm3ca]

Here is the EFI folder: https://www.dropbox.com/s/1pfyzf8nyplr9on/efi.zip?dl=0

 

Attached is the kernel panic message if I attempt to use AAPL,ig-platform-id    00001E59    DATA.

 

 

[Hervé]

Try an post an IOReg when you boot your PixelBook with an inappropriate framebuffer value.

[olm3ca]

Sorry, I'm not sure I know how to do that. Can you elaborate?

[Leon]

Hey @Hervé - Thank you for helping out olm3ca - since i have the i7 model i have a special interest in this build (but not the time for it) - and should you guys succeed i will donate 100usd to OSXL