Using the RK Royal Kludge keyboard configuration webapp on Linux PC

Okay today I managed to accidentally trigger “locked” function keys on my rather new M70 RK Royal Kludge. There is a modifier hotkey for this that I didn’t know of before (FN + LEFT CTRL) and I was lost for a hot minute how to turn it off again. Ah well, we’re still getting to know each other.

Anyway, I know from a previous attempt that RKGaming offers a webapp to configure the keyboard (especially it’s macro keys) on https://drive.rkgaming.com/. This works to this date only in Google Chrome (Webserial in Firefox is coming though). Here we can click a button and connect to the wireless receiver and… nothing. Ah yes, we’re on Linux PC and random browsers shall not write to our hardware devices. This is in principle a good idea and I did encounter this before with my Viture XR glasses so I had an idea where to start poking.

First things first: Confirming my theory I checked the browser console and sure enough it was not allowed to open the device:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:1 NotAllowedError: Failed to open the device.

HIDEvent[12:08:56] Failed to open '/dev/hidraw10': FILE_ERROR_ACCESS_DENIED
HIDEvent[12:08:56] Access denied opening device read-write, trying read-only.

new full-speed USB device number 17 using xhci_hcd
New USB device found, idVendor=3554, idProduct=fa09, bcdDevice= 1.02
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Product: 2.4G Wireless Receiver
Manufacturer: CX

crw-rw----. 1 root root 241, 9  8. Jun 12:05 /dev/hidraw10

# Udev processes rules in alphabetical/numerical order. The actual
# application of the uaccess tag happens in systemd's built-in
# 73-seat-late.rules so make sure this is run *before* by saving 
# this as e.g. 72-rk-royal-kludge.rules
# uaccess tag means that logind assigns the permissions to users
# dynamically via ACLs according to which session is currently active
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"

crw-rw----+ 1 root root 241, 10  8. Jun 12:34 /dev/hidraw10

# file: dev/hidraw10
# owner: root
# group: root
user::rw-
user:beko:rw-
group::rw-
mask::rw-
other::---

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:2388 Device [2.4G Wireless Receiver] is open

What a time to be alive.

#Linux #JustLinuxThings #udev #keyboard #RoyalKludge

This content is licensed under a Creative Commons Attribution 4.0 International license.

https://beko.famkos.net/2026/06/08/using-the-rk-royal-kludge-keyboard-configuration-webapp-on-linux-pc/#JustLinuxThings #keyboard #linux #RoyalKludge #udev

Beko Pharm

2026-06-08 11:14:08

Using the RK Royal Kludge keyboard configuration webapp on Linux PC

Okay today I managed to accidentally trigger “locked” function keys on my rather new M70 RK Royal Kludge. There is a modifier hotkey for this that I didn’t know of before (FN + LEFT CTRL) and I was lost for a hot minute how to turn it off again. Ah well, we’re still getting to know each other.

Anyway, I know from a previous attempt that RKGaming offers a webapp to configure the keyboard (especially it’s macro keys) on https://drive.rkgaming.com/. This works to this date only in Google Chrome (Webserial in Firefox is coming though). Here we can click a button and connect to the wireless receiver and… nothing. Ah yes, we’re on Linux PC and random browsers shall not write to our hardware devices. This is in principle a good idea and I did encounter this before with my Viture XR glasses so I had an idea where to start poking.

First things first: Confirming my theory I checked the browser console and sure enough it was not allowed to open the device:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:1 NotAllowedError: Failed to open the device.

There is also this special chrome://device-log/ address in Chrome that has some more details:

HIDEvent[12:08:56] Failed to open '/dev/hidraw10': FILE_ERROR_ACCESS_DENIED
HIDEvent[12:08:56] Access denied opening device read-write, trying read-only.

With this information we do have the Vendor ID (0x3554) the Product ID (0xfa09) and the subsystem (hidraw) in question. This is btw the dmesg output for the connected device, confirming what we know already:

new full-speed USB device number 17 using xhci_hcd
New USB device found, idVendor=3554, idProduct=fa09, bcdDevice= 1.02
New USB device strings: Mfr=1, Product=2, SerialNumber=0
Product: 2.4G Wireless Receiver
Manufacturer: CX

And a quick check on /dev/hidraw10 confirms that we simply to not have permission to read or write to this hidraw device, since it belongs to root.

crw-rw----. 1 root root 241, 9  8. Jun 12:05 /dev/hidraw10

Now a quick and dirty fix for the current session would be to simply change the ownership of that device but I really want this to stick around after the next reboot so I created the udev rule file /usr/lib/udev/rules.d/72-rk-royal-kludge.rules:

# Udev processes rules in alphabetical/numerical order. The actual
# application of the uaccess tag happens in systemd's built-in
# 73-seat-late.rules so make sure this is run *before* by saving 
# this as e.g. 72-rk-royal-kludge.rules
# uaccess tag means that logind assigns the permissions to users
# dynamically via ACLs according to which session is currently active
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"
SUBSYSTEM=="hidraw", KERNEL=="hidraw*", ATTRS{idVendor}=="3554", ATTRS{idProduct}=="fa09", MODE="0660", TAG+="uaccess"

Changes in such files have to be reloaded with e.g. udevadm control --reload. After that… nothing happens. This is because the device exists already so it’s time to unplug that receiver briefly. Now udev kicks in and creates the device files with the new rules applied. There is now a slight difference:

crw-rw----+ 1 root root 241, 10  8. Jun 12:34 /dev/hidraw10

The “+” indicates additional ACL rules. If you did not know about ACLs before: Oh boy, you’re in for a ride. Anyway, I confirmed that I now have access to this by checking the ACLs with e.g. getfacl /dev/hidraw10

# file: dev/hidraw10
# owner: root
# group: root
user::rw-
user:beko:rw-
group::rw-
mask::rw-
other::---

And presto. My user beko has read-write access. Another visit to https://drive.rkgaming.com/ yields a far better result:

[HID] Selected device: 2.4G Wireless Receiver vid=0x3554 pid=0xfa09
index-JWjn01Gh.js:2388 Device [2.4G Wireless Receiver] is open

Now I can configure my keyboard on Linux PC via a gorram web application like any other cool kid in 2026. I say this because the app will probably have a half-life of 2 years and stop working soon enough again.

What a time to be alive.

#Linux #JustLinuxThings #udev #keyboard #RoyalKludge

This content is licensed under a Creative Commons Attribution 4.0 International license.

https://beko.famkos.net/2026/06/08/using-the-rk-royal-kludge-keyboard-configuration-webapp-on-linux-pc/#JustLinuxThings #keyboard #linux #RoyalKludge #udev

RK Web App

^{drive.rkgaming.com}

Mein Lüfterproblem (ständig Vollspeed, dementsprechend laut) habe ich jetzt endlich folgendermaßen in den Griff bekommen:

1. #Thinkfan installieren: apt install thinkfan
2. Eine Config Datei für thinkfan erstellen: nano /etc/thinkfan.yaml
3. Folgende Konfiguration für diese Datei:
   

   fans:
     - tpacpi: /proc/acpi/ibm/fan
   
   sensors:
     - hwmon: /sys/class/hwmon
       name: coretemp
       indices: [1, 2, 3, 4, 5]   # Package id 0 + Core 0–3
   
     - hwmon: /sys/class/hwmon
       name: nvme
       indices: [1]                # NVMe Composite
   
   #              Stufe  min°C  max°C
   levels:
     - [0,          0,    50]    # Lüfter aus
     - [1,         46,    57]    # kaum hörbar
     - [2,         54,    64]    # sehr leise
     - [4,         61,    71]    # moderat
     - [6,         68,    80]    # schnell
     - ["level auto", 77, 32767] # BIOS übernimmt ab 77°C

4. Mit sudo thinkfan -n testen, ob thinkfan tut, was es machen soll.
5. Nachdem der Test erfolgreich gelaufen ist, thinkfan dauerhaft aktiviert:
   

   sudo systemctl enable --now thinkfan
   sudo systemctl status thinkfan

Damit kann ich meinen #Lenovo #Thinkpad #T14 jetzt komplett geräuscharm nutzen.

#Linux #Debian

Das lange Wochenende steht vor der Tür - schon was vor in #Berlin?

Wie wäre es am Samstag mit einem Ausflug nach #Spandau - da veranstaltet die Berliner Gruppe der FSFE zusammen mit dem @Digital-Zebra in der Bezikzentralsbibliothek Spandau zwischen 12 und 14 Uhr eine Linux Presentation Day.

Programm

• Vortrag: Was ist Linux überhaupt?
• Vortrag: Gängige Programme für den Alltag unter Linux wieder finden
• Frage und Antwort Runde um Ihre Fragen zum Umstieg zu beantworten
• Vorführgeräte mit Linux zum Ausprobieren

Termin

• Wann: 16.5.2026, 12 bis 14 Uhr
• Wo: Bezikzentralsbibliothek Spandau, Carl-Schurz Straße 13
• Eintritt ist frei, um Anmeldung wird gebeten unter https://share.fsfe.org/apps/forms/s/F8QRtL7q4477Q7CtCXqLf5iK
• Der Zugang ist Behindertengerecht
• Die Veranstaltung wird im wesentlichen auf Deutsch gehalten. Fragen können aber auch auf Englisch beantwortet werden.

https://fsfe.org/events/events.de.html#event-20260516-01

#FSFE #FreieSoftware #Linux #LinuxPresentationDay #LPD

@Friendica Support hello, i would like some help please to understand how to solve my confusion about the "right" way to follow #hashtags, using #Channels ... or otherwise some better way.

i follow a large number of hashtags [as a glance at my profile would attest]. afaict / afaik, fediverse posts bearing these tags appear [or are supposed to] in my "Network" timeline [with "Everybody" Circle & "Latest posts" Channel selected].

of my many tags, possibly my most "important" ones are #AusPol, #FOSS, & #Linux. in order to be able to efficiently locate all posts with these tags each day, rather than have to meticulously scroll down the full "Network" timeline [which is dissipated via also having all the other tags, & all my Followed accounts' posts], in Settings i created three dedicated Channels [one for each of those tags, ofc]. then i added each of those custom Channels to my Timelines, in Display Settings.

however, the result is just hopeless; really disappointing & frustrating. over recent years i have had several Friendica accounts, ie, at several instances, & doing the above has never worked properly in any of them, not only my current instance.

using the AusPol Channel for example, as it is the worst by far, every time i check it, its most recent post is several hours old, & often as bad as 12 - 18 hours old, with numerous other posts entirely missing.

i say "missing" because otoh, reviewing my Saved Search for #AusPol shows all these other posts, which therefore also appear, buried, in my full "Network" timeline.

over the months & years in exasperation, i have revisited the dedicated Channels in Settings, & for the Circle/Channel field have tried each of Latest posts, Latest Creation, Global community, & Latest activity, but none of them has solved the problem [indeed, a few make it even worse!].

please, what am i doing wrong? what aspect of Friendica's Settings have i been consistently misunderstanding / misusing, that causes this disappointment?