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
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 Bikash
      Hello.. 
      I am trying to install macOS Mojave in my laptop but the is very slow.. I tried different methods and tutorials but all have same result.
       
      Install of High Sierra, Sierra and El capitan is fast and have no issue.
       
      Specifications:
      hp notebook v5d75pa#acj
      i5-4210u
      Intel HD 4400
      4gb ram ddr3
    • By kushwavez
      A really good motherboard with macOS compatible bult-in Wifi & Bluetooth

      ASUS Z170-Deluxe (with Wifi)
      BIOS: v3801
      CPU: i7-6700K 4.0 to 4.2 GHz (w/o OC)
      RAM: 1x 16 GB Corsair DDR4 2400 MHz
      GPU: Intel HD 530 (Headless) & ASUS Radeon RX 5700 OC 8 GB
      Audio: ALC 1150
      Ethernet: I219V2, I211-AT
      WiFi & Bluetooth: Broadcom BCM94360HMB Half-Mini-PCI-E
      More Specs: https://www.asus.com/Motherboards/Z170-DELUXE/specifications/
       
      Catalina 10.15.2 - Windows 10
      What is working:
      BCM94360HMB Wifi and Bluetooth AirDrop, Handoff, FaceTime, Messages, App Store, iCloud, etc. Intel HD 530 (QE/CI tested, but now I'm using it in headless) Sleep RX 5700 (QE/CI with 2 1080p monitors connected) Sound USB Ports Two Ethernet ports macOS with a light OC (4.12 GHz - 4.5 Ghz, XMP, ASUS optimal) No problem so far  
      What is not working:
      -  
       
      Not tested:
      VideoProc says that Hardware Decoding\Encoding is fully supported and enabled on both HD 530 and RX 5700 but I didn't test it Thunderbolt (no equipment)  
      Issues:
      None  
      BIOS Settings:
      Boot\CSM (Compatibility Support Module): Launch CSM: Disabled Boot\Secure Boot: OS type: Other OS Secure Boot State: Disabled Advanced\System agent (sa) Configuration: VT-d: Enabled Graphics Configuration: Primary Display: Auto iGPU Multi-monitor: Enabled RC6(Render Standby): Enabled DVMT Pre-Allocated: 128M Advanced\PCH Storage Configuration: SATA Mode Selection: AHCI Advanced\CPU Configuration: Intel Virtualization Technology: Enabled CPU- Power Management Control: Intel SpeedStep: Enabled CPU- C-States: Enabled Intel SpeedShift: Enabled  
      Getting ready for installation:
      Download the bootpack (Clover v5098): Click here -> ASUS-Z170_catalina.zip  
      Installation:
      Create an installer with any method you know (- Mac: createinstallmedia - Windows: Transmac, Vmware, Win32diskimager) Copy my Clover folder to the USB's EFI folder Boot with the Installer USB If you have any problem (kp or freeze) boot with config_debug.plist to see what causes the issue  
      Post Installation:
      Download Clover Configurator and generate a new Serial Number for yourself  
      Some pictures:
       

       




       
       
       
      Catalina & Windows 10 Dual-Boot (clean install, on one drive):
       Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it doesn't matter what you choose), 1 for Mac)
       Install Mac, boot with your USB, mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder (if there is no folder), copy the CLOVER folder I attached to the EFI folder, restart
      Boot into your Win installer, Format the partition you created for Win, install. 
      Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type: 
      bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi  
      You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)  
      Mounting EFI from Windows:
      Open cmd in administrator mode and type: mountvol b: /s (This will mount your EFI) Open Total Commander or Explorer++ in administrator mode to manage EFI mountvol b: /d (This will unmount your EFI)  
      Notes:
       
      2020.01.12: Tested system with OC, added more informations to BIOS settings
      2020.01.11: Added SmallTreeIntel82576.kext for 2nd Ethernet, Tested Ethernet ports
      2020.01.11: First upload
       
    • By TorqueX86
      Hi guys,

      I'm at my wit's end. I really need a hand here.
      I found only one clover setup for my motherboard, and works absolutely flawlessly for Mojave.

      Today I added an Asus Thunderbolt EX3 card, and that won't even let me boot my Mojave installation.

      My config.plist in attachment. Let's solve at least the Thunderbolt issue for now.
       
      There are also other issues, but let's solve this one first.
       
      Asus WS Z390 PRO + i9 9900K
      32GB 3200
      Nvidia 2080Ti for Windows and AMD RX480 for MacOS.
      Samsung NVME 950PRO
      config.plist
    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext (alongside Lilu.kext) and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By tlefko
      Now updated for 10.13.6+ Designed for i7 Skylake, QHD+, 256/8GB memory
      https://github.com/tlefko/OSX-XPS13-9350
      INSTALL
      you may want to disable Configure BIOS settings for EFI Booting. Disable RAID, enable AHCI, virtualization, make sure VRAM is over 32. and you should be set. also disable secure boot and enable UEFI booting You should create an EFI folder onto the USB and copy the contents of the USB onto the drive Boot off the usb using external mouse/keyboard (if required) and follow the installer prompts boot off the MAC HDD NOTES
      You may want to remove the DSDT patches if you have an issue. and manually repatch. however if you have the same model it should not be an issue. POST INSTALL
      Copy the folders from the root of the USB onto the computer efi folder. NOTES
      Some sleep bugs Tested with 10.13.6, not with 10.14 DSDT patches may have an issues if not the same model, you can remove them if there is an issue. CREDITS
      @Rehabman @maz-1 @syscl @darkvoid SUPPORT
      feel free to ask questions / open answers, you can also check out my other repository covering a previous mac version for the same model for other files for that / information on this topic Files.zip
×