Search Criteria
Package Details: ddcci-driver-linux-dkms 0.4.5-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/ddcci-driver-linux-dkms.git (read-only, click to copy) |
---|---|
Package Base: | ddcci-driver-linux-dkms |
Description: | A pair of Linux kernel drivers for DDC/CI monitors (DKMS) |
Upstream URL: | https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/ |
Keywords: | backlight hdmi monitor |
Licenses: | GPL2 |
Conflicts: | ddcci-driver-linux |
Submitter: | irtimmer |
Maintainer: | ewout (Porous3247) |
Last Packager: | Porous3247 |
Votes: | 34 |
Popularity: | 0.007751 |
First Submitted: | 2017-04-15 18:51 (UTC) |
Last Updated: | 2024-07-24 04:30 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
LarryDave commented on 2024-03-26 19:16 (UTC)
@vighbox You could use ddcutil to set the brightness manualy, maybe bind the commands to a key.
https://wiki.archlinux.org/title/Backlight#External_monitors
LarryDave commented on 2024-03-26 19:14 (UTC)
I don't consider this important enough to downgrade. Just have to use the physical monitor buttons like plebs in the meantime. Updates on this package are very slow, we might wait for a very long time or it may never get fixed too.
vighbox commented on 2024-03-24 03:43 (UTC) (edited on 2024-03-24 03:58 (UTC) by vighbox)
@LarryDave I came here looking for a solution. I'm glad I found your post so I know it wasn't me.
(I tried to rebuild the dkms but failed)
So what do you think the best course of action? Downgrade Linux to the previous version?
EDIT: It looks like they are working on a solution https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/-/issues/39
LarryDave commented on 2024-03-21 15:20 (UTC)
Does not work anymore with kernel 6.8 as some stuff related to it was removed from the kernel. mkinitcpio also fails with this installed and I had to remove it.
GPereira commented on 2023-10-09 19:20 (UTC)
I am loading the ddcci module in mkinitcpio and the slider doesn't show up on GNOME. What do I need to do?
Andrei_Korshikov commented on 2023-06-10 10:26 (UTC)
@dxwil I upgraded the kernel to 6.3.6 and got the same behavior as you. My solution is to modprobe ddcci_backlight in 3 seconds after starting SDDM service (
After=sddm.service
and additionalExecStart=/usr/bin/sleep 3
beforeExecStart=/usr/bin/modprobe ddcci_backlight
).Porous3247 commented on 2023-05-06 16:07 (UTC) (edited on 2023-05-07 00:34 (UTC) by Porous3247)
@UmarJ
Thanks for letting me know, I applied your changes.
Note that the patch does not work on kernel versions before 6.3. Sorry to anyone who can't get it working for kernels older than 6.3--I don't know how to make it work for everyone.
Edit: I updated to patch to use the
LINUX_VERSION_CODE
macro so that building now works on any kernel versionUmarJ commented on 2023-05-06 13:49 (UTC)
Apply this patch for compatibility with Linux 6.3 and above.
Source
joshtau commented on 2023-04-02 11:12 (UTC) (edited on 2023-04-02 11:12 (UTC) by joshtau)
Yeah, I have to modprobe when my desktop env starts.
I have a super hacky script I whipped up in 30s, which is (note 6 is my monitor ID):
I have this in my labwc autostart file. If I wasn't lazy, or was using sway, I would have a systemd service which would listen for when the DE started.
dxwil commented on 2023-04-01 10:29 (UTC)
@Andrei_Korshikov I tried using your systemd file but it still did not work,
dmesg
returned this:[ 26.153345] ddcci 4-0037: core device [6e] probe failed: -19 [ 26.153362] i2c i2c-4: new_device: Instantiated device ddcci at 0x37
Only modprobing ddcci when the desktop is loaded works for me so far
« First ‹ Previous 1 2 3 4 5 6 Next › Last »