You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New .12 report: DRM and DCP select3456x2234@120, but modetest with the compositor stopped measures about60 Hz over repeated page flips. Honeykrisp FIFO vkgears stays near60fps while MAILBOX exceeds500fps. The report does not yet distinguish physical60Hz scanout from completions on every second vblank.
Completion criteria: Compare firmware timing selection, actual swap-completion cadence and physical scanout; expose usable timing diagnostics if existing tracepoints are silent. A supported120Hz mode must have correct presentation/completion cadence, and60Hz/external modes must retain correct timing. Keep this separate from vkQuake’s throughput deficit and do not change mode labels to conceal it.
This separates the two: the panel scans out at 120 Hz, and the 60 Hz comes from the swap records on the 14.x path. Tested on the j516s with 2026.10.10.12 (a462e43). The patch below is rebased onto 5dcdeb8 and compiles there.
iomfb_v26_6_swap.h already describes it: with the swap record's presentation timing words all zero, swaps on the 120 Hz ProMotion panel complete 16.7 ms apart, and a non-zero "target long past" value makes the firmware present at 120 Hz. The 26.6 path sets them for J613 (dcp_v26_swap_set_timing(swap, 120)), and the M1/M2 template does too. dcp_v14_encode_swap() zeroes the record and never sets them, so T6030 swaps complete on every second refresh.
The patch adds two parameters, both default off:
t6030_swap_timestamps writes the three words (0x00, 0x08, 0x30, the 12.x/13.x/26.6 offsets) for T6030 swaps with a surface.
t6030_early_flip sends the flip event before dcp_v14_present(). dcp_v14_swap() blocks until the firmware completes the swap (about 2.75 ms with the timing words), so the compositor could not start its next frame until then. The next commit still waits on v14->lock. With Aquamarine's 3-buffer round-robin swapchain, the compositor renders into the buffer from two flips back, which is already off screen. A two-buffer client with direct scanout could see a released buffer early, which is why it is opt-in.
Test
Stock
Timing words
+ early flip
modetest -M apple -s 40@38:3456x2234 -v, sddm stopped
Over 5 s of fullscreen video with both on, all 600 swaps took 8.0 to 8.5 ms back to back, so the completion cadence is a steady 120 Hz. dcp-t6030failed stayed 0, and there was no flip failed, GPU fault or DEVICE LOST across five boots with the module, both parameters on from boot in the last. I timed the swap steps with a local debugfs histogram (A406 under 0.5 ms, A407 about 2.75 ms when the compositor submits late, 8.0 to 8.5 ms back to back). It is not in this patch.
I had the same issue on a MacBook Pro M3 Max and found a workaround: boot into macOS, open Display Settings, and change the refresh rate from 60 Hz to ProMotion. After booting back into Omarchy, the direct-display test went from 60.02 FPS to 120.18 FPS.
I verified that the fix in PR #182 was present and active in my Omarchy 4.5.0-3 installation. Before changing the macOS setting, I measured a consistent 15.18 ms between submitting a frame and the display firmware reporting completion, with completions arriving 16.67 ms apart. That’s consistent with 60 Hz pacing, though I cant really say at this stage how or where that's coming from.
My suspicion is that the macOS refresh-rate setting leaves persistent display or firmware state that carries across reboots. That’s a hypothesis for now; I have an M1 Pro that I’ll use to try to reproduce the behaviour.
Hardware isn’t my specialty, but an optional installer check recommending ProMotion or potentially just setting pro motion during install seems worth considering. I’ll keep digging and report back.
Kernel-side fix confirmed on J514S / T6030 (MacBook Pro 14", M3 Pro) — GNOME/mutter
Machine:apple,j514s / T6030 DCP, same 14.7 firmware generation as the OP's j516s Stack: Fedora Aurora Remix, kernel 7.3.0-36.fc44.aurora.aarch64 (built from aurora-silicon/linux @ 9219565939723cd5bc381941bc3978d52610d753), GNOME 50.6 / mutter on Wayland
Same behaviour as in the OP: the panel scans out at 120 Hz (T6030 display started: 3024x1890@120, 74 notch rows hidden) but mutter and everything on it pace at ~60 fps, because dcp_v14_encode_swap() zeroes the presentation timing words on the 14.x path.
With t6030_swap_timestampsandt6030_early_flip on, presentation is back at 120 Hz: UFO tester in Firefox reports ~120 fps and it looks right in real use. Several boots with both parameters on from boot — no GPU faults, no flip failed, no display errors.
Porting notes for this tree:
The aurora-silicon tree already ships the J613/25G83 equivalent — dcp_v14_swap_timestamps() in iomfb_v14_7_swap.h writes the same three offsets (0x00/0x08/0x30) with value 120 — so I wired the stamping hook to that instead of adding dcp_v14_swap_set_timing().
Condition: added !v14->external, dropped the surface check (blank swaps get stamped too). t6030_early_flip ported as-is.
Activity
aronvandepol commentedon Oct 11, 2026
This separates the two: the panel scans out at 120 Hz, and the 60 Hz comes from the swap records on the 14.x path. Tested on the j516s with 2026.10.10.12 (
a462e43). The patch below is rebased onto5dcdeb8and compiles there.iomfb_v26_6_swap.halready describes it: with the swap record's presentation timing words all zero, swaps on the 120 Hz ProMotion panel complete 16.7 ms apart, and a non-zero "target long past" value makes the firmware present at 120 Hz. The 26.6 path sets them for J613 (dcp_v26_swap_set_timing(swap, 120)), and the M1/M2 template does too.dcp_v14_encode_swap()zeroes the record and never sets them, so T6030 swaps complete on every second refresh.The patch adds two parameters, both default off:
t6030_swap_timestampswrites the three words (0x00, 0x08, 0x30, the 12.x/13.x/26.6 offsets) for T6030 swaps with a surface.t6030_early_flipsends the flip event beforedcp_v14_present().dcp_v14_swap()blocks until the firmware completes the swap (about 2.75 ms with the timing words), so the compositor could not start its next frame until then. The next commit still waits onv14->lock. With Aquamarine's 3-buffer round-robin swapchain, the compositor renders into the buffer from two flips back, which is already off screen. A two-buffer client with direct scanout could see a released buffer early, which is why it is opt-in.modetest -M apple -s 40@38:3456x2234 -v, sddm stoppedvkgears -fullscreen(FIFO), Hyprland 0.56.2vkgearswindowed (FIFO)Over 5 s of fullscreen video with both on, all 600 swaps took 8.0 to 8.5 ms back to back, so the completion cadence is a steady 120 Hz.
dcp-t6030failedstayed 0, and there was noflip failed, GPU fault orDEVICE LOSTacross five boots with the module, both parameters on from boot in the last. I timed the swap steps with a local debugfs histogram (A406 under 0.5 ms, A407 about 2.75 ms when the compositor submits late, 8.0 to 8.5 ms back to back). It is not in this patch.Patch (against 5dcdeb8)
JamesRoche commentedon Nov 6, 2026
I had the same issue on a MacBook Pro M3 Max and found a workaround: boot into macOS, open Display Settings, and change the refresh rate from 60 Hz to ProMotion. After booting back into Omarchy, the direct-display test went from 60.02 FPS to 120.18 FPS.
I verified that the fix in PR #182 was present and active in my Omarchy 4.5.0-3 installation. Before changing the macOS setting, I measured a consistent 15.18 ms between submitting a frame and the display firmware reporting completion, with completions arriving 16.67 ms apart. That’s consistent with 60 Hz pacing, though I cant really say at this stage how or where that's coming from.
My suspicion is that the macOS refresh-rate setting leaves persistent display or firmware state that carries across reboots. That’s a hypothesis for now; I have an M1 Pro that I’ll use to try to reproduce the behaviour.
Hardware isn’t my specialty, but an optional installer check recommending ProMotion or potentially just setting pro motion during install seems worth considering. I’ll keep digging and report back.
knalekar commentedon Nov 13, 2026
Kernel-side fix confirmed on J514S / T6030 (MacBook Pro 14", M3 Pro) — GNOME/mutter
Machine:
apple,j514s/ T6030 DCP, same 14.7 firmware generation as the OP's j516sStack: Fedora Aurora Remix, kernel
7.3.0-36.fc44.aurora.aarch64(built fromaurora-silicon/linux@9219565939723cd5bc381941bc3978d52610d753), GNOME 50.6 / mutter on WaylandSame behaviour as in the OP: the panel scans out at 120 Hz (
T6030 display started: 3024x1890@120, 74 notch rows hidden) but mutter and everything on it pace at ~60 fps, becausedcp_v14_encode_swap()zeroes the presentation timing words on the 14.x path.With
t6030_swap_timestampsandt6030_early_flipon, presentation is back at 120 Hz: UFO tester in Firefox reports ~120 fps and it looks right in real use. Several boots with both parameters on from boot — no GPU faults, noflip failed, no display errors.Porting notes for this tree:
dcp_v14_swap_timestamps()iniomfb_v14_7_swap.hwrites the same three offsets (0x00/0x08/0x30) with value 120 — so I wired the stamping hook to that instead of addingdcp_v14_swap_set_timing().!v14->external, dropped thesurfacecheck (blank swaps get stamped too).t6030_early_flipported as-is.