Arch Linux

jonnyDumb

Guest

Audient iD4 recognised by kernel, but no usable profile defined?

Hello

After an update some time ago, the USB-Mic/instrument ADC Audient iD4  stopped having a selectable profile in pavucontrol-qt. Switched form pulsaudio to pipwire as it seems to integrate much better, but did not fix the issue either. The device is recognized, although with some errors regarding min max values of a controls. I believe this is not the issue as those warnings do not always appear. On third plug in, the segfault message was gone.

# dmesg:

...
[ 2711.193608] usb 3-2.1.1: new high-speed USB device number 7 using xhci_hcd
[ 2711.290555] usb 3-2.1.1: New USB device found, idVendor=2708, idProduct=0009, bcdDevice= 0.31
[ 2711.290562] usb 3-2.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2711.290564] usb 3-2.1.1: Product: Audient iD4
[ 2711.290566] usb 3-2.1.1: Manufacturer: Audient
[ 2712.423924] usb 3-2.1.1: 11:0: cannot get min/max values for control 11 (id 11)                                                                             
[ 2712.425912] input: Audient Audient iD4 as /devices/pci0000:00/0000:00:08.1/0000:0b:00.3/usb3/3-2/3-2.1/3-2.1.1/3-2.1.1:1.3/0003:2708:0009.000B/input/input35
[ 2712.426000] hid-generic 0003:2708:0009.000B: input,hidraw9: USB HID v1.10 Mouse [Audient Audient iD4] on usb-0000:0b:00.3-2.1.1/input3
[ 2712.453906] usb 3-2.1.1: 11:0: cannot get min/max values for control 11 (id 11)                                                                             
[ 2712.454157] usb 3-2.1.1: 11:0: cannot get min/max values for control 11 (id 11)                                                                             
[ 2712.454399] usb 3-2.1.1: 11:0: cannot get min/max values for control 11 (id 11)                                                                             
[ 2712.680445] wireplumber[16154]: segfault at 550030303031 ip 00007fe3d2708830 sp 00007fffa7512f10 error 6 in libasound.so.2.0.0[7fe3d26a9000+8b000]           
[ 2712.680455] Code: ed 0f 84 b6 fe ff ff 0f 1f 00 66 89 0b 48 01 c3 83 ea 01 73 f5 e9 a3 fe ff ff 41 8d 55 ff 45 85 ed 0f 84 96 fe ff ff 0f 1f 00 <89> 0b 48 01 c3 83 ea 01 73 f6 e9 84 fe ff ff 48 89 da e9 c6 fe ff
[ 2712.680483] audit: type=1701 audit(1665292762.055:104): auid=1000 uid=1000 gid=1000 ses=2 pid=16154 comm="wireplumber" exe="/usr/bin/wireplumber" sig=11 res=1
[ 2712.704018] audit: type=1334 audit(1665292762.078:105): prog-id=23 op=LOAD
[ 2712.704089] audit: type=1334 audit(1665292762.078:106): prog-id=24 op=LOAD
[ 2712.704113] audit: type=1334 audit(1665292762.078:107): prog-id=25 op=LOAD
[ 2712.704860] audit: type=1130 audit(1665292762.078:108): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-16187-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2712.802858] audit: type=1131 audit(1665292762.175:109): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-16187-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2712.920092] audit: type=1334 audit(1665292762.295:110): prog-id=0 op=UNLOAD
[ 2712.920097] audit: type=1334 audit(1665292762.295:111): prog-id=0 op=UNLOAD
[ 2712.920099] audit: type=1334 audit(1665292762.295:112): prog-id=0 op=UNLOAD

Downgrading the kernel below 5.19.8 fixed a similar issue (https://gitlab.freedesktop.org/pipewire … ssues/2703). I had 5.19.7 still on the disk and downgrade to that, did not solve the problem.

aplay -l recognizes the the device.

...
card 3: iD4 [Audient iD4], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #

I believe the problem is the same as this: https://bugs.archlinux.org/task/69228. Going down that route, i found:
-  The berhinger card is indeed found /usr/lib/udev/rules.d/90-pipewire-alsa.rules, but points to a more generic "texas-instruments-pcm2902.conf" (found here /usr/share/alsa-card-profile/mixer/profile-sets/texas-instruments-pcm2902.conf):
   ATTRS{idVendor}=="08bb", ATTRS{idProduct}=="2902", ENV{ACP_PROFILE_SET}="texas-instruments-pcm2902.conf"
- Audient iD4 vendor id (2708) and device id (in my case 0009) are not found in /usr/lib/udev/rules.d/90-pipewire-alsa.rules. Grep-ing unearthed Audient iD4 related files here:
  /usr/share/alsa/ucm2/USB-Audio/Audient/Audient-iD4-0009.conf
  /usr/share/alsa/ucm2/USB-Audio/USB-Audio.conf

What is ucm? I got a headache trying to find out. Currently my believe is that:
- I need an entry in /usr/lib/udev/rules.d/90-pipewire-alsa.rules or better create a new rule file and add an entry there. Should be achievable.
- I need a APC file usr/share/alsa-card-profile/mixer/profile-sets/. I have no idea how to create one and searching online yielded not results. In part probably because I do not have sufficient understanding what to search for. Also, the kernel issue keeps coming up, but as 5.19.7 did not solve the problem, I doubt its the problem.

Kernel: 5.19.13-arch1-1

I ran a system update just now and alsa-card-profiles and pipewire where part of it. No visible change....

Any suggestions?

pesky_pear

Member

Registered: 2022-11-01

Posts: 1

Re: Audient iD4 recognised by kernel, but no usable profile defined?

Hi!

Unfortunately I do not have an answer at the moment, but I have the very same problem. Also switched from pulseaudio to pipewire.

Kernel 6.0.6-arch1-1 / pipewire 1:0.3.59-3 / wireplumber 0.4.12-1 / alsa-lib 1.2.8-1

Output from dmesg:

[ +36.813903] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[  +0.207271] usb 3-1: New USB device found, idVendor=2708, idProduct=0009, bcdDevice= 0.31
[  +0.000009] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  +0.000002] usb 3-1: Product: Audient iD4
[  +0.000002] usb 3-1: Manufacturer: Audient
[  +0.758801] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.001092] input: Audient Audient iD4 as /devices/pci0000:00/0000:00:01.2/0000:02:00.2/0000:03:00.0/0000:04:00.0/usb3/3-1/3-1:1.3/0003:2708:0009.000C/input/input30
[  +0.000128] hid-generic 0003:2708:0009.000C: input,hidraw0: USB HID v1.10 Mouse [Audient Audient iD4] on usb-0000:04:00.0-1/input3
[  +0.043572] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.000376] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.000386] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.000367] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.165870] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.000067] audit: type=1701 audit(1667323608.869:279): auid=1000 uid=1000 gid=1000 ses=3 pid=27132 comm="wireplumber" exe="/usr/bin/wireplumber" sig=6 res=1
[  +0.005557] audit: type=1334 audit(1667323608.876:280): prog-id=57 op=LOAD
[  +0.000071] audit: type=1334 audit(1667323608.876:281): prog-id=58 op=LOAD
[  +0.000024] audit: type=1334 audit(1667323608.876:282): prog-id=59 op=LOAD
[  +0.029626] audit: type=1130 audit(1667323608.906:283): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@7-27196-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
[  +0.127819] audit: type=1131 audit(1667323609.032:284): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@7-27196-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termina>
[  +0.068447] audit: type=1334 audit(1667323609.102:285): prog-id=0 op=UNLOAD
[  +0.000006] audit: type=1334 audit(1667323609.102:286): prog-id=0 op=UNLOAD
[  +0.000002] audit: type=1334 audit(1667323609.102:287): prog-id=0 op=UNLOAD
[  +0.075897] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.000911] usb 3-1: 11:0: cannot get min/max values for control 11 (id 11)
[  +0.251566] usb 2-1: current rate 16000 is different from the runtime rate 48000
[  +0.015163] usb 2-1: current rate 16000 is different from the runtime rate 48000
[  +0.019770] usb 2-1: current rate 16000 is different from the runtime rate 48000
[  +0.009716] traps: wireplumber[27209] general protection fault ip:7f0834141770 sp:7ffd608a1100 error:0 in libasound.so.2.0.0[7f08340e2000+8b000]

However, the messages in dmesg are not always the same, I also saw pipewire reporting a segfault in libasound.so.2.0.0

With some research, I stumpled upon these discussions:
https://gitlab.freedesktop.org/pipewire … ssues/1119
https://github.com/alsa-project/alsa-ucm-conf/pull/151

So ALSA seems to have a dedicated UCM (User Case Manager Configuration) for the device and in general it should work. However, I am not sure if that is actually used, and if not, how I can enforce it. The last thing I tried was trying to enable it by setting ["api.alsa.use-ucm"] = true in the configuration file. Therefore I copied 50-alsa-config.lua from /usr/share/wireplumber to /etc/wireplumber/main.lua.d (Note: that path did't exist before) before and uncommented the respective line. However, that did not have the desired effect.

Edit:
Ok, my post was  a bit premature, just found these reports when searching for the USB-Error:
https://bbs.archlinux.org/viewtopic.php?id=279758
https://bugzilla.kernel.org/show_bug.cgi?id=216500

Based on that it should already be fixed since kernel 5.19.12

Last edited by pesky_pear (2022-11-01 18:37:56)

jonnyDumb

Guest

Re: Audient iD4 recognised by kernel, but no usable profile defined?

Hello pesky_pear

I am a bit short on time this week but wanted to at least give a quick reply.

My understanding is that this is not a kernel issue because:
- the device is enumerated and correctly identified by aplay -l
- the device does not need a specific driver, it is a generic audio device. I had another such device for a short time (Centrance dacport) and it worked flawlessly.
- downgrading to an older kernel did not solve the issue. I believe this is because the issue lies in the configuration files.

It was my understanding that the /usr/lib/udev/rules.d/90-pipewire-alsa.rules points to the configuration that will be used for a device. This file contains lines like this one, note the bold part:
ATTRS{idVendor}=="08bb", ATTRS{idProduct}=="2902", ENV{ ACP_PROFILE_SET}="texas-instruments-pcm2902.conf

ACP -> ALSA Card Profile. I found texas-instruments-pcm2902.conf here:
/usr/share/alsa-card-profile/mixer/profile-sets/texas-instruments-pcm2902.conf

All this makes me believe that the ALSA Card Profile is missing (an entry in the udev rules files is probably needed as well, but that should be easy to accomplish).

From what I can read in the last bug report you linked, there are profile choices, but the Pro Audio one caused an error for the reporter.

It is therefore currently still my believe that this https://bugs.archlinux.org/task/69228 is in essence the issue I am seeing. Along the way, the ACP for the Audient iD4 got dropped and the entry in 90-pipewire-alsa.rules deleted. Why believe and not certainty? Maybe there is another way this is intended to work, but that is broken. I am hopping someone with a birds eye view could shed some light on this. Searching online brought me back to the same conclusion over and over again.

If someone has a ACP for the Audient iD4, the above could be tested. I am also uncertain whether and where a bug report should be created. Is this an arch packaging problem, a problem somewhere upstream, or was it a conscious and intended decision to drop support for the iD4?

As time passes, I am would seek to write my own ACP file, if I manage to understand how. Time is currently an issue. If that happens and it works, I will report back.

jonnyDumb

Guest

Re: Audient iD4 recognised by kernel, but no usable profile defined?

Doing a bit more troubleshooting:

- Added this lines to /usr/lib/udev/rules.d/90-pipewire-alsa.rules:

ATTRS{idVendor}=="2708", ATTRS{idProduct}=="0009", ENV{ACP_PROFILE_SET}="analog-only.conf"

  Tried also with profile "default.conf". Restarted the system in both cases, same result, no profiles in pavucontrol-qt.

- Audient iD4 works in the live environment of the currently newest Ubuntu Studio: 22.10. Interestingly, Ubuntu Studio uses pulseaudio, not pipewire. While i was in the environment, I looked into /usr/lib/udev/rules.d/90-pulseaudio.rules. No trance of "2708" and "0009" either. As far as I could tell, there was no Audient specific file in /usr/share/alsa-card-profile/mixer/profile-sets/ either. So i thought that pipwire on my system must be the issue.

- On my arch installation: yay -S pulseaudio pulseaudio-alsa pulseaudio-jack. After rebooting no sound, odd... As it turns out, with the Audient iD4 now plugged in, pulseaudio does not want to start. This error appears twice:

E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="3" name="usb-Audient_Audient_iD4-00" card_name="alsa_card.usb-Audient_Audient_iD4-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=yes card_properties="module-udev-detect.discovered=1""): initialization failed.

Noteworthy may be that pulseaudio also failed to find my on-board sound card while the Audient iD4 was plugged in. This error only appears once in the output:

E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="2" name="pci-0000_0b_00.6" card_name="alsa_card.pci-0000_0b_00.6" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=yes card_properties="module-udev-detect.discovered=1""): initialization failed.

As I failed to see what Ubuntu Studio has, but my arch installation doesn't, I am completely lost right now.... I don't know where the missing information is located and what it looks like.

For now, as I would soon like to use the Audient iD4, my cumbersome workaround is this:
- Stick with pipewire on Arch, as it removes latency issues without the sometimes cumbersome jack. qpgraph is a must though for connecting midi devices to the right places. Finding the correct setting in LMMS took a bit of trial, but the settings are stored, so headache only once. I also can leave the Audient iD4 plugged in.
- Use Ubuntu studio live form a USB stick (dd if=/path/to/ubuntustudio-iso of=/dev/get-me-right-USB-device). On my system, selecting the UFEI option failed to load ubuntu studio, using the last option in the menu succeeded. Mount a hard disk/partition and safe what i like to safe there, for later use. Luckily, this is just a hobby, otherwise I would consider buying another hard disk an install Ubuntu studio there.

If some has suggestions, they are certainly still welcome

jonnyDumb

Guest

Re: Audient iD4 recognised by kernel, but no usable profile defined?

It works!

How and why, I do not know, but after trying again today, the Audient iD4 had a single profile "Pro Audio". Tested playback through headphone jack and recording through XLR microphone input.

Some recent update (past 2 months) must have fixed the issue.

(Topic can be closed, not sure if a moderator needs to do that? I don't see an option.)

Last edited by jonnyDumb (2023-03-08 17:45:36)