Jump to content

59 posts in this topic

Recommended Posts

Folks, it would appear a warning and reminder is required here! This thread is a general discussion related to getting Ice Lake graphics working in Catalina, it's not a thread to discuss issues related to audio, Youtube video playback, CPU power management, TouchPad or Thunderbolt ports issues on your own Ice Lake platforms.

:offtopic: :offtopic: :offtopic:

 

Given that small group of people had began hijacking this thread for unrelated matters, substantial cleanup was made and all off-topic posts were removed. Any further off-topic posts will deleted without prior notice. I remind everyone that unrelated matters can be discussed in their own dedicated and fully appropriate threads.

 

Thank you for keeping this thread on-topic and not turning it into a trash can.

Share this post


Link to post
Share on other sites
Advertisement
On 9/12/2020 at 4:31 PM, hrishi654 said:

@Ab2774 or @vokhotnikov were you able to fix your black screen isuue? It seems that the display works but no backlight as I can see the login screen if I use a flashlight. But the backlight starts working after approximately 5 min.

 

No, I'm still having the same issue as yours. Every reboot it's a lottery. Sometimes the screen works fine, but other times I have to wait some 5 minutes before the screen turns on.

 

I have activated SSH and VNC sharing - I can login into the laptop during the black screen period.

 

Also I tried several times to find anything in the logs (captured via log show --info --debug) at the moment when the screen turns on. As far as I can tell, there's absolutely nothing there that might be related (there are a number of messages during the time period in question, but for all of them similar messages happen many times before, while the screen is blank.

 

Very weird.

Share this post


Link to post
Share on other sites

Does someone managed to fix the kernel panic at sleep/wake? (i don't know exactly when)

 

Spoiler

panic(cpu 2 caller 0xffffff7f8611c09e): "[IGFB][PANIC][POWER    ] " "Cannot allow DC9 without disallowing DC6\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-14.7.8/IONDRV/ICLLP/AppleIntelFramebuffer/AppleIntelController.cpp:5531
Backtrace (CPU 2), Frame : Return Address
0xffffff810febb970 : 0xffffff800151a65d mach_kernel : _handle_debugger_trap + 0x49d
0xffffff810febb9c0 : 0xffffff8001654a75 mach_kernel : _kdp_i386_trap + 0x155
0xffffff810febba00 : 0xffffff80016465fe mach_kernel : _kernel_trap + 0x4ee
0xffffff810febba50 : 0xffffff80014c0a40 mach_kernel : _return_from_trap + 0xe0
0xffffff810febba70 : 0xffffff8001519d27 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff810febbb70 : 0xffffff800151a117 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff810febbbc0 : 0xffffff8001cc1abc mach_kernel : _panic + 0x54
0xffffff810febbc30 : 0xffffff7f8611c09e com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController11enableHWDC6Ev.cold.1
0xffffff810febbc40 : 0xffffff7f860cb635 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController9enableDC9Ev + 0x3b
0xffffff810febbc60 : 0xffffff7f860cb531 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController10setDCStateEb + 0x361
0xffffff810febbca0 : 0xffffff7f8609b0e2 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer24setFramebufferPowerStateEj + 0x224
0xffffff810febbcd0 : 0xffffff7f860b0b9f com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer12setAttributeEjm + 0x1ad
0xffffff810febbd20 : 0xffffff7f860b0c6a com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer12setAttributeEjm + 0x278
0xffffff810febbd70 : 0xffffff7f85f47faa com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer14checkPowerWorkEj + 0x280
0xffffff810febbe10 : 0xffffff7f85f47d08 com.apple.iokit.IOGraphicsFamily : __ZN14IOFBController14checkPowerWorkEj + 0x9a
0xffffff810febbe40 : 0xffffff7f85f4eaeb com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x123
0xffffff810febbee0 : 0xffffff8001c2d54d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff810febbf30 : 0xffffff8001c2be1e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffff810febbf70 : 0xffffff8001c2b416 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffff810febbfa0 : 0xffffff80014c013e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7f85f3d000->0xffffff7f85f8dfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f81f12000
         com.apple.driver.AppleIntelICLLPGraphicsFramebuffer(14.0.7)[18868C3D-C807-3435-BBD6-D95A2F4D2FA7]@0xffffff7f86084000->0xffffff7f86321fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f81f12000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f81f09000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7f85fb6000
            dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f81e49000
            dependency: com.apple.AppleGraphicsDeviceControl(5.2.6)[372B091D-3A52-3749-AE17-E8A5103D8DB0]@0xffffff7f8607a000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7f85f3d000

BSD process name corresponding to current thread: kernel_task
Boot args: debug=0x100 keepsyms=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide:     0x0000000001200000
Kernel text base: 0xffffff8001400000
__HIB  text base: 0xffffff8001300000
System model name: MacBookPro16,2 (Mac-5F9802EFE386AA28)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 486125505360


 

 

Share this post


Link to post
Share on other sites
On 9/14/2020 at 2:03 PM, Paolo7297 said:

Does someone managed to fix the kernel panic at sleep/wake? (i don't know exactly when)

 

  Reveal hidden contents

panic(cpu 2 caller 0xffffff7f8611c09e): "[IGFB][PANIC][POWER    ] " "Cannot allow DC9 without disallowing DC6\n"@/Library/Caches/com.apple.xbs/Sources/GPUDriversIntel/GPUDriversIntel-14.7.8/IONDRV/ICLLP/AppleIntelFramebuffer/AppleIntelController.cpp:5531
Backtrace (CPU 2), Frame : Return Address
0xffffff810febb970 : 0xffffff800151a65d mach_kernel : _handle_debugger_trap + 0x49d
0xffffff810febb9c0 : 0xffffff8001654a75 mach_kernel : _kdp_i386_trap + 0x155
0xffffff810febba00 : 0xffffff80016465fe mach_kernel : _kernel_trap + 0x4ee
0xffffff810febba50 : 0xffffff80014c0a40 mach_kernel : _return_from_trap + 0xe0
0xffffff810febba70 : 0xffffff8001519d27 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff810febbb70 : 0xffffff800151a117 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff810febbbc0 : 0xffffff8001cc1abc mach_kernel : _panic + 0x54
0xffffff810febbc30 : 0xffffff7f8611c09e com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController11enableHWDC6Ev.cold.1
0xffffff810febbc40 : 0xffffff7f860cb635 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController9enableDC9Ev + 0x3b
0xffffff810febbc60 : 0xffffff7f860cb531 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN31AppleIntelFramebufferController10setDCStateEb + 0x361
0xffffff810febbca0 : 0xffffff7f8609b0e2 com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer24setFramebufferPowerStateEj + 0x224
0xffffff810febbcd0 : 0xffffff7f860b0b9f com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer12setAttributeEjm + 0x1ad
0xffffff810febbd20 : 0xffffff7f860b0c6a com.apple.driver.AppleIntelICLLPGraphicsFramebuffer : __ZN21AppleIntelFramebuffer12setAttributeEjm + 0x278
0xffffff810febbd70 : 0xffffff7f85f47faa com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer14checkPowerWorkEj + 0x280
0xffffff810febbe10 : 0xffffff7f85f47d08 com.apple.iokit.IOGraphicsFamily : __ZN14IOFBController14checkPowerWorkEj + 0x9a
0xffffff810febbe40 : 0xffffff7f85f4eaeb com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer10systemWorkEP8OSObjectP22IOInterruptEventSourcei + 0x123
0xffffff810febbee0 : 0xffffff8001c2d54d mach_kernel : __ZN22IOInterruptEventSource12checkForWorkEv + 0x17d
0xffffff810febbf30 : 0xffffff8001c2be1e mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffff810febbf70 : 0xffffff8001c2b416 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffff810febbfa0 : 0xffffff80014c013e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7f85f3d000->0xffffff7f85f8dfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f81f12000
         com.apple.driver.AppleIntelICLLPGraphicsFramebuffer(14.0.7)[18868C3D-C807-3435-BBD6-D95A2F4D2FA7]@0xffffff7f86084000->0xffffff7f86321fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[DF219CC1-366A-31FC-B8ED-17C584BA2549]@0xffffff7f81f12000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f81f09000
            dependency: com.apple.iokit.IOAcceleratorFamily2(438.7.3)[9D052246-9911-3EB3-89E9-BDF771949C45]@0xffffff7f85fb6000
            dependency: com.apple.iokit.IOReportFamily(47)[8F7948CF-5C25-33F4-A687-67F8A5B7906E]@0xffffff7f81e49000
            dependency: com.apple.AppleGraphicsDeviceControl(5.2.6)[372B091D-3A52-3749-AE17-E8A5103D8DB0]@0xffffff7f8607a000
            dependency: com.apple.iokit.IOGraphicsFamily(576.1)[92A3DAC1-1745-37AC-88DE-FA87B5EB2526]@0xffffff7f85f3d000

BSD process name corresponding to current thread: kernel_task
Boot args: debug=0x100 keepsyms=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19G2021

Kernel version:
Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Kernel UUID: 1D3A0F3D-D908-397B-BD16-8F48C0823A2E
Kernel slide:     0x0000000001200000
Kernel text base: 0xffffff8001400000
__HIB  text base: 0xffffff8001300000
System model name: MacBookPro16,2 (Mac-5F9802EFE386AA28)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 486125505360


 

 

Can you share your ACPI folder and config.plist? also, which kexts are you using?

On 9/12/2020 at 10:31 AM, hrishi654 said:

@Ab2774 or @vokhotnikov were you able to fix your black screen isuue? It seems that the display works but no backlight as I can see the login screen if I use a flashlight. But the backlight starts working after approximately 5 min.

Do you have SSDT-PNLF-CFL or SSDT-PNLF? is it properly patched?

Share this post


Link to post
Share on other sites
14 minutes ago, LireMei said:

Can you share your ACPI folder and config.plist? also, which kexts are you using?

On 9/12/2020 at 3:31 PM, hrishi654 said:

Here it is.

In the folder are missings itlwm.kext and IntelBluetoothFirmware.kext, because they are too big to be uploaded

OC.zip

Edited by Paolo7297

Share this post


Link to post
Share on other sites
13 hours ago, LireMei said:

Can you share your ACPI folder and config.plist? also, which kexts are you using?

Do you have SSDT-PNLF-CFL or SSDT-PNLF? is it properly patched? 

 

Me, I do have SSDT-PNFL-CFL:

 

/*
 * Pulled from AppleLife's Intel WEG manual
 */
DefinitionBlock ("", "SSDT", 2, "DRTNIA", "PNLFCFL", 0x00000000)
{
    External (_SB.PCI0.GFX0, DeviceObj)

    Device (_SB.PCI0.GFX0.PNLF)
    {
        Name (_ADR, Zero)  // _ADR: Address
        Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID
        Name (_CID, "backlight")  // _CID: Compatible ID
        Name (_UID, 0x13)  // _UID: Unique ID
        Name (_STA, 0x0B)  // _STA: Status
    }
}

My DSDT have GFX0 device, which gets renamed into IGPU by WhateverGreen.

 

I also have the PNLF device visible in ioreg.

 

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000017c, registered, matched, active, busy 0 (67 ms), retain 9>
    | | | {
    | | |   "compatible" = <"backlight">
    | | |   "AppleBacklightAtBoot" = 70781
    | | |   "AppleMaxBrightness" = 65403
    | | |   "_UID" = "19"
    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/GFX0@20000/PNLF@0"}
    | | |   "ApplePanelRawBrightness" = 8228
    | | |   "_STA" = 11
    | | |   "_ADR" = 0
    | | |   "name" = <"APP0002">
    | | | }
    | | |

 

Share this post


Link to post
Share on other sites

I am trying to understand if the main issue is the G1 or if its a general Ice Lake issue.

 

For instance, would I be safer getting a 1065G7 than a 1035G1?

 

I am asking since I am considering an Acer Aspire 3 with the 1065G7 or an Acer Aspire 5 with the 1035G1. They are exactly the same price right now with similar specs so it would seem the 1065G7 is a better choice but I wonder if it will also make hackintoshing it easier?

Share this post


Link to post
Share on other sites
13 hours ago, hubbobubbo said:

I am trying to understand if the main issue is the G1 or if its a general Ice Lake issue.

 

For instance, would I be safer getting a 1065G7 than a 1035G1?

 

I am asking since I am considering an Acer Aspire 3 with the 1065G7 or an Acer Aspire 5 with the 1035G1. They are exactly the same price right now with similar specs so it would seem the 1065G7 is a better choice but I wonder if it will also make hackintoshing it easier?

The best option would be a 1065G7 laptop with no dedicated gpu (eg: an MX 250/MX 350 etc...).

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 miliuco
      macOS Catalina on: Gigabyte Z390 Aorus Elite motherboard + i3 9100 Coffee Lake processor + AMD Radeon RX 580 graphics card + fenvi FV-T919 WIFI and Bluetooth card + Clover r5121 + AppleALC, Lilu, VirtualSMC, XHCI-unsupported, IntelMausiEthernet, USBPorts and WhateverGreen.

      Hardware
       
      Gigabyte Z390 Aorus Elite motherboard: support for Intel 8 and 9 generation processors, Realtek ALC1220 audio, Intel I219V Ethernet, 4 PCI-E slots, 2, 3 and 3.1 USB ports, Intel Graphics 630 integrated graphics card 9th generation Intel i3 9100 processor Nox Hummer H-212 120mm CPU Fan Corsair Vengeance LPX 3200 MHz 16 GB RAM (2 x 8) AMD Radeon RX 580 8GB graphics card Wifi and Bluetooth Card Fenvi FV-T919 Mars Gaming MPII850 Power Supply (850W) Samsung EVO 860 SSD disk.
        What works well?

      Pretty much everything I've tried:
      Radeon RX 580: 3 DP ports and 1 HDMI port, output to 2 displays simultaneously Shutdown, reboot and sleep Integrated sound and HDMI sound output USB ports (2, 3 and 3.1) Enable TRIM for SSD drive AirDrop, Sidecar, etc.
        What is not working well?

      Integrated Intel UHD Graphics 630 card: see below.

      BIOS settings (version F9)

      I only write down the significant options, there are many other options that do not influence macOS and that you can configure to your liking (for example the LEDs on the board, etc.).
      XMP Profile: Auto / Profile 1 / Enabled (eXtreme Memory Profile, I use 3200 MHz memory and without this profile it works at 2600) Platform Power Management: Disabled VT-d: Disabled XHCI Hand-Off: Enabled Legacy USB Support: Enabled Network Stack: Disabled CSM: Disabled Secure Boot: Disabled Fast Boot: Disabled OS Type: Other OS Wake on LAN: Disabled Integrated Graphics: Auto Initial Display Output: PCIe 1 Slot DVMT Pre-Allocated: 256M or higher.
        EFI folder for Clover (installation USB stick / SSD disk with Catalina)

      SSDT

      Some SSDT.aml files in EFI/CLOVER/ACPI/patched.

      SSDT-DTPG.aml (helper module for SSDT)
      SSDT-EC.aml (USB power charge)
      SSDT-UIAC.aml (USB port mapping)
      SSDT-USBX.aml (USB port mapping)
      SSDT-PMC.aml got from OpenCore to have native NVRAM on Z390 mother boards
      SSDT-Z390-RP21-SLOT4-TB3HP.aml (Thunderbolt devices hot plug) it can be skipped.

      Drivers in EFI/CLOVER/drivers/UEFI

      ApfsDriverLoader.efi
      AudioDxe.efi
      DataHubDxe.efi
      FSInject.efi
      VBoxHfs.efi
      SMCHelper.efi
      OcQuirks.efi *
      OpenRuntime.efi *
      OcQuirks.plist *.

      * see OC Quirks below.

      Extensions in EFI / CLOVER / kexts / Other

      AppleALC.kext
      IntelMausi.kext
      Lilu.kext
      USBPorts.kext
      VirtualSMC.kext
      WhateverGreen.kext
      XHCI-unsupported.kext.

      NOTE 1: The USBPorts.kext extension along with 3 aml files included in patched folder (SSDT-EC.aml, SSDT-UIAC.aml y SSDT-USBX.aml) were generated by joanserramiret with the configuration of USB ports for this motherboard so that the limit defined by macOS of 15 ports is not exceeded. Leaves the system configured in this way:
      Enabled all USB2 ports that are not part of a USB3 port (1 internal for BT + 4 rear that are together + 2 on the front) Enabled the USB2 ports that are part of the 2 rear red USB3.1 ports Disabled the USB2 ports that are part of the 4 rear blue USB3 ports Enabled all USB3 ports except the internal one for USB type C connection. Summary: Rear blue ports do not recognize USB2 devices.

      NOTE 2: XHCI-unsupported.kext is required for XHC chipsets whose Device ID is not included in macOS. Depending on the USB driver of your board, it may be necessary to install some additional extension:
      8086: 8CB1 on macOS 10.11.1 or lower: XHCI-9-series.kext 8086: 8D31, 8086: A2AF, 8086: A36D, 8086: 9DED: XHCI-unsupported.kext 8086: 1E31, 8086: 8C31, 8086: 8CB1, 8086: 8D31, 8086: 9C31, 8086: 9CB1: FakePCIID.kext + FakePCIID_XHCIMux.kext. This board (generally Z390 chipset boards) carries the USB 3.1 controller with device ID A36D so the XHCI-unsupported kext is required. You can check your device ID at
      /System/Library/Extensions/IOUSBHostFamily.kext/Contents/Plugins/AppleUSBXHCIPCI.kext/Contents/Info.plist Config.plist file

      The differential options are:

      Acpi> DSDT: change HECI to IMEI / change SAT0 to SATA
      Acpi> Fixes: FixShutdown
      Acpi> Drop OEM_DSM
      Acpi> Drop Tables> DMAR / MATS
      Acpi> SSDT> PluginType selected (Plugin Type number blank)
      Acpi> Halt Enabler / FixHeaders

      Boot> Boot Arguments> slide = 0 / darkwake = 8

      Devices> USB> Inject / FixOwnership / HighCurrent
      Devices> Audio> Inject 11

      Kernel and Kext Patches> Apple RTC and KernelXCPM selected
      Kernel and Kext Patches> KextsToPatch> Name: com.apple.driver.AppleAHCIPort / Find: 40600200 / Replace: 00000000 / Comment: SATA hot plug
      Kernel and Kext Patches> KextsToPatch> Name: com.apple.driver.AppleAHCIPort / Find: 45787465 726E616C / Replace: 496E7465 726E616C / SATA orange icons

      SMBIOS> iMac19.1

      System Parameters> Inject Kexts: Yes / Inject System ID: selected.

      Quirks > select AvoidRuntimeDefrag – DevirtualiseMmio – EnableSafeModeSlide – ForceExitBootServices – ProtectUefiServices – ProvideConsoleGopEnable – ProvideCustomSlide – SetupVirtualMap – SyncRuntimePermissions and set ProvideMaxSlide = 0. *

      Set true DevirtualiseMmio and ProtectUefiServices in OcQuirks.plist file (recommended on Z390 mother boards).

      * see OC Quirks below.

      macOS Catalina install

      There are many publications with instructions so I will only comment on a few specific details.
      The installation USB memory must have a GUID partition scheme so that the board's UEFI can boot from it. I have prepared the USB with the createinstallmedia method + the application "Install macOS Catalina" in the Applications folder The device is USB 3 and, connected to the front USB 3 port, it performs the task quite quickly I have used Clover r5121 which is currently the latest version. The EFI folder of the installation USB can be the same as that of the hard disk with 2 differences: Acpi> SSDT> PluginType deselected and Acpi> Boot leave Default Boot Volume blank and Timeout -1 (so that no volume will boot automatically from the Clover menu). To mount the EFI partition (of the disk or the USB device) I have used Clover Configurator which makes this task very simple or the command line (diskutil), first finding out what disk and partition number is the EFI (diskutil list) and showing it later (mountdisk):
      sudo diskutil list
      sudo diskutil mountdisk / dev / disk2s3  
      RX 580

      Although my RX 580 card is a model from the XFX brand, known for using custom VBios and giving problems in macOS, in my case it seems to work well with Lilu and WhatEverGreen. Booting the operating system it does not show artifacts, the 3 DP ports and the only HDMI port work, you can send the image simultaneously to 2 screens (I have not tried more) with the usual duplication options, yo can send sound in addition to image to one TV by HDMI, during the installation of the operating system it works correctly provided that Lilu and WhatEverGreen are in the USB device, etc. GeekBench 5 Scores: Metal 50100 / OpenCL 44100. As a comparison, the integrated card does not reach 4800 in Metal.
      Regarding the hardware decoding of H264 and HEVC videos, the Hackintool tool and the VideoProc application report that it is not supported although the playback of files of both types with rates of up to 20 mbps is correct so I suspect that it actually encodes well. In order for hardware decoding to appear as supported in the commented applications, the integrated Intel Graphics 630 card must be enabled even if it is disconnected in headless mode (using the RX 580 card as primary sending image to the screen).
       


      Sound

      This board incorporates the Realtek ALC1220 chip that needs the AppleALC extension to work. AppleALC is a Lilu plugin so both must be properly installed.
      Note: Clover > Devices > Audio > Inject 11 or 13 or 15. I’ve tried several layouts and this are the only valid at least in my case.
      Some users have commented that the system does not load AppleALC and they have no sound despite having the extensions in EFI / CLOVER / kexts / Other. In these cases it can be successful to install AppleALC and Lilu in / Library / Extensions and rebuild the extensions cache with Hackintool (a very convenient way to do it) or with this Terminal command:
      sudo spctl --master-disable; sudo mount -uw /; killall Finder; sudo chown -v -R root: wheel / System / Library / Extensions; sudo touch / System / Library / Extensions; sudo chmod -v -R 755 / Library / Extensions; sudo chown -v -R root: wheel / Library / Extensions; sudo touch / Library / Extensions; sudo kextcache -i /  
      What this command does is disable Gatekeeper, mount the system disk in read / write mode, repair permissions on the extensions folders and rebuild the cache. But all of that is done by Hackintool with less work on our part.

      Ethernet

      This board carries the Intel I219V chip that works well with the IntelMausiEthernet extension.

      Wifi & Bluetooth

      I use a Fenvi FV T-919 mini PCI-E card that carries both wifi and bluetooth chips. This card works perfectly in macOS without needing anything other than placing it on the board because it is recognized as Airport Extreme and Bluetooth Apple. Has its own article on perez987.

      Disks

      Samsung EVO 860 SSD. It is a solid state disk with references to work well in Mac. In my case it works well, with a read speed of 430 and a write speed of 250. I have tried faster SSDs but they have given problems to install Catalina, instead with the EVO 860 everything has worked perfectly.

      Integrated graphics

      Integrated Intel Graphics 630 card: we can to make it work correctly by adding some properties in Clover's Devices tab. For it to work you have to:

      - enable it on the board as primary graphics: Initial Display Output IGFX instead of PCIe 1 Slot (actually this is the final step after modifying config.plist)
      - add in config.plist: Boot> Boot Arguments> igfxonln = 1
      - apply a patch (video and audio) in config.plist: Devices> Properties. It is easier to do it from the config.plist file in text mode than from Clover Configurator. With the file open as text find the lines
      <key>Audio</key> <dict> <key>ResetHDA</key> <false/> <key>Inject</key> <integer>11</integer> </dict>  
      Immediately above of them paste this text:
      <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x1F,0x3)</key> <dict> <key>layout-id</key> <data>CwAAAA==</data> <key>model</key> <string>Cannon Lake HDMI</string> <key>hda-gfx</key> <string>onboard-2</string> <key>AAPL,slot-name</key> <string>Internal@0,31,3</string> <key>device_type</key> <string>Audio device</string> </dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>framebuffer-con0-busid</key> <data>AAAAAA==</data> <key>framebuffer-con0-type</key> <data>AAgAAA==</data> <key>framebuffer-con2-flags</key> <data>xwMAAA==</data> <key>model</key> <string>Intel UHD Graphics 630</string> <key>framebuffer-con1-busid</key> <data>AAAAAA==</data> <key>device-id</key> <data>kT4AAA==</data> <key>framebuffer-con2-type</key> <data>AAgAAA==</data> <key>framebuffer-con2-busid</key> <data>BAAAAA==</data> <key>device_type</key> <string>Display controller</string> <key>hda-gfx</key> <string>onboard-1</string> <key>framebuffer-patch-enable</key> <data>AQAAAA==</data> <key>framebuffer-con1-type</key> <data>AAgAAA==</data> <key>AAPL,slot-name</key> <string>Internal@0,2,0</string> <key>AAPL,ig-platform-id</key> <data>BwCbPg==</data> <key>framebuffer-con2-enable</key> <data>AQAAAA==</data> <key>framebuffer-con1-enable</key> <data>AQAAAA==</data> <key>framebuffer-con0-enable</key> <data>AQAAAA==</data> </dict> </dict> But the system crashes when comes out of sleep mode (the PC restarts after a few seconds of leaving sleep mode). This behavior occurs if the cable that comes out from the HDMI port on the motherboard (the only existing connector on this Mobo) plugs in a DisplayPort port on the monitor; if it plugs directly into another HDMI port (monitor or TV) the bug does not occurs and the PC goes in and out of sleep normally.

      Currently the only way to have the graphics card connected to a port other than HDMI without this crash is by replacing the "hda-gfx" property with "no-hda-gfx" in the above code of config.plist. The 2 lines
      <key>hda-gfx</key> <string>onboard-2</string> must be replaced by
      <key>No-hda-gfx</key> <data>AAAAAAAAAAA=</data> After adding this property, you will no longer have sound over HDMI / DP but sleep works very well.

      In summary:
      - Intel HDMI to DisplayPort monitor> has HDMI audio output but has kernel panic when coming from sleep
      - Intel HDMI to HDMI TV> has HDMI audio output and sleep works fine
      - Intel HDMI to DisplayPort monitor with "no-hda-gfx"> sleep works fine but HDMI audio output is lost.

      (based on the post "[GUIDE] General Framebuffer Patching Guide (HDMI Black Screen Problem)" by CaseySJ; thanks also to deeveedee for his help).

      This card can be left activated without connection to the monitor (headless mode) and apparently does not show any interference with the rest of the system.

      With the integrated card as the main card, the system shows enabled both graphics cards and allows to have a screen connected to the Intel 630 via HDMI and a different screen connected to the RX 580 via DP or HDMI, in this case the primary screen is that from the Intel and the other only works when the graphics driver is loaded but, once the system is up and running, the screens allow duplication options as if they depend on a single card.
       
       
       
       
       
      Evolution to Oc Quirks

      OC Quirks is an EFI driver for Clover that replaces AptioMemoryFix and all OsxAptioFix variants. It supports the OpenCore quirks model. AptioMemoryFix has evolved little in the most recent stage and is in a way becoming obsolete. Next versions of Clover will probably stop installing AptioMemoryFix and switch to OC Quirks which is evolving and receiving frequent improvements. You can read about this on the working group website: ReddestDream.

      Migrating our installation from AptioMemoryFix to OC Quirks is relatively simple:
      download the latest version of OC Quirks (search Releases, current version is 23) have a USB device that boots up properly to use in case of failure mount the disk's EFI partition delete AptioMemoryFix and any other OsxAptioFix variant add OcQuirks.efi, OpenRuntime.efi and OcQuirks.plist to Clover's drivers/UEFI folder change to true DevirtualiseMmio and ProtectUefiServices in the file OcQuirks.plist (recommended on boards with Z390 chipset) in Clover> Quirks config.plist file, check the boxes AvoidRuntimeDefrag - DevirtualiseMmio - EnableSafeModeSlide - ForceExitBootServices - ProtectUefiServices - ProvideConsoleGopEnable - ProvideCustomSlide - SetupVirtualMap - SyncRuntimePermissions and assign the value 0 to ProvideMaxSlide Restart the PC.  
      Kernel Panic with BIOS F10c if integrated graphics is enabled

      The Z390 Aorus Elite board comes with BIOS F9 with which the text of this post has been written.

      A few days ago I updated to the current version which is F10c and, since then, I have suffered a kernel panic with the forbidden symbol when going from the Clover menu to the macOS boot screen if the integrated card was enabled in BIOS. This happened regardless of whether the Intel UHD Graphics 630 card was set to Clover (fully for monitor output or headless mode for encoding) or not.

      Returning to BIOS F9 the system has returned to working as before and the kernel panic has disappeared. I can have the card enabled or disabled again in BIOS without problems.
       
      efi-quirks.zip
    • By Sudo User
      Model: Dell XPS 9300
      CPU: Intel Core i7-1065g7
      Video: Intel Iris Plus G7
      Screen: UHD+
      Memory: 16GB DDR4
       
      I think i have tried all of the AAPL,ig-platform-ids on the WhateverGreen manual.
      Can't get it to work and i think i have some special case since it's a dell laptop i`m dealing with.
      Here is a pic of where i am stuck.

       
      Here is the a link to my current EFI
      https://www.dropbox.com/sh/bessnr9pmx14asv/AACiigB6ldp-Ebvxx1oxQfnja?dl=0
    • 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 or 02.12.00 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 OcQuirks (replaces 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 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) r5122 Lilu.kext 1.4.7 WhateverGreen.kext 1.4.2 AppleALC.kext 1.5.2 IntelMausi.kext 1.0.3 (acidanthera version, not IntelMausiEthernet) NVMeFix.kext 1.0.3 EFIChecikDisabler.kext 0.5  
      Credits To be provided
       
      ScreenShots
       
       
      HP EliteDesk 800 G4 Mini BIOS Configuration.pdf
      EliteDesk800 G4 Mini - Rev 1.2.zip
    • By Forzenny
      Hi there,
       
      I managed to install Mojave on my MSI GP62-6QE laptop with somewhat success. The only annoying thing left is that everytime I shut it down it seemingly kernel panics and I get the "Your computer has restarted because of a problem" at startup.
       
      I tried many different things such as removing emuvariablesuefi64, checking FixShutdown in CloverConfig but it seems the NVRAM is causing this issue.
       
      I have deleted the nvram file from the EFI partition but it seems stuck somewhere else, I can't clear out the nvram from the terminal or in single user mode as it returns a "Not permitted" error.
      Clearing out the nvram by pressing F11 at the boot menu screen works however.
      crashlog.rtf
    • By IvanOnMac51
      Help!!!
       
      I was running my MacPro 5,1 happily with GeForce GTX 970 with the n-1'th versions of nvidia web driver / High Sierra for several months, when suddenly, yesterday, whilst using zoom (vidconf), system reboots with kernel panic. So,
       
      1. I tested GPU RAM and main RAM using Tech Tool Pro, all fine.
      2. I swapped in the original graphics card so I could ..
      3. install latest High Sierra (17G14019) (I had been holding off for several weeks until an nvidia update became available, you know the drill...)
      4. install latest nvidia web driver (387.10.10.10.40.138)
      5. reboot and run Heaven graphics test
       
      Heaven ran for a few minutes before the kernel panic rebooted the system (attached kernel panic report).
      I managed to get "chat" support from nVidia but the tech was useless, saying there were no drivers for GTX 9series for mac (which actually he seems to be right, as I can't find it listed in the supported cards on their website, but then I and many others have been happily using this for years...).
       
      Any ideas? The computer keeps crashing with the same kernel panic. I want to keep using my GTX 970 as the stock GPU is deadly slow on any kind of games :-(
       
      Thanks in advance for your help!
      error log.pdf
×