public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: sof-audio-pci-intel-tgl/soundwire 6.6.8 kernel outputs no sound on speakers but works on headphones
Date: Tue, 2 Jan 2024 02:23:49 -0800	[thread overview]
Message-ID: <ZZPkNRuMXYKOe-Os@merlins.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2401021117370.14041@eliteleevi.tm.intel.com>

On Tue, Jan 02, 2024 at 11:26:18AM +0200, Kai Vehmanen wrote:
> Hi,
> 
> On Sat, 23 Dec 2023, Marc MERLIN wrote:
> 
> > Howdy,
> > 
> > First, apologies if I'm not sending this to the right place, I could not
> > find an approrpriate soundwire/sof mailing list, please redirect me as
> > needed (I had to find an old soundwire message for reference)
> > 
> > laptop; Dell XPS 17 9730
> > 
> > merlin:~# lspci | grep -i audio
> > 0000:00:1f.3 Multimedia audio controller: Intel Corporation Device 51ca (rev 01)
> > 
> > stock mainline 6.6.8 shows the device, but no sound comes out, as if it
> > were muted, but I do not see anyting muted in alsamixer. If I plug in
> 
> we'd need a bit more info, especially alsa-info output, to figure out 
> whether this is an issue with the mixer settings and/or the drivers. 
> Instructions how to get alsa-info output availbale at 
> https://thesofproject.github.io/latest/getting_started/intel_debug/suggestions.html

Sure thing. I tried to give a lot fo machine info in my first 2 Emails,
sorry that I missed some.
Reading that page, the good news is that sound output works with the
same 6.5.0-14.generic kernel under ubuntu 23, so at least linux can make
it work without windows needed.

looks like alsa-info mostly gathered what I had captured manually and
posted, but here it is
https://alsa-project.org/db/?f=d732a80cdb3d8e569a97c7dc73a32ddc76aea8a9

I added the modprobe.conf debugging recommended in your page, and that
seems to have killed sound:
https://alsa-project.org/db/?f=7397a0f60194cc275fe7e6c0ed38733559d91382

> Please file a bug at 
> https://github.com/thesofproject/linux/issues
 
THanks, done: https://github.com/thesofproject/linux/issues/4758

> There was one bug affecting 9730 variants, but I don't think your case
> is the the same:
> https://github.com/thesofproject/linux/issues/4380

Indeed, I referenced them, thanks.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
 
Home page: http://marc.merlins.org/                       | PGP 7F55D5F27AAF9D08

  reply	other threads:[~2024-01-02 10:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23 23:44 sof-audio-pci-intel-tgl/soundwire 6.6.8 kernel outputs no sound on speakers but works on headphones Marc MERLIN
2023-12-27 19:02 ` Marc MERLIN
2024-01-02  9:26 ` Kai Vehmanen
2024-01-02 10:23   ` Marc MERLIN [this message]
2024-01-02 18:03   ` sof-audio-pci-intel-tgl/soundwire 6.6.8 kernel outputs no sound on speakers but works on headphones => missing alsa-ucm-conf Marc MERLIN
2024-01-02 19:14     ` Marc MERLIN
2024-01-02 21:24     ` Marc MERLIN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZZPkNRuMXYKOe-Os@merlins.org \
    --to=marc@merlins.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox