Corsair: Difference between revisions

(2 intermediate revisions by 2 users not shown)

Line 1:

~~The following page talks about running~~ [https://~~github~~.com~~/ckb-next/ckb-next ckb-next~~] ~~on NixOS to configure your Corsair~~ peripherals!

[https://www.corsair.com CORSAIR] is an American computer peripherals and gaming brand.

== Example config ==

Its possible to configure its keyboards and mice with an open source driver: [https://github.com/ckb-next/ckb-next ckb-next]

== Example config for ckb-next ==

# /etc/nixos/configuration.nix

Line 12:

Line 13:

</syntaxhighlight>

~~Further configuration can be done~~: ~~see the~~ hardware.ckb-next options ~~on [https://search.nixos.org/options?type=packages&query=hardware.ckb-next search.nixos.org]~~.

See{{nixos:option|hardware.ckb-next}}for more configuration options.

== Limitations ==

Line 19:

Line 20:

If you find a way to automate this, please append to the wiki!

Not a great way of doing it, but it works for me. Create '''~/.config/autostart/ckb-next.desktop''', open it in your favorite text editor and type:<syntaxhighlight lang="desktop">[Desktop Entry]

Categories=Settings;System;

Comment[en_US]=Corsair keyboard driver user interface

Comment=Corsair keyboard driver user interface

Exec=<Location of ckb-next executable> -b

GenericName[en_US]=

GenericName=

Icon=ckb-next

Keywords=ckb;corsair;keyboard;rgb;

MimeType=

Name[en_US]=ckb-next

Name=ckb-next

Path=

StartupNotify=true

Terminal=false

TerminalOptions=

TryExec=<Location of ckb-next executable>

Type=Application

Version=1.0

X-KDE-SubstituteUID=false

X-KDE-Username=</syntaxhighlight>

[[Category:Hardware]]

''The -b makes it run in the background''

I was also running into [https://github.com/ckb-next/ckb-next/issues/604 this issue] when I was running it manually; by using the .desktop file, I no longer have this issue. Lastly, '''every time you get a new version of ckb-next, you'll need to update the path in TryExec and Exec''' (both are the same).

A simple way to find the location of ckb-next is to search for it in the Kickoff Application Launcher (or equivalent, not KRunner) > Right Click > Edit Application then copy what is in the "Program" field. That way, if you haven't run a clean in a while and have an older version of ckb-next still installed, you're grabbing the right one.

@@ Line 1: / Line 1: @@
-The following page talks about running [https://github.com/ckb-next/ckb-next ckb-next] on NixOS to configure your Corsair peripherals!
+[https://www.corsair.com CORSAIR] is an American computer peripherals and gaming brand.
-== Example config ==
+Its possible to configure its keyboards and mice with an open source driver: [https://github.com/ckb-next/ckb-next ckb-next]
+== Example config for ckb-next ==
 <syntaxhighlight lang="nixos">
 # /etc/nixos/configuration.nix
@@ Line 12: / Line 13: @@
 </syntaxhighlight>
-Further configuration can be done: see the hardware.ckb-next options on [https://search.nixos.org/options?type=packages&query=hardware.ckb-next search.nixos.org].
+See{{nixos:option|hardware.ckb-next}}for more configuration options.
 == Limitations ==
@@ Line 19: / Line 20: @@
 If you find a way to automate this, please append to the wiki!
+Not a great way of doing it, but it works for me. Create '''~/.config/autostart/ckb-next.desktop''', open it in your favorite text editor and type:<syntaxhighlight lang="desktop">[Desktop Entry]
+Categories=Settings;System;
+Comment[en_US]=Corsair keyboard driver user interface
+Comment=Corsair keyboard driver user interface
+Exec=<Location of ckb-next executable> -b
+GenericName[en_US]=
+GenericName=
+Icon=ckb-next
+Keywords=ckb;corsair;keyboard;rgb;
+MimeType=
+Name[en_US]=ckb-next
+Name=ckb-next
+Path=
+StartupNotify=true
+Terminal=false
+TerminalOptions=
+TryExec=<Location of ckb-next executable>
+Type=Application
+Version=1.0
+X-KDE-SubstituteUID=false
+X-KDE-Username=</syntaxhighlight>
+[[Category:Hardware]]
+''The -b makes it run in the background''
+I was also running into [https://github.com/ckb-next/ckb-next/issues/604 this issue] when I was running it manually; by using the .desktop file, I no longer have this issue. Lastly, '''every time you get a new version of ckb-next, you'll need to update the path in TryExec and Exec''' (both are the same).
+A simple way to find the location of ckb-next is to search for it in the Kickoff Application Launcher (or equivalent, not KRunner) > Right Click > Edit Application then copy what is in the "Program" field. That way, if you haven't run a clean in a while and have an older version of ckb-next still installed, you're grabbing the right one.