Arch Linux

Darklighter

Member

Registered: 2011-08-10

Posts: 11

failed to initialize for relative axes

Is there a way to prevent xorg from registering keyboards as mice? Whenever I run xinit, I get:

(EE) Logitech Logitech Illuminated Keyboard: failed to initialize for relative axes.

Harmless, but mildly annoying. Relevant log:

[  8902.107] (--) Logitech Logitech Illuminated Keyboard: Found 1 mouse buttons
[  8902.107] (--) Logitech Logitech Illuminated Keyboard: Found scroll wheel(s)
[  8902.107] (--) Logitech Logitech Illuminated Keyboard: Found relative axes
[  8902.107] (--) Logitech Logitech Illuminated Keyboard: Found absolute axes
[  8902.107] (--) Logitech Logitech Illuminated Keyboard: Found keys
[  8902.107] (II) Logitech Logitech Illuminated Keyboard: Configuring as mouse
[  8902.107] (II) Logitech Logitech Illuminated Keyboard: Configuring as keyboard
[  8902.107] (II) Logitech Logitech Illuminated Keyboard: Adding scrollwheel support
[  8902.107] (**) Logitech Logitech Illuminated Keyboard: YAxisMapping: buttons 4 and 5
[  8902.107] (**) Logitech Logitech Illuminated Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200

It's also very hard to get hits on Google, as the message appears in pretty much everyone's logs.

lorin

Member

Registered: 2011-12-06

Posts: 28

Re: failed to initialize for relative axes

Yeah, I've been baffled by this as well. I know it's not exactly useful, but I was plagued by these for some time and then with the last update to xorg they just disappeared. (Along with the much more annoying behaviour of scrolling through countless screen modes before finally starting X.)

---

github ○