Touch Display does not work on Acer Spin 3(SP-314-53N-77AJ) after Installing Arch Linux

archicusrex
archicusrex Member Posts: 2 New User
edited November 2023 in 2020 Archives
Hello, 

This is my first time posting to this forum or any forum in a long time so please forgive me if I commit a faux pas - it will have been done out of ignorance.

I recently purchased an Acer Spin 3 Convertible Laptop, model number: SP-314-53N-77AJ.

I successfully installed Arch Linux to the machine and subsequently installed Xorg and GNOME 3 as well.

The machine functions more than perfectly as a laptop, but I have been unable to activate the stylus or register any touch events on the display screen. I would like to ask the community for more information and background knowledge as to how to enable the stylus and touch screen for this Acer model with the Arch Linux distro.

In the event that this is not possible due to driver or hardware limitations, I would like to know why.

The machine does, however, successfully perform screen rotations in accordance with its accelerometer after I installed the iio-sensor-proxy module via pacman.

I will include some standard linux tool command outputs that pertain to the hardware on my machine. I cannot find a feature in this text editor to include the terminal outputs in a code-readable format. Please excuse the inconvenience.

To my knowledge, a thorough google search does not yield any other experiential instances of other users installing Arch Linux on a SP-314-53N-77AJ .

Here is the xinput --list results:
$ xinput --list
WARNING: running xinput against an Xwayland server. See the xinput man page for details.
⎡ Virtual core pointer                     id=2 [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer               id=4 [slave  pointer  (2)]
⎜   ↳ xwayland-pointer:16                     id=6 [slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:16             id=7 [slave  pointer  (2)]
⎣ Virtual core keyboard                   id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard             id=5 [slave  keyboard (3)]
    ↳ xwayland-keyboard:16                     id=8 [slave  keyboard (3)]

Here is the xrandr output:
$ xrandr
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.96*+

Here is the lsusb output:
lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0408:a060 Quanta Computer, Inc. HD Webcam
Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 007: ID 04ca:3016 Lite-On Technology Corp.
Bus 001 Device 002: ID 25a7:fa23 Compx 2.4G Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And lastly, here is the output for
$
less /proc/bus/input/devices:
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: PROP=0
B: EV=3
B: KEY=4000 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:01/input/input2
U: Uniq=
H: Handlers=event2 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=10000 c020000000000 0 0 700f02000003 3802078f870f401 febfffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Intel HID events"
P: Phys=
S: Sysfs=/devices/platform/INT33D5:00/input/input4
U: Uniq=
H: Handlers=kbd event4 rfkill 
B: PROP=0
B: EV=13
B: KEY=81000300000000 5000004000 1e294000000020 0
B: MSC=10

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Intel HID 5 button array"
P: Phys=
S: Sysfs=/devices/platform/INT33D5:00/input/input5
U: Uniq=
H: Handlers=kbd event5 
B: PROP=0
B: EV=13
B: KEY=2000000000000 0 0 0 0 1000000000000 0 201c000000000000 0
B: MSC=10

I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0

I: Bus=0003 Vendor=25a7 Product=fa23 Version=0110
N: Name="Compx 2.4G Receiver"
P: Phys=usb-0000:00:14.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:25A7:FA23.0003/input/input10
U: Uniq=
H: Handlers=sysrq kbd event10 leds 
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Acer WMI hotkeys"
P: Phys=wmi/input0
S: Sysfs=/devices/virtual/input/input11
U: Uniq=
H: Handlers=kbd event11 rfkill 
B: PROP=0
B: EV=13
B: KEY=1c0000 0 0 0 0 1600800000c00 300000 10000000000000 0
B: MSC=10

I: Bus=0003 Vendor=0408 Product=a060 Version=0001
N: Name="HD WebCam: HD WebCam"
P: Phys=usb-0000:00:14.0-7/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input12
U: Uniq=
H: Handlers=kbd event12 
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0003 Vendor=25a7 Product=fa23 Version=0110
N: Name="Compx 2.4G Receiver Mouse"
P: Phys=usb-0000:00:14.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0004/input/input13
U: Uniq=
H: Handlers=event13 mouse0 
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0003 Vendor=25a7 Product=fa23 Version=0110
N: Name="Compx 2.4G Receiver"
P: Phys=usb-0000:00:14.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0004/input/input14
U: Uniq=
H: Handlers=event14 
B: PROP=0
B: EV=100001

I: Bus=0003 Vendor=25a7 Product=fa23 Version=0110
N: Name="Compx 2.4G Receiver Consumer Control"
P: Phys=usb-0000:00:14.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0004/input/input15
U: Uniq=
H: Handlers=kbd event15 
B: PROP=0
B: EV=1f
B: KEY=300ff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=25a7 Product=fa23 Version=0110
N: Name="Compx 2.4G Receiver System Control"
P: Phys=usb-0000:00:14.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0004/input/input16
U: Uniq=
H: Handlers=kbd event16 
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=3041 Version=0100
N: Name="ELAN0511:00 04F3:3041 Mouse"
P: Phys=i2c-ELAN0511:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN0511:00/0018:04F3:3041.0001/input/input18
U: Uniq=
H: Handlers=event8 mouse1 
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=3041 Version=0100
N: Name="ELAN0511:00 04F3:3041 Touchpad"
P: Phys=i2c-ELAN0511:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN0511:00/0018:04F3:3041.0001/input/input19
U: Uniq=
H: Handlers=event9 mouse2 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

I: Bus=0001 Vendor=10ec Product=0255 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input20
U: Uniq=
H: Handlers=kbd event17 
B: PROP=0
B: EV=40001
B: SND=6

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input21
U: Uniq=
H: Handlers=event18 
B: PROP=0
B: EV=21
B: SW=4

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input22
U: Uniq=
H: Handlers=event19 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input23
U: Uniq=
H: Handlers=event20 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input24
U: Uniq=
H: Handlers=event21 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=9"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input25
U: Uniq=
H: Handlers=event22 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=10"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input26
U: Uniq=
H: Handlers=event23 
B: PROP=0
B: EV=21
B: SW=140

Answers

  • billsey
    billsey ACE Posts: 34,234 Trailblazer
    I assume you've gone through their wiki entry on touchscreens. Did it show a compatible device or will you need a kernel rebuild in order to support it? Acer doesn't ship these with Arch installed, so I doubt if they've done any testing with it.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • archicusrex
    archicusrex Member Posts: 2 New User
    Yes, I did go through their wiki entry on Touch screens and checked for devices. I was not able to find any touch screen or stylus related devices detected by the computer.

    My very last code snippet is a printout of input devices connected to my machine. I am not well versed in hardware device names, but I do not seem to be able to find anything relevant to the touch display.

    I was not aware that rebuilding the kernel was a possible option in order to support the device. Please forgive the stupid question, but does this mean that I need to look into kernel modules that enable touch screen capability? The issue is that I cannot seem to either find the brand names/manufacturers names of the stylus and touch display that is installed on my machine. This is impeding my ability to look into compatible kernel modules or drivers pertaining to the relevant hardware devices.

  • billsey
    billsey ACE Posts: 34,234 Trailblazer
    I think I'd start with support forums for the OS, and maybe with some similar OSes, like the Ubuntu/Debian flavors of Linux. See if any are supporting that touchscreen yet, then see how they are doing it. You could make a request on the github page for Arch, but I don't how active their development community is. My understanding is they are less well known than some of the others.
    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.