Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [Regression] v1.2.13 broke my laptop's headphone microphone
Date: Sat, 22 Mar 2025 15:56:40 +0100 (CET)	[thread overview]
Message-ID: <182f27da2d89b500-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <182f27da2d827f00-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #530 was opened from vixalien:

Hello everyone!

I have a HP ProBook 440 G8 Notebook PC, and sound and microphones were working correctly on v1.2.12, but now the microphone is not working after upgrading to v1.2.13.

Here's my system details:

```
OS: Alpine Linux edge x86_64
Host: HP ProBook 440 G8 Notebook PC
Kernel: Linux 6.13.7-0-edge
```

```
$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
```

The `arecord` commands only works when I set the device to 0,6 and 0,7

```
arecord --duration=5 --format=dat --device=hw:0,0 test-mic.wav # does not work, empty audio
arecord --duration=5 --format=dat --device=hw:0,6 test-mic.wav # works
arecord --duration=5 --format=dat --device=hw:0,7 test-mic.wav # works
```

On v1.2.12, pipewire is automatically configured to use `0,6`, but on v1.12.13, it seems like it's configured to use `0,0` which causes that audio does not work.

I'm sorry this is my first issue report. I'm happy to provie more details if necessary.

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/530
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2025-03-22 14:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <182f27da2d827f00-webhooks-bot@alsa-project.org>]

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=182f27da2d89b500-webhooks-bot@alsa-project.org \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.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