https://olarila.com/rss/1-rss-feed.xml/The Olarila Hackintosh RSS FeedenHello, I'm currently on Tahoe Beta 9, and I want to update to the latest version using the InstallAssistant.pkg file I found online. Can I install it right away, or is there anything I need to do first? Thanks.Sat, 13 Jun 2026 13:15:42 +0000RAM: 20GB DDR4 Storage: NVMe SSD (AHCI) Bootloader: OpenCore 1.0.7 Current status macOS Tahoe boots normally Full graphics acceleration working Internal display working perfectly Wi-Fi working with BCM94360CD-based solution Bluetooth working iCloud services working HDMI output not tested / looking for confirmed reports My question Has anyone successfully enabled HDMI output on an Ice Lake UHD G1 (i3-1005G1) system? If yes, could you please share: EFI reference Framebuffer configuration DeviceProperties IORegistry screenshots GitHub repository Any HDMI-related patches I'm specifically interested in confirmed working HDMI output on UHD G1, not UHD 620, UHD 630, Comet Lake, or other generations. Thanks in advance!Fri, 12 Jun 2026 23:15:01 +0000Hi everyone, I'm new here, and I'm looking for the EFI firmware for a Lenovo Ideapad Gaming 3 15IMH05 notebook. I would really appreciate your help, as I've tried several different EFI firmwares and none of them work.Thu, 11 Jun 2026 19:02:13 +0000So I'm using an Aspire 3830th with intel i5-2410M 8.00 GB Ram 233gb storage. GRAPHICS is HD Graphics 3000, hvidia GEFORCE GT540m(nvidia dosent work on macos ) Wifi card Broadcom BCM943227MM4L audio device is Conexant CX20672 trackpad Synaptics TouchPad legacy bios no UEFI(its from 2011) so i am using https://www.mediafire.com/file/qk4ocb4bq2a7s6m/Olarila+Monterey+Legacy.raw/file So when i edit my drivers folder ( adding ps2mouse,ps2keyboard) and the the config file and the reboot it works, but when i add anything in the kexts like VoodooPS2Controller.kext,AirportBrcmFixup.kext,BrightnessKeys.kext,etc then properly edit the config file they don't work even after reset nvram, no matter how i edit the kexts,config.plist file it dosent work.Everything works in the olarila menu, but in macosrecovery, my keyboard,trackpad,wifi,etc never works. this is my first time doing a hackintosh EFI.7zTue, 09 Jun 2026 09:38:16 +0000macOS Golden Gate is the next major macOS generation, introduced as macOS 27 during WWDC 2026. This release represents an important transition point for the Mac platform, with a stronger focus on Apple Silicon, performance improvements, system responsiveness, and newer macOS technologies. For Apple Silicon users, macOS Golden Gate continues Apple’s modern architecture direction, bringing the best compatibility, performance, and long-term support to Macs powered by M-series chips. This includes better integration with Apple’s latest frameworks, improved system-level features, enhanced efficiency, and deeper optimization for Apple Silicon hardware. Intel Mac support appears to be ending with macOS Golden Gate. Early reports indicate that macOS 27 drops support for Intel-based Macs and is designed for Apple Silicon Macs only. This means that macOS Tahoe is likely the final major macOS release for supported Intel Macs, while Golden Gate starts a new Apple Silicon-only era. Because this is still a pre-release stage, compatibility may change during the beta cycle. Some features, APIs, drivers, kernel behavior, and system protections can still be adjusted by Apple before the final public release. For this reason, support for macOS Golden Gate should be considered experimental until the final version is officially released. Our tools and apps are being prepared and tested for macOS Golden Gate with priority support for Apple Silicon. Intel support will continue where possible on older macOS versions, but Golden Gate support will focus on Apple Silicon due to Apple’s platform direction. With macOS Golden Gate, Apple has officially moved macOS into an Apple Silicon-only generation. Intel Mac support has been removed entirely, meaning that the last Intel models supported by macOS Tahoe are no longer eligible for this release. This includes the MacBook Pro 16-inch 2019, MacBook Pro 13-inch 2020 with four Thunderbolt 3 ports, iMac 27-inch 2020, and Mac Pro 2019. These machines may continue to receive security updates on older macOS versions, but they are not part of the macOS Golden Gate compatibility list. Key Points macOS Golden Gate is macOS 27. Apple Silicon is the primary supported platform. Intel Mac support is expected to end with this release. Intel users should remain on macOS Tahoe or earlier supported macOS versions. Golden Gate support is currently pre-release and experimental. Final compatibility depends on Apple’s public release and final system requirements.Mon, 08 Jun 2026 19:40:39 +0000AMD VBIOS Patcher is a lightweight and secure utility created to patch AMD Radeon RX580 2048SP VBIOS ROM files for better macOS Hackintosh compatibility. The app automates the known RX580 2048SP VBIOS modification process, helping users convert compatible RX580 2048SP ROM patterns into RX580-compatible values used by macOS. This tool is designed for users who need to edit an AMD Radeon RX580 2048SP VBIOS without manually searching and replacing hexadecimal values. AMD VBIOS Patcher scans the selected .rom or .bin file, detects the required byte patterns, applies the correct RX580 2048SP to RX580 patches, verifies the PCI ROM structure, and optionally repairs the PCI Option ROM checksum after patching. Download for macOS HERE Download for Windows HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Warning: Flashing a modified VBIOS always involves risk. This application only edits and saves a new VBIOS ROM file. It does not flash your graphics card. Flashing any modified, incorrect, incompatible, or corrupted VBIOS can permanently brick your GPU or make the system unable to boot. Always keep a verified backup of your original VBIOS before flashing. Make sure the patched ROM is correct for your exact GPU model, memory type, and board revision. You are fully responsible for any VBIOS flashing procedure. Use this tool and flash any modified ROM at your own risk. Main Features AMD Radeon RX580 2048SP VBIOS patcher for macOS compatibility Supports .rom and .bin VBIOS files Automatic detection of original and already patched ROMs Applies all supported RX580 2048SP byte patches Patches both Device ID entries when present Preserves AMD/ATI Vendor ID 0x1002 Repairs PCI ROM checksum safely Creates automatic backup with SHA256 hash Generates a detailed patch report Shows patch offsets, checksum status, and ROM validation results Drag and drop support Simple Analyze and Patch workflow Available for macOS, Windows 10, and Windows 11 Windows version can be built as a standalone single .exe No telemetry, no internet connection, no driver installation, no GPU flashing What the App Does AMD VBIOS Patcher checks the AMD Radeon RX580 2048SP VBIOS and searches for the known byte patterns required for macOS compatibility. When the supported patterns are found, the app applies the correct replacements, updates the Device ID from RX580 2048SP to RX580-compatible values, and fixes the checksum of each PCI ROM image when needed. The original ROM is never overwritten automatically. A backup is created before saving the patched file, and a complete local report is generated beside the output ROM. Safety AMD VBIOS Patcher does not flash your graphics card. It only edits and saves a new VBIOS ROM file. Users must verify the patched ROM and flash it manually using their preferred external flashing tool. Always keep the original VBIOS backup before flashing any modified ROM. Flashing an incorrect or corrupted VBIOS can brick the GPU. Recommended For AMD Radeon RX580 2048SP Hackintosh users macOS users with RX580 2048SP compatibility issues Users who need to convert RX580 2048SP VBIOS to RX580-compatible Device ID Hackintosh builders who want a safer VBIOS patching workflow Users who want to avoid manual hex editing Credits Created by MaLd0n / Daniel Maldonado / Olarila. Official Hackintosh support and releases: Olarila.comMon, 08 Jun 2026 02:48:56 +0000ZeroRPMBuilder is a Windows and macOS utility designed to create ready-to-use OpenCore or Clover DeviceProperties patches for AMD RDNA2 graphics cards on Hackintosh systems. The app reads a saved AMD GPU VBIOS ROM or SPPT/PowerPlay table, applies a built-in Zero RPM or Fan 35 °C patch, and automatically generates a patched config.plist with PP_PhmSoftPowerPlayTable injected under DeviceProperties. Download for macOS HERE Download for Windows HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE ZeroRPMBuilder supports AMD RDNA2 Navi21, Navi22 and Navi23 GPUs, including: Radeon RX 6600 / RX 6600 XT Radeon RX 6650 XT Radeon RX 6700 / RX 6700 XT Radeon RX 6750 XT Radeon RX 6800 / RX 6800 XT Radeon RX 6900 XT Radeon RX 6950 XT The app includes two patch modes: ZeroRPM Pure Solution Disables Zero RPM behavior by patching the PowerPlay table so the GPU fan does not remain stopped under low-temperature conditions. Fan 35 °C Solution Keeps Zero RPM enabled but changes the fan temperature curve so the fan starts at 35 °C and stops at 30 °C, offering a safer and quieter cooling profile for many Hackintosh builds. ZeroRPMBuilder does not flash the VBIOS, does not write firmware, does not install drivers, does not generate SSDTs, and does not modify the system. It only creates OpenCore-ready files for manual use. Each ZIP includes the patched config.plist, modified PowerPlay table, backup files, report, README, and DeviceProperties snippets. ZeroRPMBuilder is ideal for Hackintosh users who want a simple and safe way to apply AMD RX 6000 series fan control patches without MorePowerTool, SSDT injection, firmware flashing, or manual hex editing. How to Use ZeroRPMBuilder Save your AMD GPU VBIOS Use GPU-Z on Windows or another trusted tool to save your AMD RX 6000 series VBIOS ROM. Supported input files: .rom .bin .reg .txt .sppt .pp_table Open ZeroRPMBuilder Launch the app on Windows or macOS. Load your VBIOS or SPPT file Click: Load VBIOS ROM / SPPT Select your saved VBIOS ROM or exported PowerPlay/SPPT file. Choose the patch mode Use one of the available buttons: Generate ZeroRPM Pure Solution This disables Zero RPM completely. Or: Generate FAN 35 °C Solution This keeps Zero RPM enabled but changes the fan behavior: Fan starts at 35 °C Fan stops at 30 °C Check the DeviceProperties path Before using the generated config.plist, confirm that the GPU DeviceProperties path is correct for your machine. RX6xxx cards must use this full path format: PciRoot(...) / Pci(...) / Pci(...) / Pci(...) / Pci(...) Example: PciRoot(0x0)/Pci(0x6,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) Get the generated files The app creates the output on your Desktop: ZeroRPM.zip ZeroRPM35.zip Each ZIP contains: config.plist ZeroRPM-Report.txt README.txt Backup/ Modified/ Snippets/ Use the generated config.plist Copy the generated config.plist to your OpenCore EFI, or copy only the generated DeviceProperties section into your current OpenCore config.plist. Reboot and test Reboot macOS and check the GPU fan behavior. Start with FAN 35 °C Solution first if you want the safer/conservative option. Important Notes ZeroRPMBuilder does not flash VBIOS, does not write firmware, does not install drivers, does not generate SSDTs, and does not modify your system. It only reads the selected file and generates OpenCore-ready files. Created by ®Daniel Maldonado – OlarilaMon, 08 Jun 2026 01:17:22 +0000Sun, 07 Jun 2026 18:57:13 +0000DMIDecode Hardware List is a modern macOS hardware information app designed to display useful system details from dmidecode in a clean, organized and searchable interface. The app reads hardware data directly on each machine and dynamically lists the detected components, making it useful for real Macs and Hackintosh systems. It helps users inspect SMBIOS, CPU, memory, BIOS, baseboard, PCI devices, GPU, network adapters, storage controllers, audio devices, USB controllers and other important hardware information. Unlike raw terminal output, DMIDecode Hardware List filters the useful data and presents it in categorized sections, making hardware inspection faster and easier. It is especially useful for Hackintosh troubleshooting, EFI creation, ACPI work, device property checks, PCI device identification and system compatibility analysis. Download: HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Key Features Modern macOS dark interface Dynamic hardware detection per machine Clean categorized hardware list Search and filter system information Detects CPU, memory, BIOS, baseboard and platform data Lists PCI devices, GPU, network, storage, audio and USB information Shows useful IDs such as vendor-id, device-id, class-code and subsystem IDs when available Helps identify Hackintosh hardware for EFI, ACPI and DeviceProperties work Includes raw dmidecode output viewer Export report to TXT Copy visible filtered data Runs locally without sending data to the internet No background service after quitting the app Hackintosh Usage DMIDecode Hardware List is useful for Hackintosh users who need to inspect hardware details quickly before creating or adjusting an EFI folder. The app can help identify real PCI devices, GPU, Ethernet, Wi-Fi, storage, USB and audio controllers exposed by macOS and IORegistry. This makes it easier to check hardware compatibility, prepare OpenCore or Clover configurations, review DeviceProperties, inspect SMBIOS data and troubleshoot missing or incorrectly detected devices. Privacy and Safety The app runs locally on macOS. It does not collect, upload, transmit or store private user data online. All hardware detection is performed locally using the bundled dmidecode tool and macOS system information exposed by the machine. Security Notice All release files are checked with VirusTotal before publication. The app is distributed clean, without adware, spyware, miners, telemetry, unwanted installers or any malicious components. Credits This app uses dmidecode as its hardware information backend. Credits and third-party notices are included in the app package. Created by MaLd0n / Daniel Maldonado / Olarila.Sun, 07 Jun 2026 18:39:53 +0000Sun, 07 Jun 2026 01:56:11 +0000BootLoaderSelector is a lightweight and fast UEFI bootloader selector designed for Hackintosh users who want to easily choose between OpenCore and Clover from the same EFI partition. It provides a clean visual interface, automatic OpenCore/Clover detection, hardware information display, timeout boot, last selected bootloader memory, and safe fallback behavior without modifying NVRAM, BootOrder, BootNext, or creating unwanted UEFI boot entries. Inspired by the original work and concept from jief666, BootLoaderSelector was created as a clean, modern and simplified project focused on speed, safety and compatibility for Hackintosh environments. Download BOOTX64-Release.zip Just replace BOOTX64.efi in EFI/BOOT folder Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE Up Arrow Hotkey Explanation BootLoaderSelector includes a silent recovery hotkey using the Up Arrow key. When Remember last selected bootloader is enabled, BootLoaderSelector automatically starts the last bootloader selected by the user on the next boot. This means that after choosing OpenCore or Clover once, the next boot can go directly to that bootloader without showing the BootLoaderSelector menu again. To open the BootLoaderSelector menu again, press or hold the Up Arrow key during the BIOS/UEFI logo screen. No warning screen is shown. The hotkey works silently before the automatic boot starts. This behavior was chosen to avoid conflicts with common BIOS and motherboard hotkeys such as F8, which many systems already use for boot menu or firmware options. In short: First boot: BootLoaderSelector menu is shown. Select OpenCore or Clover. Next boot: the last selected bootloader starts automatically. To show BootLoaderSelector again: press/hold Up Arrow during the BIOS/UEFI logo. No NVRAM, BootOrder or BootNext changes are made. BootLoaderSelector is a clean UEFI application for selecting between OpenCore and Clover at boot time. It is designed for users who keep both bootloaders available in the same EFI and want a simple, safe and fast way to choose which one to start. The selector runs before macOS and loads the selected bootloader directly using standard UEFI methods. It does not patch firmware, does not modify OpenCore or Clover, does not write to NVRAM, does not create Boot#### entries, and does not change BootOrder or BootNext. Main features: Supports OpenCore and Clover Clean visual UEFI interface Automatic bootloader detection Hardware information display: CPU GPU Board Memory Default 10-second timeout Options menu for timeout and behavior Remember last selected bootloader, enabled by default Silent hotkey access using Up Arrow during BIOS/UEFI logo F10 screenshot support Uses BLS.plist inside EFI/BOOT Generates both: BootLoaderSelector.efi BOOTX64.efi No NVRAM modification No BootOrder modification No BootNext modification No UEFI boot entry creation BootLoaderSelector is especially useful for Hackintosh testing, dual-bootloader EFI setups, OpenCore/Clover comparison, recovery environments and users who want a safer boot selection layer without relying on firmware boot menus. This project was inspired by jief666, whose work and ideas helped guide the concept of a dedicated UEFI bootloader chooser for Hackintosh systems.Sun, 07 Jun 2026 01:46:54 +0000iGpu is a lightweight macOS utility for viewing detailed graphics card information, including GPU model, VRAM, Metal support, connected displays, hardware properties, validation data, and real-time sensor readings when available. It supports AMD Radeon GPUs, Intel iGPU, and Apple Silicon detection, with a clean modern interface, Sparkle update support, and privacy-focused local diagnostics. Download HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HEREThu, 04 Jun 2026 02:23:17 +0000Adobe apps Are Crashing on My AMD Hackingtosh [Ryzen 5 5600G, IGPU,macOS Tahoe 26.5] please Help MeWed, 03 Jun 2026 20:23:25 +0000I have an HP 246 G6 laptop and I am trying to install macOS Ventura / Sonoma using Olarila images, but I am getting a kernel panic during boot. My hardware specifications are: HP 246 G6 Intel Core i3-7020U (Kaby Lake) Intel HD Graphics 620 12 GB DDR4 RAM Kingston A400 480 GB SSD Realtek RTL8723BE Wi-Fi UEFI BIOS Secure Boot disabled I tested the latest Olarila Sonoma image and received a kernel panic before the installer loads. I am currently testing Ventura 13.7.8. Could someone please share or recommend: A working EFI folder for HP 246 G6 The correct drivers and kexts for this model Recommended SMBIOS settings Any BIOS settings that may be required Any specific patches for Intel HD 620 / Kaby Lake laptops If anyone has successfully installed macOS on an HP 246 G6 or a similar Kaby Lake laptop, I would greatly appreciate your help. Thank you very much.Wed, 03 Jun 2026 14:26:22 +0000Hello MaLd0n A really nice app with a great interface. As shown in the photo, audio codec “not found”, installed VoodoHDA.kext 4.0 (yours) Here’s the report If you need to test the app, let me know I hope I've posted this in the right section; if not, please move it Mac-Info-Report.txt.zipMon, 01 Jun 2026 13:42:08 +0000SMCReader is a lightweight macOS menu bar sensor monitor designed for Hackintosh systems, Intel Macs, AMD Hackintosh builds, and Apple Silicon Macs. It reads real-time hardware sensor data using VirtualSMC, FakeSMC, AppleSMC-compatible keys, and supported sensor plugins, providing a clean and fast way to monitor temperatures, fans, voltages, power usage, storage health, battery data, and GPU/iGPU sensors directly from the macOS menu bar. The app is especially useful for Hackintosh users who need a modern alternative to traditional SMC monitoring tools. SMCReader supports sensor data from Intel CPUs, AMD CPUs via SMCAMDProcessor, Intel iGPU, AMD GPUs, compatible dGPUs, storage sensors, fan tachometers, voltage rails, current sensors, power readings, and thermal zones when the correct VirtualSMC or FakeSMC plugins are installed. Security and stability are also a major focus. SMCReader is a read-only sensor monitoring app. It does not install kexts, does not use a privileged helper, does not write SMC keys, does not modify system files, and does not collect user data. The app is designed for fast opening, low CPU usage, low memory usage, and real-time hardware monitoring with a clean dark glass interface. Main features: macOS menu bar hardware sensor monitor Hackintosh sensor monitoring with VirtualSMC and FakeSMC Intel CPU temperature and power monitoring AMD CPU support through SMCAMDProcessor Apple Silicon native fallback telemetry GPU and iGPU temperature monitoring Fan speed monitoring with dynamic 0 rpm filtering Voltage, current, power, storage, battery and thermal readings Up to six pinned sensors in the macOS menu bar Dynamic sensor list: only valid keys with real values are shown Read-only operation with no SMC writes No kext installation, no helper, no system modification Lightweight dark glass interface optimized for speed Download HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERESat, 30 May 2026 03:27:05 +0000hello , i am new here , i have installed hackintosh monetorywell , but i hit by the problem of wifi (intel) , so i heard something about https://github.com/OpenIntelWireless/itlwm/releases , but i really do not know how use it , where..... , thnks for respond.Fri, 29 May 2026 15:45:19 +0000Hey, how do I get my Broadcom 4350 working on Tahoe 26.4? I tried to patch it with OCLP Plus but my system won't boot after that. Screenshot 2026-05-28 at 12.57.48.zipThu, 28 May 2026 19:58:13 +0000can someone help me fix this blackscreen on wake issue on i3-1005G1? thxThu, 28 May 2026 15:43:36 +0000iCpu is a modern macOS hardware information utility created for users who want a clear, fast and organized view of their system. Built with a native macOS interface and a dark metallic glass design, iCpu helps you inspect CPU, cache, mainboard, memory, SPD, graphics and benchmark information in one place. Download iCpu for macOS HERE Anyone who would like to support the project with donations is very welcome and greatly appreciated. Link HERE iCpu is a modern hardware information utility for macOS, designed for Mac users, Hackintosh users, technicians and hardware enthusiasts, with a clean dark metallic glass interface, native system reading, organized tabs and fast access to CPU, cache, mainboard, memory, SPD, graphics and benchmark information. The app shows processor name, vendor, architecture, cores, threads, frequency, instruction flags, cache data, motherboard information, firmware details, macOS SMBIOS, board ID, system UUID, serial number with hide/show control, memory size, memory type, memory speed, populated slots, memory pressure, dynamic SPD module information, GPU details, Metal support, connected displays and quick benchmark results. iCpu supports Intel, AMD and Apple Silicon systems, filters generic or misleading memory values, ignores empty memory slots, separates physical hardware data from macOS SMBIOS identity, and can use optional dmidecode data when available for deeper DMI and SMBIOS inspection. Built for local diagnostics, system validation, OpenCore checking, hardware comparison and troubleshooting, iCpu reads system information through macOS tools such as sysctl, system_profiler, ioreg, vm_stat and memory_pressure, without requesting camera, microphone, contacts, calendar or location access. If you need a native macOS app to inspect CPU, memory, SPD, graphics, SMBIOS, motherboard, firmware and benchmark information, iCpu provides a fast, clean and practical hardware dashboard.Thu, 28 May 2026 01:37:55 +0000Hello, I am running an Asus Vivobook, and I've been encountering this seemingly 'Invalid frame pointer' problem. Here is my laptop system information: Processor Intel Core i3-1005G1 Display: Intel UHD Graphics I've also attached my config.plist file. config.rarWed, 27 May 2026 16:48:37 +0000Tue, 26 May 2026 11:27:33 +0000I know that this is quick fixable, but for me it`s not. I have a Aspire 3 A315-59 with I5-1235U and Iris Xe graphics. So, back to winter 2026, i buyed this laptop and started to hackintosh it. Quirks, EFIs, Kexts, ACPI, config, and i done the opencore EFI. When i tried to boot: i started this chain. Every fix isn`t work for me. Only all that i seen EXITBS:START. I tried -igfxvesa, tried another quirks, ACPIs, kexts, and anything isn`t work, and i stop this project. Week early, i again start this project because i fing the NootedGreekext, i tried again and anything didn`t work again. I tried all guids, and fail again. Maybe some experts know what problem i have. I attached my EFI folder and the last log. Thank. https://drive.google.com/drive/folders/1j02Pngii2B0A8oK2NRYl17oLcOs8jzmY?usp=drive_linkMon, 25 May 2026 12:27:13 +0000Mon, 25 May 2026 09:41:38 +0000Title: bootplim=0 / forced_idle_ratio=100 — Package C-states stuck at 0% on Z390 + i5-9600K (Ventura) cpufriendkext andCPUFriendDataProvider also added --- System: - Board: Gigabyte Z390I Aorus Pro WiFi (BIOS F8h) - CPU: Intel i5-9600K - SMBIOS: iMac19,1 - macOS: Ventura 13.7.8 (22H730) - OpenCore: 0.9.7 (REL-107) - Boot: USB OpenCore (test EFI) --- Problem: Package C-states are completely stuck at 0% across all states (C2/C3/C6/C7/C8/C9/C10). Individual core C-states work fine (C6 at 84–97% residency). powermetrics shows TURBO_ATTENUATION limiter active even at 2.6W idle. Key sysctl values on every boot: machdep.xcpm.bootplim: 0 machdep.xcpm.forced_idle_ratio: 100 machdep.xcpm.mid_cst_control_limit: 0 IORegistry X86PlatformPlugin shows: CPUPLimitDict: pMax=0, pMin=38 IdlePLimitDict: pMax=0, pMin=100 IGPUPLimitDict: pMax=0, pMin=16 ForcedIdleTable is active --- What I have tried (none resolved bootplim=0): 1. AppleCpuPmCfgLock: true 2. AppleXcpmCfgLock: true 3. AppleXcpmExtraMsrs: true 4. ProvideCurrentCpuInfo: true 5. CFG Lock disabled via GRUB (MSR 0xE2 confirmed 0x00) 6. MSR 0xE2 kernel NOP patch (correct bytes for kernel 22.6.0) 7. SSDT-PMC — already present in SSDT-OLARILA 8. BIOS C-state settings — C8/C10 enabled, Package C State = Auto 9. BIOS SGX disabled 10. BIOS PL1/PL2 manually set to 95W (no visible setting on this board) 11. wrmsr 0x610 via GRUB shell with correct PL1=PL2=95W value 12. boot-args: xcpm_pkg_scope_msrs=1, xcpm_idle_disable=1 — both ignored --- MSR values read via modGRUBShell: MSR 0x606 (Power Unit): 0xa0e83 → 0.125W per unit MSR 0x610 (Pkg Power): 0x42ffd0001affd0 → PL1=PL2=0x7FFF (unlimited/no limit) MSR 0x1FC (Power Control): 0x38005f → power mgmt enabled The BIOS writes 0x7FFF (unlimited) to MSR 0x610 on this board and resets it on every boot. wrmsr fix doesn't survive reboot. --- Root cause assumption: On a real iMac19,1, X86PlatformPlugin reads CPU power budget from SMC keys (MSAL, PDTR) rather than MSR 0x610. VirtualSMC + SMCProcessor do not publish these SMC power budget keys, so X86PlatformPlugin receives nothing, sets bootplim=0, and activates ForcedIdleTable permanently. --- Question: Is there a known fix or workaround for this on Z390 + Coffee Lake desktop? Specifically — does SSDT-OLARILA or any custom SSDT provide a way to inject the missing SMC power budget data, or is there a VirtualSMC plugin that covers MSAL/PDTR for iMac19,1 SMBIOS? CPUFriend is working correctly (vectors_loaded_count=1, CPUFloor=800MHz, P-states 800MHz–4600MHz all correct). The only remaining issue is the package-level power budget injection. Archive.zipSun, 24 May 2026 13:19:59 +0000