Open xerootg opened 2 weeks ago
miskcoo
commented
2 weeks ago It seems the message comes from the duplicated call of ugreen-probe-leds in both ugreen-diskiomon and ugreen-netdevmon.
Can you try to only enable one of them, and check whether this message will disappear? If so, then try to start another service and check whether the message appear again.
If that is the case, I've updated ugreen-probe-leds and you can try the new version.
xerootg
commented
2 weeks ago oh, that last commit seems to have atleast killed the error:
[ 7.395324] i2c_dev: i2c /dev entries driver
[ 7.405321] led_ugreen: loading out-of-tree module taints kernel.
[ 7.405328] led_ugreen: module verification failed: signature and/or required key missing - tainting kernel
[ 7.405561] led_ugreen: initializing
[ 7.412167] led_ugreen: i2c probed
[ 7.416055] led_ugreen: probed led id 0, status 1, rgb 0xffffff, brightness 128, t_on 256, t_cycle 768
[ 7.420299] led_ugreen: probed led id 1, status 1, rgb 0xffa500, brightness 255, t_on 256, t_cycle 4864
[ 7.473987] led_ugreen: probed led id 2, status 1, rgb 0xffffff, brightness 255, t_on 256, t_cycle 4864
[ 7.484873] led_ugreen: probed led id 3, status 1, rgb 0xffffff, brightness 255, t_on 256, t_cycle 4864
[ 7.531837] led_ugreen: probed led id 4, status 1, rgb 0xffffff, brightness 255, t_on 256, t_cycle 4864
[ 7.541828] led_ugreen: probed led id 5, status 1, rgb 0xffffff, brightness 255, t_on 256, t_cycle 4864
[ 8.121078] i2c i2c-10: new_device: Instantiated device led-ugreen at 0x3aI just need to figure out signing the dkms produced module and I'd consider this absolutely a working solution! :)
xerootg
commented
2 weeks ago actually, it looks like I'm missing something for ugreen_leds_cli
[xero@nas ~]$ sudo ugreen_leds_cli all
Err: fail to open the I2C device.
Please check that (1) you have the root permission;
and (2) the i2c-dev module is loaded.strace:
getdents64(3, 0x34dded00 /* 13 entries */, 32768) = 400
newfstatat(AT_FDCWD, "/sys/class/i2c-dev/i2c-3", {st_mode=S_IFDIR|0755, st_size=0, ...}, 0) = 0
openat(AT_FDCWD, "/sys/class/i2c-dev/i2c-3/device/name", O_RDONLY) = 4
read(4, "i915 gmbus tc1\n", 8191) = 15
close(4) = 0
newfstatat(AT_FDCWD, "/sys/class/i2c-dev/i2c-10", {st_mode=S_IFDIR|0755, st_size=0, ...}, 0) = 0
openat(AT_FDCWD, "/sys/class/i2c-dev/i2c-10/device/name", O_RDONLY) = 4
read(4, "SMBus I801 adapter at efa0\n", 8191) = 27
openat(AT_FDCWD, "/dev/i2c-10", O_RDWR) = 5
ioctl(5, _IOC(_IOC_NONE, 0x7, 0x3, 0), 0x3a) = -1 EBUSY (Device or resource busy)
close(5) = 0
close(4) = 0
close(3) = 0I'm running arch linux-zen 6.11, and i2c_dev is loaded:
[xero@nas ~]$ lsmod | grep i2c
i2c_dev 28672 0
i2c_i801 40960 0
i2c_smbus 20480 1 i2c_i801
i2c_mux 16384 1 i2c_i801
i2c_algo_bit 24576 2 xe,i915@xerootg Once the driver is loaded, ugreen_leds_cli can no longer controls the lights -- you should directly write files in /sys/class/leds/; or unload the driver.
xerootg
commented
2 weeks ago I wondered if that was a thing. I assume it would be a reasonable thing to check if the driver is loaded and either use the driver or exit with a more concise error message?
miskcoo
commented
2 weeks ago Of course it is reasonable. There is some unmerged code for this, and I can merge them recently.
I have this working on arch. I've got some fun stuff in dmesg though. I'll take the readme I wrote up and script it as a contribution, possibly even as a PKGBUILD so it can be handled as an AUR if I have time, if this isn't concerning (it seems concerning). arch install readme