XPost: linux.debian.maint.boot

Package: installation-reports
Severity: minor
X-Debbugs-Cc: rclobus@rclobus.nl

Boot method: USB
Image version: https://people.debian.org/~kibi/bug-1092977+intel/debian-13.0.0-amd64-NETINST-1+depmod+efd.iso
Date: 2025-05-26

Machine: Lenovo Thinkpad P16s Gen3

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot: [O]
Detect network card: [ ]
Configure network: [ ]
Detect media: [ ]
Load installer modules: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]

Comments/Problems:

When booting with the graphical installer, the integrated touchpad was not working, the USB mouse was working fine.

The following is generated after booting a live image.

The touchpad is (lspci)
00:15.0 Serial bus controller: Intel Corporation Meteor Lake-P Serial IO I2C Controller #0 (rev 20)
00:15.0 0c80: 8086:7e78 (rev 20)

The output of: dmesg | grep input/input

[ 2.359678] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 2.728713] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[ 2.746204] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
[ 2.746433] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
[ 3.177803] input: TPPS/2 Elan TrackPoint as /devices/platform/i8042/serio1/input/input5
[ 3.411138] input: SYNA801A:00 06CB:CEC6 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input6
[ 3.411304] input: SYNA801A:00 06CB:CEC6 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input7
[ 3.506847] input: SYNA801A:00 06CB:CEC6 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input9
[ 3.506921] input: SYNA801A:00 06CB:CEC6 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA801A:00/0018:06CB:CEC6.0001/input/input10
[ 4.096454] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
[ 5.069065] input: PixArt Microsoft USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.4/3-7.4:1.0/0003:045E:00CB.0004/input/input13
[ 5.081977] input: HID 046a:0023 as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.3/3-7.3:1.0/0003:046A:0023.0002/input/input14
[ 5.206403] input: HID 046a:0023 as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7.3/3-7.3:1.1/0003:046A:0023.0003/input/input15
[ 17.711826] input: Intel HID events as /devices/platform/INTC1070:00/input/input16
[ 17.718986] input: PC Speaker as /devices/platform/pcspkr/input/input17
[ 18.242258] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input18

The output of: dmesg | grep -i firm
[ 0.287264] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 3.164472] psmouse serio1: trackpoint: Elan TrackPoint firmware: 0x00, buttons: 3/3
[ 3.896195] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.23)
[ 3.922316] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.36.0
[ 3.937856] i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.36.0
[ 3.937858] i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
[ 4.112598] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
[ 16.056778] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67).
[ 17.903672] intel_vpu 0000:00:0b.0: firmware: failed to load vpu_37xx.bin (-2)
[ 17.904656] intel_vpu 0000:00:0b.0: firmware: failed to load vpu_37xx.bin (-2)
[ 17.904895] intel_vpu 0000:00:0b.0: firmware: failed to load vpu_37xx.bin (-2)
[ 17.943513] intel_vpu 0000:00:0b.0: [drm] Firmware: intel/vpu/vpu_37xx_v0.0.bin, version: 20250306*MTL_CLIENT_SILICON- release*1130*ci_tag_ud202512_vpu_rc_20250306_1130*5064b5debc3
[ 18.044248] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug- yoyo.bin (-2)
[ 18.044264] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug- yoyo.bin (-2)
[ 18.044278] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug- yoyo.bin (-2)
[ 18.044279] iwlwifi 0000:00:14.3: loaded firmware version 89.4d42c933.0 ma-b0-gf-a0-89.ucode op_mode iwlmvm
[ 18.197058] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 18.205119] Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi [ 18.205131] Bluetooth: hci0: Firmware Version: 20-49.24
[ 18.880448] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1:
[ 18.880451] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri
[ 18.880452] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl
[ 18.881007] sof-audio-pci-intel-mtl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.12.0.1
[ 18.999412] sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.12.0.1
[ 19.705464] Bluetooth: hci0: Waiting for firmware download to complete
[ 19.707009] Bluetooth: hci0: Firmware loaded in 1466686 usecs
[ 19.757045] Bluetooth: hci0: Firmware timestamp 2024.48 buildtype 1 build 3604
[ 19.757048] Bluetooth: hci0: Firmware SHA1: 0xc115e35a

The output of: lsmod | grep i2c
i2c_algo_bit 16384 3 xe,i915,nouveau
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
i2c_i801 36864 0
hid 262144 5 i2c_hid,usbhid,hid_multitouch,hid_generic,hid_cherry
i2c_smbus 16384 1 i2c_i801
drm 770048 31 gpu_sched,intel_vpu,i2c_hid,drm_kms_helper,drm_exec,bochs,drm_gpuvm,drm_vram_helper,drm_suballoc_helper,drm_shmem_helper,drm_display_helper,drm_buddy,thinkpad_acpi,drm_ttm_helper,xe,i915,ttm,nouveau

With kind regards,
Roland Clobus

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.maint.boot

On 27/05/2025 at 16:30, Roland Clobus wrote:

When booting with the graphical installer, the integrated touchpad was not working, the USB mouse was working fine.

It looks like #1104057. Does lsmod show a pinctrl* module on a system
with working touchpad ?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel, linux.debian.maint.boot

Hi,

Looping in debian-kernel@, context being missing touchpad support on an
amd64 machine, unless an extra module is added to the installer.

Feel free to steal the bug report away from us and adjust debian/installer/modules as you see fit!

Roland Clobus <rclobus@rclobus.nl> (2025-05-28):

On 27/05/2025 19:20, Pascal Hambourg wrote:

It looks like #1104057. Does lsmod show a pinctrl* module on a
system with working touchpad ?

I've built a custom installer and `pinctrl-meteorlake` does the trick.
With this additional kernel module the touchpad works in the graphical installer.

Checking linux.git, it seems pinctrl modules are only shipped in udebs
for a single arch:

kibi@tokyo:~/debian-kernel/linux.git (debian/6.12/trixie <)$ git grep pinctrl -- debian/installer/
debian/installer/modules/arm64/kernel-image:drivers/pinctrl/**

I'm not sure how many pinctrl modules would make sense to ship, or in
which udeb, for other architectures.

Looking at the amd64 config, the modular ones are:

CONFIG_PINCTRL_ALDERLAKE=m
CONFIG_PINCTRL_CS42L43=m
CONFIG_PINCTRL_ELKHARTLAKE=m
CONFIG_PINCTRL_EMMITSBURG=m
CONFIG_PINCTRL_INTEL_PLATFORM=m
CONFIG_PINCTRL_JASPERLAKE=m
CONFIG_PINCTRL_LAKEFIELD=m
CONFIG_PINCTRL_METEORLAKE=m
CONFIG_PINCTRL_METEORPOINT=m

while the built-in ones are:

CONFIG_PINCTRL_AMD=y
CONFIG_PINCTRL_BAYTRAIL=y
CONFIG_PINCTRL_CHERRYVIEW=y
CONFIG_PINCTRL_INTEL=y
CONFIG_PINCTRL_BROXTON=y
CONFIG_PINCTRL_CANNONLAKE=y
CONFIG_PINCTRL_CEDARFORK=y
CONFIG_PINCTRL_DENVERTON=y
CONFIG_PINCTRL_GEMINILAKE=y
CONFIG_PINCTRL_ICELAKE=y
CONFIG_PINCTRL_LEWISBURG=y
CONFIG_PINCTRL_SUNRISEPOINT=y
CONFIG_PINCTRL_TIGERLAKE=y


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmg3ZksACgkQ/5FK8MKz VSDhMBAAlbrW+VbE5/bL0oGpBJWlJgNoUHB2EntD07NVaU8puUleMV/76Uw5ltFB 6oK54E9YwSowl6XhYeu0GLoVEDbwsxp9vbj3RwndSNks9EkWZBpWOKbH+IhHAX3t YV5JdVFeABMEsVsIUbP8INbrkcGox6OwRbyy2e4LvRJ+h444hHPD+pvwluXgVhTH 0OGF8Qy5PTYusGyAlBwmwfjE/ZpxMAn9+32PEH7R9tQ4czASZ2tQdt3RB0N/Eve+ sS7TdqSgeGQuPBqAPE0XpRNyqGdHeVPwATUIMhOBV1Xio6KYrCaVocPolvTxz40I UUpwEi3CFQCV4b/kPM6iVJQlAsC1qJyaJr07g7fxEXwjjZkG3wxpkm0xKnViq1dt cErruBPDcbnBsM42S6X3DA9tfIJzywWpJb2mtpgUK8zAsV1ZjSqE15JEE3fUI1WZ NGgEUlNIgRRmp3N6QR2kqeByxIN613V2qzDCUHYk0kSWd3H4VKS43HbFxXbfVaMg 7fCRJqKr1NKBHUdI5CDx0zrQ0pjuuuwAx8KOOYhpisB24dvTYrhTzFu7GRaY8BPt pjLpn3y8gxek74NawhlIgzYf9roWSBktWXxbuEiTA4weOfL/rPvSGcph5MUH4wHK 1mMF7jQtYGKBHSrz8hZ/1cvwE3U/3XDdUWrJMBbplaJvlJpG+fc=
=jZLA
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.kernel, linux.debian.maint.boot

Hi Cyril,

On Wed, May 28, 2025 at 09:38:51PM +0200, Cyril Brulebois wrote:

Hi,

Looping in debian-kernel@, context being missing touchpad support on an
amd64 machine, unless an extra module is added to the installer.

Feel free to steal the bug report away from us and adjust debian/installer/modules as you see fit!

Roland Clobus <rclobus@rclobus.nl> (2025-05-28):

On 27/05/2025 19:20, Pascal Hambourg wrote:

It looks like #1104057. Does lsmod show a pinctrl* module on a
system with working touchpad ?

I've built a custom installer and `pinctrl-meteorlake` does the trick.
With this additional kernel module the touchpad works in the graphical installer.

Checking linux.git, it seems pinctrl modules are only shipped in udebs
for a single arch:

kibi@tokyo:~/debian-kernel/linux.git (debian/6.12/trixie <)$ git grep pinctrl -- debian/installer/
debian/installer/modules/arm64/kernel-image:drivers/pinctrl/**

I'm not sure how many pinctrl modules would make sense to ship, or in
which udeb, for other architectures.

Looking at the amd64 config, the modular ones are:

CONFIG_PINCTRL_ALDERLAKE=m
CONFIG_PINCTRL_CS42L43=m
CONFIG_PINCTRL_ELKHARTLAKE=m
CONFIG_PINCTRL_EMMITSBURG=m
CONFIG_PINCTRL_INTEL_PLATFORM=m
CONFIG_PINCTRL_JASPERLAKE=m
CONFIG_PINCTRL_LAKEFIELD=m
CONFIG_PINCTRL_METEORLAKE=m
CONFIG_PINCTRL_METEORPOINT=m

while the built-in ones are:

CONFIG_PINCTRL_AMD=y
CONFIG_PINCTRL_BAYTRAIL=y
CONFIG_PINCTRL_CHERRYVIEW=y
CONFIG_PINCTRL_INTEL=y
CONFIG_PINCTRL_BROXTON=y
CONFIG_PINCTRL_CANNONLAKE=y
CONFIG_PINCTRL_CEDARFORK=y
CONFIG_PINCTRL_DENVERTON=y
CONFIG_PINCTRL_GEMINILAKE=y
CONFIG_PINCTRL_ICELAKE=y
CONFIG_PINCTRL_LEWISBURG=y
CONFIG_PINCTRL_SUNRISEPOINT=y
CONFIG_PINCTRL_TIGERLAKE=y

Can you double-check if https://salsa.debian.org/kernel-team/linux/-/merge_requests/1530 make
sense to you?

If yes, feel free to reassign it to src:linux. And then we should mark
it as well as to be backported for 6.12.y for trixie.

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.kernel, linux.debian.maint.boot

Hi,

Roland Clobus <rclobus@rclobus.nl> (2025-05-29):

Looking at this MR, I'm wondering where the required kernel modules
for d-i should be listed.

The list in `debian/installer/modules/amd64/kernel-image`
(kernel-team/linux) is rather short.
Recently we discussed adding i915 and a few of its dependencies, which are not listed here, but somewhere else [1].

The kernel-image udeb is used everywhere. i915, *if* it is to be added somewhere, does *not* belong there. See other files in that directory, fb-modules might make sense, speakup-modules might as well.

I'd prefer not touching the kernel udebs at the moment (for the i915
thing, which really is orthogonal to this bug report and this MR). We can add/remove things autonomously through the debian-installer source
package, and I really don't want to have through linux source uploads to
adjust stuff, especially given the amount of blur currently surrounding firmware-sof-signed vs. firmware-intel-sound…

If yes, feel free to reassign it to src:linux. And then we should mark
it as well as to be backported for 6.12.y for trixie.

That would look good to me (at least given the current state of things on
the arm64 side). If pinctrl were only about touchpads and stuff, one
could argue they only make sense for the graphical installer, but I
suppose this could control other internal stuff, so adding the whole
series of pinctrl modules, in kernel-image, might be the easiest.


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmg4Zb8ACgkQ/5FK8MKz VSB5MxAAu+/ekVRpKtH6DVa5LTR82Fu/O1kkcVS4m3gpfeHq+knoMnYkasLu7dfH nLFnDzoHLMJcMeVIGOqRNAC9MwVQbWkEptBpgmKCxmmo1uXyxbVWKDPhozV0sDsa RCj3zlKC/LmENDpZhe9K//hqL1mob5NPtq5jrzbpfxqd88O54Ljcn7RSQOu4JxUV KBIg8pRroQpZcPI+YbKU+7NjO2b2e+onsz/9CeA00QNGmAMl8GcWVaI0IBAhIxv+ Bd4K6g4ziM2OCvcyrtCk7p4ysySYrgjjfMCwVbqhWf/3CLyGEapCU+eRWz2ibCDa oEGQkG98cXO4b8JE6bdMl9pYt7orfQ04HwOjg0awXHob7ukGPfZwOabLsP7G7qBy e9TyPTOISrl+ntfWwsEjfwXHLIJV7L7zFKOM+JyaC9zZRVIncPMbM7GTUFm+O0YP rxtkAznGGZzGf51WbzACQPz6K7S+MwAf8SXydUFhNKetdLjAbzz8L77/z0uYdSYN weXe0G+nB7CBqDdb0WIkxw62PRZBuU9kfPduLWpV6yigbzgAn+FJQmFamlsENbak DbkI9hmdskFvE0BKXxi5CQtFGLHpgTZAwofrxlCekA+i9z+n1iAgcU/mPpvJbYAW PQfptPDv6P+jJwXV+v8z0Z2+mkj7Uht4wU7qyJGvfTMW59m9pbE=
=KPiM
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.kernel, linux.debian.maint.boot

On 29/05/2025 at 09:43, Salvatore Bonaccorso wrote:

On Wed, May 28, 2025 at 09:38:51PM +0200, Cyril Brulebois wrote:

I'm not sure how many pinctrl modules would make sense to ship, or in
which udeb, for other architectures.

Looking at the amd64 config, the modular ones are:

CONFIG_PINCTRL_ALDERLAKE=m
CONFIG_PINCTRL_CS42L43=m

(...)> Can you double-check if

https://salsa.debian.org/kernel-team/linux/-/merge_requests/1530 make
sense to you?

The MR adds pinctrl/intel/* but what about
pinctrl/cirrus/pinctrl-cs42l43.ko.xz which is enabled by CONFIG_PINCTRL_CS42L43=m and was mentioned by Cyril in the duplicate bug #1104057 [1] ?

[1] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104057#65>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)