Bug#1103830: linux-image-6.12.22-amd64: No keyboard or touchpad functionality on a Macbook Pro 14,1
- To: Uwe Kleine-K??nig <ukleinek@debian.org>, 1103830@bugs.debian.org
- Cc: Ted To <wintrymix@theo.to>
- Subject: Bug#1103830: linux-image-6.12.22-amd64: No keyboard or touchpad functionality on a Macbook Pro 14,1
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Wed, 7 May 2025 12:23:57 +0200
- Message-id: <[🔎] aBs0vZCFOEJZztzB@lorien.valinor.li>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1103830@bugs.debian.org
- In-reply-to: <4wlbsa2mr2dtpmqeedpyuokcj4d4n4zrtqmkvbjnk2jmqwl2q2@wunmucgszwut>
- References: <174525742623.3368.12430394840586676406.reportbug@localhost> <k7xgolmycjauiwltll2cceajhgfgkp5mwdkz6shehst3lqy7de@odjrl6hhbpxr> <174525742623.3368.12430394840586676406.reportbug@localhost> <f6964875-2625-40e0-b014-38f91b939a39@theo.to> <174525742623.3368.12430394840586676406.reportbug@localhost> <4wlbsa2mr2dtpmqeedpyuokcj4d4n4zrtqmkvbjnk2jmqwl2q2@wunmucgszwut> <174525742623.3368.12430394840586676406.reportbug@localhost>
Control: tags -1 + upstream
Control: forwarded -1 https://lore.kernel.org/stable/4dada48a-c5dd-4c30-9c85-5b03b0aa01f0@bfh.ch/
Hi,
On Wed, Apr 30, 2025 at 09:47:21PM +0200, Uwe Kleine-K??nig wrote:
> Control: tag -1 + moreinfo
>
> hello Ted,
>
> On Wed, Apr 23, 2025 at 08:43:03AM -0400, Ted To wrote:
> > Hi Uwe,
> >
> > It is definitely a regression. I am able to boot up a Bookworm based
> > distribution with keyboard and touchpad functionality.
> >
> > Distributions with functionality are:
> > * Debian Bookworm
> > * Current Manjaro Gnome release
> > * Fedora 42 Workstation release
> > These have only been with live ISOs and I have not tested them extensively
> > so they may have other problems.
> >
> > Distributions without functionality are:
> > * Ubuntu 25.04
> > * Debian Trixie
> >
> > I do have an external keyboard/mouse so I can provide other diagnostic
> > information. I prefer Debian over the other alternatives so I would love if
> > this can be fixed!
>
> Understandable :-)
>
> Given that we don't have that hardware, can you bisect the problem? At
> least to identify the first broken debian kernel image? That might help
> us pinpoint the problem.
FWIW, it seems that this has now been reported as well upstream, so
linking both.
Regards,
Salvatore
Reply to: