Jump to content
poles89

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

28 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.

Announcements

  • Similar Content

    • By tonyx86
      **********************************************************************************
      In this thread, I have fully documented the installation of macOS Catalina on my HP EliteDesk 800 G4 Mini. It is a PERFECT HackMini8,1 and is running very well for me without any issues. I hope this documentation helps you to install macOS on your hack. Please leave feedback if you think there is anything I can improve and let me know if you have any questions.
      **********************************************************************************
       
      Background
      This is my first "modern" hack supporting UEFI and my first hack using Clover "on-the-fly" patches.  My previous hacks
      Laptop: Thinkpad T61 / Nvidia NVS 140m Laptop: Dell Latitude E6410 / Nvidia G3100m Desktop: Gigabyte G31 / GeForce 9600 Desktop: Biostar TH55HD / Sapphire Pulse RX580 (Google "Catalina Biostar TH55HD" and look for user name deeveedee)  
      are all perfectly running Catalina and I patched them all "manually" - all DSDT patches applied with MaciSL with virtually no Clover on-the-fly patching and all booted Legacy Clover.  This UEFI hack was MUCH easier and took about 20 hours vs. a combined hundreds of hours for the old hacks.  I wanted a hack that was a little more future proof and I think this is it.  I hope you enjoy this as much as I am enjoying it.  It is a perfect MacMini8,1.
       

       
      My system specs
      HP EliteDesk 800 G4 Mini (I7-8700T / UHD 630 / Q370 Chipset / 32GB DDR4 RAM) 3 x DP Ports (connected to monitors using DP -> DVI adapters) 6 x USB 3.1 1 x USB Type-C 3.1 2 x NVMe SSD (M.2 PCIe x4 2280/2230 combo ports) 1 x SATA6 SSD 1 x Intel Ethernet RJ-45 Conexant CX20632 Audio Codec Unsupported M.2 PCIe x1 2230 Intel Wi-Fi.  A possible solution is here, but I am NOT offering any support for this.  
      macOS Installation 
      Important: You MUST BE LOGGED-IN to download attachments from this forum
      See macOS installation steps here See Known Issues here for additional installation steps that may not yet be included in my attached config files See CLOVER (UEFI) installation later in this first post
      See BIOS configuration in attached BIOS configuration PDF document
      See EFI and /L/E kexts in attached EliteDesk.zip archive See how I developed my installation methodology here See references here See instructions here for installing two M.2 2280 NVMe SSDs and one SATA HD / SSD  
      What is not working
      Microphone port  
      What is not tested
      USB c 3.1 port (I have partially tested the USB 3 functionality of the port and it seems to be working fine with the SSDT-UIAC.aml in the attached EliteDesk800.zip archive) Wi-Fi / Bluetooth (intentional since I have not yet replaced my Intel card). A possible solution is here, but I am not offering any support for this.
       
      What is working
      Everything not mentioned above Sleep / Wake Multiple displays with IGPU graphics acceleration, hot pluggable display ports and DP->DVI adapters USB 3.1 ports Audio (internal speaker and headphone jack) Ethernet Auto-sensing headphone jack automatically switches to internal speaker when headphones removed  
      Known Issues and their solutions - see here
       
      BIOS Version / Configuration
      Version: 02.11.01 Rev.A See attached BIOS configuration in PDF document "HP EliteDesk 800 G4 Mini BIOS Configuration.pdf" Intel ME must be enabled for proper sleep / wake of UHD 630
       
      Clover Configuration
      Clover for UEFI booting only Install Clover in the ESP UEFI Drivers Recommended drivers DataHubDxe FSInject SMCHelper File System drivers ApfsDriverLoader VBoxHfs Memory fix drivers AptioMemoryFix Additional drivers NvmExpressDxe Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane (option not available when installing on USB thumb drive)  
      UHD 630 Framebuffer Patching
      See here and here to understand my graphics properties for use with WhateverGreen.kext Read this to see my attempt at graphics patching without WhateverGreen.kext (WEG) to get a better understanding of what WEG is doing
       
      Current Versions
      Catalina 10.15.6 Clover (UEFI) r5119 Lilu.kext 1.4.5 WhateverGreen.kext 1.4.0 AppleALC.kext 1.5.0 IntelMausi 1.0.3 (Not IntelMausiEthernet)  
      Credits To be provided
       
      ScreenShots
       
       
      HP EliteDesk 800 G4 Mini BIOS Configuration.pdf
       
      EliteDesk800 G4 Mini - Rev 1.0.zip
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive.  Edit: Recommend 16GB or larger for macOS Catalina 10.16 Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
       
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.6_18G103
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....
       
      eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD  
      This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.
       
      Updated Download Links for macOS Catalina 10.15.6_19G73
      Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
      InstallInfo.plist_edited_10.13.6.zip
      InstallInfo.plist_edited_10.14.6.zip
      InstallInfo.plist_edited_10.15.6.zip
    • By Lakkantha
      i install mac Catalina osx but can't boot without fake intel inject. And no audio or wifi. Can you help to make my clover config please
      Efi folder
       


    • By rawmassen
      Hi there,
       
      If anyone could help I'd be very grateful, I'm trying to move from Clover to OC but have hit a brick wall for the last 2 days.
       
      It's an ACPI table error: SB_.PCIO.XHC_RHUB.HS11, Namespace lookup failure.
       


      Skylake Build:
      OpenCore 0.5.9
      Mojave 10.14.6, iMac17,1
      Asus Maximus Hero VIII
      6700K
       
      I've attached the config.plist and ACPI folder.
       
      EFI Drivers: OpenRuntime.efi and HfsPlus.efi
      Kexts: IntelMausi, Lilu, VirtualSMC, Whatevergreen
       
      Things I've tried...
       
      1) Clearing NVRAM (as it was previously booted by Clover)
       
      2) Hackintool USB Mapping: both the SSDT files and the USBPorts.kext
       
      3) USBInjectAll.kext (with and without SSDT files)
       
      4) SSDT-RHUB.aml. This seems to be directly involved, spent a long time with this but with no luck.
       
      I followed this guide:
       
      https://dortania.github.io/Getting-Started-With-ACPI/Universal/rhub-methods/manual.html
       
      Everything is XHC in my DSDT, except these definitions at the top (line 72 and 73):
       
          External (_SB_.PCI0.XHC_.DUAM, MethodObj)    // Warning: Unknown method, guessing 0 arguments     External (_SB_.PCI0.XHC_.RHUB.INIR, MethodObj)    // Warning: Unknown method, guessing 0 arguments  
      So I edited the SSDT-RHUB.dsl to this:
       
      /* * Goal of this SSDT is to shut off the RHUB to force macOS into * manually building ports when the ACPI is screwed up */ DefinitionBlock ("", "SSDT", 2, "DRTNIA", "RhubOff", 0x00001000) { External (_SB_.PCI0.XHC.RHUB, DeviceObj) // Full pathing to RHUB, change to yours Scope (_SB.PCI0.XHC.RHUB) // Full pathing to RHUB, change to yours { Method (_STA, 0, NotSerialized) { If (_OSI ("Darwin")) { Return (Zero) // This disables the device only in macOS } Else { } } } } Which results in this AML version:
      DefinitionBlock ("", "SSDT", 2, "DRTNIA", "RhubOff", 0x00001000) { External (_SB_.PCI0.XHC_.RHUB, DeviceObj) Scope (_SB.PCI0.XHC.RHUB) { Method (_STA, 0, NotSerialized) // _STA: Status { If (_OSI ("Darwin")) { Return (Zero) } Else { } } } } But I get the same error. 
       
      I'm at a complete loss, can anyone help?
       
       
      config.plist
      ACPI.zip
×