Your message dated Tue, 24 Feb 2026 12:55:54 +0100
with message-id <[email protected]>
and subject line Re: Bug#1128888: linux-image-amd64: [PATCH] Add Intel THC
device ID 0xA0D0 (Tiger Lake) support to intel-thc-hid module
has caused the Debian Bug report #1128888,
regarding linux-image-amd64: [PATCH] Add Intel THC device ID 0xA0D0 (Tiger
Lake) support to intel-thc-hid module
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1128888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128888
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.18.12-1
Severity: wishlist
Tags: patch
X-Debbugs-Cc: [email protected], [email protected]
User: [email protected]
Usertags: amd64
Dear Maintainer,
The touchscreen on LAPBC710 (Intel THC device ID 0x8086:0xA0D0) was not working
on Debian kernel 6.18, despite the intel-thc-hid module being compiled.
Investigation showed the device ID 0xA0D0 was missing from the kernel's
pci_device_id table, even though it was added to mainline Linux 6.14 in March
2025.
I verified that Debian kernel 6.19 experimental still lacks device ID 0xA0D0 in
the compiled intel-thc-hid module, despite the source code containing support
for it. The device ID needs to be included in the kernel compilation
configuration for Debian 6.19+.
The touchscreen remains non-functional on Debian kernel 6.18 and 6.19 without
an external DKMS module. Users must install the ithc DKMS module as a
workaround to enable native kernel support.
The device ID 0xA0D0 should be included in Debian kernel 6.19+ compilation,
allowing native touchscreen support without requiring external DKMS modules.
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.18.12+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-amd64 depends on:
ii linux-base-amd64 6.18.12-1
ii linux-image-6.18.12+deb14-amd64 6.18.12-1
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Yuri,
On Mon, Feb 23, 2026 at 10:27:37PM -0300, Yuri Musachio wrote:
> Package: linux-image-amd64
> Version: 6.18.12-1
> Severity: wishlist
> Tags: patch
> X-Debbugs-Cc: [email protected], [email protected]
> User: [email protected]
> Usertags: amd64
>
> Dear Maintainer,
>
> The touchscreen on LAPBC710 (Intel THC device ID 0x8086:0xA0D0) was
> not working on Debian kernel 6.18, despite the intel-thc-hid module
> being compiled. Investigation showed the device ID 0xA0D0 was
> missing from the kernel's pci_device_id table, even though it was
> added to mainline Linux 6.14 in March 2025.
>
> I verified that Debian kernel 6.19 experimental still lacks device
> ID 0xA0D0 in the compiled intel-thc-hid module, despite the source
> code containing support for it. The device ID needs to be included
> in the kernel compilation configuration for Debian 6.19+.
>
> The touchscreen remains non-functional on Debian kernel 6.18 and
> 6.19 without an external DKMS module. Users must install the ithc
> DKMS module as a workaround to enable native kernel support.
>
> The device ID 0xA0D0 should be included in Debian kernel 6.19+
> compilation, allowing native touchscreen support without requiring
> external DKMS modules.
I have to close this. We won't pick patches which are not upstream.
The best thing you can do here is to help upstreaming the patches
needed and Debian can pick those up in future updates. But we won't
pick patches from https://github.com/linux-surface/linux-surface/ .
Regards,
Salvatore
--- End Message ---
