Jump to content
poles89

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

22 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

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 karthiksh1989
      can somebody walkthrough with the mojave installation guide?
      i have a mac high sierra 13.6 version on my macbook pro and want to install mojave on my desktop
      Exact config is Gigabyte gaming wifi 7 motherboard amy ryzen 7 2nd gen 2700X processor Gigabyte G1 8GB grapgic card VEGA 64
      running 2 nvme Samsung 256gb cards and 1 intel 180gb ssd internal and 1tb WD HDD, with 64 GB 3200Mhz Ram
       
      https://wa.me/919611736534 (whatsapp)
    • By ltooz_audis
      I always want to have a long lasting battery ultrabook to install Mojave on. I was looking at Dell XPS 13 but its design is not very good with the camera and other problems. HP Spectre x360 is a nice design but the wifi module is soldered on board. The Envy 13" is the best one in the bunch for MacOS Mojave. I would not use any other macOS besides Mojave, it's the best one so far. If you can't get it done with macOS Mojave, you don't do it correctly, it's much more refined and given than older macOS's.
      I wanted the 8th generation because of the 4 cores which is almost 1.5 times faster than this 7th generation i7-7500u, but the price is too high. I picked up this one on Craigslist for $400. I've just ordered the 500GB NVME WD Black for $104 and DW1560 for $29. So, the perfect MacBook Pro 14,2 is less than $600 that last 5-6 hours with Mojave and 8-9 hours on Windows 10. The bench mark is the same as the real MacBookPro 14,2. BTW, this is the first try, there will be on going testing and confirming. 250GB hard drive is hardly enough for dual boot Windows and Mac. You need at least 500GB, I don't use Windows at all, so I'll partition 200GB for Windows and 300GB for Mojave.
      All new HP laptops will have kernel panic if using Clover to boot UEFI, at least a fix was found. I'll have more videos and info when I have time to write them. Watch the videos and ask questions if you have any problems.
      1. Clover 4558 - Lilu.kext (1.3.3) - AppleALC.kext (1.3.1) - Whatevergreen.kext (1.2.3) - USBInjectAll.kext (0.6.5) - Fakesmc.kext (6.25-332-gf3a8525c.1758) - ACPIBatteryManager.kext (1.81.4) - AHCIPortInjector.kext - BrcmFirmwareRepo.kext (2.2.7) - BrcmPatchRAM2.kext (2.2.7) - CodecCommander.kext (2.6.2) - FakePCIID_Broadcom_WiFi.kext (1.3.9) - FakePCIID_Intel_HD_Graphics.kext (1.3.9) - FakePCIID.kext (1.3.9) - SSDT-AUIC-ALL.aml - SSDT-USBX.aml - SSDT-PNLF.aml - SSDT-PluginType1.aml - PreLoader.efi.
      2. For the keys F2 & F3 to work with backlight slider - the Fakesmc.kext version is important for some reasons, I'm still trying to find out why.
      The touchscreen actually works without the voodooI2C kexts, just need to patch the clover.
       
      I've been playing with the laptop for over a week now. Ordered the WD 500GB WDS500G2X0C from Amazon for $104, the 256GB is too small for dual booting Windows 10 & Mojave. It's really plug and play.
       
      Hardware - needed to make this a perfect macbook Pro14,2.
      1. DW1560 BCM94352Z - make sure it has 2 notches - Tape the 2 right pins on the 4 pins tab for it to work without a hitch on both Windows 10 and Mojave. You can buy from Ebay cheaper but you have to wait for months.
      2. 500GB NVMe SSD m.2 connector M is a must for dual boot - the cheaper one will be slower - Crucial NVMe 500GB is $25 less than WD.
      3. NOVOO USB-C to HDMI hub that works and inexpensive.
       
      Let's start to get this Kaby Lake working on the HP - I believe HP has the same components for similar configuration on different models. In order to get Mojave to work on Intel Laptop, we need a few important components - Sound is important (look for Realtek - ALC295) - Ethernet if any -Realtek - Trackpad  and TouchScreen (Synaptics or Elan).
       
      REPLACE VNMe SSD HARD DRIVE and DW1560 BCM94352Z
       
      The current BIOS is F22, the newest one is F27 but I don't want to update since it's working well. Since I don't really need the original Windows 10 with Junk software in it, I install the latest Windows 10 using Media Creation USB Boot Drive. The important thing is we have to prepare the SSD correctly or our EFI folder will only be set at 100MB which is not enough to install Clover or any other boot loaders. So instead of letting the Windows installer to create the EFI folder automatically, we can set the size ourselves using "diskpart" command. In order to use diskpart, we need to boot with Windows 10 USB installer (hit F9 then select UEFI USB installer) - select system repair and not installation - then select command prompt, from here we can create EFI folder and MSR for Windows installer to install. The product ID is already in the UEFI bios, so we don't really have to manually activate the Windows 10.

       
       
      diskpart
      select disk 0
      clean
      convert gpt
      create partition efi=300 !!! you can change it from 300MB to any size.
      format quick fs=fat32 label="EFI"
      create partition msr size=16
      exit

      After exit, reboot with the USB installer again in UEFI mode, select the custom. The Windows installer will select the 300MB EFI folder we've just created.
       
       
      How to fix KP on Clover UEFI Boot.
       
       
      This is the macBook Pro 14,2 from HP 13-ad010nr
       
       
       
      Louis
       
    • By yehia2amer
      Problem:
      When I Attempt to wake my Machine from sleep, the screen stays black, although the computer is obviously awake !
      This Machine has a 1300W Power Supply So Sleep is Very Useful.
       
      I Tried:
      1) FIX_WAK and FixShutdown as per Clover Wiki.
      2) Although I am using "SAPPHIRE Radeon PULSE RX 580 8GB GDDR5", which Should be completely Supported by Mojave, I Also changed the Part Number to "113-4E353BU-O4E" as per this Guide: http://www.xlr8yourmac.com/archives/feb18/RadeonRX-580_MacPro.html. The GPU is working GREAT without even Clover Inject
      3) Tried to Run this command: disablehibernate.command.zip
      4) Tried darkwake=0 to 10
      5) Disabled wake on USB & Wake on LAN (BIOS)
       
      Logs:
      sudo pmset -g
      System-wide power settings: Currently in use: hibernatemode 0 disksleep 10 womp 0 networkoversleep 0 sleep 0 Sleep On Power Button 1 ttyskeepawake 1 hibernatefile /var/vm/sleepimage autorestart 0 gpuswitch 2 displaysleep 10 pmset -g assertions
      2019-02-19 18:51:04 +0200 Assertion status system-wide: BackgroundTask 1 ApplePushServiceTask 0 UserIsActive 1 PreventUserIdleDisplaySleep 0 PreventSystemSleep 0 ExternalMedia 1 PreventUserIdleSystemSleep 0 NetworkClientActive 0 Listed by owning process: pid 56(powerd): [0x0000001700088000] 00:13:44 ExternalMedia named: "com.apple.powermanagement.externalmediamounted" pid 100(hidd): [0x00000025000980a7] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968578.17" Timeout will fire in 600 secs Action=TimeoutActionRelease pid 200(mds_stores): [0x0000034e000b8279] 00:00:00 BackgroundTask named: "com.apple.metadata.mds_stores.power" Kernel Assertions: 0x4=USB id=502 level=255 0x4=USB mod=1/1/70, 2:00 AM description=com.apple.usb.externaldevice.1d130000 owner=USB Keyboard id=503 level=255 0x4=USB mod=1/1/70, 2:00 AM description=com.apple.usb.externaldevice.1d120000 owner=Lenovo Optical Mouse Idle sleep preventers: IODisplayWrangler  
      Specs:
      CPU: 2x Xeon E5-2680 v2 2.8GHz Ten Core Processors
      RAM: 128 GB 1333 MHz DDR3 ECC Memory
      GPU: SAPPHIRE Radeon PULSE RX 580 8GB GDDR5
      Chipset: Intel C602
      Audio: Realtek ALC3220 (ALC280) High Definition Audio
      SAS Drive Controllers (RAID): LSI 2308 SATA/SAS 6Gb/s controller with host based RAID 0, 1, 10 (4  
      Network Controller 1: Intel 82579 Gigabit Ethernet controller with Remote Wake UP, PXE and Jumbo frames support
      Network Controller 2: Intel Ethernet Controller I210 
      NEC USB3.0 xHCI Controller: Renesas Electronics uPD720201 & uPD720202
       
      for more info:
       
      Any Help will be appreciated, Thanks !
       
      Send me Yehias-Mac-Pro.zip
    • By yehia2amer
      Dell Precision T7610 Workstation
      Hackintosh GUIDE (Work in Progress)
       
                        
      Introduction: 
      Hi Everyone,
      This Workstation used to be a Beast with Dual CPUs and tons of RAM, I Know it is now normal to get that much cores in a Desktop but it is still a very decent machine for me (As a Programmer), and I thought it would be a good idea to Install MacOS as the Daily Driver Rather than Linux and It turns out to be a very Great Experience (with Some Challenges ).
       
      Specs:
      CPU: 2x Xeon E5-2680 v2 2.8GHz Ten Core Processors RAM: 128 GB 1333 MHz DDR3 ECC Memory GPU: SAPPHIRE PULSE Radeon RX 580 8GD5 Chipset: Intel C602 Audio: Realtek ALC3220 (ALC280) High Definition Audio SAS Drive Controllers (RAID): LSI 2308 SATA/SAS 6Gb/s controller with host based RAID 0, 1, 10 (4  Network Controller 1: Intel 82579 Gigabit Ethernet controller with Remote Wake UP, PXE and Jumbo frames support
      Network Controller 2: Intel Ethernet Controller I210
      NEC USB3.0 xHCI Controller: Renesas Electronics uPD720201 & uPD720202
       
      Working:
      Both "Xeon E5-2680 v2" and all cores with Power Management and P-States (using VoodooTSCSync & ssdtPRGen.sh) ATI Radeon HD 4870 (Vanilla) Realtek ALC3220 (ALC280)  (using VoodooHDA till Now - it is partially working with AppleALC using layout-id 13) LSI 2308 SAS (using AstekFusion2) Intel 82579 Network Controller (Vanilla) Intel I210 Network Controller (IntelMausiEthernet) USB 2.0  
      Not Working:
      NEC USB3.0 xHCI Controller (Renesas Electronics uPD720201 & uPD720202) Sleep  
      https://github.com/yehia2amer/Dell-Precision-T7610-Workstation-Hackintosh-Guide
    • By wen1
      Work in progress
       
      This is mini guide and config files for installing Mojave on a Dell XPS 13 9370.
       
      I took inspiration from sensibleJoe at on reddit
       
      My laptop's specs
       
      i7-8550U Intel HD 620 Graphics UHD Display 256GB Samsung NVMe SSD PM961 Killer 1435 Wifi  
      Here is what works
       
      Intel HD Graphics  Sleep Sound & Mic USB Wifi (Internal Killer Wifi will not work) Bluetooth Power Management Battery Management Screen Brightness Control  
      What does not work
       
      Internal Wifi Camera SD Card reader  
       
       
      I followed the vanilla guide here to create the Mac OS Mojave install USB. I used Mac OS 10.14.3.
       
      Here are some rough steps
       
      1. Create the USB installer for Mojave. You can use apple's own instructions
      2. Once the installer USB creation is complete, Install the latest version of clover to the USB disk with the following options 
      Install Clover for UEFI booting only
      Install Clover to the ESP
       
      Leave everything else as default (minimal install without a bunch of drivers)
       
      3. Then mount the EFI folder on the USB drive and replace the files in the config folder with the ones from the attached zip file over writing the files already there. This config is specifically for Dell XPS 13 9370.
      4. Go into the UEFI/BIOS on the laptop, Make sure your SATA mode is set to AHCI (And not Raid). Save and Exit
      5. Boot with the USB disk and install Mojave
      6. After the install is complete, Use the USB to boot again but this time boot into the newly installed Mojave partition.
      7. Install Clover on to the SSD with the same options as before.
      8. Then copy the config files to the EFI folder on the SSD overwriting the config folder there.
      9. Acquire the backlight AppleBacklightFixup.kext from here and install to /Library/Extensions (Thanks to Rehabman for the kext)
      10. Reboot.
       
      EDIT: V4 fixes many things, like powermanagement, backlight control etc. you also need to install AppleBacklightFixup.kext to /Library/Extensions
       
       
      CLOVER-v4.zip
×