JSubelj / g910-gkey-macro-support

GKey support for Logitech G910 Keyboard on Linux
GNU General Public License v3.0
99 stars 31 forks source link

usb dev: not found. retrying #7

Closed panagiotisgts closed 5 years ago

panagiotisgts commented 5 years ago

Hello, After following your instructions to install your package and ensuring uinput is already installed, under the log file ( /var/log/g910-gkeys.log ) there is an endless amount of :

2019-01-22 13:15:56,866 [DEBUG] {lib.keyboard_initialization.usb_and_keyboard_device_init} - usb dev: not found. retrying

The test macro key under G1 is not functioning, although using g810-led --list-keyboards correctly returns my G910 keyboard information.

Under Manjaro, kernel 4.19.14

JSubelj commented 5 years ago

First thank you for using my software.

This can sometimes happen if you run the driver when some other program already locked onto the keyboard. Have you tried restarting the service/enabling the service and restarting the computer? If that dosen't work try unplugging all usb devices and re plug the keyboard.

panagiotisgts commented 5 years ago

Thanks for your reply. Tried all of the above mentions but still no luck on getting macros to work. Systemctl status displays it as active since boot but showkey -a only registers macro presses when keys are mapped to F* keys. Also, during bootup keyboard gets disconnected ~4 times before finally becoming available. Will test this on another computer running stock Arch to see if it works properly.

JSubelj commented 5 years ago

Afaik macros don't get registered by showkey, because they are not normal keys and their signal does not correspond to any known key. Do you still get same usb dev: not found messages? If so then maybe your keyboard does not have the same product id (or maybe even vendor id). Currently this two variables are set to:

USB_VENDOR = 0x046d
USB_PRODUCT = 0xc335

The 4 time disconnect is a known issue caused by g810-led it is described here: https://github.com/MatMoul/g810-led/blob/master/INSTALL.md#boot-profiles-

Also please include logs produced byjournalctl -u g910-gkeys, logs stored in /var/log/g910-gkeys.log and your current configuration stored in /etc/g910-gkeys/config.json via pastebin or any other method.

panagiotisgts commented 5 years ago

Managed to get it working with your USB_VENDOR and USB_PRODUCT variables hint. Dug into the python files and changed them and rebuilt it. Works like a charm now! Thank you very much for your help and for your software!

JSubelj commented 5 years ago

Glad I can be of help! Can you please share your USB_VENDOR and USB_PRODUCT variables and where you found them so I can add the data to wiki for troubleshooting.

Also, do you have Orion Spark or Orion Spectrum keyboard?

panagiotisgts commented 5 years ago

I think it's the Spark, the first generation.

My product Information :
USB_VENDOR = 0x046d
USB_PRODUCT = 0x0c32b

To get your keyboard specific info execute g910-led --print-device . The variables are initialized on the file /build/lib/lib/keyboard_initialization/usb_and_keyboard_device_init.py

Glad I was able to provide some help :)

JSubelj commented 5 years ago

Thank you very much. I edited the wiki and will fix this in the future release.

JSubelj commented 5 years ago

I added your USB_PRODUCT variable into the driver so it should work when installed without any modifications. If you have any questions or problems please open a new issue request or comment here (related issue).

Have fun.