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

1 2 3 Next › Last »

ArchMcGee commented on 2024-10-18 22:27 (UTC)

Issue: The current clevo-xsm-wmi-dkms module fails to compile on newer kernels due to a function pointer type mismatch in the .remove callback. Additionally, there are warnings about macro usage that could affect portability.

Proposed Fix:

Change the return type of clevo_xsm_wmi_remove from int to void to match the expected signature. Update macro usage (#if CLEVO_HAS_HWMON) to a more portable form (#ifdef CLEVO_HAS_HWMON). Resources:

You can find the patch and a script to automate these changes below: Patch and Script on Pastebin. Applying this patch ensures compatibility with recent kernels and resolves the mentioned warnings. Thank you for considering this update.

Patch: https://pastebin.com/F5xPPGA9 Script to automate installation for users to use temporarily until repo updated: https://pastebin.com/6rRKXfhX

ArchMcGee commented on 2024-09-24 14:37 (UTC) (edited on 2024-09-24 14:38 (UTC) by ArchMcGee)

Regarding the license issue the best way to fix it is to use the following commands prior to installing the package.

sudo mkdir -p /usr/share/licenses/common/GPL2

sudo cp /usr/share/licenses/spdx/GPL-2.0-or-later.txt /usr/share/licenses/common/GPL2/license.txt

The comment below that suggests removing the license is an alternative but the above commands will make sure the license is in the correct place for the package to install.

Hubbleexplorer commented on 2024-06-08 22:32 (UTC)

Not working anymore


==> Starting package()...
install: cannot stat '/usr/share/licenses/common/GPL2/license.txt': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...
error: failed to build 'clevo-xsm-wmi-1.1-3': 
error: can't build clevo-xsm-wmi-util-1.1-1, deps not satisfied: clevo-xsm-wmi
error: packages failed to build: clevo-xsm-wmi-1.1-3

removing


install -D -m644 /usr/share/licenses/common/GPL2/license.txt "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

fixes the issue

shawnpok33 commented on 2023-05-20 01:16 (UTC) (edited on 2023-05-20 01:19 (UTC) by shawnpok33)

I figured out how to apply the local patch, but i figured i would leave a record that GIGABYTE G5 MD is supported by this

{ .ident = "G5 MD", .matches = { DMI_MATCH(DMI_PRODUCT_NAME, "G5 MD"), }, .callback = clevo_xsm_dmi_matched, .driver_data = &kb_full_color_ops, },

first time on here

mjtarch commented on 2019-11-22 07:29 (UTC)

Hi mrozanc, Your efforts are very much appreciated. I have downloaded your version and followed the steps outlined in the link you provided. Still no luck i'm afraid. The steps are easy to follow but I just don't have control of the lights at the end. I can't think what, but I must be doing something wrong - missing some step. I wonder if i'd fare any better if that change was made into a full release AUR package - say version clevo-xsm-wmi-dkms 1.1-8 and then I could install in the usual manner? Like I said, all steps seem to go as expected until the last - when I try to adjust the values in the device interface files to control such as brighness/colour/etc, I get an error :

[vel-uk-026 /]# echo 1 > /sys/devices/platform/clevo_xsm_wmi/kb_state && echo blue yellow red > /sys/devices/platform/clevo_xsm_wmi/kb_color -bash: echo: write error: Invalid argument

Thank you

mrozanc commented on 2019-11-18 20:09 (UTC)

According to this topic it should work: https://www.pcspecialist.co.uk/forums/threads/successful-ubuntu-18-04-bionic-beaver-installation-on-optimus-ix-15-6.59573/. Just to be sure can you verify you get the same outputs as reported on this topic?

I've compiled a version with the patch here you can test if it works: https://rozanc.cloud/s/R9WZnAerKDaB7ye

mjtarch commented on 2019-11-18 14:15 (UTC)

Hi mrozanc I was assuming my attempts had been incorrect. It seemed right, but by virtue of the fact the keyboard lights still couldn't be configured where other user's can - I figured i'd done something wrong :/

mrozanc commented on 2019-11-18 08:30 (UTC)

Hello mjtarch, I don't understand, if your patch doesn't work. Why would it work if I patch the package?

I'd integrate if it worked but I don't want to have to maintain the module and support has been dropped by upstream...

mjtarch commented on 2019-11-13 17:06 (UTC) (edited on 2019-11-13 17:07 (UTC) by mjtarch)

Still have had no luck getting this working. It's an annoyance only - the laptop is pretty good, but would be great if I had some control over the keyboard backlight.

Is there any chance you could release a new version 1.1-8 with support for my model?

{
    .ident = "Clevo N8xEJEK",
            .matches = {
                DMI_MATCH(DMI_PRODUCT_NAME, "N8xEJEK"),
            },
            .callback = clevo_xsm_dmi_matched,
            .driver_data = &kb_full_color_with_extra_ops,
},

I tried doing a patch for N8xEJEK - still nothing. Thanks