Wacom One CTL-672 is not detected anymore in Ubuntu 18.04 about input-wacom HOT 14 CLOSED

If you are using the 4.16 kernel, you just have to unplug it and plug it back in, and after that, it should work.

from input-wacom.

maybe you should try to install the dependent component first as it indicates.

Makefile:975: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"

As for the SSL error, it seems that the module is not signed, so either validating the module with signed keys or turning off the module signing will help.
BUT, the these won't influence the installation and use in fact.

sign-file: certs/signing_key.pem: No such file or directory

from input-wacom.

Did any of the above suggestions help?

from input-wacom.

Did any of the above suggestions help?

Unfortunately, those suggestions did not help. I also installed the newest version 0.42.0, but still no result
Now when I run grep "" /sys/module/wacom*/version it says "No such file or directory", but actually in "/sys/module" there is a folder wacom_w8001. I tried rebooting, running steps from "Troubleshooting" section.

from input-wacom.

+1

from input-wacom.

+1

from input-wacom.

Please try running our sysinfo.sh script and attaching the generated tarball to this issue. It will gather a number of logs and other system information that should give us a better idea of what's going on...

from input-wacom.

Please try running our sysinfo.sh script and attaching the generated tarball to this issue. It will gather a number of logs and other system information that should give us a better idea of what's going on...

sysinfo.HIPhUh736S.tar.gz

@jigpu Here is the tarball you requested.

from input-wacom.

It looks like the kernel is refusing to load the wacom.ko kernel module that you've compiled and installed. Specifically, the dmesg log states Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 right after detecting the device and when it would normally load the module.

You could try temporarily disabling Secure Boot to see if the device starts working. If it does (and you want to continue using Secure Boot), then you'll need to sign the kernel module and ensure that the key is registered with your system. The following two links look helpful in this regard:

• "How can I do non-automated signing of drivers?"
• "How to sign your own UEFI binaries for Secure Boot"

Read through the above links to be sure, but I think the following three commands should do the trick:

$ sudo update-secureboot-policy --new-key
$ sudo update-secureboot-policy --enroll-key
$ sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/$(uname -r)/extra/wacom.ko

After generating and enrolling a key with the first two commands its possible that modules will be automatically signed in the future. If not, the last command should be all that's necessary to sign updated versions of the module.

from input-wacom.

It looks like the kernel is refusing to load the wacom.ko kernel module that you've compiled and installed. Specifically, the dmesg log states Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 right after detecting the device and when it would normally load the module.

You could try temporarily disabling Secure Boot to see if the device starts working. If it does (and you want to continue using Secure Boot), then you'll need to sign the kernel module and ensure that the key is registered with your system. The following two links look helpful in this regard:

* "[How can I do non-automated signing of drivers?](https://wiki.ubuntu.com/UEFI/SecureBoot#How_can_I_do_non-automated_signing_of_drivers.3F)"

* "[How to sign your own UEFI binaries for Secure Boot](https://wiki.ubuntu.com/UEFI/SecureBoot/Signing)"

Read through the above links to be sure, but I think the following three commands should do the trick:

$ sudo update-secureboot-policy --new-key
$ sudo update-secureboot-policy --enroll-key
$ sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/$(uname -r)/extra/wacom.ko

After generating and enrolling a key with the first two commands its possible that modules will be automatically signed in the future. If not, the last command should be all that's necessary to sign updated versions of the module.

Sorry for the late update. The above method works. I was able to manually sign and use the module.

from input-wacom.

I can't get this to work with secure boot enabled.

$ sudo update-secureboot-policy --new-key
$ sudo update-secureboot-policy --enroll-key
No DKMS modules installed.
$ sudo kmodsign sha512 /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der /lib/modules/$(uname -r)/extra/wacom.ko
$ sudo insmod 4.5/wacom.ko
insmod: ERROR: could not insert module 4.5/wacom.ko: Required key not available

Any ideas what I might be doing wrong?

from input-wacom.

Did the second command ask you for a temporary password and then instruct you to reboot? If not, then its likely that the key wasn't actually enrolled and was never loaded into the kernel. Try running the following command, which should ask you for a temporary password and then instruct you to reboot:

$ sudo mokutil --enable-validation

After rebooting, the blue-colored "MokManager" utility should start up instead of Linux. You'll need to tell it to Enroll MOK and then you can either View Key 0 or Continue. When asked to enroll the key, select Yes and enter the temporary password. Afterwards tell it to Reboot and the system should restart into Linux. At this point the kernel should have the key loaded into memory and be able to load the kernel module (and indeed, if your tablet was connected, already have done so without you needing to run insmod manually).

from input-wacom.

Aha yeah I've since found the rest of the instructions and got it installed. Thanks!

from input-wacom.

Yes also facing the same problem.
Setting is detecting the device name but unable to move pointer with pen and xsetwacom commands are not working in the terminal and a only the xsetwacom --help is working .
I think that the driver is not detecting it properly . plz help

from input-wacom.