Jump to content
poles89

[Solved] Native graphics acceleration from Intel UHD 630 of i3-8100 on mojave 10.14.2

26 posts in this topic

Recommended Posts

Hi guys,

 

Though native graphics acceleration is supported on i3 from Mojave, I'm not able to manage to get it.

 

This is my system configuration :

Motherboard:  Asus Prime H370-Plus
CPU: i3-8100 (UHD 630)
OS: Mojave 10.14.2

 

I'm trying every possible way to get full graphics acceleration. But whatever I try it shows only 4MB video memory or leads to Kernal Panic. Here are some ways I have tried so far:

 

Prerequisites: 

  • Installed latest Lilu+WEG on L/E.
  • set DMVT prealloc to 64MB on bios.

 

Option 1: IntelGFX-> 0x3E928086, ig-platform-id-> 0x3E9B0007, Inject Intel = true. Output:  Kernal Panic

Option 2: Blank IntelGFX, blank ig-platform-id, Inject Intel = false Output:  Kernal Panic

Option 3:  IntelGFX-> 0x3E928086, ig-platform-id-> 0x5912000, Inject Intel = true.  Output: Booted Successfully but no graphics acceleration.

               I knew that ig-platform-id-> 0x5912000 doesn't work in mojave and its works only for high sierra but I set this because with this ig-platform-id I can boot. Another way I can boot it by

               setting invalid Fake IntelGFX value like 0x12345678.

Option 4:  Downloaded Intel FBPatcher & followed this guide. But as I opened the app, its shows like this:

 

                U46xfOX.png

              

               It clearly indicates it neither can detect Intel CPU generation nor GPU memory (currently shows 0 MB). I changed to different PlatformId from the drop down but no improvement. Anyway I

               applied a patch with SMBIOS ->Macmini8,1 by someione's recommendation . I attached a config file (config_fbpather.plist) for this. Output:  Kernal Panic

 

I have tried the upper mentioned methods with SMBIOS like  iMac14,2 / iMac18[1,2,3]  and Macmini8,1. I'm using HDMI port for display output. Now I don't know whats wrong with theses methods but maybe someone can help me to figure out this problem. I have also attached those config.plist files.

 

Thanks in advance.

 

config_fakeid_0x3E928086.plist

config_fbpatcher.plist

config_fbpatcher_with_device_id.plist

config_platform-id_0x59120000.plist

Edited by poles89
forget to attached files.

Share this post


Link to post
Share on other sites
Advertisement

Helping someone out has become very hard on this website as a lot of people are coming to Hackintosh world lately.

Once I was trying to help a user to chose his new hardware for Hackintosh then I faced a Nvidia fanboy fighting me for something I wasn't sure about. Helping in Hackintosh means (try things out till fix the problem), no one can help another user with straight forward steps which will lead to a super successful Hackintosh, though it can happen but only by luck.

 

Anyway, I thing 0x5912000 shouldn't be there because its for Caby Lake and you should delete any iGPU related configs in config.plis, use only WEG+Lilu before you run FB-Patch (as its already mentioned in the guide).

Your FB-Patcher is detecting 0x3E92 as Device Id, so that should be the correct one which you can choose also as PlatformId, for PlatformId I select 0x3E920003 because I also have 0x3E92 Device Id, other way to know the correct Device Id is in Windows by running GPU-Z.

 

SMBIOS also should be Macmini8,1 or iMac 18,1 as I see people making UHD 630 work successfully, in my case I have a discrete GPU so I think its different but my goal is still try to help.

 

Share this post


Link to post
Share on other sites
6 hours ago, RandomTech said:

Helping someone out has become very hard on this website as a lot of people are coming to Hackintosh world lately.

Once I was trying to help a user to chose his new hardware for Hackintosh then I faced a Nvidia fanboy fighting me for something I wasn't sure about. Helping in Hackintosh means (try things out till fix the problem), no one can help another user with straight forward steps which will lead to a super successful Hackintosh, though it can happen but only by luck.

 

Anyway, I thing 0x5912000 shouldn't be there because its for Caby Lake and you should delete any iGPU related configs in config.plis, use only WEG+Lilu before you run FB-Patch (as its already mentioned in the guide).

Your FB-Patcher is detecting 0x3E92 as Device Id, so that should be the correct one which you can choose also as PlatformId, for PlatformId I select 0x3E920003 because I also have 0x3E92 Device Id, other way to know the correct Device Id is in Windows by running GPU-Z.

 

SMBIOS also should be Macmini8,1 or iMac 18,1 as I see people making UHD 630 work successfully, in my case I have a discrete GPU so I think its different but my goal is still try to help.

 

 

Thanks for the suggestion.

I'm using WEG+Lilu. FB-Patcher is detecting 0x3E92 beacuse I thought its the right one. But still fb-pathcer can't detect it. You are right that I have to know the right device id. I will install windows and run GPU Z to see the device id.

Share this post


Link to post
Share on other sites
1 hour ago, poles89 said:

 

Thanks for the suggestion.

I'm using WEG+Lilu. FB-Patcher is detecting 0x3E92 beacuse I thought its the right one. But still fb-pathcer can't detect it. You are right that I have to know the right device id. I will install windows and run GPU Z to see the device id.

 

You probably don't need to install windows to find out your device id for your gpu.  Just use DPCIManager.  Here's the link and disregard the malware warning. It's a false positive because it can get beneath your OS to read the device ids.

 

https://sourceforge.net/projects/dpcimanager/

Share this post


Link to post
Share on other sites
19 hours ago, mnfesq said:

 

You probably don't need to install windows to find out your device id for your gpu.  Just use DPCIManager.  Here's the link and disregard the malware warning. It's a false positive because it can get beneath your OS to read the device ids.

 

https://sourceforge.net/projects/dpcimanager/

 

Sorry man, I already used it.:cry:

 

I found that my device id is 0x3E91. But I still can't boot with IntelGFX: 0x3E910000 & ig-platform-id: 0x3E9B0007 or 0X3E910003. I tried to boot only with IntelGFX: 0x3E910000 and blank ig-platgform-id too but no improvement.

 

r1Ib90Eg.jpg

Share this post


Link to post
Share on other sites

Someone reported success with your setup by removing the FakeID for IntelGFX.  Here's the link:

 

 

 

Edited by mnfesq

Share this post


Link to post
Share on other sites
6 hours ago, poles89 said:

I found that my device id is 0x3E91. But I still can't boot

You might also need to configure the display connectors by using FB-Patcher, wether is HDMI or DP depending on your display and motherboard's connection, I cannot be sure of course onemanOSX knows better if that's the case or not.

Share this post


Link to post
Share on other sites
9 hours ago, RandomTech said:

You might also need to configure the display connectors by using FB-Patcher, wether is HDMI or DP depending on your display and motherboard's connection, I cannot be sure of course onemanOSX knows better if that's the case or not.

Thanks. If you see my original post then there is a image I posted where the fb pathcer can't detect Intel generation and graphics memory. Even after changing device id to 0x3E91 .

Share this post


Link to post
Share on other sites
5 hours ago, ellaosx said:

i am only using lilu,weg & Inject Intel=true. No other special settings in config.plist

 

Tried already. Didn't work.

Share this post


Link to post
Share on other sites
5 hours ago, poles89 said:

Thanks. If you see my original post then there is a image I posted where the fb pathcer can't detect Intel generation and graphics memory. Even after changing device id to 0x3E91 .

I ignored the first post because is all wrong, it detects 0x5912000 and I think is duo to config.plist wrong iGPU information.

The only thing to do is to set BIOS correctly for iGPU and follow the FB-Patcher guide with more attention.

What happens to you is not FB-Patcher fault, Im sure there is something wrong with the steps you taking.

I hope you fix it. Merry Christmas and happy new year.

Share this post


Link to post
Share on other sites
5 hours ago, RandomTech said:

I ignored the first post because is all wrong, it detects 0x5912000 and I think is duo to config.plist wrong iGPU information.

The only thing to do is to set BIOS correctly for iGPU and follow the FB-Patcher guide with more attention.

What happens to you is not FB-Patcher fault, Im sure there is something wrong with the steps you taking.

I hope you fix it. Merry Christmas and happy new year.

 

Merry Christmas !!!

 

The thing is I can't boot with proper ig-platform-id which is 0x3E9B0007 for Mojave. I can only boot in these following conditions:

1> IntelGFX -> 0x12345678 & blank ig-platform-id. Means with an invalid fakeID.

2> IntelGFX -> 0x3E918086 & High Sierra's ig-platform-id 0x5912000. I know its not correct & I don't get any graphics acceleration but at least I can boot.

 

I think maybe the Intel FB-Patcher can only be useful when you can boot with proper IntelGFX value & ig-platform-id. Intel FB-Patcher's guide doesn't tell you what you should do if you can't boot your machine without those value. It assumes that you already booted with proper fakeID & ig-platform-id. Still I tried to use it by assuming that my IntelGFX value 0x3E918086 & ig-platform-id as 0x3E9B0007 and generated a patch which didn't work out (FYI, the OP's image of fb-pathcer's device id is 0x3E92 which was wrong but I tried the same app with my actual device id 0x3E91, which leads to same result).

 

Intel FB-Patcher is a great app which helped lot of users to create patches. But for me, it didn't work out. I know I'm missing something but if you can't boot with proper value & and even if you boot with invalid ig-platform-id, the app doesn't show you cpu generation & video memory then how could you generate a proper patch?

 

Maybe @headkaze can give some suggestion about how you should use the fb-pathcer app if you can't boot your machine with proper id.

 

 

Share this post


Link to post
Share on other sites
3 hours ago, poles89 said:

It assumes that you already booted with proper fakeID & ig-platform-id

I didn't use any fakeID & ig-platform-id to boot (only WEG+Lilu as the FB-Patcher guide says)

3 hours ago, poles89 said:

but if you can't boot with proper value

No need to a proper value for boot (only WEG+Lilu as the FB-Patcher guide says)

3 hours ago, poles89 said:

how you should use the fb-pathcer app if you can't boot your machine with proper id.

There is no need for proper id to boot machine (only WEG+Lilu as the FB-Patcher guide says)

 

If this doesn't work for you then maybe its another issue

 

Good luck

Share this post


Link to post
Share on other sites

@poles89

cleanup config.plist w/o fake IntelGFX & ig-platform-id

 

1. Install Lilu & Weg.

2. Install Rehabman's FakePCIID & FakePCIID_Intel_HD_Graphics

3. Inject Intel=true

4. set DVMT to 96

Edited by ellaosx

Share this post


Link to post
Share on other sites
15 hours ago, RandomTech said:

I didn't use any fakeID & ig-platform-id to boot (only WEG+Lilu as the FB-Patcher guide says)

No need to a proper value for boot (only WEG+Lilu as the FB-Patcher guide says)

There is no need for proper id to boot machine (only WEG+Lilu as the FB-Patcher guide says)

 

If this doesn't work for you then maybe its another issue

 

Good luck

 

Thanks. What Fb-pathcer guide says is, you need to remove any fakeID & ig-platform-id before applying that patch but for that you need to boot the machine...so that you can run the app and do necessary steps. You guys are lucky that you can boot machine without those ids.

13 hours ago, ellaosx said:

@poles89

cleanup config.plist w/o fake IntelGFX & ig-platform-id

 

1. Install Lilu & Weg.

2. Install Rehabman's FakePCIID & FakePCIID_Intel_HD_Graphics

3. Inject Intel=true

4. set DVMT to 96

 

Ok I will try that. But what will be the installed location of all those? L/E or kexts/other?

Edited by poles89

Share this post


Link to post
Share on other sites
On 12/28/2018 at 5:41 AM, ellaosx said:

@poles89

cleanup config.plist w/o fake IntelGFX & ig-platform-id

 

1. Install Lilu & Weg.

2. Install Rehabman's FakePCIID & FakePCIID_Intel_HD_Graphics

3. Inject Intel=true

4. set DVMT to 96

 

Tried but it didn't work.

Share this post


Link to post
Share on other sites

But I find something in the boot log

 

Quote

WARNING: IOPlatformPluginUtil : getCPUIDInfo: this is an unknown CPU model 0x9e

 

Which means it can't detect the cpu and I think thats why FB-patcher is showing ??? in cpu generation section. The Lilu+WEG is already installed. I also tried @RehabMan FakeCPUID.kext but no luck.

 

I also find that AppleFramebuffer is not loading at all when I opened ioreg.

 

IGPU@2.thumb.png.9d1a6bdcc1697154a7eeb2277c7d965e.png

 

I also added  -liludbgall -wegdbg liludump=60 boot flags with debug version of lilu+WEG. Here are the attached files.

 

 

Lilu_1.3.1_18.2.txt

bootlog.txt

Share this post


Link to post
Share on other sites
On 12/28/2018 at 5:18 AM, poles89 said:

 

Thanks. What Fb-pathcer guide says is, you need to remove any fakeID & ig-platform-id before applying that patch but for that you need to boot the machine...so that you can run the app and do necessary steps. You guys are lucky that you can boot machine without those ids.

 

Ok I will try that. But what will be the installed location of all those? L/E or kexts/other?

 

Exactly this.  The guides say to remove FakeID for IntelGFX, don't inject anything, basically, remove any graphics related configs, but when I do that, I can't boot.  Like you, the only way I can boot is with IntelGFX FakeID of 0x12345678 and inject Intel.  Like you, no acceleration, but at least I can boot.

 

I would up just buying a RX 560 4GB for $120 and get fully supported, accelerated graphics, and more performance than the UHD 630.  I have found an interesting issue with my UHD 630 when the RX 560 is installed and am going to post about it in this forum now.

Share this post


Link to post
Share on other sites

It has been solved by using a connectors patch orginally used by Asus Prime H370M-Plus.

As I have DVI-D, HDMI & VGA ports my connectors tab settings in Intel FB-Pathcer a.k.a Hackintool should be

 

Row 1: Index 2, BusID 0x02, Type HDMI
Row 2: Index 3, BusID 0x04, Type HDMI
Row 3: Index 1, BusID 0x01, Type DP

 

Here DVI-D type also written as HDMI. Otherwise the DVI-D port will not work. And the patch:

 

Spoiler

<key>Properties</key>
<dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,ig-platform-id</key>
<data>
BwCbPg==
</data>
<key>device-id</key>
<data>
mz4AAA==
</data>
<key>framebuffer-con0-busid</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con0-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con0-index</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-pipe</key>
<data>
CgAAAA==
</data>
<key>framebuffer-con0-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con1-busid</key>
<data>
BAAAAA==
</data>
<key>framebuffer-con1-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con1-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con1-index</key>
<data>
AwAAAA==
</data>
<key>framebuffer-con1-pipe</key>
<data>
CAAAAA==
</data>
<key>framebuffer-con1-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con2-busid</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con2-index</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-pipe</key>
<data>
CQAAAA==
</data>
<key>framebuffer-con2-type</key>
<data>
AAQAAA==
</data>
<key>framebuffer-patch-enable</key>
<data>
AQAAAA==
</data>
</dict>
</dict>

 

Now my both DVI-D & HDMI ports are working.

Share this post


Link to post
Share on other sites
On 1/26/2019 at 2:55 PM, poles89 said:

It has been solved by using a connectors patch orginally used by Asus Prime H370M-Plus.

As I have DVI-D, HDMI & VGA ports my connectors tab settings in Intel FB-Pathcer a.k.a Hackintool should be

 

Row 1: Index 2, BusID 0x02, Type HDMI
Row 2: Index 3, BusID 0x04, Type HDMI
Row 3: Index 1, BusID 0x01, Type DP

 

Here DVI-D type also written as HDMI. Otherwise the DVI-D port will not work. And the patch:

 

  Hide contents

<key>Properties</key>
<dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,ig-platform-id</key>
<data>
BwCbPg==
</data>
<key>device-id</key>
<data>
mz4AAA==
</data>
<key>framebuffer-con0-busid</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con0-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con0-index</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-pipe</key>
<data>
CgAAAA==
</data>
<key>framebuffer-con0-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con1-busid</key>
<data>
BAAAAA==
</data>
<key>framebuffer-con1-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con1-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con1-index</key>
<data>
AwAAAA==
</data>
<key>framebuffer-con1-pipe</key>
<data>
CAAAAA==
</data>
<key>framebuffer-con1-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con2-busid</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con2-index</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-pipe</key>
<data>
CQAAAA==
</data>
<key>framebuffer-con2-type</key>
<data>
AAQAAA==
</data>
<key>framebuffer-patch-enable</key>
<data>
AQAAAA==
</data>
</dict>
</dict>

 

Now my both DVI-D & HDMI ports are working.

 

Do you use a DVI-D port to connect to a monitor?

Share this post


Link to post
Share on other sites
On 2/4/2019 at 2:58 AM, idk said:

 

Do you use a DVI-D port to connect to a monitor?

 

I know its been late. But yes, I use DVI-D port for monitor.

Share this post


Link to post
Share on other sites
On 1/26/2019 at 7:55 AM, poles89 said:

It has been solved by using a connectors patch orginally used by Asus Prime H370M-Plus.

As I have DVI-D, HDMI & VGA ports my connectors tab settings in Intel FB-Pathcer a.k.a Hackintool should be

 

Row 1: Index 2, BusID 0x02, Type HDMI
Row 2: Index 3, BusID 0x04, Type HDMI
Row 3: Index 1, BusID 0x01, Type DP

 

Here DVI-D type also written as HDMI. Otherwise the DVI-D port will not work. And the patch:

 

  Reveal hidden contents

<key>Properties</key>
<dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
<key>AAPL,ig-platform-id</key>
<data>
BwCbPg==
</data>
<key>device-id</key>
<data>
mz4AAA==
</data>
<key>framebuffer-con0-busid</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con0-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con0-index</key>
<data>
AgAAAA==
</data>
<key>framebuffer-con0-pipe</key>
<data>
CgAAAA==
</data>
<key>framebuffer-con0-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con1-busid</key>
<data>
BAAAAA==
</data>
<key>framebuffer-con1-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con1-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con1-index</key>
<data>
AwAAAA==
</data>
<key>framebuffer-con1-pipe</key>
<data>
CAAAAA==
</data>
<key>framebuffer-con1-type</key>
<data>
AAgAAA==
</data>
<key>framebuffer-con2-busid</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-enable</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-flags</key>
<data>
xwMAAA==
</data>
<key>framebuffer-con2-index</key>
<data>
AQAAAA==
</data>
<key>framebuffer-con2-pipe</key>
<data>
CQAAAA==
</data>
<key>framebuffer-con2-type</key>
<data>
AAQAAA==
</data>
<key>framebuffer-patch-enable</key>
<data>
AQAAAA==
</data>
</dict>
</dict>

 

Now my both DVI-D & HDMI ports are working.

 

Would you mind telling me where that patch goes? I believe I have the same problem. MSI Z390 motherboard, i5-9600 with Intel UHD 630 graphics. Have a DVI and HDMI port. I get a black screen about half way through boot, unless I fake the device in Clover boot with 0x12345678

 

Thanks,

Mark

 

 

Share this post


Link to post
Share on other sites
Posted (edited)
17 hours ago, mdurg said:

 

Would you mind telling me where that patch goes? I believe I have the same problem. MSI Z390 motherboard, i5-9600 with Intel UHD 630 graphics. Have a DVI and HDMI port. I get a black screen about half way through boot, unless I fake the device in Clover boot with 0x12345678

 

Thanks,

Mark

 

 

 

It goes to Devices -> Properties section on your config.plist

 

Can you try the following code which is working for MSI Z390M Gaming Plus motherboard:

 

Spoiler

		<key>Properties</key>
		<dict>
			<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
			<dict>
				<key>AAPL,ig-platform-id</key>
				<data>
				BwCbPg==
				</data>
				<key>device-id</key>
				<data>
				mz4AAA==
				</data>
				<key>enable-hdmi20</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con0-busid</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con0-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con0-flags</key>
				<data>
				xwMAAA==
				</data>
				<key>framebuffer-con0-index</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con0-pipe</key>
				<data>
				EgAAAA==
				</data>
				<key>framebuffer-con0-type</key>
				<data>
				AAgAAA==
				</data>
				<key>framebuffer-con1-busid</key>
				<data>
				AAAAAA==
				</data>
				<key>framebuffer-con1-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con1-flags</key>
				<data>
				xwMAAA==
				</data>
				<key>framebuffer-con1-index</key>
				<data>
				AgAAAA==
				</data>
				<key>framebuffer-con1-pipe</key>
				<data>
				EgAAAA==
				</data>
				<key>framebuffer-con1-type</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con2-busid</key>
				<data>
				AAAAAA==
				</data>
				<key>framebuffer-con2-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con2-flags</key>
				<data>
				xwMAAA==
				</data>
				<key>framebuffer-con2-index</key>
				<data>
				AwAAAA==
				</data>
				<key>framebuffer-con2-pipe</key>
				<data>
				EgAAAA==
				</data>
				<key>framebuffer-con2-type</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con3-busid</key>
				<data>
				AAAAAA==
				</data>
				<key>framebuffer-con3-enable</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-con3-flags</key>
				<data>
				IAAAAA==
				</data>
				<key>framebuffer-con3-index</key>
				<data>
				/////w==
				</data>
				<key>framebuffer-con3-pipe</key>
				<data>
				AAAAAA==
				</data>
				<key>framebuffer-con3-type</key>
				<data>
				AQAAAA==
				</data>
				<key>framebuffer-patch-enable</key>
				<data>
				AQAAAA==
				</data>
			</dict>
		</dict>

 

Try HDMI first.

Edited by poles89

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can download the official release binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Spoofing Intel CPU Gen
      If you need to spoof a different Intel CPU generation you can use the lilucpu=N boot flag. The N refers to the following Intel generations:
      4    SandyBridge 5    IvyBridge 6    Haswell 7    Broadwell 8    Skylake 9    KabyLake 10   CoffeeLake To spoof a CPU you will need to set a valid device-id in your GPU entry in Devices/Properties for the appropriate Intel generation.
       
      Eg. Spoofing Skylake (lilucpu=8 boot flag with device-id=0x16190000), Kaby Lake (lilucpu=9 boot flag with device-id=0x12590000).
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - S/L/E/AppleIntelSNBGraphicsFB.kext
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - device-id: 0x0102 0x0106 0x010A 0x0112 0x0116 0x0122 0x0126
      - AAPL,snb-platform-id (desktop): 0x00030010 (default)
      - AAPL,snb-platform-id (laptop): 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - S/L/E/AppleIntelFramebufferCapri.kext
      - Support started with OS X 10.8.x
      - device-id: 0x0152 0x0156 0x0162 0x0166
      - AAPL,ig-platform-id (desktop): 0x0166000A (default), 0x01620005
      - AAPL,ig-platform-id (laptop): 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - S/L/E/AppleIntelFramebufferAzul.kext
      - Support started with OS X 10.9.x
      - device-id: 0x0D26 0x0A26 0x0A2E 0x0D22 0x0412
      - AAPL,ig-platform-id (desktop): 0x0D220003 (default)
      - AAPL,ig-platform-id (laptop): 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - S/L/E/AppleIntelBDWGraphicsFramebuffer.kext
      - Support started with OS X 10.10.2
      - device-id: 0x0BD1 0x0BD2 0x0BD3 0x1606 0x160E 0x1616 0x161E 0x1626 0x1622 0x1612 0x162B
      - AAPL,ig-platform-id (desktop): 0x16220007 (default)
      - AAPL,ig-platform-id (laptop): 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - S/L/E/AppleIntelSKLGraphicsFramebuffer.kext
      - Support started with OS X 10.11.4
      - device-id: 0x1916 0x191E 0x1926 0x1927 0x1912 0x1932 0x1902 0x1917 0x193B 0x191B
      - AAPL,ig-platform-id (desktop): 0x19120000 (default)
      - AAPL,ig-platform-id (laptop): 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - S/L/E/AppleIntelKBLGraphicsFramebuffer.kext
      - Support started with macOS 10.12.6
      - device-id: 0x5912 0x5916 0x591B 0x591C 0x591E 0x5926 0x5927 0x5923 0x87C0
      - AAPL,ig-platform-id (desktop): 0x59160000 (default)
      - AAPL,ig-platform-id (laptop): 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - device-id: 0x3E9B 0x3EA5 0x3EA6 0x3E92 0x3E91 0x3E98
      - AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - AAPL,ig-platform-id (laptop): 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM for 4K users who experience graphical glitches (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-camellia framebuffer-flags framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Hackintool File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Hackintool File->Import->IOReg Dump menu
       
      3. Using Hackintool Framebuffer->macOS 10.14 menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall liludump=60 boot flags. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work. Log files should be located at /var/log/Lilu_*.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt Getting Help

      To help the users of this forum diagnose issues with your configuration please generate a Lilu debug log and then run gen_debug.sh to generate a folder of debug files you can attach to a forum post requesting help.

      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
×