[solved] GPU HD5300 problems (on Core-M 5Y70)

[zohaad]

I have some issues with graphics on my Yoga 3 Pro: block formation and lag. It is very slow

I have attached the necessary files (Problem Reporting files with the tool), some things to note:

SMBIOS->ProductName=MacBookPro11,5 because I wanted my 3200x1800 to work with HiDPI (which it didn't..)
Note that the machine with the 5Y71 chip is MacBook8,1. Apparently HiDPI isn't supported in this machine

DVMT Pre-alloc is set to 96MB using UEFI Shell: setup_var 0x18c 0x4 (I tried 0x5, didn't boot), I then did:

Using config_HD5300_5500_6000.plist as a starting point:

Graphics->Inject->Intel->NO (I have inserted a pic of About this Mac, when injection is YES)

Graphics->ig-platform-id=0x161e0001 (because I have a 5Y70 chip)

Devices->FakeID->IntelGFX=0x161e0001

Furthermore, in KernelAndKextPatches->KextsToPatch I have disabled Item 0 which is the 32MB BIOS fix for AppleIntelBDWGraphicsFramebuffer by RehabMan which is not needed anymore as DVMT Pre-alloc is 96MB. Also I enabled everything that has 0x161e0001 in the comment.


Slowly getting to know how everything works, when something is clear another rabbit hole shows up. Have made many trivial mistakes (and am sure I'm making them right now), but it is part of the learning process

 

[zohaad]

Here are the debug files when Inject->Intel->YES, this is the system I use now

 

[RehabMan]

I have some issues with graphics on my Yoga 3 Pro: block formation and lag. It is very slow

I have attached the necessary files (Problem Reporting files with the tool), some things to note:

SMBIOS->ProductName=MacBookPro11,5 because I wanted my 3200x1800 to work with HiDPI (which it didn't..)
Note that the machine with the 5Y71 chip is MacBook8,1. Apparently HiDPI isn't supported in this machine

DVMT Pre-alloc is set to 96MB using UEFI Shell: setup_var 0x18c 0x4 (I tried 0x5, didn't boot), I then did:

Using config_HD5300_5500_6000.plist as a starting point:

Graphics->Inject->Intel->NO (I have inserted a pic of About this Mac, when injection is YES)

Graphics->ig-platform-id=0x161e0001 (because I have a 5Y70 chip)

Devices->FakeID->IntelGFX=0x161e0001

Furthermore, in KernelAndKextPatches->KextsToPatch I have disabled Item 0 which is the 32MB BIOS fix for AppleIntelBDWGraphicsFramebuffer by RehabMan which is not needed anymore as DVMT Pre-alloc is 96MB. Also I enabled everything that has 0x161e0001 in the comment.


Slowly getting to know how everything works, when something is clear another rabbit hole shows up. Have made many trivial mistakes (and am sure I'm making them right now), but it is part of the learning process

You cannot expect working graphics without injecting a valid ig-platform-id.
See guide for good starter plists:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

 

[zohaad]

You cannot expect working graphics without injecting a valid ig-platform-id.
See guide for good starter plists:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

I used config_HD5300_5500_6000.plist as starter plist.

Then I blindly copied from this: https://www.firewolf.science/2015/0...from-appleintelbdwgraphicsframebuffer-binary/

I copied 0x161e0001 from there as it was under Intel HD Graphics 5300 (Device ID: 0x8086161e) CPUs: Core-M 5Y10/5Y10a/5Y10c/5Y31/5Y51/5Y70/5Y71 and my About this Mac says Intel HD Graphics 5300 21 MB. Both have "21MB", coincidence?

Question: Does FakeID and ig-platform-id need to be the same? What do they both do?

So, I need to change them to one of the following?

0x161E8086
0x161e0000
0x161e0001

what does Device ID mean? e.g. Intel HD Graphics 5300 (Device ID: 0x8086161e). Is 0x8086161e what I need to put in ig-platform-id?


Sorry for being clueless..

EDIT:

The 21MB is apparently the total VRAM

 

[RehabMan]

I used config_HD5300_5500_6000.plist as starter plist.

Then I blindly copied from this: https://www.firewolf.science/2015/0...from-appleintelbdwgraphicsframebuffer-binary/

I copied 0x161e0001 from there as it was under Intel HD Graphics 5300 (Device ID: 0x8086161e) CPUs: Core-M 5Y10/5Y10a/5Y10c/5Y31/5Y51/5Y70/5Y71 and my About this Mac says Intel HD Graphics 5300 21 MB. Both have "21MB", coincidence?

Question: Does FakeID and ig-platform-id need to be the same? What do they both do?

So, I need to change them to one of the following?

0x161E8086
0x161e0000
0x161e0001

what does Device ID mean? e.g. Intel HD Graphics 5300 (Device ID: 0x8086161e). Is 0x8086161e what I need to put in ig-platform-id?


Sorry for being clueless..

EDIT:

The 21MB is apparently the total VRAM

The plist you attached has config.plist/Graphics/Inject/Intel=false.
FakeID and ig-platform-id settings have no effect without Inject/Intel=true.

 

[zohaad]

The plist you attached has config.plist/Graphics/Inject/Intel=false.
FakeID and ig-platform-id settings have no effect without Inject/Intel=true.

Sorry, was a mistake, I uploaded the correct config.plist in the OP as well.

 

[RehabMan]

Sorry, was a mistake, I uploaded the correct config.plist in the OP as well.

Any change requires all new problem reporting files.

 

[zohaad]

Any change requires all new problem reporting files.

Yes, I updated problem reporting files as well as per the guide, it's called debug_23326.zip now.

 

[RehabMan]

Yes, I updated problem reporting files as well as per the guide, it's called debug_23326.zip now.

Here are the debug files when Inject->Intel->YES, this is the system I use now

You're using an incorrect FakeID (0x161e0001 is not valid... it is disabling the graphics drivers).
FakeID not needed... remove.

 

[zohaad]

Disabled FakeID. I am clueless which ig-platform-id to use.. I have tried:

0x161e0000
0x161e0001
0x16260004
0x16260006

With each one of them I have selected the appropriate AppleIntelBDWGraphicsFramebuffer patches from config_HD5300_5500_6000.plist

Now I am using 0x12345678, it boots but graphics are obviously disabled.

The only other edit I made is setting SMBIOS to MacBook8,1 as it is needed for the patched SSDT.aml (native power management)

I will post problem reporting files in a bit