Arch Linux

bjl32

Member

Registered: 2026-01-24

Posts: 4

[SOLVED] Audio system failure after kernel and alsa-lib update

Hi,
After a recent yay -Syu, which updated alsa-lib and linux, all audio stopped working on my system.
I tried downgrading alsa-lib and linux. It still fails. I switched to linux-lts. Still fails.
I tried switching from pipewire to pulseaudio, but still fails, so I believe this is a kernel/driver issue rather than a userspace audio stack problem.
The speaker is detected by USB:

Bus 001 Device 013: ID 2717:d004 Xiaomi Inc. REDMI 电脑音箱 2 Pro

But it never appears as an audio device.
lsusb -t shows it as a HID device instead:

|__ Port 003: Dev 013, If 0, Class=Human Interface Device, Driver=[none], 12M

dmesg on plug-in:

usb 1-4: New USB device found, idVendor=2717, idProduct=d004
usb 1-4: Product: REDMI 电脑音箱 2 Pro
usb 1-4: Manufacturer: Mi
usbhid 1-4:1.0: couldn't find an input interrupt endpoint

No snd-usb-audio binding happens for this device.

Whether the speaker is plugged in or not:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1
card 1: Generic [HD-Audio Generic], device 3: HDMI 0
card 1: Generic [HD-Audio Generic], device 7: HDMI 1
card 1: Generic [HD-Audio Generic], device 8: HDMI 2
card 2: Generic_1 [HD-Audio Generic], device 0: ALC897 Analog
card 2: Generic_1 [HD-Audio Generic], device 1: ALC897 Digital

These cards exist even when the USB speaker is unplugged.
The speaker device is never listed by ALSA.
lsusb -v -d <the speaker> output:

❯ lsusb -v -d 2717:d004

Bus 001 Device 013: ID 2717:d004 Xiaomi Inc. REDMI 电脑音箱 2 Pro
Couldn't open device, some information will be missing
Negotiated speed: Full Speed (12Mbps)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2717 Xiaomi Inc.
  idProduct          0xd004 REDMI 电脑音箱 2 Pro
  bcdDevice            1.00
  iManufacturer           1 Mi
  iProduct                2 REDMI 电脑音箱 2 Pro
  iSerial                 3 20190808
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001b
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         3 Human Interface Device
      bInterfaceSubClass      0 [unknown]
      bInterfaceProtocol      0 
      iInterface              0 
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               2.01
          bCountryCode            0 Not supported
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      36
          Report Descriptors: 
            ** UNAVAILABLE **

I'd appreciate any advice.
Thanks.

EDIT:
I have reinstalled archlinux, and its working again.

Last edited by bjl32 (2026-02-07 10:53:29)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,116

Re: [SOLVED] Audio system failure after kernel and alsa-lib update

This board uses bbcode  [code][/code] tags not markdown, please edit your post in this regard

This dmesg error does look rather kernelish and the "bad thing" about LTS kernels is that they will receive all the stable patches just the same as long as they pertain to functionality present there as well.

So what happens if you do an actual kernel downgrade to a known working version? Also when was "recent" which exact versions? There were some known bugs in alsa-lib/alsa-ucm-conf prior to 1.2.15.3 and these updates have been somewhat recent, if your update predates that, try updating again.