zeroz41
commented
3 days ago potentially worth mentioning too, i installed on KDE wayland. If switching to X11 service fails. But i'm not worried about that for now, and is not the issue ;)
Open zeroz41 opened 3 days ago
zeroz41
commented
3 days ago potentially worth mentioning too, i installed on KDE wayland. If switching to X11 service fails. But i'm not worried about that for now, and is not the issue ;)
ldrahnik
commented
3 days ago @zeroz41 Hm. I would try reboot after installation + switch to Windows in case you have dual boot whether it works there / enable, disable there and back.
And try manually send activation i2c commands to each i2c with 0x15 address. Maybe first one found was not NumberPad.
Also, post here dsdt table please:
$ sudo apt-get install iasl
$ cd <work-dir>
$ sudo cp /sys/firmware/acpi/tables/DSDT DSDT
$ sudo iasl -d DSDT
$ sudo gedit DSDT.dslHello thanks for response. With the driver active: i2ctransfer -f -y 5 w13@0x15 0x05 0x00 0x3d 0x03 0x06 0x00 0x07 0x00 0x0d 0x14 0x03 $<0x01> 0xad turns on the "circle" led as expected and 0x00 turns it off. i2clist: i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-6 i2c Synopsys DesignWare I2C adapter I2C adapter
Tried messing with 4 and 6 but they seemed to not be active not accept read write. heres full list. [tj@lappy asus-numberpad-driver-6.4.0]$ i2cdetect -l i2c-0 i2c NVIDIA i2c adapter 1 at 1:00.0 I2C adapter i2c-1 i2c NVIDIA i2c adapter 3 at 1:00.0 I2C adapter i2c-2 i2c NVIDIA i2c adapter 5 at 1:00.0 I2C adapter i2c-3 i2c NVIDIA i2c adapter 6 at 1:00.0 I2C adapter i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-6 i2c Synopsys DesignWare I2C adapter I2C adapter i2c-7 smbus SMBus I801 adapter at efa0 SMBus adapter i2c-8 i2c i915 gmbus dpa I2C adapter i2c-9 i2c i915 gmbus dpb I2C adapter i2c-10 i2c i915 gmbus dpc I2C adapter i2c-11 i2c i915 gmbus tc1 I2C adapter i2c-12 i2c i915 gmbus tc2 I2C adapter i2c-13 i2c i915 gmbus tc3 I2C adapter i2c-14 i2c i915 gmbus tc4 I2C adapter i2c-15 i2c i915 gmbus tc5 I2C adapter i2c-16 i2c i915 gmbus tc6 I2C adapter i2c-17 i2c AUX A/DDI A/PHY A I2C adapter i2c-18 i2c AUX USBC1/DDI TC1/PHY TC1 I2C adapter i2c-19 i2c AUX USBC2/DDI TC2/PHY TC2 I2C adapter
I tried i2c 0x15 for 456, where 5 is the only one that accepted the command. maybe there is a second activation i need to find on device 5? I'm not sure.
Here's dsdt.dsl. its quite large.
ldrahnik
commented
3 days ago @zeroz41 Second activation is 60,61 (more in Readme) but it is implemented in the driver.
ldrahnik
commented
3 days ago @zeroz41 What is the output of $ cat /proc/bus/input/devices. Should be there probably one device for Dialpad and second one for NumberPad.
ldrahnik
commented
3 days ago potentially worth mentioning too, i installed on KDE wayland. If switching to X11 service fails. But i'm not worried about that for now, and is not the issue ;)
@zeroz41 Unfortunatelly you have to reinstall driver each switch in case you use systemd service.
ldrahnik
commented
3 days ago @zeroz41 Ah, not NumberPad, dialpad doesn't work. Yeah, it will be necessary to listen communication on Windows. Do you have Windows? I am open to instruct you how.
zeroz41
commented
3 days ago @ldrahnik roger on reinstall for swithing x11, no big deal. Also i do not have a windows partition. Here's the devices cat. :) cat_devices.txt
ldrahnik
commented
3 days ago @zeroz41 On Linux try click on Dialpad while you run these commands: sudo evtest or sudo libinput debug-events
zeroz41
commented
3 days ago sure thing. Gere is some output from libinput debug-events. Can see the mapped dialpad presses on the left of some event12s
sudo libinput debug-events -event2 DEVICE_ADDED Power Button seat0 default group1 cap:k -event23 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event18 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event0 DEVICE_ADDED Lid Switch seat0 default group3 cap:S -event1 DEVICE_ADDED Power Button seat0 default group4 cap:k -event22 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k -event25 DEVICE_ADDED BY Tech Gaming Keyboard System Control seat0 default group5 cap:k -event26 DEVICE_ADDED BY Tech Gaming Keyboard Consumer Control seat0 default group5 cap:kp scroll-nat -event27 DEVICE_ADDED BY Tech Gaming Keyboard seat0 default group5 cap:k -event28 DEVICE_ADDED BY Tech Gaming Keyboard Mouse seat0 default group5 cap:p left scroll-nat scroll-button -event15 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse seat0 default group6 cap:p left scroll-nat scroll-button -event16 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse Keyboard seat0 default group6 cap:kp scroll-nat -event19 DEVICE_ADDED EVGA Corporation EVGA X12 Gaming Mouse Keyboard seat0 default group6 cap:k -event3 DEVICE_ADDED ELAN9008:00 04F3:4116 seat0 default group7 cap:t size 300x188mm ntouches 10 calib -event6 DEVICE_ADDED ELAN9008:00 04F3:4116 Stylus seat0 default group7 cap:T size 310x194mm left calib -event11 DEVICE_ADDED ASUE1A03:00 04F3:32A0 Mouse seat0 default group8 cap:p left scroll-nat scroll-button -event12 DEVICE_ADDED ASUE1A03:00 04F3:32A0 Touchpad seat0 default group8 cap:pg size 129x80mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on dwtp-on -event14 DEVICE_ADDED Asus WMI hotkeys seat0 default group9 cap:k -event10 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group10 cap:k -event257 DEVICE_ADDED ASUE1A03:00 04F3:32A0 NumberPad seat0 default group11 cap:kp left scroll-nat -event12 POINTER_MOTION +0.038s -0.29/ 0.00 ( -2.00/ +0.00) event12 GESTURE_HOLD_BEGIN +0.040s 1 event12 GESTURE_HOLD_END +0.051s 1 -event257 KEYBOARD_KEY +0.055s (-1) pressed event257 KEYBOARD_KEY +0.055s (-1) released 2-event12 POINTER_MOTION +1.189s 0.00/ -0.46 ( +0.00/ -2.00) event12 POINTER_MOTION +1.196s 0.00/ -0.28 ( +0.00/ -1.00) event12 POINTER_MOTION +1.203s 0.32/ -0.32 ( +1.00/ -1.00) event12 POINTER_MOTION +1.210s -0.32/ 0.00 ( -1.00/ +0.00) event12 GESTURE_HOLD_BEGIN +1.214s 1 event12 GESTURE_HOLD_END +1.229s 1 -event257 KEYBOARD_KEY +1.232s (-1) pressed event257 KEYBOARD_KEY +1.233s (-1) released --event12 POINTER_MOTION +4.798s 0.28/ -0.28 ( +1.00/ -1.00) event12 POINTER_MOTION +4.805s 0.32/ -0.32 ( +1.00/ -1.00) event12 POINTER_MOTION +4.819s 0.28/ 0.00 ( +1.00/ +0.00) event12 POINTER_MOTION +4.827s 0.24/ 0.00 ( +1.00/ +0.00) event12 GESTURE_HOLD_BEGIN +4.828s 1 event12 GESTURE_HOLD_END +4.840s 1 -event257 KEYBOARD_KEY +4.843s (-1) pressed event257 KEYBOARD_KEY +4.844s (-1) released /-event12 POINTER_MOTION +6.451s 0.00/ -0.62 ( +0.00/ -2.00) event12 POINTER_MOTION +6.458s 0.00/ -0.68 ( +0.00/ -2.00) event12 POINTER_MOTION +6.465s -0.34/ -0.34 ( -1.00/ -1.00) event12 POINTER_MOTION +6.472s -0.34/ -0.34 ( -1.00/ -1.00) event12 POINTER_MOTION +6.479s -0.34/ -0.34 ( -1.00/ -1.00) event12 GESTURE_HOLD_BEGIN +6.481s 1 event12 POINTER_MOTION +6.486s -0.68/ -0.34 ( -2.00/ -1.00) event12 GESTURE_HOLD_END +6.500s 1 -event257 KEYBOARD_KEY +6.503s (-1) pressed event257 KEYBOARD_KEY +6.504s (-1) released 9-event12 POINTER_MOTION +8.181s 2.04/ -0.68 ( +6.00/ -2.00) event12 POINTER_MOTION +8.188s 1.70/ -0.68 ( +5.00/ -2.00) event12 POINTER_MOTION +8.195s 1.70/ -1.36 ( +5.00/ -4.00) -event257 KEYBOARD_KEY +8.208s (-1) pressed event257 KEYBOARD_KEY +8.208s (-1) released 3-event12 POINTER_MOTION +9.448s 0.68/ -1.36 ( +2.00/ -4.00) -event257 KEYBOARD_KEY +9.463s (-1) pressed event257 KEYBOARD_KEY +9.463s (-1) released 8-event12 POINTER_MOTION +10.529s 0.68/ -1.70 ( +2.00/ -5.00) event12 POINTER_MOTION +10.537s 1.02/ -2.38 ( +3.00/ -7.00) -event257 KEYBOARD_KEY +10.551s (-1) pressed event257 KEYBOARD_KEY +10.551s (-1) released 6-event12 POINTER_MOTION +17.688s 0.00/ 0.31 ( +0.00/ +1.00) event12 POINTER_MOTION +17.695s 0.00/ 0.93 ( +0.00/ +3.00) event12 GESTURE_HOLD_BEGIN +17.704s 1 event12 GESTURE_HOLD_END +17.715s 1 -event257 KEYBOARD_KEY +17.716s (-1) pressed event257 KEYBOARD_KEY +17.717s (-1) released 9-event12 POINTER_MOTION +18.494s -0.67/ -0.33 ( -2.00/ -1.00) event12 POINTER_MOTION +18.501s -0.67/ -0.33 ( -2.00/ -1.00) event12 POINTER_MOTION +18.509s -0.68/ -0.34 ( -2.00/ -1.00) event12 POINTER_MOTION +18.516s -1.02/ 0.00 ( -3.00/ +0.00) event12 GESTURE_HOLD_BEGIN +18.520s 1
ldrahnik
commented
2 days ago @zeroz41 So these events are send from Touchpad device but are associated to DialPad? Try sudo evemu-record /dev/input/event<xyz touchpad device event id> and try describe what you are doing on DialPad / simple should be for example figure out scan code for middle button inside Dialpad in case it is button and can be pressed.
zeroz41
commented
2 days ago @ldrahnik It seems I was misled and mistaken about the model I own and it only features ASUS dialpad. I wanted to scour the internet and youtube videos to confirm. I thought it featured both numberpad and dialpad when purchased. My apologies for the time sunk but regardless thanks for the support. We did at least learn that the same numpad activations also enable disable dialpad led, and gesture support works the same. So non issue, we can close.
ldrahnik
commented
2 days ago @zeroz41 This NumberPad driver adds NumberPad functionality with no hardware support except backlight leds. So Dialpad works out of the box? I am open to create new repository fór Dialpad driver if it does make sense.
zeroz41
commented
2 days ago I will check functionality of dialpad without your driver installed soon.
. MY uncertainty from watching youtube videos was still is if my model/other dialpads even have the full backlight led or just the led that lights up the circle shown here. I haven't confirmed 100%
To be honest if you were to create a dialpad driver it looks like much of your numberpad code pretty much just works the same for the gestures and activation. Everything functioned for numpad as expected expect the numberpad actually being visible lol.
From what i've looked at the dialpad basically acts as a rotary knob upon activation around the circle, which the gestures being clockwise or counter clockwise around the circle to use. While much more advanced on windows, i'd imagine some base functionality of hooking into volume controls or brightness.
Found this btw. https://github.com/fredaime/openwheel But appears to be related to physical Asus Dials, which differ from dialpads.
Describe the bug
No backlight display lighting up numbers for Asus Dialpad. No errors noticed in logs so far, installation passed. Rebooted machine. Sorry didn't find an exact previous issue match and thought this could be appropriate.
What works:
What doesn't work: No numberpad shows up when enabled. No light at all besides previously mentioned circle enablement LED.
btw same behavior whether or not external keyboard plugged it. Also no difference if enableing/disabling manually without systemd service.
Expected behavior
Relevant log output
no error.log exists or is populated in /var/log/asus-numberpad-driver/
Desktop