Jump to content
85 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.

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.

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


 

 

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?

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
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">
    | | | }
    | | |

 

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?

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

  • Allan pinned and featured this topic
On 9/12/2020 at 8: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.

I was experiencing the same issue. My screen wasn't completely black but extremely dim (essentially my brightness slider was at minimum). Screen would go normal brightness after ~4-5 minutes. The issue was an incorrect SSDT-PNLFCFL.aml. I followed the instructions here to find that my ACPI path was PCI0.GFX0. But the SSDT I had downloaded was for PCI0.IGPU. I compiled the sample SSDT given on this site and put in my ACPI folder and the back lighting issue was solved. Here is the correct SSDT for the GFX0. I have a Dell 5593, non-touch 1080P display with 1035G1.

SSDT-PNLFCFL.aml

 

EDIT: Well that lasted about a day. Now it has reverted to being dim for the first 4 minutes. Occasionally it will be fine from the start. No changes being made, just rebooting...

Edited by bmwhitetx
Updated info
On 10/4/2020 at 7:31 AM, bmwhitetx said:

EDIT: Well that lasted about a day. Now it has reverted to being dim for the first 4 minutes. Occasionally it will be fine from the start. No changes being made, just rebooting...

Yeah exactly. Dont know when or if we will get a fix for it.

  • 2 weeks later...
On 10/15/2020 at 9:23 PM, fREefRaNk said:

I'm on a hp x360 spectre aw0023dx, 1065g7 with 4k oled screen.

tried 528A and all other device id, no acceleration. 

with 

<string>-v alcid=3 -igfxcdc -igfxdvmt -cdfon</string>

it wont boot into system, just reboot on iGPU setting up. 

But I can see 3D rendering log in the bootlog.

Any suggestions?

config.plist

 

Your config.plist is invalid (no value for the ACPI/Add/Comment key), Xcode refuses to open it at all.

  • 2 weeks later...
On 9/14/2020 at 8:03 PM, Paolo7297 said:

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

 


For those who have problem with sleep (wake is not working at all, only reboot will help and also got panics about DC9/DC6 - here is the solution: https://github.com/acidanthera/bugtracker/issues/1207

 

Try to use bootargs -noDC9 or -nodisplaysleepDC6 (in my case -noDC9 worked well, so i didn't test the second one, but i saw guy, who have used the second one too and it's worked as well as first one)

 

Edited by b0ltun
On 10/26/2020 at 3:33 PM, b0ltun said:


For those who have problem with sleep (wake is not working at all, only reboot will help and also got panics about DC9/DC6 - here is the solution: https://github.com/acidanthera/bugtracker/issues/1207

 

Try to use bootargs -noDC9 or -nodisplaysleepDC6 (in my case -noDC9 worked well, so i didn't test the second one, but i saw guy, who have used the second one too and it's worked as well as first one)

 

Thanks! Now KPs are gone, but when it goes to sleep, it wake up immediately, without backlight...

23 hours ago, Paolo7297 said:

Thanks! Now KPs are gone, but when it goes to sleep, it wake up immediately, without backlight...

 

Make sure that your usb mapped correctly, plus that's might be usb mouse wake-up

 

Btw, i don't no if that method working correctly on G1 graphics, because afaik you have problem with brightness glitches. So that's might be the problem.

 

If you have G4/G7 graphics - you can try to test it with other framebuffers. Default one for Ice Lake which is mentioned in Dortania docs is not working properly for sleep/wake, it's unstable. 

 

On 10/1/2020 at 2:43 PM, cakehonolulu said:

Patching seems broken on Big Sur!

CD Clock Panic again!

initCDClockEv related

i have no problem with Big Sur beta 10. Working as well as Catalina.

 

UPDATE: 

Got the glitch of Apple logo to disappear after half of progress bar is done - after update to Big Sur 11,0,1 beta that's seems to be fixed. Now Apple logo not disappearing until progress bar fully loaded, after that i got black screen for 5-7 seconds and login screen appear. that's might be still strange, but something changed, heh

Edited by b0ltun
add
On 10/28/2020 at 3:27 PM, b0ltun said:

Make sure that your usb mapped correctly, plus that's might be usb mouse wake-up

 

Btw, i don't no if that method working correctly on G1 graphics, because afaik you have problem with brightness glitches. So that's might be the problem.

 

If you have G4/G7 graphics - you can try to test it with other framebuffers. Default one for Ice Lake which is mentioned in Dortania docs is not working properly for sleep/wake, it's unstable. 

I have G7, i'll try to change others...

About USB map, i haven't find how to do correctly, with USBInjectAll type c port didn't worked well... And i haven't usb mouse...

 

EDIT: About the after-sleep issue: I have a completely black screen

Edited by Paolo7297
9 hours ago, Paolo7297 said:

EDIT: About the after-sleep issue: I have a completely black screen

told you. i have the same issue if i use "default" framebuffer from Dortania guides. just change it, until you find one which is working okay for you. 

Hi Guys,
I need your support for correct brightness.

 

I use the ID 538A0000 under i7-1065G7 (Lenovo S340-15IIL IceLake with MacBookPro16,2 Smbios)
SSDT-ALS0.aml in use = ambient light works.
SSDT-PNLFCFL.aml (_SB.PCI0.GFX0.PNLF) in use = PNLF works.
USB is patched = works.
with bootargs -noDC9, sleep also works to.
Nvram works, also retains the brightness level that was set last.

 

well, on windows it's much brighter.

 

when i starting MacOS shortly before IGPU initializes it dims a little, which is also the maximum brightness of the screen.
I can control with the buttons minimal and maximal, no problems.
when I go to sleep and wake up it is suddenly much brighter, like on windows.
Otherwise I couldn't find any negative symptoms.

How can I achieve that it has the same brightness level as windows without sleep and wake?
Can someone help me with this?

 

Thanks and greetings Coban

Bildschirmfoto 2020-11-04 um 23.36.57.png

Bildschirmfoto 2020-11-04 um 23.37.06.png

On 10/30/2020 at 5:13 PM, b0ltun said:

 

0x8A5C0002

 

I am still testing others, there maybe any other good too.

Using this ig-platform make my cursor issue come back and vram drop from 3gb to 1.5gb. previously i've been fix the issue by set stolenmem and unifiedmem but doesn't work with this ig-platform. 

 

Did you get this issue on your device?

×
×
  • Create New...