Package Details: clevo-xsm-wmi-dkms 1.1-7

Git Clone URL: https://aur.archlinux.org/clevo-xsm-wmi-dkms.git (read-only, click to copy)
Package Base: clevo-xsm-wmi-dkms
Description: A reverse engineering driver for the Clevo SM series backlight keyboard (DKMS version)
Upstream URL: https://bitbucket.org/tuxedocomputers/clevo-xsm-wmi
Licenses: GPL
Conflicts: clevo-xsm-wmi, tuxedo-wmi, tuxedo-wmi-dkms
Provides: clevo-xsm-wmi
Submitter: mrozanc
Maintainer: dariost
Last Packager: mrozanc
Votes: 5
Popularity: 0.000000
First Submitted: 2015-07-06 21:59 (UTC)
Last Updated: 2018-07-22 12:37 (UTC)

Pinned Comments

mrozanc commented on 2019-04-04 18:53 (UTC) (edited on 2019-04-04 18:53 (UTC) by mrozanc)

Sorry for the late reply mjtarch, I have a lot to do these times and I don't use my clevo laptop much.

The upstream project is abandonned as stated on the bitbucket page (https://bitbucket.org/tuxedocomputers/clevo-xsm-wmi -> https://bitbucket.org/tuxedocomputers/clevo-xsm-wmi/issues/44/the-status-and-the-future-of-tuxedo-clevo -> https://github.com/tuxedocomputers/tuxedo-keyboard).

If the replacement project don't support your hardware, you can still create a patch file for clevo-xsm-wmi.c using the diff command or git, then apply your patch as I did for P950ER in your modified PKGBUILD. Then you build the package using makepkg and install it with pacman -U.

I didn't have any feedbacks from users of the new modules, maybe is there no reason to continue this PKGBUILD?

Latest Comments

« First ‹ Previous 1 2 3

dariost commented on 2017-07-29 18:30 (UTC)

The source fails the validation: ==> Validating source files with sha256sums... clevo-xsm-wmi-1.1.src.tar.gz ... FAILED dkms.conf ... Passed Makefile ... Passed

mrozanc commented on 2017-07-29 13:36 (UTC)

Hi aatoma! Thanks, I changed the URL.

aatoma commented on 2017-07-29 10:43 (UTC)

Hi mrozanc, build fails because upstream URL is no longer valid

<deleted-account> commented on 2017-05-12 19:25 (UTC)

Now I confirm that it is works for Clevo W650SC (airplane LED and key). Yes you are right about dependency on gcc, though DKMS itself depends on it - no need to doubling it. Anyway, thanks, because the main issue was fixed.

mrozanc commented on 2017-05-11 20:57 (UTC) (edited on 2017-05-11 21:24 (UTC) by mrozanc)

Hello arisudesu, As this is a DKMS package, the module is built on each kernel update, so gcc is needed to compile it. I think assuming base-devel is installed on an AUR PKGBUILD should be relevant only in the makedepends context, not in the actual package dependencies (cf. the wiki about makedepends: https://wiki.archlinux.org/index.php/PKGBUILD#makedepends) otherwise anyone installing my package without using AUR could have a broken dependency. About your custom kernel compatibility issue, you are right, I pushed it with linux-headers only.

<deleted-account> commented on 2017-05-09 19:32 (UTC)

Maybe you should do some cleanup on dependencies: first, gcc and make (base-devel) are assumed to be installed, when using AUR, so they are not needed. The second, dependency on linux does not work well with custom kernels (e.g. linux-ck-haswell). Maybe depend only on linux-headers?

« First ‹ Previous 1 2 3