Which Linux distro are you using?
OpenSUSE Tumbleweed
Which release version?
(if rolling release without a release version, skip this question)
(If rolling release, last date updated?)
20241105
Which kernel are you using?
6.11.6-2-default
Which BIOS version are you using?
3.03
Which Framework Laptop 16 model are you using? AMD Ryzen™ 7040 Series
keyboard.frame.work just doesn’t work on my laptop, just saying “Permission denied”
I have attached the csv I got when I downloaded the error messages
timestamp, productName, vendorId, productId, message
14:14:29.254, Framework Laptop 16 Keyboard Module - ANSI, 0x32AC, 0x0012, "NotAllowedError: Failed to open the device."
14:14:29.261, Framework Laptop 16 Keyboard Module - ANSI, 0x32AC, 0x0012, "Received invalid protocol version from device"
I have a feeling this is going to be really annoying.
Probably not. invalid protocol is a sign that you just need to add a udev rule.
But what browser? And is it is installed as a normal system package?
Snap, flatpak, or AppImage can sometimes add additional permission issues. And Via, the interface at keyboard.frame.work requires WebHID/WebUSB to work, occasionally with some builds of less popular browsers it can just be broken. A couple of people have reported that.
Udev rules
Place this file into /etc/udev/rules.d/.
Once added, run the following:
sudo udevadm control --reload-rules
sudo udevadm trigger
Then reopen your browser.
And of course be sure to authorize the connection to the keyboard. Your browser should prompt for this.
I just used Chromium from the repos, because Vivaldi was reporting other weird errors when I last used it for hardware modification web apps. I usually use Floorp, but I couldn’t use it for this because it’s based on Firefox.
I just did the following based on some advice I found on Google from the Arch Forums:
sudo chmod a+rw /dev/hidraw[n]
where n is the id of the keyboard. It got the site working, but it seemed a bit extreme and required me to do the following when I was done:
sudo chmod 600 /dev/hidraw[n]
Anyway, I was on the site long enough to confirm that VIA may not be the solution to the problem I was hoping to solve. That udev rule is probably the secure way to do things.
I was hoping to use the fn key on my Framework 16 to do really complicated modifier combinations like Ctl+Shift or Ctl+Shift+Alt so that I could use a single modifier key to do stuff like open tofi without conflicting with KDE’s built in shortcuts.
Yeah, I don’t believe there is a suitable way to combine layer keys with other functions in Via. You could use tapdance or combos, but Via doesn’t offer configuration of QMK tapdances or combos. Via is kind of limited.
On my mouse, I combine a couple of my layer change keys with other functions using tapdance, and for one of them, also a custom function for finer control of triggering keydown & keyup.
Do you only have, only need to configure an ANSI keyboard? I see your error messages are for ANSI. A community member created a Vial/QMK port for the FWL16, Keyboard: VIA / VIAL support? - #50 by Allen_S (despite the name of the repo, ANSI files are also included). Vial is an alternive interface, instead of Via. Vial offers more options, including configuring tapdance & combos. https://get.vial.today/