diff options
| -rw-r--r-- | archive/task-archive.org | 27 | ||||
| -rw-r--r-- | todo.org | 68 |
2 files changed, 68 insertions, 27 deletions
diff --git a/archive/task-archive.org b/archive/task-archive.org index 44f044b..f1185c5 100644 --- a/archive/task-archive.org +++ b/archive/task-archive.org @@ -3858,3 +3858,30 @@ systemd user environment, and probed from a throwaway frame: =(pgtk-backend-display-class)= → =GdkWaylandDisplay=, =*Warnings*= alive. Ratio still wants a reboot for =linux 7.1.9=. Pacnews to review there: =/etc/ssh/sshd_config.pacnew= and two =/etc/tpm2-tss/fapi-profiles/*.json=. +** DONE [#B] Function keys issue media actions instead of F-keys :bug:velox: +CLOSED: [2026-09-01 Tue] +:PROPERTIES: +:CREATED: [2026-08-19 Wed] +:LAST_REVIEWED: 2026-08-19 +:END: + +From the roam inbox, Craig's words: "function keys should issue F+number +functionality rather than their media functionality when the button is hit. +currently it's reversed and I have to hit function and the f button for F+number +functionality." + +Check first whether this belongs to archsetup at all. On a Framework the Fn-lock +is a firmware-level toggle held in the keyboard itself (Fn+Esc on most +revisions), not something the OS sets, in which case this is one keystroke +rather than a change here. If it is instead a hid/keyboard-module quirk, it is +ours. + +Grading: Minor severity (the keys work, they are on the wrong layer, and there +is a workaround) x every user every time (every F-key press) = P2 = [#B]. + +Resolved 2026-09-01: not ours, as the body suspected. The Fn layer is decided +in the EC (the keyboard reaches Linux as a plain AT keyboard on i8042), so no +OS-side knob exists. One keystroke: Fn+Esc toggles Fn Lock; Craig confirmed +F1-F12 now send F-keys by default. The EC holds the state across reboots; it +reverts only if the EC loses power (battery disconnect or mainboard reset), +which is likely why it flipped around the August reinstall. @@ -46,6 +46,47 @@ below): input-side-spec.org (DRAFT, four decisions open). * Archsetup Open Work +** TODO [#B] Ship the Framework 13 AMD internal-mic workaround in the installer :bug:velox:audio:solo: +:PROPERTIES: +:CREATED: [2026-10-06 Tue] +:LAST_REVIEWED: 2026-10-06 +:END: +From home's 2026-10-06 handoff, verified live the same morning. On velox +(Framework 13, Ryzen AI 9 HX 370, linux-lts 6.18.55, BIOS 04.02) the internal +microphone was dead in every app. Root cause is a known upstream kernel bug in +the AMD ACP PDM digital-mic path on the Ryzen AI 300 Framework 13: the DMIC +card (=acp-pdm-mach=, =hw:acppdmmach=) emits a constant full-scale rail (rms +0.99999) instead of audio, and with UCM on PipeWire exposes only that broken +DMIC as the internal mic (Framework community threads 81866 and 75748). + +Workaround home applied by hand, now live on velox: +=/etc/wireplumber/wireplumber.conf.d/50-disable-ucm.conf= sets +=monitor.alsa.properties { alsa.use-ucm = false }= and a =monitor.alsa.rules= +entry with =device.disabled = true= for +=alsa_card.pci-0000_c1_00.5-platform-acp-pdm-mach=, then =systemctl --user +restart wireplumber=. The ALC285 falls back to its analog-stereo profile whose +Internal Microphone pin (0x12) carries real audio; the default source is +=alsa_input.pci-0000_c1_00.6.analog-stereo=, port =analog-input-internal-mic=, +with the source volume lowered because the analog path stacks +30 dB capture +on +30 dB boost. Revert: delete the file and restart wireplumber. + +What the installer needs: write that drop-in on this hardware only (gate on +the =acp-pdm-mach= card or the Framework 13 AMD board id, not on the +hostname), beside the existing pipewire/wireplumber package install, with a +fixture test in the installer-steps suite. The live file on velox is the +reference content. The audio failure taxonomy already lists =use-ucm= both +ways as an audio-doctor AUTO remedy +([[file:docs/design/2026-07-10-audio-failure-taxonomy.org][docs/design/2026-07-10-audio-failure-taxonomy.org]]), so the +doctor's remedy and this drop-in should agree. The standing re-check after +each kernel update (remove the drop-in once the upstream fix lands, UCM back +on) lives in velox's machine notes, the KB node "velox's internal mic needs +UCM off and the ACP PDM card disabled until the AMD digital-mic kernel bug is +fixed", linked from the velox hardware node's neighbourhood, not in this +one-shot task. + +Verify: =pactl get-default-source= names the analog-stereo source, and a +short =arecord= of the internal mic has an rms well below 0.99. + ** TODO [#B] calendar-sync fails headless after every boot until authinfo is unlocked :bug:dotfiles:gpg: :PROPERTIES: :LAST_REVIEWED: 2026-10-04 @@ -5644,33 +5685,6 @@ problem is separate and unchanged. repair_tunnel_dot_off (dotfiles net/src/net/repair.py) puts a tunnel link back to its DoT mode when turning DoT off didn't bring names back, and the evidence says "put back to <mode>" only when that restore succeeded. The restore-declined branch has no direct test. Give fake-resolvectl a second failure switch (FAKE_RESOLVECTL_DOT_RESTORE_FAIL) so the wording can be asserted absent as well as present. Follow-up from the f56fd1a review. * Archsetup Resolved -** DONE [#B] Function keys issue media actions instead of F-keys :bug:velox: -CLOSED: [2026-09-01 Tue] -:PROPERTIES: -:CREATED: [2026-08-19 Wed] -:LAST_REVIEWED: 2026-08-19 -:END: - -From the roam inbox, Craig's words: "function keys should issue F+number -functionality rather than their media functionality when the button is hit. -currently it's reversed and I have to hit function and the f button for F+number -functionality." - -Check first whether this belongs to archsetup at all. On a Framework the Fn-lock -is a firmware-level toggle held in the keyboard itself (Fn+Esc on most -revisions), not something the OS sets, in which case this is one keystroke -rather than a change here. If it is instead a hid/keyboard-module quirk, it is -ours. - -Grading: Minor severity (the keys work, they are on the wrong layer, and there -is a workaround) x every user every time (every F-key press) = P2 = [#B]. - -Resolved 2026-09-01: not ours, as the body suspected. The Fn layer is decided -in the EC (the keyboard reaches Linux as a plain AT keyboard on i8042), so no -OS-side knob exists. One keystroke: Fn+Esc toggles Fn Lock; Craig confirmed -F1-F12 now send F-keys by default. The EC holds the state across reboots; it -reverts only if the EC loses power (battery disconnect or mainboard reset), -which is likely why it flipped around the August reinstall. ** DONE [#A] Lock-screen clock stale after a real sleep :bug:hyprland:dotfiles:velox: CLOSED: [2026-09-13 Sun] SCHEDULED: <2026-08-25 Tue> :PROPERTIES: |