[RESPONDED] Function Key becomes permanently pressed after a couple of minutes after boot (temporary fix: reboot)


========================== Kernel ===============================
Installed kernel: 6.6.7-200.fc39.x86_64
========================== Operating System =====================
OS: Fedora Linux 39 (Workstation Edition) x86_64 
Host: Laptop (12th Gen Intel Core) A4 
Kernel: 6.6.7-200.fc39.x86_64 
Uptime: 2 hours, 27 mins 
Packages: 7193 (rpm), 202 (brew), 45 (flatpak) 
Shell: bash 5.2.21 
Resolution: 2256x1504 
DE: GNOME 45.2 
WM: Mutter 
WM Theme: Adwaita 
Theme: NumixSolarizedDarkOrange [GTK2/3] 
Icons: Solarized-FLAT-Orange [GTK2/3] 
Terminal: vscode 
CPU: 12th Gen Intel i5-1240P (16) @ 4.400GHz 
GPU: Intel Alder Lake-P GT2 [Iris Xe Graphics] 
Memory: 8191MiB / 31802MiB 

Display Server: wayland
Systemd Version: systemd 254 (254.7-1.fc39)
  Type: Laptop System: Framework product: Laptop (12th Gen Intel Core) v: A4
    serial: FRANDACPA42382002Q
  Mobo: Framework model: FRANMACP04 v: A4 serial: FRANMACPA423620037
    UEFI: INSYDE v: 03.06 date: 11/10/2022
  Info: 12-core (4-mt/8-st) model: 12th Gen Intel Core i5-1240P bits: 64
    type: MST AMCP cache: L2: 9 MiB
  Speed (MHz): avg: 697 min/max: 400/4400:3300 cores: 1: 808 2: 848 3: 860
    4: 900 5: 698 6: 1042 7: 942 8: 400 9: 400 10: 400 11: 896 12: 400 13: 747
    14: 400 15: 1020 16: 400
  System RAM: total: 32 GiB available: 31.06 GiB used: 8.48 GiB (27.3%)
    igpu: 60 MiB
  Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
  Device-1: Controller0-ChannelA-DIMM0 type: DDR4 size: 16 GiB
    speed: 3200 MT/s
  Device-2: Controller1-ChannelA-DIMM0 type: DDR4 size: 16 GiB
    speed: 3200 MT/s
  Local Storage: total: 1.82 TiB used: 677.67 GiB (36.4%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
  Message: No optical or floppy data found.
  Device-1: VG: vgubuntu type: LVM2 size: 1.82 TiB free: 0 KiB
  LV-1: Backup type: linear size: 100 GiB Components: p-1: nvme0n1p5
  LV-2: Data type: linear size: 100 GiB Components: p-1: nvme0n1p5
  LV-3: Documents type: linear size: 250 GiB Components: p-1: nvme0n1p5
  LV-4: FedoraHome type: linear size: 18 GiB Components: p-1: nvme0n1p5
  LV-5: FedoraRoot type: linear size: 100 GiB Components: p-1: nvme0n1p5
  LV-6: FedoraSwap type: linear size: 32 GiB Components: p-1: nvme0n1p5
  LV-7: Harddisk type: linear size: 660.64 GiB Components: p-1: nvme0n1p5
  LV-8: Media type: linear size: 500 GiB Components: p-1: nvme0n1p5
  LV-9: UbuntuHome type: linear size: 18 GiB Components: p-1: nvme0n1p5
  LV-10: UbuntuRoot type: linear size: 50 GiB Components: p-1: nvme0n1p5
  LV-11: UbuntuSwap type: linear size: 32 GiB Components: p-1: nvme0n1p5
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Realtek [] driver: uvcvideo type: USB
  Display: server: X.Org v: 23.2.3 with: Xwayland v: 23.2.3 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
    resolution: 2256x1504~60Hz
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.3.1 renderer: Mesa Intel
    Graphics (ADL GT2)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.6.7-200.fc39.x86_64 status: kernel-api
  ID-1: BAT1 charge: 31.0 Wh (60.2%) condition: 51.5/55.0 Wh (93.5%)
    volts: 15.8 min: 15.4
  Device-1: Intel AX210 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: 8C:F8:C5:ED:74:4C bt-v: 5.3
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
  IF: wlp166s0 state: up mac: 1a:35:8a:7f:96:29
  • The top bar of my inbuilt laptop keyboard has media keys and some other functions. The media keys work as F1, F2, F3…,F12, when I press them along with the fn key.

  • I was on Fedora Linux (6.5.10-300.fc39.x86_64) 39 (Workstation Edition) from past few months. From last week the function key on my laptop fn becomes permanently pressed randomly after a couple of minutes of reboot . That means I am unable to play media keys as when I press those without pressing fn F1,…,F12 keys get activated. This fixes temporarily for few minutes after reboot. But again its the same issue.

  • Today I updated to kernel: 6.6.7-200.fc39.x86_64 and every software on my Fedora 39, but I am still facing the issue.

What should I do?

Hi Lamy,

Making sure I am following here.

  • This is a recent issue, only showing itself from the last week and is ongoing.
  • Due to this issue, media keys are unable to work as they did previously.
  • Updating to the latest kernel has not resolved the issue.

If the above is correct, I’d want to rule out the input kit itself. Can you boot to a live USB of Fedora, see if the issue takes place there in that environment? If it does happen in the live environment, we have a clear path forward.

If it does not happen in the live environment, then something with packaging, updates or config may be in play.

The points are correct.

Could you please explain what is the path in this case?

Sure, we know whether this is user config, OS or hardware. Getting to a vanilla state is always step one.

I understand that live environment is vanilla state. But you said that it will be a clear path if it happens there as well. This is what I wanted to know what is that clear path?

@Matt_Hartley Its happening with Fedora Live USB as well. What is the path forward?

Are you sure its not firmware issue: Function (Fn) Keys Sticking + Fix for Linux - Framework Laptop 13 / Linux - Framework Community

An issue from 2022? I don’t believe so, no. I have not run into it myself, either. Now, as this is 12th gen, perhaps. Best way to be sure is to try as suggested, we’ll go from there.

Again, if it was wide spread, I would have seen a lot more of this. But, yes, it could be, so let’s test it against the Live USB, it should fail there as well and then, we’d say it relates to that thread. :slight_smile:

TLTR: We generally like to rule out other possibilities before we immediately blame older BIOS straight away. Indeed could be, but we are in assume territory until we test against a proper vanilla environment first.

Clear path being, this is not OS/user config, therefore, it’s hardware/BIOS/Related. Clear path being we know what we’re dealing with and have a direction to go in. This is what we are wanting to determine.

@Matt_Hartley So what needs to be done? I am on the latest firmware 3.06.

You’ve probably already checked this, but when the fn key gets “stuck,” does holding the fn key cause the behavior to revert to the initial one (i.e., media functions when pressing the function keys)? If that’s the case, does pressing fn + Esc to toggle function lock bring back the original behavior for any amount of time or until you reboot?

Pressing fn + Esc to toggle function lock does not bring back the original behavior for any amount of time or until reboot.

If it fails there as well, then we can assign this to the BIOS issue or input kit. Let me know when you have followed this step.

Until we do this, I will be unable to help further on this one as I cannot replicate it here.

@Lamy can you post your kernel.config? I have yet to compile 6.6.7 or 6.6.8 (still on the Kernel of the Beast) and I’m curious :slight_smile:

zcat /proc/config.gz > kernel.config