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
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?