| Git Clone URL: | https://aur.archlinux.org/openrgb-git.git (read-only, click to copy) |
|---|---|
| Package Base: | openrgb-git |
| Description: | Configuration utility for RGB lights supporting motherboards, RAM, & peripherals |
| Upstream URL: | https://gitlab.com/CalcProgrammer1/OpenRGB |
| Keywords: | led |
| Licenses: | GPL-2.0-only |
| Conflicts: | openrgb |
| Provides: | openrgb |
| Submitter: | Myrddin |
| Maintainer: | CalcProgrammer1 |
| Last Packager: | CalcProgrammer1 |
| Votes: | 35 |
| Popularity: | 0.93 |
| First Submitted: | 2020-02-14 03:47 (UTC) |
| Last Updated: | 2024-08-15 01:12 (UTC) |
Still doesn’t work like it should. Here is what i did:
But no devices are detected.
After i reinstalled i2c-piix4-aura-dkms, devices are detected again.
The issue with 99-openrgb.rules seems to be fixed, as that was renamed and doesn’t have to be deleted anymore.
Myrddin, yes the output does include GLIBCXX_3.4.26 as well as GLIBCXX_3.4 through GLIBCXX_3.4.28. I am running 64bit not 32bit. Also, I tried reinstalling my gcc-libs but no change.
zoidby, i2c-piix-aura-dkms is now deprecated as it has been merged upstream in Linux 5.8 & backported to Linux 5.7.6. It shouldn't be necessary any longer.
mmberlin, the issue could be an outdated gcc-libs package (are you on 32-bit?). Check to see if the output of strings /usr/lib/libstdc++.so.6 | grep GLIBCXX | head -n 30 includes GLIBCXX_3.4.26.
With /usr/lib/udev/rules.d/99-openrgb.rules no devices are found.
If i delete that file openrgb works as expected.
I am using i2c-piix4-aura-dkms, maybe that leads to conflicts?
mmberlin, that log is too brief to show the issue. It does seem like a linking issue. Perhaps a missing dependency, could you provide more lines from the output?
Edit your previous comment to add as much as you can.
build error
collect2: error: ld returned 1 exit status
make: *** [Makefile:912: OpenRGB] Error 1
==> ERROR: A failure occurred in build().
Aborting...
Error making: openrgb-git
EDIT: More output lines posted on pastbin: https://pastebin.com/UwWhGhmE
@Myrddin: I2C devices are not even tagged with "uaccess" in the first place. i2c-dev is a kernel driver, that's why giving access to those device nodes to any logged user is a really bad idea.
Again, 'i2c' and 'plugdev' groups DO NOT EXIST in ArchLinux and why should they? The UDEV rules should be adapted to ArchLinux since there is no "most compatible option for all distribution". Each distro has it's own perks.
G-Skill TRIDENT Z DRAM's are not enlisted in OpenRGB if 'i2c' group does not exist and/or the user is not assigned to that group. As a workaround, you can run it as root and it just works. Or just give access to an existing group.
99-openrgb.rules belongs to the source code, Arch Linux better support should be addressed to the developer who is btw providing the Debian package files.
Udev rules should be patched for OpenRGB to read/write to I2C devices (i.e. Aura DRAM's). Group 'i2c' does not exists in ArchLinux, there is no 'uaccess' for those devices and there should NOT be: I2C devices should only be accessible to a high-level users group for security reasons.
IMHO you could remove 'plugdev' assignments altogether (since we have 'uaccess' there), replace 'i2c' group with 'wheel' and chmod 660 the devices. This is how I fixed it on my workstation:
$ cat /etc/udev/rules.d/custom-i2c.rules
KERNEL=="i2c-[0-99]*", GROUP="wheel", MODE="0660"
Pinned Comments