ziggy762

Privacy and Security in settings does not initialize properly. Icons do not display and right scrollbar does not function to give access to items. This behavior last seen in Ventura. Here is part of spindump: Date/Time: 2025-09-18 17:45:51.219 -0300 End time: 2025-09-18 17:47:01.036 -0300 OS Version: macOS 26.0 (Build 25A354) Architecture: x86_64h Report Version: 66 Data Source: Stackshots Shared Cache: 30BB8006-73D6-3EFC-8061-1346E86B262F slid base address 0x7ff809084000, slide 0x9084000 (System Primary) Shared Cache: AA04FE42-B5D5-3D6E-8EA6-591463C03340 slid base address 0x7ff82c1f3000, slide 0x2c1f3000 (DriverKit) Command: SecurityPrivacyExtension Path: /System/Library/ExtensionKit/Extensions/SecurityPrivacyExtension.appex/Contents/MacOS/SecurityPrivacyExtension Identifier: com.apple.settings.PrivacySecurity.extension Version: 1.0 (1) Build Version: 286 Project Name: SecurityPref Source Version: 621000000000000 Architecture: x86_64 Parent: launchd [1] Responsible: System Settings [902] PID: 980 Time Since Fork: 73s Duration: 69.82s Duration Sampled: 9.89s (process was unresponsive for 60 seconds before sampling) Steps: 792 (10ms sampling interval) Hardware model: MacBookPro16,2 Active cpus: 1 Memory size: 12 GB HW page size: 4096 VM page size: 4096 Shared cache residency: 22.26% (1158.89 MB / 5206.17 MB) Boot args: -v -lilubetaall cpus=1 keepsyms=1 kext-dev-mode=1 debug=0x100 -igfxsklaskbl -disablegfxfirmware -liludbgall liludump=60 Time Since Boot: 651s Time Awake Since Boot: 651s Time Since Wake: n/a (machine hasn't slept) Total CPU Time: 9.863s (25.8G cycles, 28.3G instructions, 0.91c/i) Advisory levels: Battery -> 3, User -> 2, ThermalPressure -> 0, Combined -> 2 Free disk space: 29.91 GB/62.97 GB, low space threshold 3072 MB Vnodes Available: 89.43% (176751/197632, 49905 allocated) Models: none Launchd throttled processes: locationaccessstored throttled after exit(): throttled samples 1-702, throttled samples 703-792 Preferred User Language: en-CA, en-US Country Code: CA OS Cryptex File Extents: 1 ---------------------------------------- Heavy format: stacks are sorted by count ---------------------------------------- Process: SecurityPrivacyExtension (Privacy & Security) [980] UUID: E9110013-A10A-3F94-AFA5-DDD70D17EF9E Path: /System/Library/ExtensionKit/Extensions/SecurityPrivacyExtension.appex/Contents/MacOS/SecurityPrivacyExtension Identifier: com.apple.settings.PrivacySecurity.extension Version: 1.0 (1) Build Version: 286 Project Name: SecurityPref Source Version: 621000000000000 Shared Cache: 30BB8006-73D6-3EFC-8061-1346E86B262F slid base address 0x7ff809084000, slide 0x9084000 (System Primary) Architecture: x86_64 Parent: launchd [1] Responsible: System Settings [902] RunningBoard Mgd: Yes UID: 501 Memory Limit: 1000MB Jetsam Priority: 40 Footprint: 27.47 MB Time Since Fork: 73s Num samples: 792 (1-792) CPU Time: <0.001s (1369.9K cycles, 409.1K instructions, 3.35c/i) Note: Unresponsive for 60 seconds before sampling Num threads: 4 Note: 1 idle work queue thread omitted Note: Workqueue exceeded cooperative thread limit for 792 samples (more swift tasks runnable than allowed to run concurrently) Note: Workqueue exceeded active constrained thread limit for 792 samples (more dispatch items runnable than allowed to run) Does these references indicate a programming error made by Apple? Note: Workqueue exceeded cooperative thread limit for 792 samples (more swift tasks runnable than allowed to run concurrently) Note: Workqueue exceeded active constrained thread limit for 792 samples (more dispatch items runnable than allowed to run) Is this a Swift programming error? Would appreciate any help to resolve this. Additionally, clean install does not progress past the Select Country or Region windows to complete installation. Does anyone have a fix for this. The spacebar to select fix does nothing to resolve the issue. Thank you.

All but one of the issues with Tahoe referenced here have been resolved as of beta4: https://olarila.com/applications/core/interface/file/attachment.php?id=43899&key=cc6349bcaa287f17793c5c199e120fbc The ESDT boot error message does not hang the boot but is still there. MaldOn, did I include enough information with the attachment to make a DSDT to eliminate this boot error message? Thank you.

The EFI posted to Olarila was for a Skylake laptop i5 and 520 graphics/intel wifi and realtek ethernet. If you are attempting a Sonoma install on desktop hardware I doubt my EFI would be of much help. Thank you for the reply.

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/

Better progress with beta4, trackpad, keyboard, audio and graphics. System info showing metal 3 graphics , although transition from login screen to wallpaper usually results in greenish half of desktop showing until wallpaper manually configured in system settings. This appears to a be an improvement from beta3 where only solid color background appeared to be working properly.

Thanks for the reply but virtualization was already disabled in the BIOS. I know you are busy with developer issues but I have made a new post/request for DSDT to see if it could resolve some or all of the issues related here: https://olarila.com/topic/923-dsdt-patch-requests/page/773/#replyForm Additionally, since both you and MaLdOn are contributors/moderators to Insanelymac can you tell me why my email is not accepted for signup at Insanelymac? I have been using the same company going on five years. I used to sign in to both Olarila and Insanelymac with a login name and password in both cases, one day the sign in was changed to email and password and I entered the email and password but sign in failed. Thank you.

Thank you for the DSDT patch service: Please note that the Skylake laptop MaLdOn.aml was causing a KP so I removed it from the patched directory for Clover 5162. Here is a synopsis of issues occurring with Tahoe: problem 1, method [ESDT] boot error: ACPI Error:No handler for region [RCM0] [SYSTEM CMOS] (20160930/evregion-252) ACPI Error:Region SystemCMOS (ID-5) has no handler (20160930/elfido-392) [ESDT] @00001 #002D \_SB.PCIO.LPCB.RTC.RTCM No local variables are initialized for method [ESDT] No arguments are initialized for method [ESDT] ACPI Error: Method parse/execution failed [\_SB.WMID.ESDT AE_NOT_EXIST (20160930/preparse-632) ACPI Error: Method parse/execution failed [\_SB_PCIO_LPCB_ECO_Q42 AE_NOT_EXIST (20160930/preparse-632) problem 2, trackpad/keyboard not working at Tahoe login: VoodooPS2controller with VoodooRMI/VoodooInput and VoodooSMBus working in Sonoma/Sequoia for trackpad/keyboard but trackpad/keyboard not enabled at login for Tahoe. Necessary to plug in usb mouse and keyboard. problem 3, Tahoe betas 1 through 3 KP when failing to load spoofed Skylake/Kabylake graphics. Disabling AAPL-platform-id enables boot to desktop but no graphics acceleration. Skylake/Kabylake graphics spoof working fine in Sonoma/Sequoia. It appears Tahoe is probing graphics and finding Intel Skylake device (0x19168086) and refusing to map Kabylake drivers resulting in KP.. Tahoe KP 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 problem 4, IconServiceAgent is causing high CPU usage even though I have attempted to follow the information online to revert custom icons to standard system icons. Do you have any pointers on how to resolve the high CPU usage? Thanks to Slice for the disable Vt-d for Tahoe but this virtualization was already disabled in BIOS. I had to remove all of the kexts from the "Send me" as it was over 100 MB before their removal. I have been using both FakeSMC and VirtualSMC with both Clover 5162 and Open Core 105 but encountering the same KP when attempting to load Kabylake graphics. I can boot to a non graphics accelerated desktop with both Clover/FakeSMC and Open Core/VirtualSMC by disabling the AAPL-platform-id Skylake/Kabylake graphics spoof. I don't know how much of this can be resolved with DSDL and/or associated specific .aml config files, but I certainly thank you for your expertise in resolving as many of these issue as can be resolved with DSDT/.amls. Thank you. #####-end of data-##### Send me MacBook-Pro.zip

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 #####

Tahoe beta2 booting to desktop only with clover boot arg -x for safe mode. The safe mode verbose boot shows quite a number of kexts not loading. Booting with minimum kexts for FakeSMC and associated files, lilu and weg. ACPI patched has SSDT-OLARILA-MOBILE.aml Can not use Voodoo Ps2 controller and plugins due to KP, so removed and boot proceeds. Booting Sonoma/Sequoia ok with Voodoo Ps2 controller/RMI/SMBUS and synaptics trackpad/keyboard work ok. In Tahoe beta 2 safe mode, once I am to login can plug in usb mouse and keyboard and they function. Without safe mode, laptop boots to a point shortly before login screen appears and then KPs with verbose text scrolling to a point where I cannot see any indication of what specific event triggered the KP.? Is there a specific log I can look to see if a specific kext triggered the KP?config_plist.zip Are there updates for Voodoo Ps2 controller/RMI/SMBUS that work with Tahoe? Should I post an IOreg dump? config_plist.zip