search

duncanthrax / roccat-vulcan

Linux RGB LED effect support for the Roccat Vulcan 100/120 Keyboard
GNU General Public License v3.0
79 stars 20 forks source link

Add 121 Aimo #12

Open 888iee opened 5 years ago

888iee commented 5 years ago

Hi,

pls add Support for Roccat Vulcan 121 Aimo(Bus 005 Device 003: ID 1e7d:3098 ROCCAT ). Is it possible with your Software to use static colors?

duncanthrax commented 5 years ago

Hi, the 0x3098 PID should already be supported - does the software not work for you? If so, what are the symptoms?

spo0lsh commented 4 years ago

Hello, I have ID 1e7d:3098 ROCCAT and only the wave effect works fine.

metas-jb commented 4 years ago

@duncanthrax

Having the same issue since the last update. Please note, I updated using the AUR via pacman: https://aur.archlinux.org/packages/roccat-vulcan

Environment:

Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 4 0 200 200 Ghost typing color, initial key Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 5 0 200 200 Ghost typing color, first neighbor key Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 6 0 200 200 Ghost typing color, second neighbor key Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 7 0 0 0 (null) Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 8 0 0 0 (null) Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: 9 0 0 0 (null) Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: open_device(1e7d, 3098): LED interface at USB path 0001:0005:03 Jan 12 09:53:00 tee-manjaro roccat-vulcan[23261]: Error: Unable to find keyboard Jan 12 09:53:00 tee-manjaro systemd[4657]: roccat-vulcan.service: Main process exited, code=exited, status=255/EXCEPTION Jan 12 09:53:00 tee-manjaro systemd[4657]: roccat-vulcan.service: Failed with result 'exit-code'.


---

Symptoms are as follows:
* after boot:
  * only flickering (ghost-typing) 
  * short flickering of keys (and neighbors) when typing
* running `roccat-vulcan -v` command manually
  * same error as systemd service:

occat-vulcan -v ROCCAT Vulcan for Linux [github.com/duncanthrax/roccat-vulcan] Effect Color Table (change these with -c option) colorIdx R G B Desc

0 0 0 119 Base keyboard color (dark blue) 1 2303 0 -255 Typing color, initial key (over-red, under-blue) 2 2303 0 -143 Typing color, first neighbor key 3 2303 0 0 Typing color, second neighbor key 4 187 0 204 Ghost typing color, initial key 5 153 0 187 Ghost typing color, first neighbor key 6 85 0 170 Ghost typing color, second neighbor key 7 0 0 0 (null) 8 0 0 0 (null) 9 0 0 0 (null) open_device(1e7d, 3098): ignoring non-LED interface #0 open_device(1e7d, 3098): ignoring non-LED interface #1 open_device(1e7d, 3098): ignoring non-LED interface #2 open_device(1e7d, 3098): LED interface at USB path 0001:0005:03 open_device(1e7d, 3098): Unable to open LED interface 0001:0005:03 open_device(1e7d, 307a): No LED device found Error: Unable to find keyboard



---

Testing:
* reinstalling package: NOK -> issue still persists after boot
* `sudo udevadm control --reload-rules && sudo udevadm trigger`: NOK -> issue still persists after reboot
* plugging the keyboard in/out and running the systemd-service: OK
  * rebooting: NOK -> issue still persists

---

Workaround:
1. crawl under your desk
2. pull out the keyboard from USB
3. put it back in
4. restart the systemd-service ( `systemctl --user restart roccat-vulcan.service`)
5. enjoy
6. after reboot: repeat from step 1.

---

@duncanthrax 
If you need any more infos, please let me know.
I'm happy to provide anything (related) you need.
BluntlyCat commented 4 years ago

Hello @metas-jb

I had the same issue on archlinux. I installed the package also from the AUR but my mistake was I had accidentially an other package eruption-roccat-vulcan installed which was already running. It prevented roccat-vulcan on opening the device. After disabling and uninstalling this package and if I remember right a restart everything was working fine.

Perhaps this or a similar cause is also the case on your system?

Greetings.

metas-jb commented 4 years ago

@duncanthrax @festeraddams

Solved! Thanks for the hint @festeraddams - I didn't have the https://gitlab.com/X3n0m0rph59/eruption-roccat-vulcan installed. However your suggestion put me on the right track to solve this issue. Two applications were competeing for the device which resulted in roccat-vulcan to spasm out.

I previously created a user-land systemd-unit in ~/.config/systemd/user/roccat-vulcan.service which I put in enable on login.

However, apparently the latest update (I guess) created a system-wide systemd-unit with default config settings: /etc/systemd/system/roccat-vulcan.service

So I guess the system-wide systemd unit started first - then the user systemd unit started on login and both were competeing for the device which resulted in none of the two working as intended and the keyboard started flickering and not applying either of the two settings.

In order to solve this, I disabled the systemwide service, made sure the user service is enabled and tested by rebooting:

sudo systemctl disable roccat-vulcan.service   #disable system wide systemd unit
systemctl --user enable roccat-vulcan.service  #enable user systemd unit
sudo shutdown -r now

And voilá: everything works fine now. My user settings are respected and the two units stopped cometeing for the keyboard!

Thanks again @festeraddams