MX Linux Audio

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
passiflora
Posts: 2
Joined: Wed Nov 13, 2024 4:25 am

MX Linux Audio

#1 Post by passiflora »

Hello, I have been through a number of distros and am currently using MX Linux in an attempt to replace Windows as a desktop OS. A major pain point has been that bluetooth audio seems to "just not work". There is significant stuttering on multiple different Bluetooth audio devices which i cannot find a solution to. Using Liquorix Kernel doesn't solve this problem, there are only 2 available codecs that can be selected, neither of which fix the problem, isenkram-autoinstall-firmware gives the following |info:

Code: Select all

some kernel driver requested extra firmware files: amdgpu/aldebaran_cap.bin amdgpu/gc_11_0_0_toc.bin amdgpu/gc_11_0_3_mes.bin amdgpu/ip_discovery.bin amdgpu/navi10_mes.bin amdgpu/navi12_cap.bin amdgpu/psp_14_0_2_sos.bin amdgpu/psp_14_0_2_ta.bin amdgpu/psp_14_0_3_sos.bin amdgpu/psp_14_0_3_ta.bin amdgpu/sienna_cichlid_cap.bin amdgpu/sienna_cichlid_mes1.bin amdgpu/sienna_cichlid_mes.bin amdgpu/smu_14_0_2.bin amdgpu/smu_14_0_3.bin amdgpu/vcn_5_0_0.bin amdgpu/vega10_cap.bin renesas_usb_fw.mem rtl_bt/rtl8723b_config.bin rtl_bt/rtl8723bs_config.bin rtl_bt/rtl8723cs_cg_config.bin rtl_bt/rtl8723cs_cg_fw.bin rtl_bt/rtl8723cs_vf_config.bin rtl_bt/rtl8723cs_vf_fw.bin rtl_bt/rtl8723cs_xx_config.bin rtl_bt/rtl8723cs_xx_fw.bin rtl_bt/rtl8723ds_config.bin rtl_bt/rtl8723ds_fw.bin rtl_bt/rtl8761a_config.bin rtl_bt/rtl8852bs_config.bin rtl_bt/rtl8852bs_fw.bin
info: locating packages with the requested firmware files
info: determining whether enabling other components is required
info: No new firmware package with requested firmware detected.|
I am really unsure of how to proceed; the included manual doesn't say anything about troubleshooting Bluez/Pipewire and stuff that comes up online is pretty unclear about how to actually modify possibly problematic pipewire configuration. Any help would be appreciated whether it be something i can actually do to fix the problem or a manual on how to troubleshoot Pipewire (not sure if this exists).
(Not sure if this is helpful but I am using the KDE Plasma edition of MX Linux on a DELL Inspiron 15 with 16 GB of RAM)
Here is the "Quick System Info" related to bluetooth :

Code: Select all

Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 3-1:2 chip-ID: 0bda:c829
    class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: f098 hci-v: 4.2 rev: 75b8
  Info: acl-mtu: 1021:8 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
and audio

Code: Select all

Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Dell driver: snd_rn_pci_acp3x v: kernel
    alternate: snd_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x,
    snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Dell driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.6 chip-ID: 1022:15e3
    class-ID: 0403
  API: ALSA v: k6.10.12-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Thank you in advance
Passiflora
Last edited by passiflora on Sat Nov 30, 2024 8:29 am, edited 1 time in total.

User avatar
j2mcgreg
Global Moderator
Posts: 6610
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX Linux Audio

#2 Post by j2mcgreg »

We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
passiflora
Posts: 2
Joined: Wed Nov 13, 2024 4:25 am

Re: MX Linux Audio

#3 Post by passiflora »

I edited the post and added the Bluetooth and Audio info

User avatar
j2mcgreg
Global Moderator
Posts: 6610
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX Linux Audio

#4 Post by j2mcgreg »

passiflora wrote: Sat Nov 30, 2024 8:31 am I edited the post and added the Bluetooth and Audio info
You have to post the complete QSI. An edited version is not acceptable.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

PeterO
Posts: 56
Joined: Sun Dec 22, 2019 4:18 am

Re: MX Linux Audio

#5 Post by PeterO »

Unfortunately, Linux doesn't always work well with WiFi/Bluetooth. Chip-set suppliers (who should provide relevant drivers) seems to be more focused on Windows and IOS, which is understandable if one considers market penetrations.
I have had better experience with Manjaro for both WiFi and Bluetooth, but most likely it varies much - there is a myriad of chip-sets and drivers.

Stuttering indicates there is an issue with the radio connection. Bluetooth has a weak radio link, which easily gets interfered by WiFi, microwave ovens, .... Also range is limited, usually 10 m (i free space) is stated as a max (there are all the anecdotal stories of users being much further than this, still having a good connection.).
Of course, if you do not have the same behavior using Windows with everything else identical then the radio link is less likely to be the issue.

Pipewire and pulseaudio transition is also a possible cause, somehow we seem to be in the middle of this transition, with a mix, with many dated suggestions on how to improve Linux audio.

Post Reply

Return to “MX Help”