Doesn't seem to work on Linux Mint 20

[Totone]

Hi I bought the Duo (model: UX481F)& I installed Linux Mint 20. I found this tool & tried to install it, but after reboot, anything new in /sys/class/leds I tried to remove & reinstall the tool, anything changed.

work@duo:/usr/src/asus-wmi-1.0$ uname -r
5.4.0-42-generic

On last install I launched the script prepare-for-current-kernel.sh even if I have the right kernel, but result was the same.

Here are some console I/O during install which maybe can help:

work@duo:/usr/src/asus-wmi-1.0$ ls /sys/class/leds/
asus::kbd_backlight  input25::numlock     input3::capslock  input3::scrolllock
input25::capslock    input25::scrolllock  input3::numlock   phy0-led

work@duo:/usr/src/asus-wmi-1.0$ sudo dkms add -m asus-wmi -v 1.0

Creating symlink /var/lib/dkms/asus-wmi/1.0/source ->
                 /usr/src/asus-wmi-1.0

DKMS: add completed.
work@duo:/usr/src/asus-wmi-1.0$ sudo dkms build -m asus-wmi -v 1.0

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.4.0-42-generic -C /lib/modules/5.4.0-42-generic/build M=/var/lib/dkms/asus-wmi/1.0/build...
Signing module:
 - /var/lib/dkms/asus-wmi/1.0/5.4.0-42-generic/x86_64/module/asus-nb-wmi.ko
 - /var/lib/dkms/asus-wmi/1.0/5.4.0-42-generic/x86_64/module/asus-wmi.ko
Secure Boot not enabled on this system.
cleaning build area...

DKMS: build completed.
work@duo:/usr/src/asus-wmi-1.0$ sudo dkms install -m asus-wmi -v 1.0

asus-wmi.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.0-42-generic/extra/

asus-nb-wmi.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.4.0-42-generic/extra/

depmod...

DKMS: install completed.

[Tendrid]

I'm running into a related problem. I use Ubuntu 20, with cinnamon. While im in Unity, this driver seems to work fine, but in cinnamon, the display is registered, but does not allow me to change the resolution (and the backlight doesnt seem to be working)

It should be really easy to debug with ubuntu 20 by following these steps: https://linuxconfig.org/ubuntu-20-04-cinnamon-desktop-installation

UPDATE: after i logged in using unity, and changed the brightness, i can now see the display in cinnamon! I dont know if i just needed another reboot, or if logging in to unity actually helped, but i hope this knowledge can help someone!

I'm no longer having an issue.

[Totone]

My Mint is also with Cinnamon. Maybe it is the issue. I'll try to install Mate later, maybe it solves the problem. (btw, it's akward to don't understand why there is an issue)

[Plippo]

When the screenpad is turned off using the modified kernel module, it's not visible in the display settings, this may have been the problem. As soon as you increase the brightness, it gets turned on and thus visible.

[Totone]

But the screenpad isn't turned off. The behaviour is like anything had been done (

I didn't install MATE yet. I have to learn to manage my time. I come back here after to give a feedback

[Totone]

Well, it still doesn't work.

I removed Cinnamon (I didn't like it anyway) & reinstall Mint with MATE env. I installed the module but, like before, there is no new input after reboot.

Well ok, I installed xfce desktop environment to maybe have a similar luck as Tendrid but nope. So, why not, I installed Unity desktop env that time & tried to reinstall the module. It did not do, the behaviour is the same I decribed days ago.

I let the log for last try. I'm sure I'm doing something wrong, but I don't understand what.

terminalOutput.txt

EDIT: BUT ! I got a new input in xinput list

totone@duo:~$ xinput list
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Compx 2.4G Receiver Mouse                 id=10   [slave  pointer  (2)]
⎜   ↳ Compx 2.4G Receiver Consumer Control      id=11   [slave  pointer  (2)]
⎜   ↳ ELAN1207:00 04F3:310E Mouse               id=17   [slave  pointer  (2)]
⎜   ↳ ELAN9009:00 04F3:29DE                     id=23   [slave  pointer  (2)]
⎜   ↳ ELAN1207:00 04F3:310E Touchpad            id=18   [slave  pointer  (2)]
⎜   ↳ ELAN9008:00 04F3:2B6A                     id=15   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Compx 2.4G Receiver                       id=9    [slave  keyboard (3)]
    ↳ Compx 2.4G Receiver System Control        id=12   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=20   [slave  keyboard (3)]
    ↳ Compx 2.4G Receiver Consumer Control      id=21   [slave  keyboard (3)]
    ↳ USB2.0 HD IR UVC WebCam: USB2.0           id=13   [slave  keyboard (3)]

    ↳ Asus WMI hotkeys                          id=19   [slave  keyboard (3)]

    ↳ USB2.0 HD IR UVC WebCam: USB2.0           id=14   [slave  keyboard (3)]
    ↳ ELAN9009:00 04F3:29DE                     id=22   [slave  keyboard (3)]
    ↳ ELAN9008:00 04F3:2B6A                     id=16   [slave  keyboard (3)]

The one with id=19 was not here before (id=19 was reserved to another input). Is there something I can do with this?

EDIT: So... it works!

I don't really know how I did this. I fully removed the module, restarted the computer, reinstalled it with a reboot after the sudo sh prepare-for-current-kernel.sh command, restarted once again & this time it worked.

So I guess there is no issue anymore. I think I solved the issue thank to the reboots, maybe some value that couldn't be updated without a reboot

[kevinchappell]

@Totone Seems this can be closed now?

[Totone]

Yes sorry, problem solved (months ago)