Surface touchscreen problems

Hi guys. I know I'm not the first one with the question... How can I get my touchscreen working? I installed the commands from git GitHub - linux-surface/linux-surface: Linux Kernel for Surface Devices
But without success
and
https://linux.org/threads/ubuntu-22-04-on-surface-pro-7.43071/
didn't work either.
I'm using the surface pro4

Please help!
Thanks Loeschi.

Please post in/out-put of the commands you have used. Saying "didn't work" is a bit vague to help you on.

1 Like

Sorry... I'm still learning. I will load up the commands.

marcus@marcus-Surface-Pro-4:~$ wget -qO - https://raw.githubusercontent.com/linux-surface/linux-surface/master/pkg/keys/surface.asc
| gpg --dearmor | sudo dd of=/etc/apt/trusted.gpg.d/linux-surface.gpg
[sudo] password for marcus:
4+1 records in
4+1 records out
2233 bytes (2.2 kB, 2.2 KiB) copied, 8.9715e-05 s, 24.9 MB/s
marcus@marcus-Surface-Pro-4:~$ echo "deb [arch=amd64] Index of /debian release main"
| sudo tee /etc/apt/sources.list.d/linux-surface.list
deb [arch=amd64] Index of /debian release main
marcus@marcus-Surface-Pro-4:~$
marcus@marcus-Surface-Pro-4:~$ sudo apt update
Hit:1 AARNet Mirror jammy InRelease
Hit:2 AARNet Mirror jammy-updates InRelease
Hit:3 AARNet Mirror jammy-backports InRelease
Hit:4 Index of /ubuntu jammy InRelease
Get:5 Index of /ubuntu jammy-security InRelease [129 kB]
Hit:6 Index of /stable/ jammy InRelease
Hit:7 Index of /patches/ jammy InRelease
Hit:8 Index of /debian release InRelease
Hit:9 Index of /apps/ jammy InRelease
Hit:10 Index of /drivers/ jammy InRelease
Hit:11 Zorin OS Pro - Zorin OS jammy InRelease
Hit:12 Index of /zorinos/apps/ubuntu jammy InRelease
Hit:13 https://ppa.launchpadcontent.net/zorinos/drivers/ubuntu jammy InRelease
Hit:14 https://ppa.launchpadcontent.net/zorinos/patches/ubuntu jammy InRelease
Hit:15 Index of /zorinos/stable/ubuntu jammy InRelease
Fetched 129 kB in 5s (26.8 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
10 packages can be upgraded. Run 'apt list --upgradable' to see them.
marcus@marcus-Surface-Pro-4:~$ sudo apt install linux-image-surface linux-headers-surface libwacom-surface iptsd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
iptsd is already the newest version (2-1).
linux-headers-surface is already the newest version (6.9.3-surface-2).
linux-image-surface is already the newest version (6.9.3-surface-2).
The following packages were automatically installed and are no longer required:
libgsoap-2.8.117 liblzf1 libqt5opengl5 libqt5x11extras5 libsdl1.2debian
libwmf0.2-7-gtk libwpe-1.0-1 libwpebackend-fdo-1.0-1 virtualbox
virtualbox-dkms virtualbox-qt
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
libwacom-bin-surface libwacom-common-surface libwacom2-surface
libwacom9-surface
The following packages will be upgraded:
libwacom-bin-surface libwacom-common-surface libwacom-surface
libwacom2-surface libwacom9-surface
5 to upgrade, 0 to newly install, 0 to remove and 5 not to upgrade.
3 not fully installed or removed.
Need to get 221 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 Index of /debian release/main amd64 libwacom-surface amd64 2.12.0-1 [1,870 B]
Get:2 Index of /debian release/main amd64 libwacom-bin-surface amd64 2.12.0-1 [15.5 kB]
Get:3 Index of /debian release/main amd64 libwacom9-surface amd64 2.12.0-1 [25.0 kB]
Get:4 Index of /debian release/main amd64 libwacom2-surface amd64 2.12.0-1 [22.9 kB]
Get:5 Index of /debian release/main amd64 libwacom-common-surface amd64 2.12.0-1 [156 kB]
Fetched 221 kB in 9s (24.1 kB/s)
(Reading database ... 303834 files and directories currently installed.)
Preparing to unpack .../libwacom-surface_2.12.0-1_amd64.deb ...
Unpacking libwacom-surface (2.12.0-1) over (2.10.0-1) ...
Preparing to unpack .../libwacom-bin-surface_2.12.0-1_amd64.deb ...
Unpacking libwacom-bin-surface (2.12.0-1) over (2.10.0-1) ...
Preparing to unpack .../libwacom9-surface_2.12.0-1_amd64.deb ...
Unpacking libwacom9-surface (2.12.0-1) over (2.10.0-1) ...
Preparing to unpack .../libwacom2-surface_2.12.0-1_amd64.deb ...
Unpacking libwacom2-surface (2.12.0-1) over (2.10.0-1) ...
Preparing to unpack .../libwacom-common-surface_2.12.0-1_amd64.deb ...
Unpacking libwacom-common-surface (2.12.0-1) over (2.10.0-1) ...
Setting up libwacom-common-surface (2.12.0-1) ...
Setting up libwacom9-surface (2.12.0-1) ...
Setting up virtualbox-dkms (6.1.50-dfsg-1~ubuntu1.22.04.1) ...
Removing old virtualbox-6.1.50 DKMS files...
Module virtualbox-6.1.50 for kernel 6.5.0-35-generic (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.5.0-35-generic/updates/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.5.0-35-generic/updates/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko:

  • Uninstallation
    • Deleting from: /lib/modules/6.5.0-35-generic/updates/
  • Original module
    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.

depmod.....
Deleting module virtualbox-6.1.50 completely from the DKMS tree.
Loading new virtualbox-6.1.50 DKMS files...
Building for 6.5.0-35-generic 6.9.3-surface-2
Building initial module for 6.5.0-35-generic
Done.

vboxdrv.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.5.0-35-generic/updates/

vboxnetadp.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.5.0-35-generic/updates/

vboxnetflt.ko:
Running module version sanity check.

  • Original module
    • No original module exists within this kernel
  • Installation
    • Installing to /lib/modules/6.5.0-35-generic/updates/

depmod....
Building initial module for 6.9.3-surface-2
Error! Bad return status for module build on kernel: 6.9.3-surface-2 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.50/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (--configure):
installed virtualbox-dkms package post-installation script subprocess returned
error exit status 10
Setting up libwacom-bin-surface (2.12.0-1) ...
Setting up libwacom2-surface (2.12.0-1) ...
dpkg: dependency problems prevent configuration of virtualbox:
virtualbox depends on virtualbox-dkms (>= 6.1.50-dfsg-1~ubuntu1.22.04.1) | virt
ualbox-source (>= 6.1.50-dfsg-1~ubuntu1.22.04.1) | virtualbox-modules; however:
Package virtualbox-dkms is not configured yet.
Package virtualbox-source is not installed.
Package virtualbox-modules is not installed.
Package virtualbox-dkms which provides virtualbox-modules is not configured ye
t.

dpkg: error processing package virtualbox (--configure):
dependency problems - leaving unconfigured
Setting up libwacom-surface (2.12.0-1) ...
dpkg: dependency problems prevent configuration of virtualbox-qt:
virtualbox-qt depends on virtualbox (= 6.1.50-dfsg-1~ubuntu1.22.04.1); however:
Package virtualbox is not configured yet.

dpkg: error processing package virtualbox-qt (--configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.10.2-1) ...
Errors were encountered while processing:
virtualbox-dkms
virtualbox
virtualbox-qt
E: Sub-process /usr/bin/dpkg returned an error code (1)
marcus@marcus-Surface-Pro-4:~$

i followed the instructions from git. Reboot.. in my boot system it added zorin surface. when i click it it is telling me "bad shim signature". it want let me boot into it.

The “Bad Shim Signature” error occurs when we attempt to boot a custom kernel that is not signed or has a signature that the system does not recognize.

Have you disabled secure boot in BIOS?

Thank you so much. It is working now. What a simple fix.

Would you have an answer please for the error code I'm getting
E: Sub-process /user/bin/dpkg returned an error code (1)

I need to see the whole output, but my guess is you need to disable the repositories you have added earlier. You can do that in software center in the hamburger menu.

i did a sudo apt upgrade. the output is:
marcus@marcus-Surface-Pro-4:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libgsoap-2.8.117 liblzf1 libqt5opengl5 libqt5x11extras5 libsdl1.2debian
libwmf0.2-7-gtk libwpe-1.0-1 libwpebackend-fdo-1.0-1 virtualbox
virtualbox-dkms virtualbox-qt
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
snapd
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
3 not fully installed or removed.
Need to get 25.9 MB of archives.
After this operation, 258 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 AARNet Mirror jammy-updates/main amd64 snapd amd64 2.63+22.04 [25.9 MB]
Fetched 25.9 MB in 22s (1,187 kB/s)
(Reading database ... 304652 files and directories currently installed.)
Preparing to unpack .../snapd_2.63+22.04_amd64.deb ...
Unpacking snapd (2.63+22.04) over (2.62+22.04) ...
Setting up snapd (2.63+22.04) ...
Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine
.real ...
snapd.failure.service is a disabled or a static unit not running, not starting i
t.
snapd.snap-repair.service is a disabled or a static unit not running, not starti
ng it.
Failed to restart snapd.mounts-pre.target: Operation refused, unit snapd.mounts-
pre.target may be requested by dependency only (it is configured to refuse manua
l start/stop).
See system logs and 'systemctl status snapd.mounts-pre.target' for details.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.
Setting up virtualbox-dkms (6.1.50-dfsg-1~ubuntu1.22.04.1) ...
Removing old virtualbox-6.1.50 DKMS files...
Deleting module virtualbox-6.1.50 completely from the DKMS tree.
Loading new virtualbox-6.1.50 DKMS files...
Building for 6.9.3-surface-2
Building initial module for 6.9.3-surface-2
Error! Bad return status for module build on kernel: 6.9.3-surface-2 (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.50/build/make.log for more information.
dpkg: error processing package virtualbox-dkms (--configure):
installed virtualbox-dkms package post-installation script subprocess returned
error exit status 10
dpkg: dependency problems prevent configuration of virtualbox:
virtualbox depends on virtualbox-dkms (>= 6.1.50-dfsg-1~ubuntu1.22.04.1) | virt
ualbox-source (>= 6.1.50-dfsg-1~ubuntu1.22.04.1) | virtualbox-modules; however:
Package virtualbox-dkms is not configured yet.
Package virtualbox-source is not installed.
Package virtualbox-modules is not installed.
Package virtualbox-dkms which provides virtualbox-modules is not configured ye
t.

dpkg: error processing package virtualbox (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of virtualbox-qt:
virtualbox-qt depends on virtualbox (= 6.1.50-dfsg-1~ubuntu1.22.04.1); however:
Package virtualbox is not configured yet.

dpkg: error processing package virtualbox-qt (--configure):
dependency problems - leaving unconfigured
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Errors were encountered while processing:
virtualbox-dkms
virtualbox
virtualbox-qt
E: Sub-process /usr/bin/dpkg returned an error code (1)

Do you need virtualbox?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.