<< Solved >> HDMI not working on Intel UHD Graphics 620 on Whiskey Lake CPU

[thanhdz167]

you didn't do the boot arguments suggestions

Sorry for the delay, I try the boot argument, my computer is still stuck in the debug command line screen.

 

[thanhdz167]

What should I do now?

 

[thanhdz167]

I have also tried combining these boot arguments together, and the result is that even though I have debug mode enabled, my computer immediately restarts afterwards. Here is my kernel panic info:

panic(cpu 0 caller 0xffffff8011bc4996): Kernel trap at 0xffffff7fab616cda, type 0=divide error, registers:
CR0: 0x000000008001003b, CR2: 0x00007fff80951b08, CR3: 0x000000014223b051, CR4: 0x00000000003626e0
RAX: 0x006d51d700000000, RBX: 0x006d51d700000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffffa06ac6b2f0, RBP: 0xffffffa06ac6b320, RSI: 0xffffffa06ac6b118, RDI: 0xffffff80128ac930
R8: 0x00000005f50c1e2d, R9: 0x0000020000011000, R10: 0x0000000000000001, R11: 0x0200000010000550
R12: 0x00000000091c2740, R13: 0x0000000000000000, R14: 0xffffffa06ac6b340, R15: 0x0000000009a7ec80
RFL: 0x0000000000010246, RIP: 0xffffff7fab616cda, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007fff80951b08, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xffffffa06ac6ad10 : 0xffffff8011a8cfdd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa06ac6ad60 : 0xffffff8011bd3fd3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa06ac6ada0 : 0xffffff8011bc45ca mach_kernel : _kernel_trap + 0x55a
0xffffffa06ac6adf0 : 0xffffff8011a31a2f mach_kernel : _return_from_trap + 0xff
0xffffffa06ac6ae10 : 0xffffff8011a8c7fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa06ac6af30 : 0xffffff8011a8caf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa06ac6afa0 : 0xffffff801229cdca mach_kernel : _panic + 0x54
0xffffffa06ac6b010 : 0xffffff8011bc4996 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa06ac6b190 : 0xffffff8011bc467d mach_kernel : _kernel_trap + 0x60d
0xffffffa06ac6b1e0 : 0xffffff8011a31a2f mach_kernel : _return_from_trap + 0xff
0xffffffa06ac6b200 : 0xffffff7fab616cda com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController14SetupDPTimingsEP21AppleIntelFramebufferP21AppleIntelDisplayPathPNS_10CRTCParamsE + 0xec
0xffffffa06ac6b320 : 0xffffff7fab614577 com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController9hwSetModeEP21AppleIntelFramebufferP21AppleIntelDisplayPathPK29IODetailedTimingInformationV2 + 0x263
0xffffffa06ac6b7a0 : 0xffffff7fab5e9621 com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN21AppleIntelFramebuffer14setDisplayModeEii + 0xf59
0xffffffa06ac6b960 : 0xffffff7fac952b69 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer16doSetDisplayModeEii + 0x12b
0xffffffa06ac6b9f0 : 0xffffff7fac9529c6 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer17extSetDisplayModeEP8OSObjectPvP25IOExternalMethodArguments + 0x9a
0xffffffa06ac6ba80 : 0xffffff801221d67e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffa06ac6bad0 : 0xffffff7fac95933c com.apple.iokit.IOGraphicsFamily : __ZN23IOFramebufferUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x82
0xffffffa06ac6bb20 : 0xffffff801222792b mach_kernel : _is_io_connect_method + 0x35b
0xffffffa06ac6bc80 : 0xffffff8011b7f7d1 mach_kernel : _iokit_server_routine + 0x4dd1
0xffffffa06ac6bd90 : 0xffffff8011a9265d mach_kernel : _ipc_kobject_server + 0x2fd
0xffffffa06ac6be00 : 0xffffff8011a68cd5 mach_kernel : _ipc_kmsg_send + 0x115
0xffffffa06ac6be60 : 0xffffff8011a801e2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffa06ac6bef0 : 0xffffff8011ba869d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa06ac6bfa0 : 0xffffff8011a32216 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(585.1)[240F08CD-4BC4-3093-8832-0E899EFC14F4]@0xffffff7fac935000->0xffffff7fac963fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[4E85D41F-6AD7-3C24-911C-A8B80B599F86]@0xffffff801456c000->0xffffff8014594fff
com.apple.driver.AppleIntelCFLGraphicsFramebuffer(16.0.5)[CF6362CE-7FA2-30FC-A3E1-8ED521D20B58]@0xffffff7fab5cc000->0xffffff7fab68cfff
dependency: com.apple.AppleGraphicsDeviceControl(6.3.5)[FB94A956-9AB7-3783-B7B9-5B126328606C]@0xffffff7fab150000->0xffffff7fab153fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[59A305C2-E322-3EA6-B8DB-475512053CDE]@0xffffff8014044000->0xffffff8014045fff
dependency: com.apple.iokit.IOAcceleratorFamily2(442.9)[065DAA9E-DE99-3C6D-A8D6-06BFD26CA1DC]@0xffffff7fac7b4000->0xffffff7fac81efff
dependency: com.apple.iokit.IOGraphicsFamily(585.1)[240F08CD-4BC4-3093-8832-0E899EFC14F4]@0xffffff7fac935000->0xffffff7fac963fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[4E85D41F-6AD7-3C24-911C-A8B80B599F86]@0xffffff801456c000->0xffffff8014594fff
dependency: com.apple.iokit.IOReportFamily(47)[77F098F2-012A-32EF-BD19-8A0E7ADF46E9]@0xffffff80145a3000->0xffffff80145a5fff

Process name corresponding to current thread: WindowServer
Boot args: -v -cdfon -igfxmlr -igfxmpc agdpmod=vit9696 igfxonln=1 keepsyms=1 debug=0x100 alcid=66 vsmcgen=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20G165

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
KernelCache slide: 0x0000000011800000
KernelCache base: 0xffffff8011a00000
Kernel slide: 0x0000000011810000
Kernel text base: 0xffffff8011a10000
__HIB text base: 0xffffff8011900000
System model name: MacBookPro15,2 (Mac-827FB448E656EC26)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 25586738137
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000005f516a68e
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000014607f72dc 0x0000000000000000

Luckily, I had the trail markers I went through, so I was able to boot into macOS and get the kernel panic info.

 

[Feartech]

I have also tried combining these boot arguments together, and the result is that even though I have debug mode enabled, my computer immediately restarts afterwards. Here is my kernel panic info:

panic(cpu 0 caller 0xffffff8011bc4996): Kernel trap at 0xffffff7fab616cda, type 0=divide error, registers:
CR0: 0x000000008001003b, CR2: 0x00007fff80951b08, CR3: 0x000000014223b051, CR4: 0x00000000003626e0
RAX: 0x006d51d700000000, RBX: 0x006d51d700000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffffa06ac6b2f0, RBP: 0xffffffa06ac6b320, RSI: 0xffffffa06ac6b118, RDI: 0xffffff80128ac930
R8: 0x00000005f50c1e2d, R9: 0x0000020000011000, R10: 0x0000000000000001, R11: 0x0200000010000550
R12: 0x00000000091c2740, R13: 0x0000000000000000, R14: 0xffffffa06ac6b340, R15: 0x0000000009a7ec80
RFL: 0x0000000000010246, RIP: 0xffffff7fab616cda, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007fff80951b08, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xffffffa06ac6ad10 : 0xffffff8011a8cfdd mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa06ac6ad60 : 0xffffff8011bd3fd3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa06ac6ada0 : 0xffffff8011bc45ca mach_kernel : _kernel_trap + 0x55a
0xffffffa06ac6adf0 : 0xffffff8011a31a2f mach_kernel : _return_from_trap + 0xff
0xffffffa06ac6ae10 : 0xffffff8011a8c7fd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa06ac6af30 : 0xffffff8011a8caf3 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa06ac6afa0 : 0xffffff801229cdca mach_kernel : _panic + 0x54
0xffffffa06ac6b010 : 0xffffff8011bc4996 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa06ac6b190 : 0xffffff8011bc467d mach_kernel : _kernel_trap + 0x60d
0xffffffa06ac6b1e0 : 0xffffff8011a31a2f mach_kernel : _return_from_trap + 0xff
0xffffffa06ac6b200 : 0xffffff7fab616cda com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController14SetupDPTimingsEP21AppleIntelFramebufferP21AppleIntelDisplayPathPNS_10CRTCParamsE + 0xec
0xffffffa06ac6b320 : 0xffffff7fab614577 com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN31AppleIntelFramebufferController9hwSetModeEP21AppleIntelFramebufferP21AppleIntelDisplayPathPK29IODetailedTimingInformationV2 + 0x263
0xffffffa06ac6b7a0 : 0xffffff7fab5e9621 com.apple.driver.AppleIntelCFLGraphicsFramebuffer : __ZN21AppleIntelFramebuffer14setDisplayModeEii + 0xf59
0xffffffa06ac6b960 : 0xffffff7fac952b69 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer16doSetDisplayModeEii + 0x12b
0xffffffa06ac6b9f0 : 0xffffff7fac9529c6 com.apple.iokit.IOGraphicsFamily : __ZN13IOFramebuffer17extSetDisplayModeEP8OSObjectPvP25IOExternalMethodArguments + 0x9a
0xffffffa06ac6ba80 : 0xffffff801221d67e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffa06ac6bad0 : 0xffffff7fac95933c com.apple.iokit.IOGraphicsFamily : __ZN23IOFramebufferUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x82
0xffffffa06ac6bb20 : 0xffffff801222792b mach_kernel : _is_io_connect_method + 0x35b
0xffffffa06ac6bc80 : 0xffffff8011b7f7d1 mach_kernel : _iokit_server_routine + 0x4dd1
0xffffffa06ac6bd90 : 0xffffff8011a9265d mach_kernel : _ipc_kobject_server + 0x2fd
0xffffffa06ac6be00 : 0xffffff8011a68cd5 mach_kernel : _ipc_kmsg_send + 0x115
0xffffffa06ac6be60 : 0xffffff8011a801e2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffa06ac6bef0 : 0xffffff8011ba869d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa06ac6bfa0 : 0xffffff8011a32216 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.iokit.IOGraphicsFamily(585.1)[240F08CD-4BC4-3093-8832-0E899EFC14F4]@0xffffff7fac935000->0xffffff7fac963fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[4E85D41F-6AD7-3C24-911C-A8B80B599F86]@0xffffff801456c000->0xffffff8014594fff
com.apple.driver.AppleIntelCFLGraphicsFramebuffer(16.0.5)[CF6362CE-7FA2-30FC-A3E1-8ED521D20B58]@0xffffff7fab5cc000->0xffffff7fab68cfff
dependency: com.apple.AppleGraphicsDeviceControl(6.3.5)[FB94A956-9AB7-3783-B7B9-5B126328606C]@0xffffff7fab150000->0xffffff7fab153fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[59A305C2-E322-3EA6-B8DB-475512053CDE]@0xffffff8014044000->0xffffff8014045fff
dependency: com.apple.iokit.IOAcceleratorFamily2(442.9)[065DAA9E-DE99-3C6D-A8D6-06BFD26CA1DC]@0xffffff7fac7b4000->0xffffff7fac81efff
dependency: com.apple.iokit.IOGraphicsFamily(585.1)[240F08CD-4BC4-3093-8832-0E899EFC14F4]@0xffffff7fac935000->0xffffff7fac963fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[4E85D41F-6AD7-3C24-911C-A8B80B599F86]@0xffffff801456c000->0xffffff8014594fff
dependency: com.apple.iokit.IOReportFamily(47)[77F098F2-012A-32EF-BD19-8A0E7ADF46E9]@0xffffff80145a3000->0xffffff80145a5fff

Process name corresponding to current thread: WindowServer
Boot args: -v -cdfon -igfxmlr -igfxmpc agdpmod=vit9696 igfxonln=1 keepsyms=1 debug=0x100 alcid=66 vsmcgen=1 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20G165

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
KernelCache slide: 0x0000000011800000
KernelCache base: 0xffffff8011a00000
Kernel slide: 0x0000000011810000
Kernel text base: 0xffffff8011a10000
__HIB text base: 0xffffff8011900000
System model name: MacBookPro15,2 (Mac-827FB448E656EC26)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 25586738137
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000005f516a68e
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000014607f72dc 0x0000000000000000

Luckily, I had the trail markers I went through, so I was able to boot into macOS and get the kernel panic info.

remove:
agdpmod=vit9696 vsmcgen=1 -igfxmlr -igfxmpc

 

[thanhdz167]

remove:
agdpmod=vit9696 vsmcgen=1 -igfxmlr -igfxmpc

No difference and my computer keeps hanging at the debug screen

 

[Feartech]

No difference and my computer keeps hanging at the debug screen

best you read up on:
https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md

more info here:

An iDiot's Guide To Lilu and its Plug-ins

An iDiot's Guide To Lilu and its Plug-in's Last Update: 22nd Jan 2021 (Add note about OpenCore config.plist modifications) About this Guide Note: This guide was written when Clover was the boot loader of choice as such the config.plist examples in this guide are mostley Clover specific ... if...

www.tonymacx86.com

 

[thanhdz167]

Okay, I tried and nothing else. Still the built-in screen flickers when HDMI is plugged in

However when I follow the instructions to dump the kernel log, it seems that the HDMI port is configured correctly, as the kernel log shows a difference when I try plugging and unplugging the HDMI cable. This is what I get in the kernel log when I plug in and unplug the HDMI cable both times, with the Log.rtf file being the first attempt I plug and unplug the HDMI the first time and with the Log2.rtf file the first attempt. second i plug and unplug the HDMI cable.

However, the Log.rtf log was longer, because I tried to log the logs later, when I finished the first attempt and let it settle for 5 seconds.

FIle Log2.rtf is the second file, in which I only log the event when the HDMI cable is plugged in on the second attempt

The Log4.rtf file is an additional file in which I log events after the HDMI cable is plugged in, including the HDMI cable unplugged, and subsequent events related to the graphics cards and the iGPU.

Hope it will be useful for this.

 

[thanhdz167]

Okay, I tried and nothing else. Still the built-in screen flickers when HDMI is plugged in

However when I follow the instructions to dump the kernel log, it seems that the HDMI port is configured correctly, as the kernel log shows a difference when I try plugging and unplugging the HDMI cable. This is what I get in the kernel log when I plug in and unplug the HDMI cable both times, with the Log.rtf file being the first attempt I plug and unplug the HDMI the first time and with the Log2.rtf file the first attempt. second i plug and unplug the HDMI cable.

However, the Log.rtf log was longer, because I tried to log the logs later, when I finished the first attempt and let it settle for 5 seconds.

FIle Log2.rtf is the second file, in which I only log the event when the HDMI cable is plugged in on the second attempt

The Log4.rtf file is an additional file in which I log events after the HDMI cable is plugged in, including the HDMI cable unplugged, and subsequent events related to the graphics cards and the iGPU.

Hope it will be useful for this.

More info: After a long day of searching, I finally discovered something more

First, I added to my IGPU, in DeviceProperties an entry named framebuffer-con1-preffered-lspcon-mode and framebuffer-con2-preffered-lspcon-mode and set them all to the value 00000000

Next, I add boot arguments -igfxdump and -igfxfbdump and reboot

At this point, I go to IORegistryExplorer, search for AppleIntelFramebuffer, it comes up with AppleIntelFramebuffer@0, AppleIntelFramebuffer@1 and AppleIntelFramebuffer@2. This is also when I discovered something

When looking at the value of fw-framebuffer-preffered-lspcon-mode, I noticed that at AppleIntelFramebuffer@0 it has a value of 0x1, and for AppleIntelFramebuffer@1 and AppleIntelFramebuffer@2, it is 0x0 (you can see that pictures that I attached)

Through this, I also surmised that con0 would most likely be the port I needed, however that guess was wrong because it seems that my built-in monitor was taking up the con0 port.

I've also tried going into Hackintool and trying other Intel Generations with other Platform IDs, some of which are weird: When I try going to Platform ID where the numbers in the table are: Index=0, BusID=0x0, Pipe =0, Type=Dummy, Flags=0x00000040 then all ports are green i.e. Internal?

At that time, I also tried unplugging the HDMI cable and plugging it back in, the built-in screen was still flickering and the kernel log was still the error attached to the Log.zip file in the post I was replying to. But the second screen is nothing but a black one.

And then I also read an article (Link: https://www.tonymacx86.com/threads/troubles-running-my-vga-monitor-via-hdmi-adapter-on-my-z77-ds3h.94341/). I am also using an HDMI to VGA converter with my monitor a Samsung SyncMaster SA300. However what I don't understand is how and why to fix this annoying error.

All files I will attach below

Hope someone will help me.

 

[Feartech]

More info: After a long day of searching, I finally discovered something more

First, I added to my IGPU, in DeviceProperties an entry named framebuffer-con1-preffered-lspcon-mode and framebuffer-con2-preffered-lspcon-mode and set them all to the value 00000000

Next, I add boot arguments -igfxdump and -igfxfbdump and reboot

At this point, I go to IORegistryExplorer, search for AppleIntelFramebuffer, it comes up with AppleIntelFramebuffer@0, AppleIntelFramebuffer@1 and AppleIntelFramebuffer@2. This is also when I discovered something

When looking at the value of fw-framebuffer-preffered-lspcon-mode, I noticed that at AppleIntelFramebuffer@0 it has a value of 0x1, and for AppleIntelFramebuffer@1 and AppleIntelFramebuffer@2, it is 0x0 (you can see that pictures that I attached)

Through this, I also surmised that con0 would most likely be the port I needed, however that guess was wrong because it seems that my built-in monitor was taking up the con0 port.

I've also tried going into Hackintool and trying other Intel Generations with other Platform IDs, some of which are weird: When I try going to Platform ID where the numbers in the table are: Index=0, BusID=0x0, Pipe =0, Type=Dummy, Flags=0x00000040 then all ports are green i.e. Internal?

At that time, I also tried unplugging the HDMI cable and plugging it back in, the built-in screen was still flickering and the kernel log was still the error attached to the Log.zip file in the post I was replying to. But the second screen is nothing but a black one.

And then I also read an article (Link: https://www.tonymacx86.com/threads/troubles-running-my-vga-monitor-via-hdmi-adapter-on-my-z77-ds3h .94341/). I am also using an HDMI to VGA converter with my monitor a Samsung SyncMaster SA300. However what I don't understand is how and why to fix this annoying error.

All files I will attach below

Hope someone will help me.

didn't realise you were using an adaptor... some of those don't work

 

[thanhdz167]

didn't realise you were using an adaptor... some of those don't work

So is there a way to make my adapter work? I tried with MacBook Air Early 2015 running macOS High Sierra and it works