Which Linux distro are you using? Ubuntu
Which release version? 24.04.2 LTS
Which kernel are you using? 6.8.0-53-generic
Which BIOS version are you using? 03.05
Which Framework Laptop 16 model are you using? 7940HS+7700S
I decided to attach my external ROG Swift PG35V via the DP card.
It is very difficult to use the fn+F9 keys on the FW16 keyboard to control which monitors are enabled. If you tap it quickly, you may get to the right monitor, but it seems to be luck of the draw. If you hold it down briefly, it goes to the end of the list and sits there.
Alternatively, when I use the Super(windows)-P button, it allows you to slowly cycle through the list and make a choice.
My understanding is that fn+F9 is tied to the same key, so it is curious why the behavior is different. Are the key press/releases being handled differently?
KC_SCRN is what Framework named the key, KC_LGUI is what QMK uses for the left windows / super key, and v0.2.9 is the latest firmware, which ships on all current keyboards afaik.
With Super/Win+P are you releasing the Super key or keeping it held?
The Scrn (Fn+F9), being a single key, can’t easily simulate holding Super/Win.
You could try remapping Fn+F9 to the key combo directly instead of using Framework’s KC_SCRN function. On layer 0 (zero) and layer 3 iirc.
The online configurator can be found at keyboard.frame.work, it’s known as Via. It works in Chrome, Edge, and other Google Chromium-based browsers. Note that some smaller Chromium-based browsers have been reported to fail to work because the devs either accidentally or by choice did not enable WebHID support. And on Linux, Snap or Flatpak packages can sometimes have permission issues. Regular Chromium, just named “Chromium” works for me. If it the Via site tries but fails to connect in Chrome or regular Chromium then you might need udev rules