All Activity

Release 5174 published (GCC 16.1 implemented).

One additional observation that may be relevant: Besides AirDrop, Personal Hotspot and Continuity Camera, Find My device presence also appears to be affected when using Intel AX210. For comparison, my BCM943602CDP updates its status correctly in Find My on all my Apple devices. Since replacing the BCM943602CDP with the AX210 three days ago, the Mac Pro Hackintosh still sees all devices correctly in Find My, including its own entry. However, on my iPhone, iPad Pro and MacBook Pro, the Mac Pro Hackintosh itself is no longer updated and still shows the last location/status from the time the Broadcom card was installed ("3 days ago"). This has been reproduced on the same Mac Pro Hackintosh, running the same macOS Tahoe installation, with the same Apple ID and the same surrounding Apple devices. The only hardware change was replacing the BCM943602CDP with the Intel AX210. This may indicate that the remaining awdl0 issue is not limited to AirDrop, Personal Hotspot and Continuity Camera, but also impacts other Apple services that rely on the same Nearby/Continuity infrastructure, including Find My device presence.

Perfect, ALC1220 well detected, thanks.

Since you have a Catalina in VMware and only need High Sierra, I suggest you to install macOS High Sierra on MBR, it's easy to boot with Enoch and Clover.

I may offer you to read about Clover. There is also a book CloverOfHackyColor to teach you what is what.

Have you ever wanted to customize the displayed machine information in "About This Mac" so that it displays your hackintosh PC model instead? You can customize this machine name by editing ~/Library/Preferences/com.apple.SystemProfiler.plist as follows: Copy com.apple.SystemProfiler.plist from ~/Library/Preferences to your Desktop and make a backup copy to preserve the original Open com.apple.SystemProfiler.plist on your Desktop with your favorite plist editor You will need to modify all of the machine key/value pairs in one or both of the following dictionaries (modify all machine values in both of these dictionaries if they are present) CPU Names ModelNames The value of each machine key/value pair must be preserved when editing the value. Edit only the text within the parenthesis like this: Original: MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports) Modified: MacBook Pro (15-inch, 2020, HP EliteBook 850 G7) Do NOT modify anything else in com.apple.SystemProfiler.plist After you have edited all instances of the machine key/value pairs in dictionaries "CPU Names" and "ModelNames" if present, save your modified com.apple.SystemProfiler.plist on your Desktop. The modified com.apple.SystemProfiler.plist should resemble this: Copy your modified com.apple.SystemProfiler.plist back to ~/Library/Preferences (sudo cp ~/Desktop/com.apple.SystemProfiler.plist ~/Library/Preferences) Reboot You should now see your custom machine model in About This Hack. Enjoy!

All good, Miliuco! Well done!!! 👏 Note that I have modified ~/Library/Preferences/com.apple.SystemProfiler.plist so that About This Mac displays my custom machine info ('15-inch, 2020, HP EliteBook 850 G7' in this case). It might be nice for ATH to retrieve this customized machine info from SystemProfiler. EDIT: The format of the machine string in SystemProfiler.plist must be preserved when editing SystemProfiler.plist. The initial Mac identifier must be retained (e.g., MacBook Pro), such that only the text within the parenthesis is modified. All instances of the machine string must be modified (i.e., CPU Names and ModelNames if they exist). I created a simple tutorial here.

Just enjoy!!!

Thanks Deeveedee, Here is the full config.plist for your viewing pleasure. I don't use any form of OCLP as i don't have any use for it in its current form. Cheers, Howard config.plist

All is good

O yes! It can be network preferences.

@MaLd0n you are crazy 😃 I only installed HDAUniversal (and disabled AppleALC), and it works perfectly, including my microphone. That mic wouldn't work with VoodooHDA (even though it was detected), but everything runs fine with your KEXT 🤩 Thank you so much! btw. my machine is a Fujitsu Lifebook with a Realtek ALC255. I set the layout-id via a DeviceProperty entry: "layout-id", type: data, value: <FF000000>

In a what file? Stupid AI doesn’t know that I’m using Clover instead of OpenCore.

Just enjoy, bro!

@MaLd0n is a legend! Working great on my old HP EliteBook 840 G5 (Conexant CX8200 with alcid=15). The laptop is Bang & Olufsen tuned and I am impressed by the way it sounds! Thank you, master!

Because GCC 16.1 was not yet implemented. After Shabbat is over, this will be published.

Hey guys, good news! I’ve successfully implemented image generation in the app. I’ll keep improving the app step by step every day. Here is a quick breakdown of what’s new in the last 3 versions: v0.81.44 (Today): Large Performance Leap 50% Faster Prompt Processing: Switched the AMD tiled matmul to packed half-precision math, boosting prompt processing significantly (e.g., Qwen3-8B jumped from ~310 to ~470 t/s). 3x Faster Long Chats: Implemented a new attention kernel that processes prompt tokens in groups of 16. At 4K context, speed went from 103 to 289 t/s on an 8B model, meaning deep conversations will no longer feel sluggish. v0.81.43: Local Image Generation Studio Local Image Studio: Added an experimental "Images" tab running locally via stable-diffusion.cpp on the same Metal stack. It fully supports text-to-image and image-to-image workflows. Hardware-Aware Catalog & Custom Support: Includes a built-in image model catalog tailored to your VRAM budget (from 4GB up to 24GB+ cards), plus the ability to load your own custom checkpoints, VAEs, and text encoders. Multi-GPU Selector: Added a setting to manually choose exactly how many GPUs to split a model across. v0.81.42: Smart Defaults & Clean Benchmarks GPU by Default: The custom AMD Flash Attention kernel is now enabled by default for bundled and TurboQuant engines, prioritizing the faster GPU path over the CPU fallback. Accurate Tracking: Quantized KV caches now correctly force the required parameters, and the benchmark history now explicitly labels and records the exact execution route (FA CPU, FA AMD GPU, etc.). Stay tuned for more updates!

I'm currently testing MaLd0n's new HDAUniversal.kext for audio in macOS Tahoe on our HP EliteDesk Minis. I think audio quality is outstanding. If you want to test, get the HDAUniversal installer from here and do the following: Remove your existing audio solution for macOS Tahoe (e.g., remove VoodooHDA.kext from /Library/Extensions) In your Open Core config.plist, set csr-active-config = <03000000> and reboot for the new SIP setting to take effect. If you already have csr-active-config set to something that's less restrictive than <03000000> (e.g., <03080000>) then you don't need to change SIP. Run the HDAUniversal installer and follow the prompts. Be sure to "Allow" HDAUniversal when prompted. After Restarting, you should have perfectly working audio. You may need to select the audio output (e.g., select 'Line Out' or 'Headphones') If you want more restrictive SIP, set csr-active-config = <01000000>. Just like VoodooHDA.kext, HDAUniversal needs SIP set to allow untrusted kexts since it is installed in /Library/Extensions.

I installed HDAUniversal on an HP EliteDesk 800 G4 Mini that I'm using for a multimedia system. The EliteDesk 800 G4 Mini has two audio outputs that I'm using to drive 1) main speakers and 2) a subwoofer. HDAUniversal is working perfectly with the Multi-Output Device that I created using macOS Tahoe's Audio MIDI Setup. Sound quality is outstanding. 🎶

@Slice The network configuration is bound to the system definition in the same way, as the USB port mapping.

@Slice I know you're a big fan of AI 🤣 .... Seriously, though - this might be a good question for ChatGPT. Some of the response doesn't make sense, but some of may offer a clue. If you're running a Hackintosh/OpenCore on macOS Tahoe 26.5.2 and the only variable is the SMBIOS (MacPro7,1 vs iMac20,1), then the Realtek controller itself is probably not the root cause. The SMBIOS changes how macOS configures several networking and security features. Here are the most likely explanations, roughly in order of probability: 1. Ethernet interface gets recreated or renamed - Booting with a different SMBIOS can cause macOS to treat the NIC as a different device. - Check: ifconfig networksetup -listallhardwareports - See whether the Ethernet interface is still en0 or became en1, or disappeared entirely. 2. Ethernet driver initialization timing - If you're using RealtekRTL8111.kext (Mieze) or LucyRTL8125Ethernet.kext, initialization timing may differ between SMBIOSes. - Look in: log show --last boot | grep -i RTL log show --last boot | grep -i ethernet - Also verify that the driver actually attached: kextstat | grep RTL or on newer macOS: kmutil showloaded | grep RTL 3. Different DeviceProperties or ACPI paths - Some OpenCore configurations inject properties conditionally depending on SMBIOS. - Compare: - DeviceProperties - ACPI patches - Kernel -> Add - Make sure nothing is enabled only for iMac20,1. 4. Network service order corruption macOS stores network configuration separately. Try backing up and deleting: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Then reboot so macOS recreates them. 5. MacPro7,1-specific networking behavior MacPro7,1 expects workstation-class hardware and may enable features not present on consumer boards. Rarely this affects: - Wake-on-LAN - Energy Efficient Ethernet - PCIe ASPM A Realtek driver may not handle one of these correctly. 6. Different kernel cache or loaded extensions Verify that exactly the same kexts are loaded under both SMBIOSes: kmutil showloaded Compare the output between MacPro7,1 and iMac20,1. -------------------------------------------------- Information that would be most useful -------------------------------------------------- Boot using MacPro7,1 (where networking fails) and run: ifconfig networksetup -listallhardwareports kmutil showloaded | grep -i rtl log show --last boot --predicate 'subsystem CONTAINS "network"' --style compact or simply: log show --last boot | grep -i RTL Also provide: - Which Ethernet kext are you using? - RealtekRTL8111.kext? - LucyRTL8125Ethernet.kext? - Something else? - OpenCore version. - Motherboard model. - Does the Ethernet interface appear but have no IP address? - Or is the Ethernet interface completely missing? One additional question: When you say "lose internet," which of these best describes the problem? 1. The Ethernet interface is missing. 2. The Ethernet cable shows as unplugged. 3. Ethernet connects and gets an IP address, but nothing can reach the Internet. 4. Local network works but DNS or web browsing fails. That distinction will narrow the cause significantly. One thing I'd add based on experience with recent Hackintosh setups: if the only change is SMBIOS and the problem is 100% reproducible, I'd also compare the IORegistry between the two boots (IORegistryExplorer or ioreg -l) to see whether the Realtek PCI device receives different properties. That's one of the quickest ways to determine whether the issue lies in OpenCore's device injection versus the network driver itself.

I encountered a strange situation: 1. Booted as MacPro7,1 I loose internet. Reboot - the same. 2. Reboot as iMac20,1 I got all working Tahoe 26.5.2. Realtek8111H Why it may happens?