Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/09/2024 in all areas

  1. I have built the 10.13.6 kernel. EDIT: New version with missing symbols added. System.kext needs to be installed and then the prelink will work. XCPM is enabled. XNU-10.13.6-AnV_R2.zip
    2 points
  2. I have to find the older version and try it. The scenario you described where you upgraded to Sonoma from Ventura is exactly what I did and version 2.89 is in system settings but a clean install of Sonoma hides it somewhere. Is there a way to launch it other than from visually launching it from system settings maybe command line? Edited: After a couple of reboots and reinstall attempts, maybe while System Settings was open, not sure exactly if that was the reason why, but it did finally install in the System Settings, I could see it install at the bottom of the window, like magic. I wish I could re-produce the exact steps to be of any use to someone else. Oh wait maybe this time instead of double clicking on the file to install I just right clicked then open instead that could be why.
    2 points
  3. June 10–14, 2024 View full article
    2 points
  4. ********************************************************************************** In this thread, I have fully documented the installation of macOS on my HP EliteDesk 800 G4 / G5 Mini. It is a PERFECT HackMini8,1 and is running very well for me without any issues. I hope this documentation helps you to install macOS on your hack. Please leave feedback if you think there is anything I can improve and let me know if you have any questions. ********************************************************************************** This thread is for the EliteDesk 800 G4 / G5 Mini with UHD630 iGPU graphics. If you want a solution for the HP EliteDesk 800 G4 / G5 Mini with AMD Radeon RX560x graphics, see this thread. Background This is my first "modern" hack supporting UEFI and my first hack using Clover "on-the-fly" patches. My previous hacks Laptop: Thinkpad T61 / Nvidia NVS 140m Laptop: Dell Latitude E6410 / Nvidia G3100m Desktop: Gigabyte G31 / GeForce 9600 Desktop: Biostar TH55HD / Sapphire Pulse RX580 (Google "Catalina Biostar TH55HD" and look for user name deeveedee) are all perfectly running Catalina and I patched them all "manually" - all DSDT patches applied with MaciSL with virtually no Clover on-the-fly patching and all booted Legacy Clover. This UEFI hack was MUCH easier and took about 20 hours vs. a combined hundreds of hours for the old hacks. I wanted a hack that was a little more future proof and I think this is it. I hope you enjoy this as much as I am enjoying it. It is a perfect MacMini8,1. My system specs HP EliteDesk 800 G5 Mini (I9-9900 / UHD 630 / Q370 Chipset / 32GB DDR4 RAM) (also own 800 G5 Mini with i7-9700, 800 G4 Mini with i7-8700 and have owned 800 G4 Mini with i7-8700T - all work perfectly) 3 x DP Ports (connected to monitors using DP -> DVI adapters) 6 x USB 3.1 1 x USB Type-C 3.1 2 x NVMe SSD (M.2 PCIe x4 2280/2230 combo ports) 1 x SATA6 SSD 1 x Intel Ethernet RJ-45 Conexant CX20632 Audio Codec I am not using Wi-Fi. See below in "What is not tested" for Wi-Fi solutions. macOS Installation Important: You MUST BE LOGGED-IN to download attachments from this forum See macOS installation steps for OC and CLOVER here See Known Issues here for additional installation steps that may not yet be included in my attached config files See OC and CLOVER EFIs in attached to this post See BIOS configuration in attached BIOS configuration PDF document See how I developed my installation methodology here See references here See instructions here for installing two M.2 2280 NVMe SSDs and one SATA HD / SSD What is not working DRM (no hackintosh solution for DRM with UHD 630 iGPU) Everything else that I have tested is working perfectly What is not tested USB c 3.1 port (I have partially tested the USB 3 functionality of the port and it seems to be working fine with the USBPorts.kext in the attached EFI .zip archives) Wi-Fi / Bluetooth I am not currently using Wi-Fi/Bluetooth in this hack, but starting with Sonoma, Broadcom Wi-Fi is not supported without 3rd-party macOS root patches. I am not in favor of installing Open Core Legacy Patcher (OCLP) root-patches to enable Broadcom Wi-Fi (see my opinion here). If you need basic Wi-Fi/Bluetooth (and don't care about Apple-specific functions like Airdrop), I recommend Open Wireless project to enable Intel Wi-fi/Bluetooth. I don't believe that OCLP Wi-Fi root-patches are safe for secure computing operations (e.g., online banking or even accessing your Facebook page). If you prefer Broadcom Wi-Fi/Bluetooth, replace intel Wi-Fi with Broadcom Wi-Fi here and here. What is working Everything not mentioned above Sleep / Wake Multiple displays with IGPU graphics acceleration, hot pluggable display ports and DP->DVI adapters USB 3.1 ports Audio (internal speaker and headphone jack) Ethernet Microphone / front-right audio port (tested with CTIA-style 4-connector headset) Known Issues and their solutions - see here BIOS Version / Configuration Tested BIOS Versions for G4 Mini: 02.11.01 Rev.A or 02.12.00 Rev.A or 02.14.01 Rev.A, 02.15.00 Rev.A, 02.16.00 Rev.A, 02.17.00 Rev.A, 02.19.00 Rev.A, 02.20.01 Rev A, 02.21.00 Rev.A Tested BIOS Versions for G5 Mini: 02.07.01 Rev.A, 02.08.00 Rev.A, 02.09.00 Rev.A, 02.10.01 Rev.A, 02.11.00 Rev.A, 02.12.00 Rev.A, 02.12.10 Rev.A, 02.13.00 Rev.A, 02.14.01 Rev.A, 02.15.00 Rev.A See attached BIOS configuration in PDF document "HP EliteDesk 800 G4 Mini BIOS Configuration.pdf" Intel ME must be enabled for proper sleep / wake of UHD 630 UHD 630 Framebuffer Patching See here and here to understand my graphics properties for use with WhateverGreen.kext Read this to see my attempt at graphics patching without WhateverGreen.kext (WEG) to get a better understanding of what WEG is doing Current Versions Ventura 13.6.7 & Sonoma 14.5 OpenCore 1.0.0 Lilu.kext 1.6.7 WhateverGreen.kext 1.6.6 AppleALC.kext 1.9.0 IntelMausi.kext 1.0.7 RestrictEvents.kext 1.1.3 VirtualSMC 1.3.2 NVMeFix.kext 1.1.1 Elements of this implementation that you may not see in other hacks HPET is disabled for the reason stated here RTC memory size is patched (like CLOVER's "Fix RTC") instead of using RtcMemoryFixup.kext for reasons here ScreenShots OC1.0.0-EFI-R001.zip HP EliteDesk 800 G4 Mini BIOS Configuration.pdf CLOVER-r5122-v6.zip
    1 point
  5. [GUIDE] Gigabyte Z690 AORUS ULTRA & i7-12700KF & AMD RX 6600 [Monterey] [Ventura] [Sonoma] • Guide using OpenCore 0.8.6 for macOS Monterey & Ventura • BIOS basic settings • EFI folder available • macOS installation procedure is standard and is not covered here. Hardware • Motherboard: Gigabyte Z690 AORUS ULTRA (rev. 1.0) • CPU: Intel® Core™ i7-12700KF • Memory: Kingston FURY, KF560C32RSK2-32, DDR5-6000 CL32-38-38 @1.35V • Video: SAPPHIRE PULSE AMD Radeon RX 6600 • Monitor: BENQ-BL2711U + LG TV 42LF650V • Ethernet: Intel® 2.5GbE LAN chip I225-V (Built-in) • WiFi: Intel® Wi-Fi 6 AX200 (Built-in) • Bluetooth: Intel® BLUETOOTH 5.2 (Built-in) • NVMe: M.2, PCIe 4.0, Netac, 1 Tb + M.2, PCIe 3.0, Samsung 970 EVO 250 Gb • HDD: Western Digital, 2 Tb macOS & OpenCore version • macOS Monterey, 12.6.1 (21G217), macOS Ventura, 13.0.1 (22A400) • OpenCore 0.8.6 Some important BIOS settings BIOS version F20 [03.11.2022] • CFG Lock: Disabled • CSM: Disabled • VT-d: Disabled • Fast Boot: Disable Link • Above 4G Decoding: Enabled • Windows 10 Features: Windows 10 • XHCI Hand-Off: Enabled • IO APIC 24-119 Entries: Enabled • Legacy USB Support: Enabled • USB Mass Storage Support: Enabled • Intel Platform Trust Technology (PTT): Enabled • Security Device Support: Disabled • Network Stack: Disabled • Secure Boot: Disabled • Enable VMD controller: Disabled • Initial Display Output: PCIe 1 Slot OpenСore settings and EFI files You can use settings and files from my EFI for installation and daily work in macOS. During installation, use the following specific settings in config.plist: • SecureBootModel = Default • SIP enabled (csr-active-config=00000000) After installation, you can change them depending on the third-party software you are using and other circumstances. Please read the Notes at the end of this post carefully. What works? All PC devices and Apple technologies work properly in Monterey. See below about Ventura. What does not work? Bluetooth works well in Monterey, but BlueToolFixup.kext needed for it to work, can sometimes lead to random stuck when the system is rebooted or the computer is turned off. You can disable Bluetooth (deactivate BlueToolFixup.kext, IntelBluetoothFirmware.kext and IntelBTPatcher.kext in config.plist) or tolerate this disadvantage. Bluetooth does not work in Ventura. I hope the developers will fix this in the upcoming BlueToolFixup.kext releases. Some tests Credits @Slice for personal assistance and support Acidanthera: OpenCore and kextsDortania: OpenCore guides. Notes: • About macOS Ventura. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600/?do=findComment&comment=2797479 • About macOS Sonoma. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600-monterey-ventura/?do=findComment&comment=2812278 • About macOS Monterey: • USBMap.kext in my EFI is individual. I used F_USB1 and F_U32 Motherboard Internal Connectors. You may need to edit or replace it if you are using a different connector on your motherboard or want to use another Mac-model in Platforminfo --> Generic. If you edit mine or create a new one USBMap.kext, don't forget that the Audio device, ITE device and Bluetooth device works over the USB and require separate ports to work (ports HS04, HS13, HS14). Unfortunately, this reduces the number of USB ports available (15-3=12).• CPUFriendDataProvider.kext in my EFI is CPU i7-12700K(KF) specific. Do not use it for other CPU models.• You must insert your own SeralNumber & MLB & ROM & SystemUUID in the config.plist file.• I225-V Ethernet controller works without additional kext in Monterey, only need device-id replacement in the config.plist section DeviceProperties --> Add. Note that the settings in this section are individual. Leave only those that match your hardware.• If you do not have a 4k monitor, you must replace (for the corresponding screen resolution) or just delete the file /EFI/OC/Resources/Image/Acidanthera/GoldenGate/Background.icns• Don't forget to reset NVRAM after changing OpenCore settings.• My CPU and memory are both overclocked and stable, but this guide does not discuss this due to the variation in the physical characteristics of each individual piece of hardware.• I haven't noticed any significant benefits when using MacPro7,1 Mac-model instead of iMacPro1,1 My EFI folder for Monterey: https://drive.google.com/file/d/1kILvTfn-cA6s4FFTZL_1lUhHwPIN2R53/view?usp=sharing
    1 point
  6. just disable it. you need to figure out why the driver fails. maybe try get syslog from hacintool i updated code with (base code is in whatevergreen - this is just the property added to info.plist) and no more screen flick at boot question: does any1 knows other hidden properties that can help us ? for logs i use this in terminal log show --style syslog --predicate 'processID == 0' --last 1h --info --debug > x.log i've posted some log samples few posts ago they dont need any special flags
    1 point
  7. It is not same as XCPM in disassembled codes of a kernel but maybe essential part.
    1 point
  8. Hi @Slice, this XCPM code is not of my own creation. I can't even tell you where I got it from or where I adopted it.xnu-4570.71.2-xcpm-vanillia.diff
    1 point
  9. I have a new patch. It works now (I think). Could you test this one please (It has extra symbols for 10.13.6)
    1 point
  10. New version built. Test it please. NOTE: Opemu does verbose output. It is not per se an error. If you still get an error post picture please.
    1 point
  11. 2024-03-16 00:35:59.879395+0000 localhost kernel[0]: (AppleIntelICLGraphics) [IGPU] virtual IOService *IntelAccelerator::probe(IOService *, SInt32 *): Found device with ID 0x9a498086, revision 0x1, PCH id 0x0, PCH rev 0x0 at PCI 0:2:0 previous release changed this values this release change pch id but i'm unsure how ventura uses this Mastachief your log looks like typical hang when loading scheduler 4 or 5 the default atm is 3 so idk what is causing the hang unless you have same display as me and this config breaks it (i doubt) just in case i'm gonna add extra 999 so i dont break any1 lcd 'im trying to figure out what's wrong with memory allocations 2024-03-15 23:43:27.505574+0000 localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG ][DISPLAY ] Value read from Mailbox for MEM_SS_INFO = 0x120\ 2024-03-15 23:43:27.505578+0000 localhost kernel[0]: (AppleIntelICLLPGraphicsFramebuffer) [IGFB][LOG ][DISPLAY ] RAM = 0x0\ some logs get it almost right is this a bios setting ? i added code to change Stolen Memory Size but the driver uses pciconfigreads to get some other values this code will eventually work... it's based on whatevergreen and ofc will be needed for some tweaks frame->fUnifiedMemorySize = 3*1024*1024; frame->fStolenMemorySize= NBlue::callback->stolen_size;
    1 point
  12. I thought Ventura and Sonoma can work without WEG only when using iMacPro or MacPro SMBIOS and that iMac always needed WEG. But @Slice said in a previous post that he has iMac without WEG. On my system, graphics only work fine without WEG with iMacPro or MacPro SMBIOS. If I put iMac SMBIOS and remove WEG, graphics don't work well. Answering @AslashA if you use only the AMD (iGPU doesn't exist or is disabled in BIOS) WEG has none or few advantages. Every user having AMD as main card and iGPU as headless mode card needs WEG.
    1 point
  13. I also built the kernel earlier and had to go shopping briefly. This kernel includes XCPM xnu-4570.71.2-AMD-ALL-AnV-R4.zip Edit: So, the long-awaited graphics card just arrived, and now I'll compile a kernel for Mojave since I still have a partition with Mojave installed. I'm looking forward to the tests and hope that the system now boots into the desktop 😜
    1 point
  14. If the Open Core change log remains as planned, the next release of Open Core will be version 1.0.0. There's nothing significant about this version numbering, as it is simply the numerical progression from version 0.9.9. As with recent OCLP versions after OCLP 0.9.6, there does not appear to me to be any compelling reason to upgrade to the latest Open Core binaries; however, I will be updating the OC EFI attached to Post #1 only to have an OC EFI for OC 1.0.0.
    1 point
  15. Nobody said the update size. I will
    1 point
  16. I can't help you with wifi issue. Check github about itlwm.
    0 points
×
×
  • Create New...