Well, the keyboard and mouse arrived in its own box (not a shipping carton), was easy to slide the whole thing out from the narrow end (I actually hate unpacking cartons so the less of it the better lol). Set up could not have been easier... pull plastic tabs to complete battery connections (came with 2 AA in keyboard, and 1 AA in mouse) and plug the receiver in.
Both the keyboard and mouse are a bit too small for me, but I'll just have to get used to them. The keyboard isn't horrible to type on, but it's fairly shallow stroked and doesn't have a lot of feedback. I should be able to get used to it though.
The scroll wheel on the mouse is good (notched, doesn't roll when middle clicked)
While these receivers (and that Chesen USB to PS/2 adapter) always have a bunch of confusing provisions on them, this one is a lot saner and doesn't confuse input detection systems (i.e. steam input was mis-programming that RedChunder keyboard I sent back)
Code: Select all
[grogan@nicetry ~]$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver Mouse id=10 [slave pointer (2)]
⎜ ↳ Logitech USB Receiver Consumer Control id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Logitech USB Receiver id=9 [slave keyboard (3)]
↳ Logitech USB Receiver System Control id=12 [slave keyboard (3)]
↳ Logitech USB Receiver Consumer Control id=13 [slave keyboard (3)]
Now there is something fuct here... one of those "Power Buttons" is actually the system's power button for ACPI shutdown (that's an input device). The trick is, I don't know which, from that (but it doesn't matter, it is what it is... press one of them never). Xinput (library) is not very smart to put something like that in a separate device tree, it's an abstraction.
It doesn't matter if you have just a cordless mouse too, it's going to be the same receiver with vestigial devices. The last time I had a Logitech cordless mouse I was still gaming in Windows. In both Windows 10 and Windows 7, I had to disable the "Consumer Control" devices in device manager, or I had jerky performance in some older games. Odd, but true. It was I guess causing the mouse to be mis-programmed and causing sync issues in the games.
At least on Linux you don't get that logitech updater service (can't remember the name) that loads as a mouse driver device. I used to disable that in device manager too if Logitech shitware was installed (Windows update would pull that in too)
Anyway, "Mouse and Touchpad" settings in XFCE gets the device correct this time, and the mouse acceleration slider works. But only to a point, the mouse just does not have the acceleration capabilities. It is a low DPI device and properties are simply ignored by xinput. It programs them differently. I can slow it right down, but anything above acceleration factor 7 (default 5 which was a bit too slow) with the slider has no further effect on the pointer. XFCE is kind of dumb that way too, it overrides anything it configures (such that the real settings have no effect). It takes over the mouse settings, but then doesn't give you the means to set other things like acceleration thresholds. For example if you do image editing where you select by hand, you want an acceleration threshold so acceleration doesn't kick in until you have moved a number of pixels (e.g. 4) for precision.
Note: XFCE would present an acceleration threshold slider for a high DPI device. That's an ignored property. If I change the mouse device to the "Consumer Control" pointer device (id=11), I have different acceleration controls... for a high DPI device. However, it's not the actual device it's just part of the receiver's facility... it COULD be a high DPI mouse model the receiver is to be programmed for, they just re-use chips). This is basically the same issue as that RedChunder mouse that was in a lower DPI mode by default, with only software control overrides. This mouse is only a low DPI device, though.
I'm going to have to go to IceWM now (plain jane window manager... that's where I play games) to test anything else. Maybe I can get the mouse working more nicely there, using the xinput utility, prepending commands in ~/.xinitrc
