[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1120277: linux: I'm filing this because I have a serious, persistent bug with my Intel AX210 Bluetooth audio on Debian. The problem isn't configuration; it's a kernel driver failure. My Bluetooth headset connects, but I get absolutely no sound.



Source: linux
Version: 6.16.12+deb14+1-amd64
Severity: normal
X-Debbugs-Cc: pampuski@duck.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.16.12+deb14+1-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Dear Maintainer,

I'm filing this because I have a serious, persistent bug with my Intel AX210 Bluetooth audio on Debian. The problem isn't configuration; it's a kernel driver issue preventing high-quality audio streaming (A2DP).

The Bluetooth headset connects, but I get absolutely no sound.

1. Situation

    System State: Stable on basic audio (now running PulseAudio), but the A2DP profile fails immediately upon stream activation.

    Ineffective (The Bug): I cannot get sound out of the headset. Manual activation via pactl set-card-profile [card] a2dp_sink fails immediately with an Input/Output error or No such entity, indicating a low-level driver failure upon audio stream creation.

    Ineffective (The Scope): The issue persists across multiple current distributions (Debian, openSUSE Tumbleweed), confirming it is a widespread bug in the Kernel/BlueZ stack, not a simple Debian configuration issue.

    Effective (The Clue): The exact same hardware/headset combination works perfectly on Linux Mint, suggesting the specific patch needed to fix the A2DP transport failure is missing from the current Debian kernel.

2. Evidence

A. Failure Mode (The Error):

When attempting to activate A2DP, the command fails:

pactl set-card-profile bluez_card.0C_AE_BD_DB_C9_85 a2dp_sink
Failure: Input/Output error

B. Kernel Driver Status (Proof drivers are loaded but failing):

$ sudo dmesg | grep -i 'alsa\|audio\|hda\|btusb'
[ 3.912133] usb 3-6: Product: USB Audio
[ 3.977366] hid-generic 0003:0B05:1A52.0007: hiddev3,hidraw6: USB HID v1.11 Device [Generic USB Audio] on usb-0000:12:00.0-6/input7
[ 8.877075] snd_hda_intel 0000:03:00.1: Force to non-snoop mode
[ 8.943353] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 8.945385] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input15
[ 8.945437] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input16
[ 8.945482] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input17
[ 8.945530] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input18
[ 8.945574] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.1/sound/card1/input19
[ 8.951649] usbcore: registered new interface driver btusb
[ 14.878507] usbcore: registered new interface driver snd-usb-audio

C. Audio Sink Status (Proof A2DP is visible but silent):

$ actl list sinks short
...
7       bluez_sink.F4_9D_8A_88_50_6F.a2dp_sink  module-bluez5-device.c  s16le 2ch 44100Hz       IDLE

(Note: The sink is loaded as A2DP but remains in the silent IDLE state.)

Thank you for your time in investigating this issue,

Bob


Reply to: