Durgod Keyboard - works but not programmable
by CVAlkan from LinuxQuestions.org on (#53FGJ)
Disclaimer: this may or may not be a hardware issue, but since it only occurs with a specific device, I've posted it here.
I recently purchased a Durgod Taurus K320 TKL Mechanical Keyboard, one of a series of rather impressive keyboards; it can be seen at https://www.amazon.com/dp/B078H3WPHM...v_lig_dp_it_im
This particular version is wired through a USB port and is "plug and play." So far, so good. Not quite the same feel as my treasured Northgate OmniKey (still in regular use after 28 years), but appears to play in the same league.
Durgood also provides a Windows only app for creating macros, reassigning keys and the like, called the Durgod Zeus Engine, which can be downloaded from https://www.durgod.com/Durgod-Zeus-Engine?_l=en
The company's tech support assured me that there is no way this app can be used under Linux. Of course, I refused to believe/accept that, so I attempted to run the app under Wine, and it ran just as described in the company's documentation. Once again, so far, so good.
BUT - the application didn't recognize that one of its devices was installed on my system (I've tried it on Mint 19.1, Mint 19.3 and Ubuntu 20.04). I then installed the software on a Windows 10 laptop and it immediately recognized the keyboard and opened up all the options for creating macros, etc. though I didn't actually attempt to create any yet, since as a long-term solution that would be a pain.
Trolling the web, it seems that many folks mention that Wine doesn't always recognize USB devices and there are many posts describing rather elaborate "work-arounds" for this.
As it happens, I also use another USB-connected programmable keyboard, the Kinesis Freestyle Edge, which can be seen at https://www.amazon.com/KINESIS-Gamin...43&sr=1-3&th=1
While basic programming of the Kinesis can be done from the keyboard itself, Kinesis also supplies a Windows app, called the Smartset Programming app. When I run that program using Wine, it recognizes the keyboard and works just fine for remapping keys and creating macros.
So, therefore, I have a difficult time believing that Wine support for USB is somehow at fault for the failure of Durgod's app to recognize its own keyboard.
Using the lsusb command, I get the following line when the Durgod keyboard is plugged in:
Bus 001 Device 003: ID 2f68:0082 (no other description)
The fact that there is no human-readable description (e.g. my mouse shows up as "Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver") is the only odd thing I've been able to locate, but I don't know if that might have any relevance to my issue.
Does anyone have any ideas?
Thanks, and stay safe.
I recently purchased a Durgod Taurus K320 TKL Mechanical Keyboard, one of a series of rather impressive keyboards; it can be seen at https://www.amazon.com/dp/B078H3WPHM...v_lig_dp_it_im
This particular version is wired through a USB port and is "plug and play." So far, so good. Not quite the same feel as my treasured Northgate OmniKey (still in regular use after 28 years), but appears to play in the same league.
Durgood also provides a Windows only app for creating macros, reassigning keys and the like, called the Durgod Zeus Engine, which can be downloaded from https://www.durgod.com/Durgod-Zeus-Engine?_l=en
The company's tech support assured me that there is no way this app can be used under Linux. Of course, I refused to believe/accept that, so I attempted to run the app under Wine, and it ran just as described in the company's documentation. Once again, so far, so good.
BUT - the application didn't recognize that one of its devices was installed on my system (I've tried it on Mint 19.1, Mint 19.3 and Ubuntu 20.04). I then installed the software on a Windows 10 laptop and it immediately recognized the keyboard and opened up all the options for creating macros, etc. though I didn't actually attempt to create any yet, since as a long-term solution that would be a pain.
Trolling the web, it seems that many folks mention that Wine doesn't always recognize USB devices and there are many posts describing rather elaborate "work-arounds" for this.
As it happens, I also use another USB-connected programmable keyboard, the Kinesis Freestyle Edge, which can be seen at https://www.amazon.com/KINESIS-Gamin...43&sr=1-3&th=1
While basic programming of the Kinesis can be done from the keyboard itself, Kinesis also supplies a Windows app, called the Smartset Programming app. When I run that program using Wine, it recognizes the keyboard and works just fine for remapping keys and creating macros.
So, therefore, I have a difficult time believing that Wine support for USB is somehow at fault for the failure of Durgod's app to recognize its own keyboard.
Using the lsusb command, I get the following line when the Durgod keyboard is plugged in:
Bus 001 Device 003: ID 2f68:0082 (no other description)
The fact that there is no human-readable description (e.g. my mouse shows up as "Bus 003 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver") is the only odd thing I've been able to locate, but I don't know if that might have any relevance to my issue.
Does anyone have any ideas?
Thanks, and stay safe.