[RESPONDED] QMK keyboard setup not working under Linux?

Framework Laptop 16 Linux
21

Hmm. Cant use https://keyboard.frame.work/ to remap using Ubuntu 22.04.4 LTS x86_64
Have done this

place this file into /etc/udev/rules.d/.

Once added, run the following:

sudo udevadm control --reload-rules
sudo udevadm trigger
%20t
I get Error: Failed to open the device.
Device: Framework Laptop 16 Keyboard Module - ANSI
Vid: 0x32AC
Pid: 0x0012

Using both chrome and Chromium, I want to remap the dollar sign on my RGB keyboard to a GBP sign.

Edit. Restarted Chrome, all good.

22

Im on Fedora 40 and also needed to run those instructions to get keyboard.frame.work to connect to my keyboard.

1 Like
23

Hi - I needed the udev rule. Framework 16, Latest Bios as of 2024-07-01, Ubuntu 22.04 with Oem kernel. Using numpad module and standard us keyboard.

24

I’m using Debian 13 trixie (in testing right now), and I needed the 50-qmk.rules file in udev’s config too. Worked a charm after that.

I needed Chromium temporarily to use keyboard.frame.work. The site works OK with throwaway default profiles, or with --incognito if you prefer.

chromium --temp-profile https://keyboard.frame.work/

Usage notes

  1. Click on Authorize device +
  2. Click on the device in the <website-name> wants to connect to a HID device dropdown, and click Connect. Mine appears as Framework laptop 16 Keyboard Module - ISO.
  3. On the next screen, click keys at the top of the page to select them, then choose what they map to underneath. Changes take effect immediately!
  4. Layers and momentary layer enabling eventually make sense, but there’s no help within the webapp,and you have to use trial and error.

Slightly confusing things

I wanted to map Fn+Right Ctrl to Menu because the Framework keyboards don’t have the menu key. I’ve used the combination on other laptops, and I’m still half used to it.

It’s really difficult to read the rollover text for each key in the page footer. It’s just too transparent and looks like a glitch.

The Fn key has MO(1) on the keyboard diagram in Layer 0, and MO(3) in Layer 2. Pretty confusing at first.

  • Turns out “MO(n)” means "momentarily enable layer n while the key is held.
  • And “∇” is for pass-though - to Layer 0, I think, but I didn’t investigate further.

I found I needed to map Right Ctrl to Menu in both Layer 3 and Layer 1. Just playing with Layer 1 at first didn’t seem to be having any effect!

  • Layer 0 is what keypresses do in Fn lock mode, and also the base layer for the firmware. Media keys live here. Normal mode for some but not for me.
    • its Fn mapping is MO(1)
  • Layer 1 is Fn lock mode but while Fn is held down. It’s mostly ∇ except for some documented special Fn-key mappings.
  • Layer 2 is regular mode: the mode I’m in normally, without any modifiers held down. It’s mostly ∇, so keystrokes pass through to layer 0.
    • its Fn key mapping is MO(3)
  • Layer 3 is used when Fn is held down outside Fn lock mode. Special Fn combinations need to go here and in Layer 1

Annoying error-proneness: when a mapping is added to a key, the highlight moves on to the next key on the keyboard display, so you can really easily remap the wrong key by accident if you try to correct what you just did. It’s really difficult to see the selected key too, leading to more errors.

Final oddity is that the Menu mapping shows as RApp on the keyboard display, and KC_APP in the footer rollover :zany_face:

But it works! Thanks to everyone in the thread for leading me in the right direction, and particularly to @MJ1 for being so awesome and helpful :+1:

2 Likes