Package Details: chromebook_keyboard_backlight_driver 1.0r24.g39568fa-2

Git Clone URL: (read-only)
Package Base: chromebook_keyboard_backlight_driver
Description: Keyboard backlight driver for various chromebook models
Upstream URL:
Licenses: GPL
Conflicts: chromebook_keyboard_backlight_driver
Provides: chromebook_keyboard_backlight_driver
Submitter: poppyschmo
Maintainer: poppyschmo
Last Packager: poppyschmo
Votes: 0
Popularity: 0.000000
First Submitted: 2016-01-20 07:07
Last Updated: 2018-01-26 01:28

Latest Comments

1 2 Next › Last »

poppyschmo commented on 2018-01-26 08:21

Thanks gustavf. Didn't think to check the src repo for a replacement to the missing shell script; just blindly deleted the install line.

If anyone still using this package feels like maintaining it, please have at it. I've long since gone the dkms route for this driver. Actually, just now posted that version, for posterity, though it'll inevitably succumb to disrepair, as well.

gustavf commented on 2018-01-25 07:11

Hiya, seems as they have substituted to a binary called keyboard_backlight, could you update the PKGBUILD?

(in this merge

el_segfaulto commented on 2017-03-18 03:37

On a Toshiba Chromebook 2. I had the same issue with insmod (No such device). I noticed the "Manufacturer" entry on the DMI table was title-case, but in the driver code it was set to all-caps. Changing DMI_MATCH(DMI_SYS_VENDOR, "GOOGLE") to DMI_MATCH(DMI_SYS_VENDOR, "Google") in chromebook_kb_backlight.c fixed the issue for me.

poppyschmo commented on 2016-05-02 02:13

Rookie error on my part. Didn't account for multiple extramodules dirs. Thanks for the pastebin/patience. As far as `make --jobs` goes, not sure at first glance, but I'll look into it. Thanks.

funn commented on 2016-05-01 21:17

Here's output of 'pacman -Ql chromebook_keyboard_backlight_driver' on my system with the recent version of the package

I have two kernel packages installed, guess there are still errors.

funn commented on 2016-05-01 20:07

Also the build breaks with "-j" flag values more than 1 in /etc/makepkg.conf
I have no idea why, and don't see it as a major problem. Thanks for maintaining this package bro.

funn commented on 2016-05-01 20:04

I really think you should keep this package as a simple kernel module, arch users all tend to deal with this stuff in their own way. We have an interface in /sys/class/leds and that's enough.

poppyschmo commented on 2016-05-01 18:20

@funn: Ah, the idiosyncrasies of naming conventions and version overflow. Never would have guessed the arch way was to truncate 3.xx to 3.x for extramodules, having been on 4.x for a year (to the day) now. Regardless, good catch && sorry for any grief this may have caused.

@TomCruise9000: Cheers for the info dump, though I wonder if it might be more at home on the wiki rather than buried in the bowels of some obscure AUR comments thread. BTW, as far as I can tell, the sole difference between upstream and the tar is the setuid binary. If upstream decides to swap out the *.sh for a *.c version, then I'll gladly include a make/install to /usr/local/bin. It's a sensible hack and the only sane way, AFAIK, to implement backlight hotkeys as an unprivileged user.

funn commented on 2016-04-30 21:09

Upstream got fixed, though PKGBUILD got an error. Extramodules directory is wrong, it's 3 digits of kernel version and kernel name, when it should be 2 digits and a name.

TomCruise9000 commented on 2016-04-23 13:10

Also some things to clarify: 1) On a fresh install, I was running Elementary OS based on Ubuntu 14.04 "Trusty Tahr") – and on kernel 3.19.XXX which should have worked. The late 2015 Toshiba CB I have worked flawlessly with Coolstar's custom ROM, but the Dell Lulu was having issues. CoolStar told me to upgrade the kernel from the general kernel to GalliumOS's customized kernel which is designed specifically for Chromebooks. After upgrading the kernel, the computer seems to be running fine. 2) When following's guide for the Toshiba CB backlight drivers (which are the same or similar to the Dell Lulu), here is the correct information to type in. On lines 8 & 9, you should type:
sudo insmod chromeos_keyboard_leds.ko
sudo insmod chromebook_kb_backlight.ko

in my original post below, website seemingly forgot to put in the .ko part.

tar zxvf backlight-driver.tar.gz
cd chromebook_keyboard_backlight_driver
sudo cp chromeos_keyboard_leds.ko chromebook_kb_backlight.ko /lib/modules/`uname -r`/kernel/drivers/platform/chrome/
sudo depmod -a
sudo insmod chromeos_keyboard_leds.ko
sudo insmod chromebook_kb_backlight.ko

sudo cp keyboard_brightness /usr/local/bin
sudo chmod u+s /usr/local/bin/keyboard_brightness

and also added "chromeos_keyboard_leds" and "chromebook_kb_backlight" to the end of /etc/modules so that they load automatically."