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 13:24:34 -0800 [thread overview]
Message-ID: <ZZR_Et3vvv-bmQ0H@merlins.org> (raw)
In-Reply-To: <ZZRP8RqT83cE-S5m@merlins.org>
On Tue, Jan 02, 2024 at 10:03:29AM -0800, Marc MERLIN wrote:
> 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
Done:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059871
alsa-ucm-conf should be a required package by libasound2-data, it's essential on some sound hardware
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059872
alsa-ucm-conf should be a required package, it's essential on some sound hardware
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
prev parent reply other threads:[~2024-01-02 21:24 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 ` 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 [this message]
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=ZZR_Et3vvv-bmQ0H@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