Can’t get audio quest dragonfly red to work on rasp pi 4b kernel 5.15

pjkemp · 14 April 2025 23:32

lsusb shows the DAC
the kernel drivers show loaded

I just cannot get applications, amixer, alsamixer, rhythm box, to see the DAC.
Anyone have any ideas?

Thanks
Phil

stephematician · 15 April 2025 02:18

I have two questions to start with:

What is the output of alsactl info?
What is the output of inxi -SMAz?

pjkemp · 15 April 2025 04:24

couldn't find info
used

pi-mate-29:~(2004)sudo alsactl init
alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
Found hardware: "bcm2835_headpho" "Broadcom Mixer" "" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2
Found hardware: "vc4-hdmi" "" "" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2
Found hardware: "vc4-hdmi" "" "" "" ""
Hardware is initialized using a generic method
pi-mate-29:~(2005)sudo inxi -SMAz
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_US"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
System:
  Kernel: 5.15.0-1075-raspi aarch64 bits: 64 Desktop: MATE
    Distro: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Machine:
  Type: ARM System: Raspberry Pi 4 Model B Rev 1.5 details: BCM2835
    rev: d03115 serial: <filter>
Audio:
  Device-1: bcm2711-hdmi0 driver: vc4_hdmi
  Device-2: bcm2711-hdmi1 driver: vc4_hdmi
  Device-3: bcm2835-audio driver: bcm2835_audio
  Device-4: AudioQuest DragonFly Red type: USB driver: hid-generic,usbhid
  Sound Server-1: ALSA v: k5.15.0-1075-raspi running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
pi-mate-29:~(2006)

so inxi can see it! thats good.
alsa cannot. not so good!

Phil

stephematician · 15 April 2025 06:12

alsactl init won't help anyway, it doesn't list (for example) the USB headset that I'm currently using. You could try arecord --list-devices.

Those drivers look a little bit old, given that alsa-utils doesn't support the 'info' command, and you're sitting on pipewire version 0.3.48 which is from about 3 years back; and a lot has changed over that time.

Two more things that might help me figure out what I'm looking at:

What does pactl info tell us?
wpctl status | grep Devices -A5 should show what devices are known to wireplumber (i.e. pipewire).

pjkemp · 15 April 2025 06:12

sorting through things.

I found these two lines in dmesg

[ 12.936853] snd-usb-audio 1-1.3:1.0: cannot find the slot for index 0 (range 0-0), error: -16
[ 12.936904] usb 1-1.3: cannot create card instance 0
[ 12.936919] snd-usb-audio: probe of 1-1.3:1.0 failed with error -16

Don't know exactly what this means (yet) but looks suspiciously like the issue....

PK

pjkemp · 15 April 2025 06:14

i-mate-29:log(2012)pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 102
Tile Size: 65472
User Name: phil
Host Name: pi-mate-29
Server Name: PulseAudio (on PipeWire 0.3.48)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: auto_null
Default Source: auto_null.monitor
Cookie: f40b:2f4d

pjkemp · 15 April 2025 06:15

pi-mate-29:log(2016)wpctl status | grep Devices -A5
 ├─ Devices:
 │  
 ├─ Sinks:
 │  *   33. Dummy Output                        [vol: 1.00]
 │  
 ├─ Sink endpoints:
--
 ├─ Devices:
 │  
 ├─ Sinks:
 │  
 ├─ Sink endpoints:
 │  
pi-mate-29:log(2017)

pjkemp · 15 April 2025 06:25

found some references to a similar error. tried a workaround but it still fails to initialize.

Apr 15 02:21:54 pi-mate-29 kernel: [ 1213.671532] usb 1-1.3: USB disconnect, device number 3
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.165562] usb 1-1.3: new full-speed USB device number 4 using xhci_hcd
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.273210] usb 1-1.3: New USB device found, idVendor=21b4, idProduct=0082, bcdDevice= 1.06
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.273250] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.273267] usb 1-1.3: Product: AudioQuest DragonFly Red v1.0
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.273281] usb 1-1.3: Manufacturer: AudioQuest
Apr 15 02:22:03 pi-mate-29 kernel: [ 1223.273294] usb 1-1.3: SerialNumber: AQDFRD0100102320
Apr 15 02:22:09 pi-mate-29 kernel: [ 1228.530140] hid-generic 0003:21B4:0082.0002: hiddev0,hidraw0: USB HID v1.11 Device [AudioQuest AudioQuest DragonFly Red v1.0] on usb-0000:01:00.0-1.3/input2
Apr 15 02:22:09 pi-mate-29 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Apr 15 02:22:09 pi-mate-29 mtp-probe: bus: 1, device: 4 was not an MTP device
Apr 15 02:22:09 pi-mate-29 kernel: [ 1228.579804] snd-usb-audio 1-1.3:1.0: cannot find the slot for index 0 (range 0-2), error: -16
Apr 15 02:22:09 pi-mate-29 kernel: [ 1228.579833] usb 1-1.3: cannot create card instance 0
Apr 15 02:22:09 pi-mate-29 kernel: [ 1228.579845] snd-usb-audio: probe of 1-1.3:1.0 failed with error -16
Apr 15 02:22:09 pi-mate-29 kernel: [ 1228.581300] usbcore: registered new interface driver snd-usb-audio
Apr 15 02:22:09 pi-mate-29 mtp-probe: checking bus 1, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3"
Apr 15 02:22:09 pi-mate-29 mtp-probe: bus: 1, device: 4 was not an MTP device

stephematician · 15 April 2025 06:26

Looks like, perhaps, an incorrect setting for modprobe?

The output of grep -r 'index=' /etc/modprobe.d might help; here's what it looks like on my UM24.04 machine (defaults):

/etc/modprobe.d/alsa-base.conf:options bt87x index=-2
/etc/modprobe.d/alsa-base.conf:options cx88_alsa index=-2
/etc/modprobe.d/alsa-base.conf:options saa7134-alsa index=-2
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-intel8x0m index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-audio index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-caiaq index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-ua101 index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-us122l index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-usx2y index=-2
/etc/modprobe.d/alsa-base.conf:options snd-pcsp index=-2
/etc/modprobe.d/alsa-base.conf:options snd-usb-audio index=-2

stephematician · 15 April 2025 06:32

Oh, also grep -r 'index=' /lib/modprobe.d might be useful.

stephematician · 17 April 2025 02:44

By the way; this is telling us that the snd-usb-audio driver is not being loaded; which means something is failing on the kernel level (i.e. potentially incorrect settings).

As an example of what we want to see; here's the output given a USB headset connected to my system:

  Device-5: Razer USA Barracuda X driver: hid-generic,snd-usb-audio,usbhid
    type: USB