Recover an AMD desktop that hard-freezes seconds after login since ddcutil 3.0.0
Symptom, Omarchy trigger and fix hold. omarchy#11499 (open) has the quoted kernel log, the RX 7600, the shell call chain down to ddcutil --skip-ddc-checks detect --brief, the $XDG_RUNTIME_DIR cache point and the 2.2.7 versus 3.0.0 A/B. /usr/share/omarchy/bin/omarchy-brightness-display-ddc on 4.0.4-1 matches. rockowitz/ddcutil#629 has the 7900 XT/XTX and 9070 XT confirmations under KDE PowerDevil. The v3.0.2 release (2026-09-23) says it replaces 3.0.0 and 3.0.1 and disables the multi-message EDID ioctl, which 'may also have triggered' the amdgpu crash. Arch extra JSON shows ddcutil 3.0.2-1 built 2026-09-23. limine-snapper-restore is owned by limine-snapper-sync here, and the ALPM guard (/usr/bin/omarchy-update-pacman-guard) only aborts transactions carrying both -S and -u, so the pacman -U downgrade is not blocked. The defect is the cause. It names the multi-message EDID ioctl as the trigger, but in #629 the maintainer identified the immediate trigger as 3.0.0's lower default for async (threaded) I2C bus checks, reset it to 99 in 3.0.1 (2026-09-13), and most reporters confirmed 3.0.1 fixed the freeze. The multi-message read was a later hunch for the few who still froze on 3.0.1, and the 3.0.2 notes say only that it may have contributed. The cause is rewritten to match. Not exercised: this workstation has ddcutil 2.2.7-1 and no affected Radeon.
Restoring a snapshot rolls back every package and system file changed since it was taken. Holding a package with IgnorePkg leaves it behind future upgrades. Remove the hold once a fixed release works for you, or the downgraded ddcutil can drift out of step with its libraries.
Symptom
Right after an update, every login freezes the whole machine 2 to 12 seconds after Hyprland starts. Mouse, keyboard and Ctrl+Alt+F2 are dead and only a hard reset works. After a reboot, journalctl -k -b -1 shows:
ddcutil[2344]: (i2c_ioctl_reader1) Error in ioctl() read, rc=-1, errno=EIO(-5): Input/output error, device=/dev/i2c-0
amdgpu 0000:03:00.0: Failed to set workload mask 0x00000001
amdgpu 0000:03:00.0: SMU is in hanged state, failed to send smu message!
amdgpu 0000:03:00.0: Failed to disable gfxoff!
Reported on discrete Radeon RX 7600, 7900 XT/XTX and 9070 XT with an external monitor.
Cause
ddcutil 3.0.0 (Arch extra, 2026-09-12) changed how it probes I2C buses, and on some discrete Radeon cards that probing is followed within seconds by an amdgpu SMU hang. In rockowitz/ddcutil#629 the maintainer traced the main trigger to 3.0.0 lowering the default for asynchronous (threaded) bus checks (--i2c-bus-checks-async-min), and reset it in 3.0.1 (2026-09-13). Most reporters confirmed 3.0.1 fixed the freeze, but a few still froze. 3.0.2 (2026-09-23) replaces 3.0.0 and 3.0.1 and also disables the single multi-message ioctl EDID read that 3.0.0 introduced, which its release notes say may have triggered the amdgpu crash. Omarchy hits it at every login on desktops with external monitors because the shell's monitor panel runs omarchy-brightness-display-ddc, which calls ddcutil --skip-ddc-checks detect --brief, and its bus cache lives in $XDG_RUNTIME_DIR, so it is empty at each login and detect always runs (omarchy#11499, with an A/B on ddcutil 2.2.7 versus 3.0.0). KDE PowerDevil users hit the same thing through libddcutil. Arch extra carried 3.0.2-1 when this was checked on 2026-10-05.
Fix
You need a working system without the graphical session running long enough to change the package.
**Omarchy 4: boot a snapshot from before the update.** At the Limine menu open the Snapshots submenu and boot the snapshot taken before the update that brought in ddcutil 3.0.0. Then make it permanent and update again, which now pulls a fixed ddcutil:
sudo limine-snapper-restore
# reboot into the restored system, then:
pacman -Q ddcutil
omarchy update
**Plain Arch, or if you can get a shell another way** (ssh from another machine, or a live USB plus arch-chroot): check the version and move off 3.0.0.
pacman -Q ddcutil
# Plain Arch: a full upgrade brings 3.0.2 or later
sudo pacman -Syu
# Omarchy 4: the ALPM guard refuses -Syu, use
omarchy update
If a 3.0.x release still freezes your card, downgrade to 2.2.7 from the Arch archive and hold it:
sudo pacman -U https://archive.archlinux.org/packages/d/ddcutil/ddcutil-2.2.7-1-x86_64.pkg.tar.zst
sudo sed -i 's/^#\?IgnorePkg *=.*/IgnorePkg = ddcutil/' /etc/pacman.conf
grep '^IgnorePkg' /etc/pacman.conf
Check that IgnorePkg line by eye: if you already held other packages, add ddcutil to the existing list instead of replacing it.
Verify
pacman -Q ddcutil shows 3.0.2 or later (or the held 2.2.7). Two or three logins in a row stay responsive, and journalctl -k -b | grep -i 'SMU is in hanged state' returns nothing.