Repository navigation
Conversation
…icon Plugging a monitor into an M1 and getting nothing is expected on Asahi today, but nothing says so. No t8103 device tree enables dcpext, the second display controller, so there is no controller for an external display to attach to. Everything below that in the chain is already merged and works, and every layer fails silently: no error in dmesg, nothing in the compositor log, and each failure looks like the one before it from userspace. Two things also mislead people here. A monitor with a USB hub enumerates a Billboard device, which reads like a failed alt mode and says nothing either way. And with DisplayPort pin assignment C all four lanes carry DP and USB drops to 2.0, so losing SuperSpeed is what success looks like, not a bad cable. Adds: - omarchy-hw-dp-altmode, which returns true only when a USB-C connector carries the displayport phandle AND the node it names is enabled. Either half alone is a half-configured machine, and reporting success there sends someone hunting a cable fault that does not exist. - omarchy debug dp-altmode, which walks the chain in order and stops at the first thing missing, saying plainly that the stock state is expected rather than a fault. - docs/apple-silicon-dp-altmode.md. Both resolve the port by i2c address, never by the portN index: that index is assigned in i2c probe order and the same physical port was observed as port1 on one boot and port0 on the next. Enabling the feature is deliberately out of scope here. It needs a patched device tree plus two out-of-tree modules, and a kernel update silently reverts all of it, so it is not safe to turn on by default in a distribution that updates kernels unattended.
|
Hey @scottjones |
scottjones
left a comment
There was a problem hiding this comment.
The tooling here is better than the description suggests, and I want the doc — "why does nothing happen when I plug in a monitor" is a real support question. Four things to fix first, one of which sends readers somewhere I do not think we want to send them.
What I verified on an M2 Max (apple,j414c, t6021): omarchy-hw-dp-altmode does not look for a node called dcpext — it follows each USB-PD connector's displayport phandle to the controller it names and checks that node's status. That generalises past M1 nicely. This machine has no dcpext at all, just three dcp@ nodes (two okay, one disabled), and no connector exposes a displayport property, so the detector correctly returns 1. Its test passes and catches an inverted status check when I mutate the detector. omarchy commands --check is clean at 455.
1. The doc never mentions the fairydust branch. Asahi has implemented DP alt mode on the fairydust branch of their downstream tree — DCP, DPXBAR, ATCPHY and ACE, demoed at 39C3 with an M1 Air driving a display over USB-C. It is experimental (one blessed port per machine, cold/hot-plug quirks, "provided strictly as-is", no support until they deem it ready), but it is the canonical work and it is converging upstream.
Right now the "Enabling it" section says M1 needs "a patched device tree plus two out-of-tree kernel modules" and sends readers to github.com/haripako/dp-altmode. A reader comes away thinking the only route is a stranger's patches, when the project itself has a named branch. Please name fairydust, describe its limits honestly, and keep your own work as the additional reference rather than the primary one.
This also makes "no t8103 device tree enables dcpext, not even in asahi-wip-7.2" read as more settled than it is — true of the branches named, misleading about the project, since fairydust is where that changes.
2. The doc never mentions HDMI, and on many of these machines HDMI works. Zero occurrences in 288 lines. This MacBook Pro 14" M2 Max has a live HDMI connector:
card2-HDMI-A-1 disconnected
card2-eDP-1 connected
Someone on a 14"/16" machine reading "external display does nothing on Apple Silicon" would reasonably conclude they cannot drive an external monitor at all, with a working port beside them. One sentence putting HDMI outside the scope fixes it.
3. omarchy-debug-dp-altmode calls the detector by bare name, which fails when run from a checkout rather than an installed PATH:
bin/omarchy-debug-dp-altmode: line 32: omarchy-hw-dp-altmode: command not found
External DP controller (dcpext): NOT enabled
It prints "NOT enabled" either way, so a missing command and a real negative look identical — the worst failure mode for a diagnostic. Worth resolving through $OMARCHY_PATH/bin or checking the command exists before reporting.
4. The explanation is t8103-specific but the title says "Apple Silicon". On t6021 the shape differs — three dcp nodes, no dcpext, no displayport property on any connector — while the outcome matches. Stating the outcome generally and keeping the t8103 detail as the M1 example would cover both without claiming more than is known.
**Point to Asahi's own work first.** The doc described the only route as a patched device tree plus out-of-tree modules and sent readers to a third-party repository, which reads as if the project had nothing. It does: `fairydust` carries the device tree changes for t8103, t8112 and t60xx plus the `tipd` change that forwards the hotplug event to DRM, and it is what converges upstream. Named it, and took it on its own terms — its commits are titled "dp-altmode dts hacks" and "HACK: Use drm oob hotplug event" by their own authors, it blesses one specific port per machine, and it is experimental. The third-party writeup is now explicitly an additional reference that backports the fairydust change unmodified, not a substitute. That also removes the "not even in asahi-wip-7.2" claim, which was true of the branches named and misleading about the project. **HDMI was never mentioned in 288 lines.** On the 14"/16" MacBook Pros and the Mac mini it works and appears as its own connector, so "external display does nothing on Apple Silicon" would tell someone with a working port beside them that they cannot drive a monitor. Scoped to DisplayPort over USB-C in the doc, in the command's header comment, and in its first line of output. **A missing detector read exactly like a real negative.** The diagnostic called `omarchy-hw-dp-altmode` by bare name, so from a checkout it printed `command not found` and then "NOT enabled" — the worst failure mode a diagnostic has. It now resolves the copy next to itself first, so a checkout answers for itself, then `$OMARCHY_PATH/bin`, then PATH, and exits 1 with a message if there is none. Two tests cover it. **Generalised past t8103.** The outcome is stated generally, with M1 as the worked example and the t6021 shape recorded beside it: no `dcpext` node at all, several `dcp@` nodes, no connector carrying `displayport`. The output label no longer says "dcpext", since on t6021 no such node exists. Suite is 11 checks, up from 7. `omarchy commands --check` passes at 455.
|
Thanks — all four are fixed in 273e939, and the fairydust one was the right call to push back on. 1. fairydust. You are right that the omission changed what the doc meant. The irony is that the linked repository credits fairydust throughout — its Named now, and described on its own terms rather than as a recommendation: the device tree changes for t8103, t8112 and t60xx plus the That also took out "not even in One thing your review gave me: the t8103 commit names the blessed port per machine, so the doc now lists them — front-left USB-C on the 13" Pro and Air, next to HDMI on the mini, back-left on the 2-port iMac, back-right-middle on the 4-port. More useful than "one port per machine". 2. HDMI. Fair, and the framing was the problem more than the omission. Scoped in three places: the doc's second paragraph, the command's header comment, and its first line of output, which now says HDMI is a separate path not covered here. 3. The bare-name call. That one was a real defect and your diagnosis of why it was the worst kind was exact — a missing command and a real negative were indistinguishable. It now resolves the copy next to the running script first, so a checkout answers for itself, then 4. Generalising past t8103. The outcome is stated generally now, with M1 as the worked example and your t6021 findings recorded beside it — no Suite is 11 checks, up from 7. |
scottjones
left a comment
There was a problem hiding this comment.
Thanks for the rework — the three things I raised last time are all properly handled now: fairydust is named as Asahi's own branch, HDMI is explicitly scoped out, and the detector lookup no longer reports a missing binary as a negative result. Each has a test. The doc itself is the valuable part of this PR, and the "every layer fails silently" framing is exactly right about why this is so expensive to diagnose.
I verified the rest on an M2 Max (apple,j414c, t6021) running Asahi, and found two things that need fixing before this lands.
1. omarchy-hw-dp-altmode cannot return 0 on any Apple Silicon Mac
The detector requires a displayport phandle property on a USB-C connector node. I grepped every Apple DTB shipped with this machine's kernel (7.1.6):
20 Apple DTBs (t8103, t6000/1/2, t6020/21/22, t8112)
displayport property: 0 of 20
usb-c-connector: 20 of 20
dcpext: 20 of 20
Zero — including t8103-j293.dtb, the exact machine the test fixture models. The property name does not appear anywhere in any of them.
On real hardware the connectors use the standard OF graph binding instead:
soc/i2c@39b040000/usb-pd@38/connector label = "USB-C Left Rear"
ports/port@0/endpoint -> soc/usb@702280000/ports/port@0/endpoint
ports/port@1/endpoint -> soc/phy@703000000/ports/port@0/endpoint
USB controller and Type-C PHY. No DisplayPort endpoint, no displayport property.
So the positive branch is unreachable and the command returns 1 unconditionally, forever, on every Apple Silicon machine. I confirmed it by building a fixture that mirrors this machine's real DTB shape with a dcpext node present and status = "okay" — the state where the route is enabled — and the detector still returned 1.
The suite passes because make_tree constructs the shape the detector assumes rather than the shape the kernel actually exposes. Worth pointing the fixture at a real DTB layout; the mismatch is invisible otherwise.
2. The t6021 claim in the doc is inverted
The doc says:
M2 Pro/Max (t6021) — there is no
dcpextnode at all, just severaldcp@nodes
On this t6021 there are three display controllers, and two of them are dcpext:
dcp@289c00000 apple,t6020-dcpext apple,dcpext status=okay <- enabled
dcp@315c00000 apple,t6020-dcpext apple,dcpext status=disabled
dcp@389c00000 apple,t6020-dcp apple,dcp status=okay <- internal panel
dcpext exists and one instance is enabled. What's true is that the node names are all dcp@ — "dcpext-ness" lives in the compatible string. That also means the soc/dcpext*@* glob matches nothing on real hardware, while soc/dcp*@* matches the internal panel controller, so the external-vs-internal half of the check isn't actually being made either.
This one goes beyond the detector: if a dcpext is enabled on this machine and external DP over USB-C still does nothing, then "the second controller is left disabled" isn't the explanation the doc is built around. Worth re-checking that on t8103 too before settling the wording — the compatible string is the thing to read, not the node name.
Suggestion
The honest signal available on every machine is the compatible string plus status, so keying on apple,*dcpext would at least be measuring something real. But given an enabled dcpext here still doesn't produce a working external display, I'm not sure the DTB can answer "does DP alt-mode work" on its own — in which case a detector that always says no is worse than no detector, because it reads as a definitive answer. It would be reasonable to land the doc and the diagnostic on their own and drop omarchy-hw-dp-altmode, or have it report an explicit "cannot determine" state.
Happy to re-test whatever you land on — this machine has the hardware and I still have the DTB comparison set up.
|
Thanks for going back to the hardware on this one. Points 2 and the glob observation are right and I'm fixing both. On the central claim I disagree, and I think we've found the thing neither of us had stated: you are testing on a stock DTB and I am testing on a patched one. That single fact explains the whole disagreement. 1. The positive branch is reachable — it is taken on this machineYour grep is correct and I reproduced it: of the 23 Apple Silicon DTBs shipped with 7.1.6 here (t8103, t600x, t602x, t8112), zero carry a But that is the stock tree. This M1 ( Comparing the two DTBs for this exact machine side by side:
So the command does not return 1 unconditionally and forever. It returns 1 on a stock tree — which is the correct answer, because DP alt mode genuinely does not work there — and 0 once the route is actually wired up. That is the distinction the check exists to make, and why it reads the live tree rather than the model. On why your fixture still returned 1 with The suite also already has a stock-state case asserting 1, so the fixtures aren't only modelling the shape that succeeds. Your underlying point still lands though: they are hand-built rather than derived from a real DTB, and I'll re-point them at the real stock and patched shapes so the difference is visible in the test rather than in this thread. I should have said in the PR that this machine runs a patched tree. Without that, your grep and my results look like a contradiction instead of the two ends of the same check. 2. The
|
The external display controller is named dcp@ like the internal one on every machine: t8103 exposes it as dcp@271c00000 with compatible "apple,t8103-dcpext", and t6020 does the same. The "dcpext@" glob therefore matched nothing anywhere, and "dcp@" matched both controllers, so the external-vs-internal distinction was resting entirely on the phandle rather than on anything the check itself asserted. Read the compatible string instead, which is where dcpext-ness actually lives, and drop the dead glob. Reshape the fixture after the real t8103-j293 tree as the kernel exposes it: both controllers present, named dcp@, carrying their compatible strings, with the internal one enabled as it always is. The previous fixture had only the external node, so a check keyed on the node name could not be caught failing. Add a case for a connector whose phandle names the internal controller, which the node-name glob accepted and the compatible check rejects. Verified on an M1 (apple,j293, t8103): the detector still exits 0 against the live patched tree, and the suite is 12 checks.
…d one The t6021 paragraph was inverted: that machine does have dcpext, two of its three display controllers are apple,t6020-dcpext, and one of those is enabled. Corrected from the review, with the consequence stated -- an enabled external controller there still yields no external display, so a disabled controller is not the whole explanation on t6021. What both shapes share is that no connector is wired to the controller at all. Say plainly that no machine names the node dcpext, since that is what makes a name-based check look reasonable and be wrong. Record what the check answers on each kind of tree. On a stock tree it reports the route as not enabled, which is correct and is where nearly every machine sits; it reports enabled only once a tree wires a connector to an enabled external controller. The M1 this was written against runs such a tree, which is why it can be seen returning both answers. Without that stated, a stock-tree result and a patched-tree result read as a contradiction rather than as the check working. Lead the explanation with the missing connector wiring rather than the disabled controller, since only the former holds on both SoCs. Suite is 13 checks.
|
Pushed as Compatible string instead of the node-name glob. The Fixtures reshaped after the real tree. Both controllers are now present and both are named Worth noting the fixture already used t6021 corrected, including the consequence you drew: an enabled external controller there still produces no external display, so a disabled controller is not the whole explanation on t6021. The doc now leads with the connector wiring, since that is the part that holds on both shapes, and says plainly that no machine names the node Stock versus patched is now stated. The doc records that on a stock tree the check reports the route as not enabled — correct, and where nearly every machine sits — and that it reports enabled only once a tree wires a connector to an enabled external controller, which the M1 this was written against does. Two greps assert it stays there. Suite is 13 checks, If you re-test on the j414c, a stock tree should give exit 1 from the connector half — no |
|
Hardware note from a stock Omarchy Mac install, if a t8112 fixture would help. Machine: Apple MacBook Air 13" M2 2022 ( Live tree matches the stock USB-C connectors (no
So t8112 stock DTB comparison (this kernel, no
The Mini line is the useful contrast: Two extra silent-failure gotchas on this box, if you want them in the “looks like a fault and is not” section:
Hyprland is already Happy to re-run |
Reported from a stock M2 Air (apple,j413) and confirmed here against the shipped DTBs. t8112 was the shape the doc did not name, and it carries the clearest evidence for testing both halves rather than one: the M2 mini (j473) ships apple,t8112-dcpext and its dptx-phy both enabled, and still has no displayport property on any USB-C connector. A check keyed on an enabled controller alone would report that machine as working. Record the likely reason an enabled controller shows up at all -- it appears to serve HDMI, and the machines that have it enabled are the ones with an HDMI port -- with the caveat that t8103 does not fit cleanly: the M1 mini has HDMI, ships dcpext disabled, and no t8103 tree carries the dptx-phy binding at all. Add the DisplayLink case to the section of things that look like faults. Adapters sold as DisplayPort are frequently DisplayLink USB graphics, which fail in exactly the shape this doc describes for an unrelated reason; the vendor id 17e9 is what tells them apart. Add the kernel messages from the layers that do work, which read like faults to someone already hunting for one. Suite is 15 checks.
|
@adamkstinson This is exactly the data the PR was missing — thank you. All of it is in as of t8112 is now the third named shape, and The DisplayLink case is in the section of things that look like faults, with Your reading of what the detector does on your Air is right: it exits 1 on the connector half first, before the controller half is ever reached. The command is in this branch now if you want that re-run. @scottjones Your open question from the last review — an enabled dcpext on t6021 that still produces nothing — I think this answers, or at least points at the answer. The enabled controller appears to serve HDMI, not USB-C. On t8112 the only machine of the four with One caveat, because it does not generalise cleanly. t8103 does not fit: the M1 mini ( If it holds, it also removes the reason to drop the detector. The Suite is 15 checks. |
|
Follow-up from the same This is the patched-tree counterpart of the stock dump I posted earlier. I have not seen a published t8112 field report before, so here is the exact shape and the four commits. What was appliedPatches pulled verbatim from
Install method, same architecture as haripako's t8103 repo:
Both halves are required. DTB alone produces Live tree after the DT change (vs the stock dump)
That is exactly the dual-half signal the detector is written for: connector phandle and enabled DRM / Hyprland with the monitor on front-left: Kernel path that actually lights it (tipd HPD → apple-dcp):
What is not this patch (still true, and easy to misread)
Happy to dump the patched |
|
One more t8112 gotcha, now that the patched
That loads before rootfs. The
Fix: after sudo mkinitcpio -P
lsinitcpio /boot/initramfs-linux-asahi.img | grep tps6598x
# want:
# …/updates/tps6598x-core.ko
# …/tipd/tps6598x.ko # i2c glue, stock, fine
# must not have:
# …/kernel/drivers/usb/typec/tipd/tps6598x-core.koConfirmed on this box after
|
scottjones
left a comment
There was a problem hiding this comment.
Withdrawing my central objection from the last review. I said omarchy-hw-dp-altmode cannot return 0 on any Apple Silicon Mac. You answered that correctly on Sept 2 and I should have replied then rather than leaving a CHANGES_REQUESTED standing over it for three days.
You were right about the cause: I was reading a stock DTB and you were running a patched one, and that single fact accounts for the whole disagreement. My fixture supplied the enabled controller without the connector phandle, which is the half-configured state the check is explicitly written to reject — the suite already had a case asserting exactly that, and I read it as a bug instead of as the design.
What settles it beyond your machine is @adamkstinson's j473: a stock M2 mini shipping apple,t8112-dcpext and its dptx-phy enabled, with no displayport property on any USB-C connector. A controller-only check reports that machine as working. That is the dual-half design justified on hardware nobody has patched, and it is a better argument than anything in my review. His two field reports are the most useful thing in this thread.
t6021 hardware session
You asked twice for this shape and nobody had it. Ran it on the M2 Max (apple,j414c, t6021), stock tree, with an external display physically plugged into the front-left USB-C port:
port2 = i2c 0-003f = usb-pd@3f = "USB-C Left Front" <- cable here
usb-pd@38 USB-C Left Rear displayport: absent
usb-pd@3b USB-C Right displayport: absent
usb-pd@3f USB-C Left Front displayport: absent
dcp@289c00000 apple,t6020-dcpext,apple,dcpext status=okay
dcp@315c00000 apple,t6020-dcpext,apple,dcpext status=disabled
dcp@389c00000 apple,t6020-dcp,apple,dcp status=okay
omarchy-hw-dp-altmode -> 1
The partner attaches and advertises zero DP alt-modes, no DRM connector is created, and the only DCP activity in the log is 389c00000.dcp — the internal controller. No oob_hotplug, no dcp_dptx_connect. The detector's answer is correct, and it fails on the connector half first, exactly as you predicted for a stock tree.
Your HDMI reading is consistent here too: this machine has a live card2-HDMI-A-1 alongside the enabled dcpext, which fits "the enabled external controller serves HDMI, and nothing wires a USB-C connector to one." Not proof, but it is the t60xx data point behind the reservation you stated.
Also verified: router integration (omarchy debug dp-altmode and omarchy hw dp-altmode both resolve and return correctly, 1 and 0 respectively), all 15 tests pass, and omarchy commands --check passes at 458 — matching your number exactly.
The one blocker
test/all fails on a single assertion, not ok - bin commands use command helpers. It is bin/omarchy-debug-dp-altmode:27:
[[ -n ${hw_dp_altmode:-} ]] || hw_dp_altmode=$(command -v omarchy-hw-dp-altmode || true)test/shell.d/bin-style-test.sh:7 forbids raw command -v in bin/ outside a small allowlist.
Deleting that line fixes it, and I verified the deletion rather than guessing:
bin-style-test.sh after deleting line 27 -> PASS
dp-altmode-test.sh after deleting line 27 -> PASS (not load-bearing)
Lines 22-26 already try $SELF_BIN/omarchy-hw-dp-altmode then $OMARCHY_PATH/bin/..., which cover the checkout case and the installed case, and still exit 1 with a message when neither resolves — so the loud-failure behaviour you added for my earlier review survives intact.
Please delete the line rather than widening the allowlist. #343 widens that same single-line regex (mac-(setup|asahi-install)$), so an allowlist entry here would collide with it on one line — the worst kind of merge conflict. Deleting also matches AGENTS.md, which says commands from the default package set are runtime invariants to be invoked directly; the detector ships in this same PR.
For completeness, the full suite locally is 3 of 249 files failing: this one plus config-test.sh and unowned-system-paths-test.sh. Both of the latter pass once OMARCHY_PKGS_PATH is set, which is why CI reports one failure and not three. One run reported "4 of 249" with the same three assertions and a clean rerun gave 3, so there may be a flaky file somewhere — I only saw it once and can't pin it down; mentioning it as an observation, not a claim against this branch.
Two suggestions
Move the display-connectors block above the stock-tree exit 0. Right now the port table, the cable position and the connector list all live after that early exit, so on a stock tree — which is nearly every machine, and the entire audience for this doc — none of it prints.
I originally talked myself out of this on the grounds that every port row reads DisplayPort: no on a stock tree, so the table is not actionable. Then someone with a monitor plugged in read the output and asked "so it didn't detect that I'm plugged in?" That is the gap: the tool knows a cable is in 0-003f, knows no port has DisplayPort wired, and knows no new DRM connector appeared, and it reports none of it. The connector list is the piece that matters most, because it is what separates @adamkstinson's DisplayLink dock from the alt-mode gap — a dock enumerates USB and creates no connector, which looks identical to this from userspace. Even one line naming the port the cable is in would close it.
@adamkstinson's mkinitcpio -P finding is not in the doc. He posted it 2026-09-04 00:41, after your last push at 09-03 18:05. Asahi's initramfs ships the stock tps6598x-core.ko, which shadows the updates/ copy, so a patched tipd silently does nothing after reboot while DP-1 still exists. That is precisely the class of silent failure this document is for, and it will bite anyone following the enablement path.
Delete line 27 and I will approve immediately. Sorry again for sitting on the last review — the disagreement was resolved by your Sept 2 comment and I left it blocking anyway.
|
Hardware validation (stock Asahi) — MacBook Air M1 j313, with USB-C↔USB-C monitor plugged
With monitor plugged
Live device-tree (unchanged by the plug):
So on real j313 stock: detector exit Happy to re-run after the |
|
The remaining blocker is mechanical and CI is showing it: remove the raw command -v fallback in omarchy-debug-dp-altmode. The two explicit detector paths already cover checkout and installed use. |
|
Can confirm this also reproduces on MacBook Air M2 (t8112), not just t8103 — so the Tested on Asahi/Omarchy (ALARM base), booted into the
Ended up fully removing the fairydust build afterward since it didn't move the needle for this model. Happy to test |
|
Strong support for documenting this — the silent-failure point is exactly right. One premise has gone stale since it was written, though, and it changes what the doc should say. The feature is reachable today
True of the release branches, but Asahi's
It does not require shipping a kernel forkThis seems worth folding into the scope note, because it's a much lighter lift than it looks. Against the packaged
The tipd half builds out-of-tree against (One build detail that will bite: compiling the DTB needs Asahi's patched Two more silent failures worth encoding in
|
M1 Mac mini (j274/t8103) USB-C display field result — 2026-09-29I tested a direct USB-C connection from an M1 Mac mini (2020, Result: the ASUS appeared as DRM Two bring-up details may help others diagnose an apparently dead connection:
Limit: this proves one direct-display reconnect and one successful desktop boot. It does not establish repeated hotplug, suspend/resume, docked display, or durable installation. The test's recovery service restored the original m1n1 boot bundle after the patched DTB had loaded, so the next ordinary boot has not been shown to retain USB-C display support. GRUB remains on its stock default for that reason. This may be useful context for the doc's distinction between a wired device-tree route and a working display, and for noting the newer Aurora path alongside Fairydust. I can provide a focused, redacted journal/DT capture if it would help the review. Field report assembled with Codex assistance; hardware observations were checked on the M1 Mac mini. |
Plugging an external monitor into an Apple Silicon Mac and getting nothing is
expected on Asahi today, but nothing in Omarchy says so. This adds the
explanation and the two commands to check it. It does not enable the feature —
see the scope note at the end.
The problem
Apple Silicon has two display controllers:
dcpfor the internal panel anddcpextfor anything external. No t8103 device tree enablesdcpext, noteven in
asahi-wip-7.2, so there is no controller for an external display toattach to. Asahi marks DisplayPort alt mode on M1 as work in progress.
Everything below that in the chain is already merged and works: the Type-C PHY
does DP mode, the display crossbar is wired, and the cd321x driver registers the
port altmodes, switches the mux and reads DisplayPort status.
What makes it expensive to diagnose is that every layer fails silently. No
error in
dmesg, nothing in the compositor log, and each failure looks exactlylike the one before it from userspace. Two things also actively mislead:
like a failed alt mode and says nothing either way.
2.0, so losing SuperSpeed is what success looks like, not a bad cable.
What this adds
omarchy debug dp-altmode— walks the chain in order, stops at the firstthing missing, and says plainly that the stock state is expected rather than a
fault. No root, reads only.
omarchy-hw-dp-altmode— hidden, for conditionals. Returns true only whena USB-C connector carries the
displayportphandle and the node it namesis enabled. Either half alone is a half-configured machine, and reporting
success there sends someone hunting a cable fault that does not exist.
docs/apple-silicon-dp-altmode.mdtest/shell.d/dp-altmode-test.sh— 7 checks against device tree fixtures.Both resolve the port by i2c address, never by the
portNindex. That indexis assigned in i2c probe order and the same physical port was observed as
port1on one boot andport0on the next.Scope: this deliberately does not enable the feature
Making external DisplayPort actually work on M1 needs a patched device tree plus
two out-of-tree kernel modules. A kernel update overwrites the modules and
leaves the DTB frozen at the old version, silently — the display just stops
working after an update, with no error. I do not think that is safe to ship
default-on in a distribution that updates kernels unattended, and it would want
a post-update guard that fails loudly first. Happy to follow up with that as a
separate PR if you want it.
Credit and status, for the record
https://github.com/haripako/dp-altmode
Grunau's and Sven Peter's from the
fairydustbranch, backported unchanged.->crashedon a powerofftimeout, which permanently rejects every atomic commit). It is not fixed in
fairydusteither, and is being sent to AsahiLinux/linux separately.DCPAVSERVservice blocks reconnection until reboot. It is not proven that suspend is the
trigger. Written up in that repo.
Testing
test/shell.d/dp-altmode-test.shpasses (7/7). The full shell suite was run:the only failures are the three that need the
omarchy-pkgssibling checkout(
config,preinstalls,unowned-system-paths), which fail the same waywithout this change.