FW16 7040 BIOS 4.03 - touchpad stops working - i2c firmware issue #164
Description
Device Information
System Model or SKU
Please select one of the following
- Framework Laptop 16 (AMD Ryzen™ 7040 Series)
BIOS VERSION
Framework Laptop 16 Ryzen 7040 BIOS 4.03 Release BETA
Linux:
dmidecode --string bios-version
04.03
DIY Edition information
If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.
Memory: F5-5600S4040A32G
G.SKILL Ripjaws DDR5 SO-DIMM Series DDR5 SO-DIMM Memory Kit, Model: F5-5600S4040A32GX2-RS
64GB total capacity kit containing 2x32GB modules, rated for up to DDR5-5600 CL40-40-40-89 at 1.10V
Storage: S6B0NU0W434824E, A7SIB34602WR3Z
/dev/nvme0n1 /dev/ng0n1 S6B0NU0W434824E Samsung SSD 980 PRO 2TB 0x1 1.97 TB / 2.00 TB 512 B + 0 B 5B2QGXA7
/dev/nvme1n1 /dev/ng1n1 A7SIB34602WR3Z Corsair MP600 CORE MINI 0x1 2.00 TB / 2.00 TB 4 KiB + 0 B ELFMC1.0
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
- Yes
- No
Describe the bug
the touchpad can stop functioning permanently when using it. It seems to be triggered when dragging the cursor (holding "mouse button" with one finger while moving cursor with another finger.
This is a rare occurrence but nearly catastrophic to undo. The only way I have been able to restore it is to rapidly mash the power button many times. In the 3+ weeks I have been running this bios version, it has happened only three times.
Steps To Reproduce
Steps to reproduce the behavior:
- Like many issues with this bios, reproducing depends on whatever "random" state the firmware is in when it decides it doesn't like me using the touchpad. When it does happen, it seems to happen when "dragging" the cursor (two+ touch points while moving).
- Touchpad will completely cease functioning completely. This broken state will survive reboots, power-off, battery disconnect, bios defaults set, etc.
- Boot into any alternate OS and it remains non-functional. Issue transcends the OS.
- rapidly power on/off by mashing on the power button 10-20 times will fix it and it will start functioning again. (further testing, it seems "resetting" the motherboard is the only way to recover it)
Expected behavior
Touchpad and i2c bus should never break in the firmware level. It should remain functional at all times. This is the type of issue that needs a recall if it can't be fixed.
Operating System (please complete the following information):
- OS/Distribution: Linux/Fedora 43
- Version: 43
- Linux Kernel Version: 6.17.9-300.fc43.x86_64
Additional context
This seems to be the i2c bus deciding to stop working. This is a major usability issue and the bios should not be marked stable.
dmesg output when it breaks. Upon rebooting or booting into any other OS, the touchpad and i2c is just....gone:
[ 963.878738] i2c_designware AMDI0010:03: controller timed out
[ 964.902743] i2c_designware AMDI0010:03: controller timed out
[ 965.926738] i2c_designware AMDI0010:03: controller timed out
[ 966.950802] i2c_designware AMDI0010:03: controller timed out
[ 967.974771] i2c_designware AMDI0010:03: controller timed out
[ 968.998788] i2c_designware AMDI0010:03: controller timed out
[ 970.023770] i2c_designware AMDI0010:03: controller timed out
[ 971.046830] i2c_designware AMDI0010:03: controller timed out
[ 972.070784] i2c_designware AMDI0010:03: controller timed out
[ 973.094798] i2c_designware AMDI0010:03: controller timed out
[ 974.118808] i2c_designware AMDI0010:03: controller timed out
[ 975.143810] i2c_designware AMDI0010:03: controller timed out
[ 976.166850] i2c_designware AMDI0010:03: controller timed out