Corsair Gaming VOID Headset on Linux

corsair_headset_linux.bash

# Corsair headsets will stuck the apps on your linux system. This is due to wrong usb-mapping.

# thx to http://www.c0urier.net/2016/corsair-gaming-void-usb-rgb-linux-fun

# 1. open terminal
# 2. type this and search the line with your headset
lsusb


# Get the USB ID of the headset and add it to xorg.conf:

sudo nano /etc/X11/xorg.conf

# in my case it looks like this:
Section "InputClass"
    Identifier "Corsair"
    MatchUSBID "1b1c:1b2a"        <----    replace the id with yours
    Option "StartKeysEnabled" "False"
    Option "StartMouseEnabled" "False"
EndSection

# restart system
shutdown -r now

Worked like a charm on the wireless variant too!

Im just about to install Linux Mint 18.1. But Im afraid that something bad is going to happen. I am running both Corsair's Wirless Headset Yellow Edition and Mad Catz RAT 9. In my case should I do anything after Ive installed Linux or will the Products still work. ? Im afraid that It will break my whole PC which is the factor that I don't upgrade from Windows to Linux. ...

It will not break your PC... If the problems the headset causes are so bad you can't do these steps, just unplug the headset until you're done

Can something similar be done for Corsair Void on OSX? I'd like to control the RGB LEDs.

I just purchased a wireless corsair void RGB gaming headset. Works like a charm on antergos and fedora. I don't use windows, not anymore so I can't testify to how it works there but it should work just fine. The only issue I ran into wasn't linux related, I couldn't find the power button. Serves me right for being blind and not using my brain lol. But on a serious note, where can I fix these corsair products (keyboards, headsets, etc) that don't work correctly? You say the USB mappings are wrong. Can this be fixed in the linux USB database, udev hardware database, or is this something corsair has to fix on their end?

@coffeking I think corsair has to fix this. Most other usb-headsets are also able to tell the linux-OS that they are a headset, not a mouse.
The thing is that corsair produce things for 'gamers' and gamers have windows in their opinion. And thats why they don't even test if their products work on linux.

But you can change this by complaining that the products don't works on linux via amazon-ratings. If we all do this, they will listen.

Not working for me on xubuntu 16.04. Tried matching USBID and vendor, but still freezes response to mouse when plugged in. The volume control also still works from headset.

#!/bin/bash
corsairId=$(xinput --list | grep "Corsair Corsair VOID Wireless Gaming Dongle" | grep -oP '(?<=id=)\d*')
if [ -z "$corsairId" ]; then
  echo "Corsair VOID Dongle was not found!"
else
  xinput set-int-prop $corsairId "Device Enabled" 8 0
fi

The above has worked for me; I'm on Kubuntu 16.04 and this script runs when I login. Something similar should be possible for any window manager/desktop.

Also you can try and add Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0 0 0" to the conf file if nothing else works

Any ideas on how to turn off the lights on the Void Pro?

Any ideas on how to turn off the lights on the Void Pro?

Check out HeadsetControl for that.

Any ideas on translating this XOrg fix to Wayland?

@Valinwolf did you figure this out?

@titaniumbones unfortunately not. I ended up throwing in the towel.

I've just bought the Corsair Gaming VOID PRO RGB Wireless SE and I followed @bewitchingme recommendation with some adjustments, works like a charm!

#!/bin/bash
corsairId=$(xinput --list | grep "Corsair Corsair VOID PRO Wireless" | grep -oP '(?<=id=)\d*')
if [ -z "$corsairId" ]; then
  echo "Corsair VOID Dongle was not found!"
else
  xinput set-int-prop $corsairId "Device Enabled" 8 0
fi

Tested on Ubuntu 19.10 and 20.04

I've just bought the Corsair Gaming VOID PRO RGB Wireless SE and I followed @bewitchingme recommendation with some adjustments, works like a charm!

#!/bin/bash
corsairId=$(xinput --list | grep "Corsair Corsair VOID PRO Wireless" | grep -oP '(?<=id=)\d*')
if [ -z "$corsairId" ]; then
  echo "Corsair VOID Dongle was not found!"
else
  xinput set-int-prop $corsairId "Device Enabled" 8 0
fi

Tested on Ubuntu 19.10 and 20.04

@bewitchingme @bLeveque42 I tested the following script in my ~/.bashrc file for my particular headset, but it still would not connect on Ubuntu 20.04:

#!/bin/bash
corsairId=$(xinput --list | grep "Corsair CORSAIR VOID ELITE Wireless Gaming Dongle" | grep -oP '(?<=id=)\d*')
if [ -z "$corsairId" ]; then
  echo "Corsair VOID Dongle was not found!"
else
  xinput set-int-prop $corsairId "Device Enabled" 8 0
fi

It did not throw the dongle not found message, so I assume it ran successfully. However, my headset did not pair with the usb dongle.

Update: I fixed the issue for Ubuntu 20.04

Here is how:

I did not need to modify any files or create any bash scripts. I contacted Corsair customer support who walked me through a hard reset of my gaming dongle:

1. Make sure your headset is turned off.
2. Connect your dongle to your PC.
3. There is a small hole on the usb device that you can insert the end of a paper clip in. You should feel a button being pressed. If you don't then your clip is not long enough as I found out when trying to use a sim extractor tool. Keep this button pressed until the light on the usb device blinks twice per second. If it is blinking only once per second, then you did not perform this step correctly.
4. Remove your paper clip or whatever tool you use. While it is blinking twice per second, press and hold the power button on the headset until the light on the usb dongle stops blinking and becomes a solid light.
5. Go into your system's sound settings (I am using Ubuntu 20.04) and make sure that the output device is selected as your headset and that the input microphone device is also set as your headset if it has a mic.

You can test the speakers within the sound settings to make sure they work. I restarted my computer, and turned off and on my headset to make sure that everything still works. I hope this helps!