Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #87744 > unrolled thread

Bug#1106658: installation-reports: Touchpad not active

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1106658: installation-reports: Touchpad not active Cyril Brulebois <kibi@debian.org> - 2025-05-28 21:50 +0200
    Bug#1106658: installation-reports: Touchpad not active Salvatore Bonaccorso <carnil@debian.org> - 2025-05-29 09:50 +0200
      Bug#1106658: installation-reports: Touchpad not active Cyril Brulebois <kibi@debian.org> - 2025-05-29 16:00 +0200
      Bug#1106658: installation-reports: Touchpad not active Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-05-29 22:10 +0200

#87744 — Bug#1106658: installation-reports: Touchpad not active

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [next] | [standalone]

#87762

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

[toc] | [prev] | [next] | [standalone]

#87765

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#87774

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>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web