[Solved] Does SMBIOS affect what GPU name is?

AnonymousMacPC · Jan 17, 2019

Laptop: Dell Inspiron 3543
i3-5005U
4GB RAM
1920x1080 Touchscreen
HD5500

Using different SMBIOS Macbook Air 7,1 & 7,2 makes the GPU spoof as Intel HD Graphics 6000 and when MacBook Pro 12,1, makes the GPU spoof as Intel HD Graphics 6100.

I am injecting ig-platform-id,AAPL via Devices/Properties using 0x16260006 (06002616) and deviceid as 16260000 (00002616)

No fakeid or nothing just using ig-platform-id and device-id.

Is this something new to Mojave?

Also not using Whatevergreen.kext or IntelGraphicsFixup.kext

jaymonkey · Jan 17, 2019

The SMBIOS will dictate what CPU & IGPU features MacOS will use.

You should always try and match the SMBIOS to the CPU Type/Generation
A good tool to use is MacTracker ..

Since you have Broadwell CPU .. MacBookPro 12,1 or MacBookAir 7,1 or MacBookAir 7,2 would be a good match.
Use Lilu + WhatEverGreen to configure IGPU with correct AAPL,ig-platform-id & device-id using Device Properties as clover can not configure/patch Mojave IGPU framebuffer.

WhatEverGreen is recommended for Mojave + IGPU.

Valid PlatformID's for HD 5500 IGPU are 0x16160000 or 0x16160002

Use which ever is the closest match based on port connector types, you can then patch the frame buffer with correct connector types if necessary.

Code:

ID: 16160000, STOLEN: 16 MB, FBMEM: 15 MB, VRAM: 1024 MB, Flags: 0x00000B06
TOTAL STOLEN: 32 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 64 MB, MAX OVERALL: 65 MB (68694016 bytes)
GPU Name: Intel HD Graphics 5500
Model Name(s):
Camelia: Disabled, Freq: 5273 Hz, FreqMax: 5273 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000004, flags: 0x00000004 - DigitalDVI
[2] busId: 0x04, pipe: 9, type: 0x00000800, flags: 0x00000082 - HDMI
00000800 02000000 30020000
01050900 04000000 04000000
02040900 00080000 82000000


ID: 16160002, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00004B02
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
GPU Name: Intel HD Graphics 5500
Model Name(s):
Camelia: V2, Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000507 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000507 - DP
00000800 02000000 30020000
01050900 00040000 07050000
02040A00 00040000 07050000

The PlatformID 0x16260006 your using is for HD 6000 IGPU

Code:

ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
GPU Name: Intel HD Graphics 6000
Model Name(s): iMac16,1 MacBookAir7,1 MacBookAir7,2
Camelia: Disabled, Freq: 2777 Hz, FreqMax: 2777 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
[2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
00000800 02000000 30020000
01050B00 00040000 07050000
02040B00 00040000 07050000

Recommended using MacBookPro 12,1 SMBIOS and IGPU PlatformID 0x16160000 if laptop has external HDMI port or 0x16160002 if laptop has external DP port .. this config should work well with your laptops hardware although it may still be necessary to further patch framebuffer if external monitor is not working.

Cheers
Jay

AnonymousMacPC · Jan 17, 2019

jaymonkey said:

The SMBIOS will dictate what CPU & IGPU features MacOS will use.

You should always try and match the SMBIOS to the CPU Type/Generation
A good tool to use is MacTracker ..

Since you have Broadwell CPU .. MacBookPro 12,1 or MacBookAir 7,1 would be a good match
Use Lilu + WhatEverGreen to configure IGPU with correct AAPL,ig-platform-id & device-id using Device Properties

Valid PlatformID's for HD 5500 IGPU are 0x16160000 or 0x16160002

Use which ever is the closest match based on port connector types, you can then patch the frame buffer with correct connector types if necessary.

Code:

ID: 16160000, STOLEN: 16 MB, FBMEM: 15 MB, VRAM: 1024 MB, Flags: 0x00000B06
TOTAL STOLEN: 32 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 64 MB, MAX OVERALL: 65 MB (68694016 bytes)
GPU Name: Intel HD Graphics 5500
Model Name(s):
Camelia: Disabled, Freq: 5273 Hz, FreqMax: 5273 Hz
Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000004, flags: 0x00000004 - DigitalDVI
[2] busId: 0x04, pipe: 9, type: 0x00000800, flags: 0x00000082 - HDMI
00000800 02000000 30020000
01050900 04000000 04000000
02040900 00080000 82000000


ID: 16160002, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00004B02
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
GPU Name: Intel HD Graphics 5500
Model Name(s):
Camelia: V2, Freq: 1388 Hz, FreqMax: 1388 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000507 - DP
[2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000507 - DP
00000800 02000000 30020000
01050900 00040000 07050000
02040A00 00040000 07050000

The PlatformID 0x16260006 your using is for HD 6000 IGPU

Code:

ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
GPU Name: Intel HD Graphics 6000
Model Name(s): iMac16,1 MacBookAir7,1 MacBookAir7,2
Camelia: Disabled, Freq: 2777 Hz, FreqMax: 2777 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
[2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
00000800 02000000 30020000
01050B00 00040000 07050000
02040B00 00040000 07050000

Cheers
Jay

Thank you

One other question, for High Sierra and below I used 16260006 and patched connector from DP to HDMI for 0204.
It originally said HD5500 but now 6000. What caused this?

AnonymousMacPC · Jan 17, 2019

Thank you

One other question, for High Sierra and below I used 16260006 and patched connector from DP to HDMI for 0204.
It originally said HD5500 but now 6000. What caused this?

Also since I am using 16260006 right now, will this affect anything? Hardware level (slow performance, minimal lag)?

jaymonkey · Jan 17, 2019

AnonymousMacPC said:
One other question, for High Sierra and below I used 16260006 and patched connector from DP to HDMI for 0204. It originally said HD5500 but now 6000. What caused this?

@AnonymousMacPC,

IGPU name comes from the IGPU framebuffer/PlatformID .

As already stated PlatformID 0x16260006 is for HD 6000, the data dump for that id clearly shows that the IGPU name is HD 6000 so thats why you see it ..

Code:

ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B
TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes)
GPU Name: Intel HD Graphics 6000
Model Name(s): iMac16,1 MacBookAir7,1 MacBookAir7,2
Camelia: Disabled, Freq: 2777 Hz, FreqMax: 2777 Hz
Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3
[0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS
[1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
[2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP
00000800 02000000 30020000
01050B00 00040000 07050000
02040B00 00040000 07050000

AnonymousMacPC said:
Also since I am using 16260006 right now, will this affect anything? Hardware level (slow performance, minimal lag)?

Using a PlatformID that does not match your IGPU is not recommended and can result in IGPU related issues.

HD 5500 has 24 Execution Units and runs between 300Mhz to 950Mhz clock speed.
HD 6000 has 48 Execution Units and runs between 300Mhz to 1050Mhz clock speed.

Thats quite a big bump in performance so running a HD 6000 PlatformID on a HD 5500 IGPU may cause problems when the IGPU is under heavy load as MacOS will not be optimally configured for your IGPU, recommend you use a HD 5500 PlatformID as previously stated.

For a smooth and trouble MacOS experience on Hackingtosh always match SMBIOS to CPU/Generation and PlatformID to nearest supported IGPU framebuffer.

Cheers
Jay

AnonymousMacPC · Jan 17, 2019

jaymonkey said:
@AnonymousMacPC,

IGPU name comes from the IGPU framebuffer/PlatformID .

As already stated PlatformID 0x16260006 is for HD 6000, the data dump for that id clearly shows that the IGPU name is HD 6000 so thats why you see it ..

Code:

ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) GPU Name: Intel HD Graphics 6000 Model Name(s): iMac16,1 MacBookAir7,1 MacBookAir7,2 Camelia: Disabled, Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000

Using a PlatformID that does not match your IGPU is not recommended and can result in IGPU related issues.

HD 5500 has 24 Execution Units and runs between 300Mhz to 950Mhz clock speed.
HD 6000 has 48 Execution Units and runs between 300Mhz to 1050Mhz clock speed.

Thats quite a big bump in performance so running a HD 6000 PlatformID on a HD 5500 IGPU may cause problems when the IGPU is under heavy load as MacOS will not be optimally configured for your IGPU, recommend you use a HD 5500 PlatformID as previously stated.

For a smooth and trouble MacOS experience on Hackingtosh always match SMBIOS to CPU/Generation and PlatformID to nearest supported IGPU framebuffer.

Cheers
Jay

Ok thank you.

AnonymousMacPC · Jan 20, 2019

jaymonkey said:
@AnonymousMacPC,

IGPU name comes from the IGPU framebuffer/PlatformID .

As already stated PlatformID 0x16260006 is for HD 6000, the data dump for that id clearly shows that the IGPU name is HD 6000 so thats why you see it ..

Code:

ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) GPU Name: Intel HD Graphics 6000 Model Name(s): iMac16,1 MacBookAir7,1 MacBookAir7,2 Camelia: Disabled, Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - LVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - DP 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000

Using a PlatformID that does not match your IGPU is not recommended and can result in IGPU related issues.

HD 5500 has 24 Execution Units and runs between 300Mhz to 950Mhz clock speed.
HD 6000 has 48 Execution Units and runs between 300Mhz to 1050Mhz clock speed.

Thats quite a big bump in performance so running a HD 6000 PlatformID on a HD 5500 IGPU may cause problems when the IGPU is under heavy load as MacOS will not be optimally configured for your IGPU, recommend you use a HD 5500 PlatformID as previously stated.

For a smooth and trouble MacOS experience on Hackingtosh always match SMBIOS to CPU/Generation and PlatformID to nearest supported IGPU framebuffer.

Cheers
Jay

Ok, I have been on this since the day I have posted, I have fresh installed and changed AAPL,ig-platform-id to both 16160000 and 16160002 and it still says Intel Iris Graphics 6100. Please take a look at my EFI folder and tell me what Im doing wrong, also the kexts Im using as well if anything is interfering.

rowas · Jan 21, 2019

Hi. Quick question. Is there a table that I can check to see what model best fits my IGPU? I'm working with Intel P630.

jaymonkey · Jan 21, 2019

AnonymousMacPC said:
I have fresh installed and changed AAPL,ig-platform-id to both 16160000 and 16160002 and it still says Intel Iris Graphics 6100. Please take a look at my EFI folder and tell me what Im doing wrong, also the kexts Im using as well if anything is interfering.

@AnonymousMacPC,

The Device Properties for AAPL,ig-platform-id & device-id look ok in your config.plist.
You could try the boot argument -lilucpu=8 which will ensure that Lilu and Plugins see the CPU/IGPU correctly as Skylake.

Biggest issue I can see is that you are injecting all your 3rd party kexts, some of those kexts will not work correctly when injected by Clover. All 3rd party kexts to be used by MacOS should be installed in /L/E and "Inject Kexts" in config.plist should be set to "detect". Injecting that many kexts can make for an unstable system.

See this guide for info on why you should install kexts to /L/E and how to do it :-
https://www.tonymacx86.com/threads/...-el-capitan-sierra-high-sierra-mojave.268964/

Once you have installed kexts correctly, if the problem remains please generate PR files :-
https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/

Cheers
Jay

AnonymousMacPC · Jan 21, 2019

jaymonkey said:
@AnonymousMacPC,

The Device Properties for AAPL,ig-platform-id & device-id look ok in your config.plist.
You could try the boot argument -lilucpu=8 which will ensure that Lilu and Plugins see the CPU/IGPU correctly as Skylake.

Biggest issue I can see is that you are injecting all your 3rd party kexts, some of those kexts will not work correctly when injected by Clover. All 3rd party kexts to be used by MacOS should be installed in /L/E and "Inject Kexts" in config.plist should be set to "detect". Injecting that many kexts can make for an unstable system.

See this guide for info on why you should install kexts to /L/E and how to do it :-
https://www.tonymacx86.com/threads/...-el-capitan-sierra-high-sierra-mojave.268964/

Once you have installed kexts correctly, if the problem remains please generate PR files :-
https://www.tonymacx86.com/threads/tool-generate-proper-problem-reporting-files.235953/

Cheers
Jay

Skylake? You mean broadwell or am I misunderstanding something?

Which third party kexts?

Search

[Solved] Does SMBIOS affect what GPU name is?

AnonymousMacPC

jaymonkey

Moderator

AnonymousMacPC

AnonymousMacPC

jaymonkey

Moderator

AnonymousMacPC

AnonymousMacPC

Attachments

rowas

jaymonkey

Moderator

AnonymousMacPC

Forum

Guides

Downloads