Target: Legion-5-15IAX10-OpenCore (Arrow Lake HX, OpenCore 1.0.8, Tahoe 25G241). Open issues: #1 battery readings, #2 Thunderbolt/USB4 controller not found. Confidence uses High / Medium / Low / Unverified.
-
Arrow Lake self-wake after sleep (Medium to Low for laptops). saspol/UltraWake (MIT).
- The problem: on Arrow Lake-S with Z890, GPE 0x6B and 0x6E stay set because macOS never runs the firmware's
_L6B/_L6Ehandlers. Every sleep after the first ends in a self-wake 10 to 20 s later. - The fix: a
_PTSSSDT clears the PCH and SoC status bits, and a kext turns a USB-keyboard DarkWake into a full wake. - Why it may apply to us: the README excludes laptops, but Arrow Lake HX is built from the S die with the same 800-series chipset (our HDA 7F50 and I2C 7F4x), and our ACPI path is
\_SB.PC02like theirs. - When: for later, when sleep is turned on. Credited.
- The problem: on Arrow Lake-S with Z890, GPE 0x6B and 0x6E stay set because macOS never runs the firmware's
-
Our fan interface is documented (High). johnfanv2/LenovoLegionLinux (GPL-2.0, facts only) supports our model as
model_s2cn(83F0/S2CN). It gives:- EC chip id 0x5508
- WMI3 for temperatures, fan speeds, power mode and the fan curve
- a 10-level fan table at EC 0xF9F0 to 0xF9F9 with no temperature fields
- the EC path
\_SB.PC00.LPCB.EC0.VPC0
Its EC3 offsets are wrong for this chip and unsafe to write. Their issue #491 (fan curve on EC 0x5508) is still open. Credited.
-
Arrow Lake HX EXITBS hang on a MUX laptop (Low). nullmoth/1401#64 (290HX, RTX 5070 Ti): reporters say turning VT-d off fixes it.
-
"Non-monotonic time" panic on a 2023 Legion (Low). nullmoth/1401#69, with AppleIntelCPUPowerManagement in the backtrace. Same Legion firmware family as ours.
The OpenCorePkg commits in the window (APM media detection, an unused header removed, OpenCanopy button darkening, Eg2Info revision, a firmware-password refactor) are all after 1.0.8 and don't change our EFI, which uses the built-in picker. A CS35L41 amplifier kext needs AppleHDA, which Tahoe no longer has. A Chromebook port is unrelated.