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: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Rander Wang <rander.wang@intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	linux-sound@vger.kernel.org, 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 => missing alsa-ucm-conf
Date: Tue, 2 Jan 2024 10:03:29 -0800	[thread overview]
Message-ID: <ZZRP8RqT83cE-S5m@merlins.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2401021117370.14041@eliteleevi.tm.intel.com>

On Tue, Jan 02, 2024 at 02:23:49AM -0800, Marc MERLIN wrote:
> > Please file a bug at 
> > https://github.com/thesofproject/linux/issues
>  
> THanks, done: https://github.com/thesofproject/linux/issues/4758

First, a big thanks for the quick reply and help.
For the benefit of archives and the next potential person looking for
this, my debian system was lacking 
alsa-ucm-conf
which for this soundcare is not optional at all. 

Long gone are the days of simple soundcards that just worked (never mind
self made DAC with resistors in the parrallel port :) ), nowadays sound
cards need a lot of things for anything to work. I had read about some
puzzling defaults of having an amp for speakers, controlled in software,
and off by default :-/  but didn't know that mine was so new/complex
that it would not show up in alsamixer where you would normally unmute
an output and be in your way. Now I've read about alsaucm and maybe
there was a magic combination that would have worked with alsamixer
but too many variables to try, hence aslaucm. 

I spent probably over 10 hours on this building kernels, and comparing
debian to ubuntu, and doing a ridiculous amount of diffs between the
setups, I was unable to see anything about the output being muted, but I
Guess it wasn't being muted, the amp needing to be turned on is yet
another thing and it didn't how up where I looked.

So, a few thoughts:
1) for sure, debian package alsa-ucm-conf should be required, not
recommended. It's not big, people who can't keep track of everything
that changes all the time, have no idea that they need it, and really
need it installed by default if their hardware requires it.
I've filed a couple of bugs with them, including on the package
description that gives little clue that the package can be so essential

Description-en: ALSA Use Case Manager configuration files
 This package contains ALSA Use Case Manager configuration of audio
 input/output names and routing for specific audio hardware. They can be
 used with the alsaucm tool.

2) I spent many hours reading the internet on all issues with sound and
muting and why sound could work on headphones and not speakers, and
nothing gave me a hint that worked, or even mentioned alsaucm.
When I have some time, I'll write a page that I'll try to get
indexed so that the next person dealing with this has a better chance
to find the answer

3) I failed to find the linux-sound list, that's on me, and my mail to
alsa-devel was bouncing for unknown reasons.

A huge huge thanks to you, Kai, for finding this Email and your help.

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

  parent reply	other threads:[~2024-01-02 18:03 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
2024-01-02 18:03   ` Marc MERLIN [this message]
2024-01-02 19:14     ` 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 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=ZZRP8RqT83cE-S5m@merlins.org \
    --to=marc@merlins.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rander.wang@intel.com \
    --cc=yung-chuan.liao@linux.intel.com \
    /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