Hi,
On Wed, Oct 23, 2024 at 09:53:47AM -0700, Forest wrote:
> On Wed, 23 Oct 2024 15:46:26 +0200, Salvatore Bonaccorso wrote:
>
> >Do you maybe can share dmesg information from booting with the old
> >kernel with the controller available?
>
> Given that we're talking about a wireless controller that is never connected
> at boot time, do you expect dmesg to show anything about it?
>
> >I wonder if this might be related to 2c1dda2acc41 ("Bluetooth: btusb:
> >Fix regression with fake CSR controllers 0a12:0001") which was
> >backported to 6.11.5.
>
> I saw that and wondered the same thing. If that turned out to be the
> applicable commit, then I would be skeptical of its description, because I
> have every reason to believe this is a genuine Sony game controller. (It has
> all the visual signs of one, and was purchased directly from a major
> brick-and-mortar retailer.) It would be a little surprising if there was a
> fake CSR chip inside, as I don't think Sony is known for using fake parts,
> although I guess it's always possible that a manufacturer used one without
> telling Sony.
As per https://lists.debian.org/debian-kernel/2024/10/msg00267.html I
uploaded 6.11.5-1 now to unstable. As we were not identifying the
upstream change fixing the issue, I have manually marked the bug as
fixed with 6.11.5-1, so once ftp-master accepts it through NEW and
packages build you should be able to get the controller back working.
Regards,
Salvatore
