Update description

Remove explicitly enabling bash completion

The only problem I see is that we don't mount the EFI partition which means the user has to do it himself when he wants to update BIOS/firmware.

A patch to the hid-steam module fix this issue is available at
https://lkml.org/lkml/2018/10/14/502. I tested it locally and it fixes the issue with hid-steam and Rocket League for me. So, with this patch, the hid-steam blacklist work-around is no longer needed with the Steam Controller.

T6895 doesn't seem to be related to this bug at all. T6895 is specific to the Steam Controller, while this issue involves a Logitech controller. Additionally, T6895 will be fixed if you downgrade kernels to >=4.17, because the hid-steam module does not exist in any version prior to 4.18.

Still doing this for me :(

Update for version 1.26.1

Update rust to 1.24.1

@jschwanebeck What you linked to is for utilizing a custom toolchain (think building a patched version of rust) from rustup. The toolchain is still managed in the user's home directory. So, while you could use this for the system rustc/cargo, it would still require each user to run rustup toolchain link... themselves.

I'll tackle this. Just a couple questions for @ikey.

Fix Cargo bash completions

A few changes that might need explanation in this update.

Update rust to 1.24.0

@kyrios123 thanks for the heads up. Patch updated for 1.17.0.

Updated patch attached. Obsoletes the other patches.

Added patch to use rustbuild instead of Makefile build system.

Updated patch for cargo 0.17.0 attached

Updated patch in OP for rust 1.16.0

In T2492#50895, @mmeinert wrote:

1. Cargo is not needed to build rust

I could not find a complete list of vendors that use this technology, but Dell is one of them.

Here's a 3rd patch updating libconfuse to 3.0. I separated this patch out, because libconfuse 3.0 introduced some API changes that can cause breakage. So applications that link against it may need patching.

Updated revision bump patch after compile test attached.

In T273#25657, @ikey wrote:

In T273#25620, @baimafeima wrote:

Any updates on this? Some of these patches are already outdated as there are newer releases.

Is there some specific functionality you need from the new NM versions?

I was watching the systemd journal while updating, not sure if this is related, but comar crashed right as the updates finished.

@tiredpixels unfortunately, CONFIG_HID_CORSAIR is only needed for the macro keys on the Vengeance K90 (non-RGB). The K90 uses non-standard HID codes for the macro keys. The RGB models operate differently and do not use these non-standard HID codes, additionally, the K65 has no macro keys. So enabling CONFIG_HID_CORSAIR will have no effect for you. There were some HID quirks added in time for the 4.7 kernel for the RGB models (and the standard K70). These quirks were mostly added to fix the boot delay (see the commit for more info). These changes would be present in your 4.7.4 Arch kernel also.

I have a K70 RGB, which is identical hardware to the K65 (minus the numpad) and it works just fine. There is a slight boot delay, but this happens in every Linux distro and seems to be an issue with the way Corsair's firmware interacts with the Linux kernel. These keyboards have always had issues with Linux, but have gotten better with the newer firmware (except for the boot delay).