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

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

Bug#986822: BUG#986822 Broadwell SST CATPT Sound module

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#986822: BUG#986822 Broadwell SST CATPT Sound module Vincent Blut <vincent.debian@free.fr> - 2021-06-04 18:10 +0200
    Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Salvatore Bonaccorso <carnil@debian.org> - 2021-06-04 21:50 +0200
      Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Vincent Blut <vincent.debian@free.fr> - 2021-06-04 23:40 +0200
        Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Vincent Blut <vincent.debian@free.fr> - 2021-06-13 20:20 +0200
          Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Vincent Blut <vincent.debian@free.fr> - 2021-06-14 10:20 +0200
          Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Dekks Herton <dekkzz76@gmail.com> - 2021-06-15 13:50 +0200
            Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Dekks Herton <dekkzz76@gmail.com> - 2021-06-21 11:50 +0200
              Bug#986822: BUG#986822 Broadwell SST CATPT Sound module Vincent Blut <vincent.debian@free.fr> - 2021-06-29 19:00 +0200

#72086 — Bug#986822: BUG#986822 Broadwell SST CATPT Sound module

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

Hi Dekks,

Le 2021-06-04 15:34, Dekks Herton a écrit :
> Hi Everyone,
> 
> As 5.10.7 was still in unstable 1 added it to my bullseye system via adding
> SId to sources.list and pulling the image and relevant headers packages. If
> there is a better or more correct way please advise.
> 
> Running 5.10.7 AFAIK installs the catpt modules correctly and all the hw
> associated correctly
> 
> 1) See aplayL txt file enc 2) GNOME shows a different slider layout
> 
> However there is still no sound on play back, parsing journalctl it seems
> the firmware IntcSST2.bin errors out and thus no firmware is loaded.
> 
> Jun 04 00:49:06 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> direct-loading firmware intel/IntcSST2.bin
> Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> direct-loading firmware intel/IntcSST2.bin
> Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware ready
> timeout
> Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: boot firmware
> failed: -110
> 
> I enclose a listing of the intel firmware folder showing IntcSST2.bin is
> there, Is it the correct firmware?
> 
> I've googled and cant find any info on this. Does intel have a github for
> this re-written driver?
> 
> Can the bug reopened or can you advise any possible solutions?

Do you have firmware-sof-signed installed? It may be needed on your system.

> Regards....

Cheers,
Vincent

[toc] | [next] | [standalone]

#72094

Hi,

On Fri, Jun 04, 2021 at 05:56:03PM +0200, Vincent Blut wrote:
> Hi Dekks,
> 
> Le 2021-06-04 15:34, Dekks Herton a écrit :
> > Hi Everyone,
> > 
> > As 5.10.7 was still in unstable 1 added it to my bullseye system via adding
> > SId to sources.list and pulling the image and relevant headers packages. If
> > there is a better or more correct way please advise.
> > 
> > Running 5.10.7 AFAIK installs the catpt modules correctly and all the hw
> > associated correctly
> > 
> > 1) See aplayL txt file enc 2) GNOME shows a different slider layout
> > 
> > However there is still no sound on play back, parsing journalctl it seems
> > the firmware IntcSST2.bin errors out and thus no firmware is loaded.
> > 
> > Jun 04 00:49:06 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> > direct-loading firmware intel/IntcSST2.bin
> > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> > direct-loading firmware intel/IntcSST2.bin
> > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware ready
> > timeout
> > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: boot firmware
> > failed: -110
> > 
> > I enclose a listing of the intel firmware folder showing IntcSST2.bin is
> > there, Is it the correct firmware?
> > 
> > I've googled and cant find any info on this. Does intel have a github for
> > this re-written driver?
> > 
> > Can the bug reopened or can you advise any possible solutions?
> 
> Do you have firmware-sof-signed installed? It may be needed on your system.

Reopened the bug for now (at least until the above question is
clarified).

Regards,
Salvatore

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

#72096

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

Hi Salvatore,

Le 2021-06-04 21:39, Salvatore Bonaccorso a écrit :
> Hi,
> 
> On Fri, Jun 04, 2021 at 05:56:03PM +0200, Vincent Blut wrote:
> > Hi Dekks,
> > 
> > Le 2021-06-04 15:34, Dekks Herton a écrit :
> > > Hi Everyone,
> > > 
> > > As 5.10.7 was still in unstable 1 added it to my bullseye system via adding
> > > SId to sources.list and pulling the image and relevant headers packages. If
> > > there is a better or more correct way please advise.
> > > 
> > > Running 5.10.7 AFAIK installs the catpt modules correctly and all the hw
> > > associated correctly
> > > 
> > > 1) See aplayL txt file enc 2) GNOME shows a different slider layout
> > > 
> > > However there is still no sound on play back, parsing journalctl it seems
> > > the firmware IntcSST2.bin errors out and thus no firmware is loaded.
> > > 
> > > Jun 04 00:49:06 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> > > direct-loading firmware intel/IntcSST2.bin
> > > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware:
> > > direct-loading firmware intel/IntcSST2.bin
> > > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: firmware ready
> > > timeout
> > > Jun 04 00:49:10 HELIX2NDGEN kernel: intel_catpt INT3438:00: boot firmware
> > > failed: -110
> > > 
> > > I enclose a listing of the intel firmware folder showing IntcSST2.bin is
> > > there, Is it the correct firmware?
> > > 
> > > I've googled and cant find any info on this. Does intel have a github for
> > > this re-written driver?
> > > 
> > > Can the bug reopened or can you advise any possible solutions?
> > 
> > Do you have firmware-sof-signed installed? It may be needed on your system.
> 
> Reopened the bug for now (at least until the above question is
> clarified).

Dekks replied to me privately. Those SOF audio firmware aren't going to help in
this case since we don't provide support for SOF on Broadwell based platforms.
I already mentioned this in [1] but I had totally forgotten that.

Dekks, out of curiosity, could you please post the output of 'pacmd list-sinks'?

> Regards,
> Salvatore

Cheers,
Vincent

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986822#10

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

#72177

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

Hi,

Le 2021-06-05 08:31, Dekks Herton a écrit :
> Hi
> 
> Additional alsa-info script output

From a quick look, alsa-info reports that you're running both PipeWire and
PulseAudio sound servers. While it may not be the root cause of your issue,
if you want to stick with the former, please disable the latter:
$ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket

Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
Debian 11 is considered experimental.

Cheers,
Vincent

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

#72187

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

Le 2021-06-13 20:08, Vincent Blut a écrit :
> Hi,
> 
> Le 2021-06-05 08:31, Dekks Herton a écrit :
> > Hi
> > 
> > Additional alsa-info script output
> 
> From a quick look, alsa-info reports that you're running both PipeWire and
> PulseAudio sound servers. While it may not be the root cause of your issue,
> if you want to stick with the former, please disable the latter:
> $ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket

Err: the above command should not be run with sudo.

> Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
> Debian 11 is considered experimental.
> 
> Cheers,
> Vincent

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

#72197

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

Hi Vincent

I'll kill the pipewire server, i would uninstall the packages but they are
hard deps for gnome now.

Is the fw file catpt is trying to load the correct one? Is there new fw
files that come with catpt that have been forgotten?
Is there a listiing for the error codes -110 and -2, are they missing files
or read permission issues?

Regards.....




On Sun, 13 Jun 2021 at 18:08, Vincent Blut <vincent.debian@free.fr> wrote:

> Hi,
>
> Le 2021-06-05 08:31, Dekks Herton a écrit :
> > Hi
> >
> > Additional alsa-info script output
>
> From a quick look, alsa-info reports that you're running both PipeWire and
> PulseAudio sound servers. While it may not be the root cause of your issue,
> if you want to stick with the former, please disable the latter:
> $ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket
>
> Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
> Debian 11 is considered experimental.
>
> Cheers,
> Vincent
>

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

#72241

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

problem resolved, i think.

new sof firmware update came out, not sure its arrival was more than a
coincidence

1 - disabling all intel vitrualisation options in the helix bios was enough
to allow the fw to load thus  pavucontrol was now seeing input bars moving
but no sound output.

2 - ran alsactl -U init after i noticed ucm errors when running alsactl
init.

3 - aplay -l now sees all 3 cards when docked and 2 when tablet only.

4 - alsamixer still showed the correct hw but a lot of outputs were muted,
by enabling and disabling them all in sequence enabling the front dac
enabled sount from the rt256 card and headphone socket.

I'm doing basic checks like detaching and reattaching to see if that
affects the sound, so far ok Only noticeable thing is the fw gets reloaded
3 or 4 times a session, but doesn't seem to affect anything . If i have not
commented more  in a week feel free to close the bug.

On Tue, 15 Jun 2021 at 11:43, Dekks Herton <dekkzz76@gmail.com> wrote:

> Hi Vincent
>
> I'll kill the pipewire server, i would uninstall the packages but they are
> hard deps for gnome now.
>
> Is the fw file catpt is trying to load the correct one? Is there new fw
> files that come with catpt that have been forgotten?
> Is there a listiing for the error codes -110 and -2, are they missing
> files or read permission issues?
>
> Regards.....
>
>
>
>
> On Sun, 13 Jun 2021 at 18:08, Vincent Blut <vincent.debian@free.fr> wrote:
>
>> Hi,
>>
>> Le 2021-06-05 08:31, Dekks Herton a écrit :
>> > Hi
>> >
>> > Additional alsa-info script output
>>
>> From a quick look, alsa-info reports that you're running both PipeWire and
>> PulseAudio sound servers. While it may not be the root cause of your
>> issue,
>> if you want to stick with the former, please disable the latter:
>> $ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket
>>
>> Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
>> Debian 11 is considered experimental.
>>
>> Cheers,
>> Vincent
>>
>

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

#72324

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

Version: 5.10.38-1

Hi,

One week has passed, as per your request I'm closing this bug report. Feel free
to reopen it if the issue recurs.

Cheers,
Vincent

Le 2021-06-21 09:34, Dekks Herton a écrit :
> problem resolved, i think.
> 
> new sof firmware update came out, not sure its arrival was more than a
> coincidence
> 
> 1 - disabling all intel vitrualisation options in the helix bios was enough
> to allow the fw to load thus  pavucontrol was now seeing input bars moving
> but no sound output.
> 
> 2 - ran alsactl -U init after i noticed ucm errors when running alsactl
> init.
> 
> 3 - aplay -l now sees all 3 cards when docked and 2 when tablet only.
> 
> 4 - alsamixer still showed the correct hw but a lot of outputs were muted,
> by enabling and disabling them all in sequence enabling the front dac
> enabled sount from the rt256 card and headphone socket.
> 
> I'm doing basic checks like detaching and reattaching to see if that
> affects the sound, so far ok Only noticeable thing is the fw gets reloaded
> 3 or 4 times a session, but doesn't seem to affect anything . If i have not
> commented more  in a week feel free to close the bug.
> 
> On Tue, 15 Jun 2021 at 11:43, Dekks Herton <dekkzz76@gmail.com> wrote:
> 
> > Hi Vincent
> >
> > I'll kill the pipewire server, i would uninstall the packages but they are
> > hard deps for gnome now.
> >
> > Is the fw file catpt is trying to load the correct one? Is there new fw
> > files that come with catpt that have been forgotten?
> > Is there a listiing for the error codes -110 and -2, are they missing
> > files or read permission issues?
> >
> > Regards.....
> >
> >
> >
> >
> > On Sun, 13 Jun 2021 at 18:08, Vincent Blut <vincent.debian@free.fr> wrote:
> >
> >> Hi,
> >>
> >> Le 2021-06-05 08:31, Dekks Herton a écrit :
> >> > Hi
> >> >
> >> > Additional alsa-info script output
> >>
> >> From a quick look, alsa-info reports that you're running both PipeWire and
> >> PulseAudio sound servers. While it may not be the root cause of your
> >> issue,
> >> if you want to stick with the former, please disable the latter:
> >> $ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket
> >>
> >> Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
> >> Debian 11 is considered experimental.
> >>
> >> Cheers,
> >> Vincent
> >>
> >

[toc] | [prev] | [standalone]

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

csiph-web