Lid close generates zero events - FW-13 AI-300 Fedora 44

[Kaden-Beck]

Device Information

System Model or SKU

Please select one of the following

• Framework Laptop 12 (13th Gen Intel® Core™)
• Framework Laptop 13 (11th Gen Intel® Core™)
• Framework Laptop 13 (12th Gen Intel® Core™)
• Framework Laptop 13 (13th Gen Intel® Core™)
• Framework Laptop 13 (AMD Ryzen™ 7040 Series)
• Framework Laptop 13 (AMD Ryzen™ AI 300 Series)
• Framework Laptop 13 (Intel® Core™ Ultra Series 1)
• Framework Laptop 16 (AMD Ryzen™ 7040 Series)
• Framework Laptop 16 (AMD Ryzen™ AI 300 Series)
• Framework Desktop (AMD Ryzen™ AI 300 PRO Series)

BIOS VERSION

BIOS VERSION: 04.02

DIY Edition information

Memory: A-DATA Technology - AD5S560016G-SFW
Storage: Framework Expansion Card 246 GB (USB DISK 3.2)

Port/Peripheral information

N/A

Standalone Operation (Laptop Only)

N/A

Describe the bug

Lid close generates zero events:

• /proc/acpi/button/lid/LID0/state stuck at "open" when opening and closing clamshell.
• evtest on the Lid Switch device (event0) shows nothing on lid close.
• journalctl -f shows no lid/suspend/sleep/acpi events on close.
• Manual suspend via power button works perfectly (s2idle confirmed working for 38+ hours).
• cros_ec: Driver loads (cros_ec_lpcs FRMWC004:00), but no /sys/kernel/debug/cros_ec/ directory exists for further diagnosis
• logind.conf / GNOME 48: Not the cause — GNOME 48 removed lid-close gsettings keys, logind.conf was configured with HandleLidSwitch=suspend, but no events ever reach logind

Steps To Reproduce

Steps to reproduce the behavior:

1. Computer awake, clamshell open
2. Close lid
3. Open lid
4. No change in state recorded to OS

Expected behavior

System should recognize lid closing action and pass event to operating system

Screenshots

N/A

Operating System (please complete the following information):

Operating System

• OS/Distribution: Fedora Workstation
• Version: Fedora 44 (GNOME 48, Wayland)
• Linux Kernel Version: 7.0.13-200.fc44.x86_64

Additional context

Not sure if this could be caused by a hardware issue, not sure how to validate that

[JohnAZoidberg]

The sensor is in the audio jack board.
Please make sure that is properly connected via the FFC cable.