jdret.blogg.se - Logitech g710 keyboard not working windows 10

#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 DRIVERS#
#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 MANUAL#
#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 DOWNLOAD#

Ensure that this file is named SFCFix.zip - do not rename it.

#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 DOWNLOAD#

Download SFCFix.zip, and save this to your Desktop.

Download SFCFix.exe (by niemiro) and save this to your Desktop.

If you are after assistance, please start a thread of your own. No one else should follow these instructions as it may cause more harm than good. Warning: this fix is specific to the user in this thread.

The keyboard should now emit your configured keycode to the system, once the key is pressed.18:13:44, Info CSI 0000089a Beginning Verify and Repair transaction.

Replace the number within 123 with your desired keycode.

I suggest KEY_PROG for the beginning, which are the keycodes 148, 149, 202 and 203.

Open up s.xml file, whereas the number corresponds to your macro key.

Go to sidewinderd configuration folder (usually /home//.local/share/sidewinderd.

Record a single keypress on your desired macro key.

#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 MANUAL#

The procedure is as the following and requires manual editing: Theoretically, all keys specified within those lines in the virtual_input.cpp file should work. It looks like not every key I've randomly tested is working though: KEY_F24 didn't work for me, eventhough it's configured in. binding KEY_PROG1 to a key and then binding it to a shortcut within the application works for me (tested with gnome-terminal). Which KDE version and Linux kernel are you using?

#LOGITECH G710 KEYBOARD NOT WORKING WINDOWS 10 DRIVERS#

If this doesn't work - either due to changes to the underlying software / drivers I'm unaware of or simply it never worked to begin with - it shouldn't be a big deal to fix / configure it. This will also work for keys, which are not physically available on your keyboard (and therefore cannot be live recorded), like KEY_F24 for example. Note: you can manually edit the macro configuration files instead of live recording, if you want to bind single keys to them. The keys get directly injected into /dev/input/uinput (aka the standard way of doing it, to my knowledge), which should be usable and bindable in all sorts of applications, including in the KDE shortcut menu you mentioned. binding some kind of placeholder keys like F13 - F24 to the macro keys and use them within KDE System Settings -> Shortcuts -> Custom Shortcuts shouldn't work. However, I can't think of a reason, why e.g. In its default configuration, sidewinderd "clears" any kind of key event codes from the G- and M-Keys (which usually emit numbers "1" to "6" on G710), so you have a clean starting point. Does that difference in the approach (service vs module) have to do something with those macro keys not working the way I expect?Įxposing keys to the system is indeed a kernel driver's job, but it should work with sidewinderd aswell. I came here to try this for the convenience of having a service instead of a kernel module (plus I had some troubles with some windows ignoring macro keys). I was using and keys where directly 'bindable' in KDE System Settings -> Shortcuts -> Custom Shortcuts (even with M* keys as modifiers). The only workaround is to record an unused bizarre combination of keys (Ctrl + Shift + Meta + Alt + whatever) with the built-in macro recorder and then bind that combination as trigger to our actions, right? Is there an option or way to expose extra keys to the system? While the macro recording works flawlessly, it seems that the G* keys are not directly exposed to the system itself, thus I can't bind my macro keys to shell commands, windows actions, etc in KDE System Settings -> Shortcuts -> Custom Shortcuts. I have a Logitech G710+ and using KDE Neon (a mix between long-term stable Ubuntu and latest cutting-edge KDE).