Skip to content

Keep T1 MacBook Pros in S3 instead of an Alpine Ridge wake loop - #12211

Open
ijt wants to merge 2 commits into
omacom:quattrofrom
ijt:fix/macbookpro14-alpine-ridge-s3
Open

ijt wants to merge 2 commits into
omacom:quattrofrom
ijt:fix/macbookpro14-alpine-ridge-s3

Conversation

@ijt

@ijt ijt commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Fixes #12194

Why

On MacBookPro14,2 (2017 13", T1, no T2 chip) the two JHL6540 Alpine Ridge Thunderbolt 3 controllers emit PME about every 45s and pull the machine out of deep S3 with the lid still closed. logind sees the closed lid and suspends again. That loop ran for hours here: the chassis got hot in a bag, and after enough cycles thunderbolt resume hung (tb_cfg_read/write: -108, pcieport … D3cold to D0, device inaccessible). Opening the lid did nothing; only a power-button hold recovered it.

install/hardware/apple/fix-suspend-nvme.sh already matches these DMI ids. T2 setup correctly no-ops (106b:180[12] is absent). This is the missing T1 half.

What

Gated on MacBookPro13,[123]|MacBookPro14,[123]:

  • Disable ACPI wakeup on RP05/RP09/XHC2/XHC3 (TB) and RP12 (Wi-Fi PME). LID0 and SPIT stay enabled.
  • udev: 8086:15d2 / 8086:15d4 power/wakeup=disabled.
  • Limine drop-in pcie_port_pm=off so those ports do not sit in D3 for ~1s each on resume.
  • Oneshoot at boot reapplies the ACPI toggles (they reset).
  • Migration sources the same installer leaf (no-op on any other machine).

Explicitly not in this PR

  • Not pm_async=off. That is correct on some T2 boxes and wrong here: it serialized the D3 waits into a ~60s black screen.
  • Not blacklist thunderbolt. USB-C charging still works without the module; docks / DP-alt would not. Wakeup disable + pcie_port_pm=off is the conservative first patch.
  • Not switching to s2idle. S3 works on this firmware; s2idle is the heat path.

Test plan

  • On MacBookPro14,2 / 13,x: close lid, leave closed. Journal should show one PM: suspend entry (deep) and no wake until lid open. Machine stays cool.
  • Open lid: resume to the lock screen.
  • Other hardware: installer/migration no-op.
  • ./test/cli and test/shell.d/alpine-ridge-suspend-test.sh.

Proven on Omarchy 4.0.2-1, MacBookPro14,2, kernel 7.1.9-arch1-2. After these local equivalents, a 30-minute lid-closed stretch came back immediately and was cool to the touch.

Sibling: lid-close debounce in #12210 (#12193).

JHL6540 PME pulls MacBookPro13,x/14,x out of deep sleep about every 45s
with the lid still closed. logind then suspends again; after enough
cycles resume hangs. Disable TB wakeup and skip PCIe port PM. Keep
thunderbolt loaded and leave pm_async on.
Resume from deep sleep on Alpine Ridge is slow enough that the portable
3s debounce still feels like a hang. Write /etc/omarchy/lid-suspend-delay
so those machines wait 20s; leave an existing value alone.
@ijt

ijt commented Sep 17, 2026

Copy link
Copy Markdown
Contributor Author

Follow-up: the installer also writes /etc/omarchy/lid-suspend-delay with 20 on these DMI ids (leaves an existing value alone). That pairs with #12210, which reads the file and also keys the same 20s delay off DMI so T1 Macs get it even before this hardware leaf runs.

@omarchybot omarchybot added bug Something isn't working compatibility Make Omarchy work better on everything! labels Sep 27, 2026
@omarchybot

Copy link
Copy Markdown
Collaborator

Reviewed at 5e177a3 by Claude Opus 5.5, with Codex Medium as a second opinion. Codex reached the findings below on its own and added the comparison with #11570 and the pcie_port_pm point. Codex can read this session's notes, so its agreement on the rest is not guaranteed to be independent.

What ran. I tested this on a disposable Omarchy VM, which has no Mac hardware. ./test/cli passes at this head. Merged into current quattro (8b4eae6) it has one failure, vscode generated theme references current theme file, and plain quattro fails that test too. test/shell.d/alpine-ridge-suspend-test.sh passes 5/5. The migration is a no-op on non-Apple DMI. With the DMI product name faked to MacBookPro14,2, the migration writes the udev rule, Limine drop-in and delay file, enables and runs the oneshot, rebuilds the UKI, and succeeds on a second run. The wake loop itself can't be reproduced without the hardware, so this is not verified. Under the review rules, only a maintainer can confirm the fix on a T1 Mac, because the reporter of #12194 is the author of this pull request.

Findings

  • install/hardware/apple/fix-suspend-alpine-ridge.sh:23 writes /etc/omarchy/lid-suspend-delay, but nothing on quattro reads it. The reader, omarchy-system-lid-suspend, only exists in Debounce lid-close suspend so a quick reopen does not sleep in the dark #12210, and Debounce lid-close suspend so a quick reopen does not sleep in the dark #12210 already keys the same 20s delay off DMI. This write belongs in Debounce lid-close suspend so a quick reopen does not sleep in the dark #12210 or should be dropped. On its own here it changes nothing.
  • Proportionality: the wake loop is fixed by disabling the wake sources (the ACPI nodes and the 8086:15d2/15d4 udev rule). pcie_port_pm=off (:35) is a different fix, for resume latency, and it turns off power management on every PCIe port of the machine, not just the Alpine Ridge ones. Suspend on 2016-2017 MacBook Pros: keep USB-C and Thunderbolt working across S3 #11570's author measured it as not helping their resume failure on the same model. RP12 disables Wi-Fi wake, not Thunderbolt wake. The proportionate pull request would be the wake-source change alone, with pcie_port_pm=off and RP12 split out unless an A/B run on the 14,2 shows they are needed.
  • The gate (:8) covers all six 13,x/14,x models, but the fixed ACPI names (RP05 RP09 XHC2 XHC3 RP12, bin/omarchy-hw-alpine-ridge-wakeup:19) were only observed on a 14,2. On another model, the same name could belong to a different device. Narrowing the gate to the tested model is the safe default until others are confirmed.
  • :53: /proc/cmdline describes the running boot, so every rerun before a reboot rebuilds the UKI. During ISO finalization the check reads the installer's own command line. The other hardware leaves that add kernel arguments (fix-t2.sh, intel/fred.sh) leave the rebuild to the installer.
  • test/shell.d/alpine-ridge-suspend-test.sh:38-45 models /proc/acpi/wakeup as a regular file, so the first write truncates it. The test can't show that several enabled nodes are each disabled, and the rest of it only checks that strings are present in the source.

Related. #11570 also disables S3 wake on the Alpine Ridge root ports for these same models, so the two compete on the wake loop. Asked separately, Codex judged this one the more targeted fix for the loop itself. #11570's remove/rescan and Wi-Fi reload address other resume failures. #10758 moves the MacBookPro14,1 to s2idle, and #9899 blacklists thunderbolt. Both contradict this pull request's keep-S3, keep-Thunderbolt approach on overlapping models. Which of these lands is the maintainer's decision.

Waiting on the author for the scope changes above. After that, it needs a maintainer to confirm it on a T1 MacBook Pro and to choose between this and #11570.

@niconistal

Copy link
Copy Markdown

A data point from a 15-inch MacBookPro14,3 (Radeon Pro 555 drives the internal panel), which this PR's gate includes. "S3 works on this firmware" does not hold for this model.

S3 (deep): every lid close since install needed a forced power-off. In the resumes that got far enough to log, amdgpu failed with SMU load firmware failed → amdgpu_device_ip_resume failed (-22). The Radeon drives the panel, so the screen stays black. The Alpine Ridge controllers also stayed in D3cold (not ready 65535ms after resume). omarchy-pkgs#596 reports the same SMU -22 on another 14,3. Dunedan/mbp-2016-linux notes that the 15-inch models resume only on the Intel GPU.

What works here: s2idle on a kernel with omarchy-pkgs#596 + #544. 18 of 18 sleeps resumed, including a 3-minute lid close. noirq resume took about 0.49 s, with no Thunderbolt -108 and Wi-Fi intact. Numbers: omacom/omarchy-pkgs#596 (comment). On the stock linux-omarchy 7.2.5-3, s2idle stalls about 65 s on resume and loses Wi-Fi and Thunderbolt, so s2idle depends on #596 landing.

The 8086:15d2/15d4 wakeup rule from this PR is also in place on that machine, and it helps in s2idle too. #596 additionally needed the T1 (05ac:8600) kept from waking the machine; without that, sleeps ended 12–141 s in.

Suggestion: keep the wakeup half for all T1 models, but don't treat MacBookPro13,3/14,3 (the Radeon-on-panel models) as S3-capable. Once #596 is in linux-omarchy, those two want s2idle. I haven't tested pcie_port_pm=off on the 14,3.

@omarchybot

Copy link
Copy Markdown
Collaborator

Re-read at the same head (5e177a3) after @niconistal's MacBookPro14,3 report, by Claude Opus 5.5 with Codex Medium as a second opinion. Codex reached the same reading. It can see this session's notes, so its agreement is not guaranteed to be independent. Nothing new was run: the code hasn't changed since the worker run in the earlier comment.

What the report changes. This pull request doesn't choose a sleep mode or touch mem_sleep on any model. It only removes wake sources and adds pcie_port_pm=off. So on a 13,3/14,3 it leaves S3 in place without fixing the amdgpu resume failure reported there, and the "S3 works on this firmware" premise in the description holds only for the 14,2 it was tested on. Moving those two models to s2idle depends on omarchy-pkgs#596 and belongs in its own change. This pull request shouldn't claim to cover them.

The gate finding, sharpened. The report confirms that the 8086:15d2/15d4 udev rule helps on a 14,3 too. That rule is keyed by PCI ID, so keeping it across the T1 models is reasonable. The /proc/acpi/wakeup toggles in bin/omarchy-hw-alpine-ridge-wakeup:19 are a different case: they disable whichever nodes are named RP05 RP09 XHC2 XHC3 RP12, and those names have only been seen on a 14,2. pcie_port_pm=off (install/hardware/apple/fix-suspend-alpine-ridge.sh:35) applies to every PCIe port and wasn't tested on the 14,3. The suggested split is to keep the PCI-ID udev rule for the full gate, and to limit the fixed ACPI names and pcie_port_pm=off to the 14,2 until another model is confirmed. The other findings in the earlier comment still stand.

This report is evidence for one part of the change, not verification of this head. It doesn't name the SHA, and the whole pull request wasn't installed.

Waiting on the author for the scope changes, then on a maintainer to confirm on a T1 MacBook Pro and to choose between this and #11570.

@niconistal

Copy link
Copy Markdown

Following up on the bot's gate finding, with the 14,3's /proc/acpi/wakeup (Omarchy 4.0.4, MacBookPro14,3):

  • XHC2 → 0000:07:00.0 and XHC3 → 0000:7d:00.0, both JHL6540 Thunderbolt 3 USB Controller, the same role as on the 14,2.
  • RP05, RP09 and RP12 do not exist on the 14,3. The script only toggles nodes that are currently enabled, so those writes are no-ops there, and the guard also keeps it from re-enabling XHC2/XHC3 when the udev rule already disabled them.
  • The 14,3's Alpine Ridge controllers hang off the CPU's PEG ports, not PCH root ports: 00:01.1 (PEG1) → 04-79, NHI at 06:00.0; 00:01.2 (PEG2) → 7a-ef, NHI at 7c:00.0. PEG0/PEG1/PEG2 stay enabled. Wi-Fi is ARPT under RP01 (00:1c.0), not RP12.

So the PCI-ID udev rule carries over to the 14,3 and the fixed ACPI names don't. On this machine, the udev rule plus the T1 rule were enough: 18 s2idle sleeps without a wake loop, with PEG1/PEG2 left enabled. pcie_port_pm=off is still untested here.

The 14,3's s2idle switch is now in its own draft, #14692, which depends on omarchy-pkgs#596 and #544, as the bot suggested.

@omarchybot

Copy link
Copy Markdown
Collaborator

Re-read at the same head (5e177a3) after @niconistal's /proc/acpi/wakeup data from the MacBookPro14,3, by Claude Opus 5.5 with Codex Medium as a second opinion. Nothing new was run, because the code hasn't changed. Codex reached the same reading and added the point about XHC2/XHC3 below. It can see this session's notes, so its agreement is not guaranteed to be independent.

The gate finding, narrowed. bin/omarchy-hw-alpine-ridge-wakeup:20 writes a name only when its row exists and reads *enabled (disabled doesn't match the pattern), so on the 14,3 the absent RP05, RP09 and RP12 are no-ops. XHC2/XHC3 are the same JHL6540 controllers there as on the 14,2, so the fixed names do carry over for those two. On the 14,3 the helper disables only the Thunderbolt xHCI wake and leaves PEG1/PEG2 and Wi-Fi alone. That rules out the "same name, different device" risk on the 14,3. It is still open for the 13,1, 13,2, 13,3 and 14,1, which the gate at install/hardware/apple/fix-suspend-alpine-ridge.sh:8 also covers and for which nobody has posted a wakeup table. Posting those tables, or narrowing the gate to the models that have been checked, would settle it.

What the data doesn't settle. The 14,3 result (no wake loop with PEG1/PEG2 left enabled) was in s2idle on a patched kernel. It doesn't show whether the root-port toggles are needed for the S3 loop on the 14,2. pcie_port_pm=off is still untested outside the 14,2. The other findings in the first comment still stand.

Related. #14692 (draft) moves the 14,3 to s2idle. It touches different files and doesn't compete with this one.

Waiting on the author for the scope changes, then on a maintainer to confirm on a T1 MacBook Pro and to choose between this and #11570.

@jandrusk

Copy link
Copy Markdown

Looks like the right direction for the Alpine Ridge PME loop on 13,x/14,x (#12194).

Two open scope questions before merge:

  • On MacBookPro14,3, @niconistal / @macmsb still see wake ~15s after entry even with RP05/RP09/XHC2/XHC3/RP12 disabled — first wake source was XHC1 (PCH xHCI hosting the T1). This helper never toggles XHC1, and the udev rule only matches 8086:15d2/15d4. Worth deciding whether 14,3 is in-scope here or deferred.
  • Suspend on 2016-2017 MacBook Pros: keep USB-C and Thunderbolt working across S3 #11570 overlaps the same model range with a different approach (keep USB-C/TB working across S3). Maintainer call on which lands / how they compose.

Also note this sets /etc/omarchy/lid-suspend-delay to 20s and assumes the lid-debounce path from #12210; that PR is currently conflicting with quattro.

@omarchybot

Copy link
Copy Markdown
Collaborator

Re-read at the same head (5e177a3) after @jandrusk's comment, by Claude Opus 5.5 with Codex Medium as a second opinion. Nothing new was run, because the code hasn't changed. Codex checked the comment against the source on its own and pointed out that it merges two separate 14,3 reports. Its agreement on the rest is not guaranteed to be independent, because it can read this session's notes.

What the source confirms. The helper only toggles RP05 RP09 XHC2 XHC3 RP12 (bin/omarchy-hw-alpine-ridge-wakeup:19), and the udev rule only matches 8086:15d2/15d4 (install/hardware/apple/fix-suspend-alpine-ridge.sh:29-30). So nothing here touches XHC1. The /etc/omarchy/lid-suspend-delay write (:23) still has no reader on quattro, and its only reader, #12210, now conflicts with quattro.

The 14,3 reports are two different results. The XHC1 wake comes from @macmsb on #12194, in deep S3 on the stock kernel. That machine kept waking about 15 s after entry, and hung on the next entry, even with every /proc/acpi/wakeup entry except LID0 disabled, which includes XHC1. So that report doesn't support adding XHC1 to this helper as a fix. @niconistal's 14,3 had no wake loop over 18 sleeps, but in s2idle on a patched kernel, with the T1 rule from omarchy-pkgs#596. Neither report tested this head. Both point the same way as the earlier comments: the 14,3 doesn't belong in this pull request's S3 gate, and #14692 (draft) moves it to s2idle instead.

Waiting on the author for the scope changes in the first comment: narrow the gate to the models that have been checked, and drop the lid-suspend-delay write or move it to #12210. After that it needs a maintainer to confirm it on a T1 MacBook Pro and to choose between this and #11570.

@hanscnelson

Copy link
Copy Markdown

One lid-closed stretch on a MacBookPro14,2, Omarchy 4.5.0-3, linux-omarchy 7.2.15-1. The local equivalent of this PR was applied before the boot: pcie_port_pm=off is on /proc/cmdline, and a oneshot disables ACPI wakeup on RP05, RP09, RP12, XHC2, and XHC3. After boot those five were disabled. LID0 and SPIT stayed enabled. pm_async was not changed. mem_sleep stayed s2idle [deep].

The screen came back much faster than the previous deep resume on this machine, which had stalled in tb_resume_noirq before the backlight. That part matches the reason for pcie_port_pm=off.

The lid was closed once. The machine did not stay down. With the lid still closed it completed four deep cycles:

entry exit asleep
446.6 499.4 ~53 s
499.7 504.4 ~5 s
531.0 534.6 ~4 s
562.5 566.6 ~4 s

logind issued the second suspend 0.2 s after the first resume, because the lid was still closed. The third and fourth followed about 25 s after the previous resume, again with no lid-open event. Lid opened is at 565.9, during the fourth resume.

The first resume still logged Host halt failed, -19 for xhci_hcd at 0000:42:00.0, 0000:06:00.0, and 0000:7c:00.0, then tb_cfg_read/write: -108. About 250 of those Thunderbolt warnings landed in this window. After the lid was opened those three xHCI devices were gone from the PCI bus. The Anker PowerExpand dock still shows as authorized on Thunderbolt router 0-3, but the PCIe devices behind it did not come back. USB on that dock is dead until the next boot.

Wi-Fi reloaded its firmware on the early resumes, then wedged. brcmf_c_set_cur_etheraddr returned -5 and then -12, scans came back empty, and nmcli connection up reported that the saved network could not be found. That is the #17124 failure. rmmod brcmfmac was not tried.

On this 4.5 / 7.2.15 boot, pcie_port_pm=off shortened the visible wake. The wakeup mask did not stop the lid-closed cycle, and the cycle cost the Thunderbolt xHCI devices and the Broadcom firmware. The original success was on 4.0.2 / 7.1.9. The local settings are still installed.

@omarchybot

Copy link
Copy Markdown
Collaborator

Re-read at the same head (5e177a3) after @hanscnelson's MacBookPro14,2 test, by Claude Opus 5.5 with Codex Medium and muse-wonder (pi, thinking high) as second opinions. Nothing new was run, because the code hasn't changed and the wake loop needs a T1 Mac that the workers don't have. Both reviewers reached the points below. muse-wonder added that the baseline run already had XHC2/XHC3 disabled. They can read this session's notes, so their agreement isn't guaranteed to be independent.

What the test shows. The 14,2 is the one model this pull request was proven on, on 4.0.2 with kernel 7.1.9. On 4.5.0-3 with linux-omarchy 7.2.15-1, with pcie_port_pm=off active and RP05 RP09 RP12 XHC2 XHC3 checked disabled after boot, a single lid close still produced four deep cycles (about 53 s, 5 s, 4 s and 4 s) before the lid was opened. On the current release, then, the ACPI mask plus the kernel argument doesn't keep that machine in a single S3. The faster screen return does match what pcie_port_pm=off is meant to do (install/hardware/apple/fix-suspend-alpine-ridge.sh:35).

What it leaves open. The report doesn't say whether the PCI half of the change was in place: the udev rule that sets power/wakeup=disabled on 8086:15d2 (NHI) and 8086:15d4 (xHCI) (install/hardware/apple/fix-suspend-alpine-ridge.sh:29-30). Disabling XHC2/XHC3 in /proc/acpi/wakeup doesn't cover the NHI, and the baseline run had those two disabled already. It also doesn't say what woke the machine. @bjhinkle's 14,2 data on #11570 shows GPE 0x32/0x33, the Thunderbolt hot-plug handlers for RP05/RP09, rising once per sleep, with pm_wakeup_irq empty. That points at the Thunderbolt side, but it doesn't show whether this change masks that path, because that machine never ran it.

Not caused by this change, as far as the data goes. The same machine without these settings already logged Host halt failed, -19 and removed the xHCI at 0000:42:00.0 after one deep resume, with tb_cfg_* -108 warnings. Losing three controllers and the #17124 Wi-Fi wedge came after four resumes in a row rather than one. Nothing in this diff removes devices or touches brcmfmac, and one run can't separate the settings from the number of cycles.

One question that would settle it, for @hanscnelson while the settings are still installed: with the dock attached as before, please run this just before one lid close.

for d in /sys/bus/pci/devices/*; do [[ $(<$d/vendor) == 0x8086 && $(<$d/device) =~ ^0x15d[24]$ ]] && echo "${d##*/} $(<$d/device) $(<$d/power/wakeup)"; done
grep -E '^(RP05|RP09|RP12|XHC2|XHC3)[[:space:]]' /proc/acpi/wakeup
grep . /sys/firmware/acpi/interrupts/gpe32 /sys/firmware/acpi/interrupts/gpe33

If it wakes by itself, please also post the two GPE counts and cat /sys/power/pm_wakeup_irq after the first wake. If every one of those devices reads disabled and it still wakes, this approach doesn't stop the wakes on this kernel. If the PCI devices read enabled, the last run didn't test the full change.

Waiting on the author for the scope changes in the first comment: narrow the gate to the models that have been checked, and drop the lid-suspend-delay write (:23) or move it to #12210. A T1 MacBook Pro result also has to account for the 14,2 run above. The choice between this and #11570 is the maintainer's. On the same model and release, #11570 didn't stop the first short wakes either, but its rescan brought the Thunderbolt tree back after the sleep that held.

@hanscnelson

Copy link
Copy Markdown

Follow-up on the same MacBookPro14,2, Omarchy 4.5.0-3, linux-omarchy 7.2.15-1, Anker PowerExpand dock authorized at 20 Gb/s. This boot had the whole change, and the PCI half was checked before the lid closed.

pcie_port_pm=off was on /proc/cmdline. Before sleep, power/wakeup read disabled on all four Alpine Ridge devices:

  • 0000:05:00.0 8086:15d2
  • 0000:06:00.0 8086:15d4
  • 0000:7b:00.0 8086:15d2
  • 0000:7c:00.0 8086:15d4

/proc/acpi/wakeup had RP05, RP09, RP12, XHC2, and XHC3 disabled. LID0 and SPIT stayed enabled. gpe32 and gpe33 were both 0.

One lid close produced five deep cycles (about 56 s, then 9 s, 3 s, 3 s, and 4 s). The lid-open event is during the fifth resume. Afterward:

  • gpe32 is 5 and gpe33 is 5, one count per cycle. /sys/power/pm_wakeup_irq is empty.
  • The T1 USB device failed its descriptor reads (t1bridge-cfgselector 1-3: device descriptor read/64, error -110). /dev/dri/touchbar still exists and points at card0, but the Touch Bar is dark.
  • Wi-Fi reloaded its firmware on the early resumes, then wedged. brcmf_c_set_cur_etheraddr returned -5 and then -12 on a repeating timer. A scan is empty, and nmcli connection up says the saved network could not be found.

Every one of those PCI devices read disabled before the lid closed, and the machine still woke. On this kernel the ACPI mask plus pcie_port_pm=off plus PCI power/wakeup=disabled on 8086:15d2 and 8086:15d4 does not stop the wakes. The local settings are being removed again. A reboot is what brings the Touch Bar and the Broadcom firmware back.

@omarchybot

Copy link
Copy Markdown
Collaborator

Re-read the source at unchanged head 5e177a33d22c32417f8d1ce82058a6539d364bcf and @hanscnelson’s follow-up, by GPT-6 in Codex (effort not reported), with Opus 5.5 High and muse-wonder (pi, thinking high) as second opinions. Both agreed on the result below; they can read the session’s notes, so that agreement is not guaranteed to be independent. No new tests ran: the code is unchanged, and the workers lack T1 Mac hardware.

The follow-up answers the PCI-wakeup question from the last review. All wake settings this diff installs were checked before sleep: both 15d2 and both 15d4 devices had power/wakeup=disabled, all five ACPI nodes were disabled, and pcie_port_pm=off was active. The five deep cycles, with lid opening during the fifth resume, establish at least four unprompted wakes. The missing-PCI-settings explanation no longer applies: these settings did not keep this MacBookPro14,2 asleep on 4.5.0-3 / 7.2.15-1 with the dock attached. This does not invalidate the earlier result on 4.0.2 / 7.1.9.

The GPE counters rising from 0 to 5 do not distinguish a wake trigger from activity during resume. The baseline already had T1 descriptor failures; the Wi-Fi wedge followed repeated resumes, so neither is established as a regression caused by this change.

Waiting on @ijt to account for this negative result with a revised approach and hardware evidence. Narrowing the model gate and removing or relocating the unused lid-suspend-delay write remain open, but those edits alone would not resolve this result. No further repeat of the same settings check is needed from @hanscnelson.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working compatibility Make Omarchy work better on everything!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MacBookPro14,2 (T1 Alpine Ridge): S3 wake loop heats the chassis and eventually hangs resume

5 participants