How to Troubleshoot Stuck in macOS Recovery with dead USB ports on a Jurassic LGA 1156 H55 "Frankenstein" board (Revenger) — Any final sanity checks on macOS
Graphics and media-app crashes are usually tied to unsupported GPUs, missing acceleration, or fragile legacy patches.
Step-by-Step Fix:
- Back up first: Make a Time Machine backup or clone before changing OpenCore, EFI, root patches, or macOS versions.
- Confirm GPU support: Check whether the exact GPU has native macOS acceleration; many NVIDIA, Iris Xe and newer iGPU paths are not viable.
- Use the correct driver path: AMD dGPUs usually need WhateverGreen/NootRX choices; AMD iGPUs using NootedRed can still break Chromium, Electron or creative apps.
- Verify acceleration: Open About This Mac and Activity Monitor; if Metal acceleration is missing, fix that before testing GarageBand, Pro Tools or browsers.
- Reduce variables: Disable browser hardware acceleration or test another macOS version when a single CEF, Electron or media app is affected.
Final check: Change one thing at a time, reboot, and keep a copy of the last working EFI before the next test.
Original Question: "Stuck in macOS Recovery with dead USB ports on a Jurassic LGA 1156 H55 "Frankenstein" board (Revenger) — Any final sanity checks?"
Stuck in macOS Recovery with dead USB ports on a Jurassic LGA 1156 H55 "Frankenstein" board (Revenger) — Any final sanity checks?
Hey everyone,
I’m doing this purely for the absolute masochism, fun, and the challenge of making any version of macOS boot on this ancient, prehistoric piece of tech.
Just to be clear: This is NOT my main rig. My daily driver is a modern setup, and I have absolutely no intention of turning my actual good hardware into a Hackintosh. This is literally just a weekend project because I felt like fighting with ancient silicon for sports.
But man... this prehistoric hardware is testing my sanity lmao.
The Specs:
CPU: Intel Core i7-870 (Lynnfield)
GPU: NVIDIA GeForce GT 610 (Fermi)
Motherboard: Revenger H55 (One of those modern Chinese remanufactured boards with a stripped-down AMI v02.67 BIOS)
Target OS: Tried High Sierra first, currently testing El Capitan (10.11.6) via OpenCore Legacy (DuetPkg/MBR boot).
The Situation:
Against all historical odds, the OpenCore structure is flawless. The Legacy bootloader fires up, passes memory mapping, verbose rolls beautifully without a single kernel panic, and BAM—I boot straight into the graphical macOS Recovery screen (tried both High Sierra and El Capitan).
The Boss Fight:
As soon as the recovery screen loads, my mouse and keyboard are completely dead. The mouse optical red light stays on (so the ports are getting 5V raw power), but the keyboard LEDs are completely black. It seems macOS is nuking the data lines (Data+ and Data-) out of existence the second the kernel takes over.
What we’ve already tried (The 38-Hour Odyssey):
BIOS Tweaks: Enabled Legacy USB, USB 2.0 Controller, and messed with SpeedStep/QuickBoot. (The BIOS is super barebones, no EHCI Hand-Off or C-States toggles available).
ACPI & Plist: Applied EHC1 to EH01 / EHC2 to EH02 patches, tried the _OSI to XOSI Windows simulation patch, threw ReleaseUsbOwnership = True and XhciPortLimit toggles back and forth.
Kexts: Swapped around USBInjectAll, GenericUSBXHCI, and completely cleaned them out for El Capitan native testing.
Physical: Tried the front panel ports, rear ports underneath the Ethernet, and even plugged them into a cheap USB 2.0 Hub. Nothing.
I know the logical answer is "the USB controller chip on this recycled cheap board is a non-standard clone and Apple's driver completely rejects it physically", and I know a $5 PCIe USB card or a PS/2 adapter would fix it instantly. But since this hardware is going straight to the recycling bin once my new PC parts arrive, I refuse to spend a single dime on it. I wanted to win this using raw code and software brute force.
Has anyone ever encountered these specific teasing Chinese H55 boards and found a magical ACPI table or property injection that forces the USB data lanes to stay alive in Recovery? Or should I just admit defeat to a 2010 motherboard clone and go touch some grass?
Any input is highly appreciated! Cheers!
[link] [comments]
Post a Comment