Welcome to AWCC Discussions!

[tr1xem]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Bdem1rel]

Hi, I had a question about the installation. I'm using CachyOS rn which is an Arch derivative. If I install the awcc-git package from the AUR, do I still need to make an udev rule for it and add myself to the plugdev group as it's the case for manual installation or is that not needed? Sorry as I'm a bit new to Linux in general.

[tr1xem]

Nope you dont need to do anything if u install it via aur

[Bdem1rel]

So I'm writing this here since I've already closed the issue about not being able to change my keyboard brightness. I wasn't able to do that without root and I think it had something to do with the udev rule. First, I renamed the file to '55-awcc.rules'. I'm not sure if the 99 in '99-awcc.rules' interfered with something or not. Then, I modified the file so that it only contained this line:

SUBSYSTEM=="usb", ATTRS{idVendor}=="187c", ATTRS{idProduct}=="0551", MODE="0660", TAG+="uaccess"

https://wiki.archlinux.org/title/Udev#Allowing_regular_users_to_use_devices -> this part in the Arch wiki recommends this approach and considers the plugdev approach a bug in Arch systems. After doing these two things and after you added my device to database, everything works as expected. Just a heads up.

[tr1xem]

Added Support for new lightpart - LightBar