ziggy762 Posted June 26 Posted June 26 Hardware is laptop with Skylake i5 CPU/ and integrated 520 graphics Tahoe will boot to desktop in safe mode but KPs with Kaby Lake graphics even though config.plist is configured for Kaby Lake. Kernel dump appears to indicate that Tahoe is probing for GPU and finding intel 19168086 skylake and the KP results even though the config.plist is configured for Kaby Lake: AAPL,ig-platform-id 00001B59 DATA device-id 16590000 DATA <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>@0,display-dual-link</key> <integer>1</integer> <key>AAPL,ig-platform-id</key> <data>AAAbWQ==</data> <key>device-id</key> <data>FlkAAA==</data> <key>enable-hdmi20</key> <data>AQAAAA==</data> <key>framebuffer-con2-enable</key> <data>AQAAAA==</data> <key>framebuffer-con2-type</key> <data>AAgAAA==</data> <key>framebuffer-fbmem</key> <data>AACQAA==</data> <key>framebuffer-patch-enable</key> <data>AQAAAA==</data> <key>framebuffer-stolenmem</key> <data>AAAwAQ==</data> <key>hda-gfx</key> <string>onboard-1</string> <key>model</key> <string>Intel HD Graphics 520</string> </dict> Here is the kernel dump: panic(cpu 0 caller 0xffffff7fa79fb4e8): "virtual IOService *IntelAccelerator::probe(IOService *, SInt32 *): Failed to map Device ID: 0x19168086 to GPU SKU!\n" @IntelAccelerator.cpp:1178 Panicked task 0xffffff8b78409b70: 121 threads: pid 0: kernel_task Backtrace (CPU 0), panicked thread: 0xffffff8b771e0598, Frame : Return Address 0xfffffffd7f8cf9b0 : 0xffffff8012f575c1 mach_kernel : _handle_debugger_trap + 0x4e1 0xfffffffd7f8cfa00 : 0xffffff80130d19b6 mach_kernel : _kdp_i386_trap + 0x126 0xfffffffd7f8cfa40 : 0xffffff80130c0bcc mach_kernel : _kernel_trap + 0x75c 0xfffffffd7f8cfb00 : 0xffffff8012eeb971 mach_kernel : _return_from_trap + 0xc1 0xfffffffd7f8cfb20 : 0xffffff8012f578b7 mach_kernel : _DebuggerTrapWithState + 0x67 0xfffffffd7f8cfc20 : 0xffffff8012f56f15 mach_kernel : _panic_trap_to_debugger + 0x1e5 0xfffffffd7f8cfc90 : 0xffffff80137857dd mach_kernel : _panic + 0x81 0xfffffffd7f8cfd80 : 0xffffff7fa79fb4e8 com.apple.driver.AppleIntelKBLGraphics : __ZN16IntelAccelerator18stopGraphicsEngineEv.cold.1 0xfffffffd7f8cfdb0 : 0xffffff7fa797f0e7 com.apple.driver.AppleIntelKBLGraphics : __ZN16IntelAccelerator5probeEP9IOServicePi + 0x441 0xfffffffd7f8cfde0 : 0xffffff801367d7c3 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xa83 0xfffffffd7f8cfec0 : 0xffffff801367cbbb mach_kernel : __ZN9IOService14doServiceMatchEj + 0x36b 0xfffffffd7f8cff20 : 0xffffff80136804b9 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x159 0xfffffffd7f8cffa0 : 0xffffff8012eeb19e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.driver.AppleIntelKBLGraphics(24.0.1)[F9A8F009-2CB0-3500-BA49-93458634D756]@0xffffff7fa7975000->0xffffff7fa7a4cfff dependency: com.apple.iokit.IOAcceleratorFamily2(486)[8530C953-B041-3E15-8DEF-73C5D628CFA4]@0xffffff7fa7e6e000->0xffffff7fa7ed7fff dependency: com.apple.iokit.IOGraphicsFamily(599)[C442ADC7-B277-32A6-B822-5C4D231E0DAC]@0xffffff7fa7fe9000->0xffffff7fa8017fff dependency: com.apple.iokit.IOPCIFamily(2.9)[2AFB6B49-C959-3F50-865C-F3594B9CCE25]@0xffffff80154ce000->0xffffff8015520fff dependency: com.apple.iokit.IOSurface(392)[7B559D0D-47A9-3ED1-8250-5D65D6F24A27]@0xffffff801565b000->0xffffff8015686fff Process name corresponding to current thread (0xffffff8b771e0598): kernel_task Boot args: -v -lilubetaall cpus=1 keepsyms=1 kext-dev-mode=1 debug=0x100 Mac OS version: 25A5295e Kernel version: Darwin Kernel Version 25.0.0: Tue Jun 17 00:07:26 PDT 2025; root:xnu-12377.0.122.0.1~120/RELEASE_X86_64 Kernel UUID: 280D8C99-1161-3AE2-9DCD-8E7F10177B11 roots installed: 0 KernelCache slide: 0x0000000012c00000 KernelCache base: 0xffffff8012e00000 Kernel slide: 0x0000000012ce8000 Kernel text base: 0xffffff8012ee8000 __HIB text base: 0xffffff8012d00000 System model name: iMac20,1 (Mac-CFF7D910A743CAAF) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 123988104682 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000001cdf942c54 Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x0000002156ee29cc 0x0000000000000000 Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space Zone info: Zone map: 0xffffff80450af000 - 0xffffffa0450af000 . VM : 0xffffff80450af000 - 0xffffff8511d7b000 . RO : 0xffffff8511d7b000 - 0xffffff86ab71f000 . GEN0 : 0xffffff86ab71f000 - 0xffffff8b783eb000 . GEN1 : 0xffffff8b783eb000 - 0xffffff90450b7000 . GEN2 : 0xffffff90450b7000 - 0xffffff9511d83000 . GEN3 : 0xffffff9511d83000 - 0xffffff99dea4f000 . DATA : 0xffffff99dea4f000 - 0xffffffa0450af000 Metadata: 0xffffffa0450bf000 - 0xffffffa0650bf000 Bitmaps : 0xffffffa0650bf000 - 0xffffffa0674bf000 Extra : 0 - 0 ##### end of post #####
ziggy762 Posted August 1 Author Posted August 1 KP appears to not be a problem if Tahoe booting is initiated via Open Core. Reverting to Clover and rebooting, no KP. Anyone with an idea why booting with Open Core resolves the KP? The same SKL spoofed to KBL in both Open Core and Clover. https://olarila.com/topic/42850-skylake-laptop-i5 520-graphics-only-boot-tahoe-beta-2-in-safe-mode/
JerrySears Posted August 6 Posted August 6 (edited) Geometry Dash OpenCore uses more accurate macOS boot argument handling and proper ACPI injection, which makes it better aligned with Apple’s native boot process than Clover. If you want to stick with Clover, you’d need to: Verify proper ig-platform-id and device-id injection. Ensure FakePCIID or WhateverGreen is fully updated and configured. Add Clover’s quirks equivalents (harder since Clover doesn’t fully support modern OpenCore quirks). Edited August 13 by JerrySears
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now