[Laptop 16] Framework 16 AMD 7040, BIOS 4.05: PD1 warning reports 2.0.0C, but direct reads show 0.0.21; intermittent touchpad failure

[piotr-yuxuan]

System Model or SKU

Framework Laptop 16 (AMD Ryzen™ 7040 Series)

BIOS Version

04.05

Port/Peripheral Information

Command inxi -Fx returns:

System:
  Host: Kernel: 7.2.4 arch: x86_64 bits: 64 compiler: gcc v: 15.2.0
  Desktop: GNOME v: 50.4 Distro: NixOS 26.05 (Yarara)
Machine:
  Type: Laptop System: Framework product: Laptop 16 (AMD Ryzen 7040 Series)
    v: A7 serial: <superuser required>
  Mobo: Framework model: FRANMZCP07 v: A7 serial: <superuser required>
    Firmware: UEFI vendor: INSYDE v: 04.05 date: 06/30/2026
Battery:
  ID-1: BAT1 charge: 44.7 Wh (58.8%) condition: 76/85 Wh (89.4%) volts: 15.71
    min: 15.48 model: NVT FRANDBA status: not charging
CPU:
  Info: 8-core model: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics bits: 64
    type: MT MCP arch: Zen 4 rev: 1 cache: L1: 512 KiB L2: 8 MiB L3: 16 MiB
  Speed (MHz): avg: 4339 min/max: 419/5138 boost: enabled cores: 1: 4339
    2: 4339 3: 4339 4: 4339 5: 4339 6: 4339 7: 4339 8: 4339 9: 4339 10: 4339
    11: 4339 12: 4339 13: 4339 14: 4339 15: 4339 16: 4339 bogomips: 121384
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Message: Required tool lspci not installed. Check --recommends
  Device-1: Generic Laptop Camera driver: uvcvideo type: USB bus-ID: 3-1:2
  Device-2: Brio 500 driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
    type: USB bus-ID: 5-1:3
  Display: wayland server: X.org v: 1.21.1.24 compositor: gnome-shell
    driver: N/A resolution: 3440x1440~60Hz
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: x11: xprop,xrandr
Audio:
  Device-1: Brio 500 driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
    type: USB bus-ID: 5-1:3
  API: ALSA v: k7.2.4 status: kernel-api
  Server-1: PipeWire v: 1.6.6 status: active
Network:
  Message: Required tool lspci not installed. Check --recommends
  Device-1: Realtek USB 10/100/1000 LAN driver: r8152 type: USB
    bus-ID: 8-1.4:5
  IF: enp195s0f4u1u4 state: down mac: a8:4a:63:90:d2:b7
  IF-ID-1: wlp1s0 state: up mac: fc:b0:de:18:1d:63
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB
    bus-ID: 1-5:5
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: FC:B0:DE:18:1D:64
Drives:
  Local Storage: total: 931.51 GiB used: 802.16 GiB (86.1%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 1000GB
    size: 931.51 GiB temp: 46.9 C
Partition:
  ID-1: / size: 858.49 GiB used: 801.83 GiB (93.4%) fs: btrfs dev: /dev/dm-2
    mapped: vg--C40C04-lv--btrfs
  ID-2: /boot size: 1022 MiB used: 331 MiB (32.4%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 72 GiB used: 4 KiB (0.0%) dev: /dev/dm-1
    mapped: vg--C40C04-lv--swap
Sensors:
  Src: /sys System Temperatures: cpu: 99.8 C mobo: 48.9 C gpu: amdgpu
    temp: 66.0 C
  Fan Speeds (rpm): fan-1: 3191 fan-2: 2943
  Power: 12v: N/A 5v: 5 3.3v: N/A vbat: N/A
Info:
  Memory: total: 64 GiB available: 60.63 GiB used: 19.84 GiB (32.7%)
  Processes: 497 Uptime: 12h 23m Init: systemd
  Packages: 1757 Compilers: gcc: 15.2.0 Shell: Zsh v: 5.9.1 inxi: 3.3.41

Standalone Operation

Full System, Standalone mode NOT enabled (normal usage)

Operating System

NixOS

Linux Kernel Version

Linux 7.2.4 #1-NixOS SMP PREEMPT_DYNAMIC Mon Sep 7 15:37:28 UTC 2026 x86_64 GNU/Linux

Additional Context

I'm seeking help diagnosing a reproducible discrepancy between the EC's reported PD firmware version and the versions read directly from the PD controllers. I have also experienced an unresponsive touchpad, although I have not established that the two problems share a cause. I initially posted in the community discourse but was advised it would be more helpful to share it here, too.

My goal is to keep this laptop reliable and correctly configured. I depend on it for job applications and interviews, so I would appreciate a supported diagnostic and recovery sequence that minimizes downtime.

System and current condition

Measurements below were collected on 10 September 2026.

Component	Details
Laptop	Framework Laptop 16, AMD Ryzen 7040 Series, mass-production mainboard
OS	NixOS, GNOME/Wayland
Current kernel	7.2.4; touchpad failures also occurred on 7.2.3
BIOS	04.05, release date reported by firmware: 06/30/2026
EC RO and RW versions	Both lotus-4.0.5-2246d58
EC build	2026-06-26 03:39:05
Executing EC image	RO
ISO keyboard firmware	0.3.1
Touchpad firmware	v0905
Diagnostic tool	framework_tool 0.6.3

The machine currently boots into the desktop, and touchpad movement, clicking and two-finger scrolling work. I have not established lasting recovery.

Boot warning and reproducible discrepancy

After shutting down and starting the laptop, a full-screen preboot warning displayed:

Please manually reinstall the BIOS to update PD1 firmware.
Currently: 2.0.0C. Expected: 0.0.21.

It included a QR code and allowed me to continue with a short press of the power button. I continued.

Later in the running system, the EC's two supported reporting protocols returned:

$ sudo framework_tool --host-command 0x3e11 1
Response (17 bytes):
00000000: 0200 0000 0018 020c 2097 0100 3762 6e21  ........ ...7bn!
00000010: 00                                       .

$ sudo framework_tool --host-command 0x3e11 0
Response (16 bytes):
00000000: 0000 0000 1802 0c20 9701 0037 626e 2100  ....... ...7bn!.

Version 1 contains a controller count of two followed by the same 16 bytes returned by version 0. Using Framework's decoder, the first controller's application version decodes to 2.0.0C, exactly matching the warning; the second decodes to 0.0.21.

However, sudo framework_tool --pd-info, run immediately after the version-1 query, returned:

Right / Ports 01
  Silicon ID:     0x3580
  Mode:           MainFw
  Flash Row Size: 256 B
  Ports Enabled:  0, 1
  Bootloader Version:   Base: 3.6.0.009,  App: 0.0.01
  FW1 (Backup) Version: Base: 3.7.0.197,  App: 0.0.21
  FW2 (Main)   Version: Base: 3.7.0.197,  App: 0.0.21
Left / Ports 23
  Silicon ID:     0x3580
  Mode:           MainFw
  Flash Row Size: 256 B
  Ports Enabled:  0, 1
  Bootloader Version:   Base: 3.6.0.009,  App: 0.0.01
  FW1 (Backup) Version: Base: 3.7.0.197,  App: 0.0.21
  FW2 (Main)   Version: Base: 3.7.0.197,  App: 0.0.21
Back
  Failed to read Silicon ID/Family

Earlier repeated --versions and --pd-info queries also reported 0.0.21 for both side controllers. That is the PD version listed in the BIOS 4.05 release notes.

Touchpad symptoms and other diagnostics

The touchpad previously became completely unresponsive. This completed successfully but did not restore it:

sudo modprobe -r i2c_hid_acpi && sudo modprobe i2c_hid_acpi

During the failure period, the kernel recorded:

i2c_hid_acpi i2c-PIXA3854:00: failed to set a report to device: -121
i2c_hid_acpi i2c-PIXA3854:00: failed to change power setting

For transparency, my NixOS configuration includes a custom touchpad watchdog that can reload i2c_hid_acpi. Consequently, some driver reinitializations in the logs were initiated by that watchdog.

After recovery, with the lid physically open, --inputdeck reported:

Chassis Closed:   true
Input Deck State: On
Touchpad present: true
SLEEP# GPIO high: true
Positions:
  Pos 0: GenericC
  Pos 1: KeyboardA
  Pos 2: Disconnected
  Pos 3: Disconnected
  Pos 4: GenericC

The current boot also contained UCSI errors, including UCSI_GET_PDOS failed (-95). I have not established a connection between these errors, the touchpad and the PD-version discrepancy.

ectool successfully communicated with the EC and reported:

EC uptime: 2757.560 seconds
AP resets since EC boot: 0
EC reset flags at last EC boot: power-on | hibernate
Command 0x3e11 supports version mask 0x00000003

Port-80 history repeatedly alternated F90D and F90E, interspersed with F022/F028. I have no authoritative interpretation of those codes.

One boot also entered initrd emergency mode. Journal inspection showed unsuccessful encrypted-volume unlock attempts followed by a root-device timeout; unlocking subsequently succeeded. I am treating that separately rather than assuming firmware caused it.

Source-level lead, not a confirmed root cause

The published input-module warning implementation uses this EC version-reporting path to generate the warning.

An earlier public EC revision's cypd_get_version()`
logs a failed version-register read but still copies from its uninitialized local buffer into the stored version record. Could this explain the discrepancy?

I have not verified that this implementation exists in my installed 2246d58 build, nor captured a boot-time READ_ALL_VERSION_REG failed message. Both protocol versions returning the same bad record suggests the issue is not limited to version-1 response formatting, but does not identify the underlying defect.

What I'm asking Framework

1. Is this a known EC version-reporting or PD-initialization issue? What additional evidence would distinguish invalid stored version data from a controller or hardware fault?
2. What exact recovery procedure do you recommend: a particular power-reset sequence, BIOS 4.05 reinstallation using a specified method, or another action? What should I capture first, and how should I verify lasting recovery?
3. Could the touchpad failure be related, or should I investigate it separately, including testing without my watchdog? If the symptoms persist after the supported recovery procedure, what findings would warrant hardware inspection or replacement?

I'm requesting diagnostic and repair guidance first. I'm willing to provide further logs and perform controlled tests, and would like advice on whether this should also become a firmware-tracker issue or a private hardware-support case.

[quinchou77]

I haven't received any related reports regarding the PD reporting an incorrect version in the input module app. The PD version retrieved via framework_tool (pdinfo) appears to be correct. Could you please double-check the PD version displayed in the BIOS Setup menu as well?
Additionally, could you try performing a full EC and PD hard reset by disconnecting the battery, reconnecting it, and testing to see if the issue persists?