Caps Lock LED Indicator is always on

Framework Laptop 16 Linux
1

Which Linux distro are you using? Fedora

Which release version? 43

Which kernel are you using? 6.17.1-300.fc43.x86_64

Which BIOS version are you using? 3.04

Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series) AMD AI 300

I received my laptop today and I’ve installed the “Keyboard (2nd Gen) - International English” keyboard. No number pad or other input module. When booting Fedora, the LED indicator on the caps lock key turns on (at the time when the framework logo is shown) and stays on. Pressing the caps lock key during boot, or after boot is complete, doesn’t toggle the LED indicator off (it stays on always).

After the OS has booted, if I press the key I can see a caps lock indicator appear on the panel next to the clock indicating caps lock is enabled (and typing shows capitals). Pressing the caps lock key again removes the indicator from the panel near the clock but doesn’t turn the LED indicator off.

The LED turns off when the laptop is shut down.

In summary, the keyboard works fine and the caps lock key does work, but its LED indicator is always on regardless of state.

Some similar topics that don’t have a posted resolution (I am only allowed to post 2 links, apparently):

The LED indicator is even turned on when I boot into BIOS, and pressing the caps lock key there doesn’t change the LED state.

I’m not sure if this is a HW issue, or some mistake I’ve made, or some SW config problem. Any help on this would be appreciated! :slight_smile:

2

if you map the capslock key to something else (via keyboard.frame.work) does the LED turn off? i would imagine if it doesn’t it might be a hardware issue

3

Thanks for the suggestion, I hadn’t heard of keyboard.frame.work before. I couldn’t find a way on that webpage to remap keys, but I did find how to do it through settings. Choosing the option to swap caps lock and esc does work (in that the operation of both those keys is then swapped) but the caps lock indicator LED stays on.

In keyboard.frame.work I can go to the “key tester” tab and each key on the keyboard does work (incl caps lock), but if I click Authorize Device and choose my keyboard I get 2 errors:

NotAllowedError: Failed to open the device.
Device: Framework Laptop 16 Keyboard Module - ANSI
Vid: 0x32AC
Pid: 0x0012

and

Received invalid protocol version from device
Device: Framework Laptop 16 Keyboard Module - ANSI
Vid: 0x32AC
Pid: 0x0012
4

make sure you’re in the “input” group and log out and back in:

sudo usermod -a -G input $USER

5

I tried that just now - I wasn’t in the input group so I added it as you suggested and rebooted. The same errors appear in keyboard.frame.work when trying to authorize the device.

FWIW I found a bluetooth keyboard and paired that with my laptop to see if it does the same thing. It doesn’t appear in the authorize device list, but when I press keys on it the the key tester tab recognises each key correctly. This bluetooth keyboard’s caps lock LED functions correctly, toggling on and off when pressed.

Maybe that does point towards something HW related. I did pull the keyboard out and re-seat it, but no change.

Thanks for your help!

6

can you try running firmware update? in console:

fwupdmgr refresh --force

fwupdmgr get-updates

fwupdmgr update

then reboot

the site by all means should be recognizing your keyboard. i’ve had to use a chromium based browser for it in the past

if a firmware update doesn’t allow you to reconfigure the keyboard and doesn’t fix the light, might be good to reach out to support

7

Thanks for the suggestion to update firmware. I ran this just now. get-updates reports that the keyboard module has the latest firmware & that there was an update available for UEFI dbx. I applied that update and rebooted, but the caps lock LED remains on.

I’m using Opera for the keyboard.frame.work site because the compatibility page said it was fully supported.

I did reach out to support yesterday - I’ll see what they say.

8

For anyone who finds this in future, Framework Support asked me to try the following as diagnostics:

  • Review box/laptop chassis for indications of damage & supply photos.
  • Clean the key with compressed air.
  • Check all other keyboard keys/functions.
  • Try different input module configurations (left, centre, right) to see if there’s any change in behaviour.
  • Reset BIOS to default.
  • Perform a mainboard reset.
  • Confirm (with video) the moment when the LED turns on (on boot, before the framework logo splash screen is shown).

At the end they concluded they’ll replace the keyboard module.

I’m not sure how to close this topic.

9

Fix for keyboard.frame.work

10

Just update the title to

(Solved) Caps Lock LED Indicator is always on

1 Like
11

Thanks, but there doesn’t appear to be an edit button for this. Perhaps you need special permissions? Not sure. It won’t let me delete it either, if I hover over the delete button it says I don’t have permission to do that.

Guess it can wait 6 months before being auto-closed.