Jump to content
1561 posts in this topic

Recommended Posts

Im not sure if this was covered before, but in CC/Devices/Properties, under PciRoot(0x0)/Pci(0x2,0x0) I'm getting 0900A53E for my AAPL,ig-platform-id in pcidevices.plist when I updated the PCIIDs through Hackintool instead of 0300923E, would this be due to the 9700K?  I had a few panics on reboot, and I apart from PciRoot(0x0)/Pci(0x2,0x0) I also edited PciRoot(0x0)/Pci(0x1f,0x3):hda-gfx to onboard-2 from onboard-1 to match my PCIID output of Hackintool. Maybe I should have done a full shutdown and startup.  As it eventually booted on the third try.

 

Update: Switched it back to 0300923E , and re-inserted device-id 70A10000 and back to onboard-1.  Not sure which was the problem for me, but it boots normally again for my setup.

Edited by Hifi33
Update
6 hours ago, telepati said:

 

Yes, I know, but which boot graphics glitch are you talking about to related AptioMemoryFix-64.efi. I was just curious.

 

No boot graphics glitch related to AptioMemoryFix-64.efi.  Was mentioning that it is recommended to use osxaptiofix2drv-free2000.efi rather than AptioMemoryFix-64.efi with Aorus Pro because AptioMemoryFix-64.efi can cause errors on boot.

 

Hence osxaptiofix2drv-free2000.efi replacing AptioMemoryFix-64.efi in this Aorus Pro guide.

 

:)

  • Thanks 1
6 hours ago, Hifi33 said:

Im not sure if this was covered before, but in CC/Devices/Properties, under PciRoot(0x0)/Pci(0x2,0x0) I'm getting 0900A53E for my AAPL,ig-platform-id in pcidevices.plist when I updated the PCIIDs through Hackintool instead of 0300923E, would this be due to the 9700K?  I had a few panics on reboot, and I apart from PciRoot(0x0)/Pci(0x2,0x0) I also edited PciRoot(0x0)/Pci(0x1f,0x3):hda-gfx to onboard-2 from onboard-1 to match my PCIID output of Hackintool. Maybe I should have done a full shutdown and startup.  As it eventually booted on the third try.

 

Update: Switched it back to 0300923E , and re-inserted device-id 70A10000 and back to onboard-1.  Not sure which was the problem for me, but it boots normally again for my setup.

 

@Hifi33

 

i7-9700K platform ID is 3E980003 better to use:

 

device-id 983E0000

 

AAPL,ig-platform-id 0300983E 

 

:)

 

  • Thanks 1
8 hours ago, blueman2010 said:

Thanks for the amazing guide.

 

I am using latest Clover and followed the guide still have iMessage and FaceTime not working.

 

I get a system freeze, how can I troubleshoot what is causing it?

 

My build is:

 

i9 9900K - Gigabyte z390 Pro - Sapphire Nitro+ RX 480 8GB - 16GB Corsair Vengeance RGB 3200 Mhz

Mac disk Samsung Evo 840 SSD 250GB

Windows 10 disk Samsung Evo plus 500GB M.2

 

config.plist.zip

 

@blueman2010

 

Hello, what Wireless / Blutooth device do you have ? When and where does the system freeze happen, does system freeze happen when you are using any specific application in macOS?  Do you have CPU / Memory overclocks ? Have you checked temperature of CPU when system freezes,  does system freeze in Windows ? 

 

 

7 hours ago, glasgood said:

 

@blueman2010

 

Hello, what Wireless / Blutooth device do you have ? When and where does the system freeze happen, does system freeze happen when you are using any specific application in macOS?  Do you have CPU / Memory overclocks ? Have you checked temperature of CPU when system freezes,  does system freeze in Windows ? 

 

 

Hey, 

I'm running on stock clock, only memory is on X. M. P 

No freezes or abnormal behavior on windows at all. Can't hear any increase of fan speed so assuming no overheats! And the freezes happened as follows :

First time happened when I installed Paragon NTFS after first reboot. Every time I start it freezes after 1 of 2 minutes. Reinstalled Mojave and while adding kexts from clover configurator I added NTFS one and after reboot freezes again then didn't boot at all after clover screen. 

Reinstalled again, this time didn't add anything different than what's in the guide, froze once so far after 2 minutes of boot, restarted and no freeze so far. I ran Geekbench 4 and no freezes so I don't think it's clocking issue. Do you think me using RX 480 would make any difference? 

I'm using built in LAN, no WiFi. 

 

1 hour ago, blueman2010 said:

Hey, 

I'm running on stock clock, only memory is on X. M. P 

No freezes or abnormal behavior on windows at all. Can't hear any increase of fan speed so assuming no overheats! And the freezes happened as follows :

First time happened when I installed Paragon NTFS after first reboot. Every time I start it freezes after 1 of 2 minutes. Reinstalled Mojave and while adding kexts from clover configurator I added NTFS one and after reboot freezes again then didn't boot at all after clover screen. 

Reinstalled again, this time didn't add anything different than what's in the guide, froze once so far after 2 minutes of boot, restarted and no freeze so far. I ran Geekbench 4 and no freezes so I don't think it's clocking issue. Do you think me using RX 480 would make any difference? 

I'm using built in LAN, no WiFi. 

 

 

Hi, 

 

iMessage's and Facetime will not work, see recommended WiFi / Bluetooth combo cards in guide for working iMessage's etc.

 

Ah, I suspect the Samsung Evo Plus drive is causing the system freeze. As far as I know there are definitely issues with the firmware, and macOS is having issues with this. Supposedly there is a firmware update that resolves the problem. 

 

 

:)

Hey buddy I hope your good.

Quick question, I'm gonna change my gpu over from my rx580 to a vega 56 as I have one spare I can use. Am I right in thinking as they are both native cards to mojave it will just be a matter of flipping the cards over and possibly correcting my pci info?

 

I'm also considering swapping out the internal USB connection to the pcie wifi card and routing it to an external usb2 socket at the back of the board instead and then using the exclude hs11 command in clover to turn off the h100i and commander pro. I've got the cables sitting around to do it so I might give it a blast and see what happens. Again what do you reckon buddy?  :)

Edited by AudioGod
1 hour ago, AudioGod said:

Hey buddy I hope your good.

Quick question, I'm gonna change my gpu over from my rx580 to a vega 56 as I have one spare I can use. Am I right in thinking as they are both native cards to mojave it will just be a matter of flipping the cards over and possibly correcting my pci info?

 

 

I have no issue switch graphic cards. I have both and have zero problem changing those. However, with Vega 56, you may want to tweak the fan and the voltage a bit. It runs quite hot and loud in Mojave. Things improve a bit in 10.15 Catalina but it's still a long way there. 

 

 

btw, @glasgood you may want to put version number to your EFI file so people know whenever there's new version comes up. My hack has been experiencing random startup hang with kernel / memory error. When that happens, I must reflash the bios to get things going again. I'm not sure what's the problem. Have you ever had something similar? 

Edited by larabee
8 hours ago, larabee said:

 

I have no issue switch graphic cards. I have both and have zero problem changing those. However, with Vega 56, you may want to tweak the fan and the voltage a bit. It runs quite hot and loud in Mojave. Things improve a bit in 10.15 Catalina but it's still a long way there. 

 

 

btw, @glasgood you may want to put version number to your EFI file so people know whenever there's new version comes up. My hack has been experiencing random startup hang with kernel / memory error. When that happens, I must reflash the bios to get things going again. I'm not sure what's the problem. Have you ever had something similar? 

 

@larabee

 

Hi, I put version number in the update section. I have no kernel / memory errors to report, though your board is different "Gigabyte Z390 Gaming X " possibly the memory driver in Aorus  EFI  is causing memory errors on your Z390 Gaming X board.  You could try using the drivers from @MaLd0n's >>Insanely HackBeast as the motherboard would be a closer match than the Aorus.  

 

:)

 

 

Edited by glasgood
9 hours ago, AudioGod said:

I'm also considering swapping out the internal USB connection to the pcie wifi card and routing it to an external usb2 socket at the back of the board instead and then using the exclude hs11 command in clover to turn off the h100i and commander pro. I've got the cables sitting around to do it so I might give it a blast and see what happens. Again what do you reckon buddy?  :)

 

 

@AudioGod

 

That may work, but could cause problems with sleep.  When you created the SSDT for usb ports fix, the internal motherboard USB2 header had its connection type set as 255, that's different from setting it as external USB 2 connector type 0. 

 

The connector type 255 for internal USB2 stops the Blutooth device from waking back from sleep.

 

Though it's worth a try. :)

 

 

Edited by glasgood
10 hours ago, larabee said:

 

I have no issue switch graphic cards. I have both and have zero problem changing those. However, with Vega 56, you may want to tweak the fan and the voltage a bit. It runs quite hot and loud in Mojave. Things improve a bit in 10.15 Catalina but it's still a long way there. 

 

Thanks for letting me know pal, nice one :)

when you say I should tweak the voltage and fans do you mean I can do them sort of tweaks from within macos?

I didn't think I would be able to do that other then from within windows and even then it wouldn't stick in macos.

Please do explain?

 

 

2 hours ago, glasgood said:

 

 

@AudioGod

 

That may work, but could cause problems with sleep.  When you created the SSDT for usb ports fix, the internal motherboard USB2 header had its connection type set as 255, that's different from setting it as external USB 2 connector type 0. 

 

The connector type 255 for internal USB2 stops the Blutooth device from waking back from sleep.

 

Though it's worth a try. :)

 

 

 

Theres only one way to find out I guess.

Let's call it a experiment just to see what happens. 

Tbh my system is so solid as is with your current efi that I should just leave it be but I'm one of them people that just can't do that. hahaha :)

il let you know what happens in a little bit buddy.

 

Edited by AudioGod
  • Like 1
10 hours ago, glasgood said:

 

@larabee

 

Hi, I put version number in the update section. I have no kernel / memory errors to report, though your board is different "Gigabyte Z390 Gaming X " possibly the memory driver in Aorus  EFI  is causing memory errors on your Z390 Gaming X board.  You could try using the drivers from @MaLd0n's >>Insanely HackBeast as the motherboard would be a closer match than the Aorus.  

 

:)

 

 

@glasgood thanks for getting back to me. I bought the exact board like yours and swap out my old board couple weeks ago, that's why I ask to see if you have anything like that. If I continue to have the issue, I will swap motherboard or my RAM to see if it's actually a hardware problem.

 

8 hours ago, AudioGod said:

 

Thanks for letting me know pal, nice one :)

when you say I should tweak the voltage and fans do you mean I can do them sort of tweaks from within macos?

I didn't think I would be able to do that other then from within windows and even then it wouldn't stick in macos.

Please do explain?

 @AudioGod With AMD Vega, the card regulate the voltage through a thing called Soft Power Play Table. You can changed the voltage and fan speed using an app called VGTAB.  It can create a Kext for you to install that regulate the fan speed / power at needed. THen you can inject those into config.plist device properties so the kext won't interfere with liliu and whatevergreen. I attached my config.plist here , you can copy paste that settings into yours and test it out. 

config.plist

  • Thanks 1

@larabee

 

Can you attach your EFI. I will have a look at it, what BIOS version are you using ?  are you using Memory X.M.P profile ? 

 

:)

1 minute ago, glasgood said:

@larabee

 

Can you attach your EFI. I will have a look at it, what BIOS version are you using ?  are you using Memory X.M.P profile ? 

 

:)

 

I'm using the exact EFI folder as your latest one with 580, removed device properties for the 580 and replaced with vega56. BIOS is at F9, and XMP is disabled. The only difference is the Vega56 device properties in my config.plist. I'm running the memory at 2400Mhz though. 

 

EFI.zip

16 minutes ago, larabee said:

 

I'm using the exact EFI folder as your latest one with 580, removed device properties for the 580 and replaced with vega56. BIOS is at F9, and XMP is disabled. The only difference is the Vega56 device properties in my config.plist. I'm running the memory at 2400Mhz though. 

 

EFI.zip

 

EFI looks fine, what make / manufacturer is your Vega 56 AMD card ? are you able to test with stock ram speed ? did you temporarily test removing Soft Power Play Table -->  PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)  to see if problem still persists.  

 

 

 

1 minute ago, glasgood said:

 

EFI looks fine, what make / manufacturer is your Vega 56 AMD card ? are you able to test with stock ram speed ? did you temporarily test removing Soft Power Play Table -->  PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)  to see if problem still persists.  

 

 

 

I'm using vega 56 sapphire pulse. The stock ram speed is at 2400 Mhz. Removing soft power play table will not affect the random boot hang. I forgot to take screenshot of the error , but it's similar to Freeing low memory (up to 0x2000000) results = 0. Then I will have to re-flash the BIOS to get my hack to work again. 

9 minutes ago, larabee said:

I'm using vega 56 sapphire pulse. The stock ram speed is at 2400 Mhz. Removing soft power play table will not affect the random boot hang. I forgot to take screenshot of the error , but it's similar to Freeing low memory (up to 0x2000000) results = 0. Then I will have to re-flash the BIOS to get my hack to work again. 

 

I can’t think why you have random boot hang. Wish I had an answer, the other memory drivers don’t seem to sit well with the Aorus Pro. Has problem persisted since early EFI folders ?

 

 

34 minutes ago, glasgood said:

 

I can’t think why you have random boot hang. Wish I had an answer, the other memory drivers don’t seem to sit well with the Aorus Pro. Has problem persisted since early EFI folders ?

 

 

@larabee @glasgood Ive got the exact same sapphire pulse vega 56 as you do. Il fit mine and let you both know if I get the same problem. (Might be a couple of days before I do as I have a massive job to finish first)

I had the same problem with the random boot hangs in the beginning of using your efi folder but for me it was my fault as when  i redid my pci info I wrote over the hd630 gpu info and it borked my boot up but as soon as I put the correct perimeters back in it was fine. Could you.of.done the same thing by any chance?

 

 

Edited by AudioGod
On 6/9/2019 at 4:03 PM, glasgood said:

 

Hi, 

 

iMessage's and Facetime will not work, see recommended WiFi / Bluetooth combo cards in guide for working iMessage's etc.

  

Ah, I suspect the Samsung Evo Plus drive is causing the system freeze. As far as I know there are definitely issues with the firmware, and macOS is having issues with this. Supposedly there is a firmware update that resolves the problem. 

  

 

:)

I don't have a BT and Wifi card on the supported list and iMessage etc works ok... just need a proper SMBIOS afaik. 

 

Also yes, the new Samsung firmware fixes the hanging issues with the Evo Plus drives.. been using mine for days now and not a problem at all.. 

6 hours ago, Cass67 said:

I don't have a BT and Wifi card on the supported list and iMessage etc works ok... just need a proper SMBIOS afaik. 

 

Also yes, the new Samsung firmware fixes the hanging issues with the Evo Plus drives.. been using mine for days now and not a problem at all.. 

 

Thanks for posting back, good to know that firmware update resolves issue. 

I have been attempting to boot my build from the recommended:

 

 Chipset  DVMT Pre-Allocated  256M

 Chipset  DVMT Total Gfx Mem  MAX 

 

The screen is hanging at Start ReadKernelCache on boot immediately after loading from the Clover EFI screen.

 

When I reset Bios back to the prior setting:

 

 Chipset  DVMT Pre-Allocated  64M

 Chipset  DVMT Total Gfx Mem  256M

 

Boots without issue.  I have gone over my settings and I can't find what I have set incorrectly, so I am curious what would cause this.  I did try • Chipset  Above 4G Decoding  Enabled but it didn't help.

1 hour ago, Hifi33 said:

I have been attempting to boot my build from the recommended:

 

 Chipset  DVMT Pre-Allocated  256M

 Chipset  DVMT Total Gfx Mem  MAX 

 

The screen is hanging at Start ReadKernelCache on boot immediately after loading from the Clover EFI screen.

 

When I reset Bios back to the prior setting:

 

 Chipset  DVMT Pre-Allocated  64M

 Chipset  DVMT Total Gfx Mem  256M

 

Boots without issue.  I have gone over my settings and I can't find what I have set incorrectly, so I am curious what would cause this.  I did try • Chipset  Above 4G Decoding  Enabled but it didn't help.

 

 

@Hifi33 

 

If  hanging persists, you can add the UseKernelCache=No Clover Boot Arguments. From previous experience it is best to keep Above 4G Decoding Disabled as it causes problem with installation.   Find attached below, the screen dumps showing the BIOS settings that I am using now.

 

BIOS SreenDumps Z390 Aorus Pro.zip

 

 

 

 

  • Thanks 1
1 hour ago, Hifi33 said:

I have been attempting to boot my build from the recommended:

 

 Chipset  DVMT Pre-Allocated  256M

 Chipset  DVMT Total Gfx Mem  MAX 

 

The screen is hanging at Start ReadKernelCache on boot immediately after loading from the Clover EFI screen.

 

When I reset Bios back to the prior setting:

 

 Chipset  DVMT Pre-Allocated  64M

 Chipset  DVMT Total Gfx Mem  256M

 

Boots without issue.  I have gone over my settings and I can't find what I have set incorrectly, so I am curious what would cause this.  I did try • Chipset  Above 4G Decoding  Enabled but it didn't help.

@glasgood I have this issue too. After boot hang, my BIOS automatically changed the integrated graphic setting from enabled to auto. Disable kernel cache solved it. Keep 4G decoding Disabled at all times. You don't use multiple PCI-E devices such as GPGPU Nvidia Tesla to mine bitcoins, so it's best to disable or it will create some memory problems. 

 

22 hours ago, glasgood said:

 

I can’t think why you have random boot hang. Wish I had an answer, the other memory drivers don’t seem to sit well with the Aorus Pro. Has problem persisted since early EFI folders ?

  

There are 2 types of boot hang I have, one is the start read kernel cache, the other is the clearing memory problem. The random Memory Clearing problem persists since the early version of your EFI. It happens more often when I update to 10.14.5 (18F132)

I tested other memory drivers, but the one we have on your EFI is the most stable one. 

My Bios sometimes does weird things such as resetting the Integrated Graphics settings from Enabled to Auto. I'm not sure if settings in hackintosh corrupt bios ? 

  • Like 1
23 minutes ago, larabee said:

@glasgood I have this issue too. After boot hang, my BIOS automatically changed the integrated graphic setting from enabled to auto. Disable kernel cache solved it. Keep 4G decoding Disabled at all times. You don't use multiple PCI-E devices such as GPGPU Nvidia Tesla to mine bitcoins, so it's best to disable or it will create some memory problems. 

 

There are 2 types of boot hang I have, one is the start read kernel cache, the other is the clearing memory problem. The random Memory Clearing problem persists since the early version of your EFI. It happens more often when I update to 10.14.5 (18F132)

I tested other memory drivers, but the one we have on your EFI is the most stable one. 

My Bios sometimes does weird things such as resetting the Integrated Graphics settings from Enabled to Auto. I'm not sure if settings in hackintosh corrupt bios ? 

 

 

I don't have any strange behaviour with BIOS settings. Could you look through the uploaded BIOS settings in last post, in the event something is missed and is causing problem. 

You could also try testing Hack with Intel only graphics and see if problem persists. 

 

Also worth reseting the CMOS, this will reset BIOS back to factory defaults:

 

225882688_Screenshot2019-06-12at18_36_36.thumb.png.714d2e3769cc5654b0251f11c802ee93.png

 

1303280252_Screenshot2019-06-12at18_36_57.thumb.png.b66ae4273d5a4c509fcd6104c6055d55.png

 

 

 

 

×
×
  • Create New...