You are not logged in.

#1 2022-09-17 07:47:47

NULLderef
Member
Registered: 2022-09-17
Posts: 1

Audio interface not picked up by pipewire after 5.19.9 kernel update

Some change in the 5.19.9 kernel update resulted in my interfaces (Behringer UMC204HD) channel layout to not be available in pipewire, the only exposed option being 'Off'. Downgrading to 5.19.8 has temporarily solved the issue, though this is not a long term fix. If anyone has figured out a fix for a similar issue any replies would be appreciated.

Offline

#2 2022-09-17 12:55:30

BoxOfXenon
Member
Registered: 2022-09-17
Posts: 1

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Can confirm on UMC202HD.

Offline

#3 2022-09-17 22:19:30

TomRobinsonIO
Member
Registered: 2022-09-17
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

I also have similar issue. On the previous kernel version, opening pavucontrol > Configuration, my Scarlett 4i4 interface would show an option "Analog Surround 4.0 Output + Analog Surround 2.1 Input" by default. After updating to 5.19.9, the only options I have are Analog Surround 4.0 Output, Analog Surround 5.1 Input, Analog Surround 4.1 Input, Analog Surround 2.1 Input, Analog Surround 5.0 Input, Pro Audio, Off.

When 4.0 Output is selected, the device only functions as an output device and the inputs do not show up in qjackctl, Reaper, Discord, etc. When the Input options are selected, the Inputs appear to work in those programs, but I get no audio out. When Pro Audio is selected, nothing appears to work.
I also see very similar behavior from my Axe-Fx II XL+ guitar interface though I don't know what options it showed previously. I do know that it was working as expected prior to the update.

Installing a fresh Arch VM and attaching the 4i4, I see the same behavior. Downgrading the kernel on the VM to 5.19.7, the behavior reverts to how I expect it to work.

Offline

#4 2022-09-18 11:14:06

TomRobinsonIO
Member
Registered: 2022-09-17
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Looks like we’re not the only ones.
https://bugzilla.kernel.org/show_bug.cgi?id=216500

Offline

#5 2022-09-21 17:11:11

dordoka
Member
Registered: 2022-09-21
Posts: 1

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Hi all.

Just wanted to post that I have also experienced problems with a TC-Helicon GoXLR usb audio device. Working fine on 5.19.8, not working on 5.19.9. Also had to rollback to 5.19.8.

Device ids are

 [    4.304781] usb 3-4.2: New USB device found, idVendor=1220, idProduct=8fe0, bcdDevice= 1.00
 [    4.304783] usb 3-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 [    4.304784] usb 3-4.2: Product: GoXLR
 [    4.304785] usb 3-4.2: Manufacturer: TC-Helicon

I have seen some changes in usb audio for kernel 5.19.9... might have generated this regression.

I also have another usb audio device that has been unaffected and works fine on 5.19.9:

 [    4.496271] usb 3-4.1.2: New USB device found, idVendor=1043, idProduct=857c, bcdDevice= 1.10
 [    4.496273] usb 3-4.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 [    4.496275] usb 3-4.1.2: Product: Xonar U7
 [    4.496275] usb 3-4.1.2: Manufacturer: ASUS

Offline

#6 2022-09-23 07:17:36

skogsmaskin
Member
From: Norway
Registered: 2016-03-23
Posts: 6
Website

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

After upgrading to kernel 5.19.10 today (was previously on 5.19.8) my soundcard isn't detected by the kernel. Or rather it errors with:

[  939.487513] usb 1-2: USB disconnect, device number 3
[  942.497809] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[  942.640650] usb 1-2: New USB device found, idVendor=2708, idProduct=0009, bcdDevice= 1.07
[  942.640656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  942.640658] usb 1-2: Product: Audient iD4
[  942.640660] usb 1-2: Manufacturer: Audient
[  943.691605] usb 1-2: 60:0: cannot get min/max values for control 1 (id 60)
[  943.695600] usb 1-2: 60:0: cannot get min/max values for control 3 (id 60)
[  943.696225] usb 1-2: 60:0: cannot get min/max values for control 4 (id 60)
[  943.697225] usb 1-2: 11:0: cannot get min/max values for control 11 (id 11)
[  943.699983] input: Audient Audient iD4 as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:06:00.1/usb1/1-2/1-2:1.3/0003:2708:0009.0008/input/input28
[  943.700067] hid-generic 0003:2708:0009.0008: input,hidraw1: USB HID v1.10 Mouse [Audient Audient iD4] on usb-0000:06:00.1-2/input3
[  943.737731] usb 1-2: 60:0: cannot get min/max values for control 1 (id 60)
[  943.737979] usb 1-2: 60:0: cannot get min/max values for control 3 (id 60)
[  943.738219] usb 1-2: 60:0: cannot get min/max values for control 4 (id 60)
[  943.738465] usb 1-2: 11:0: cannot get min/max values for control 11 (id 11)
[  943.738716] usb 1-2: 60:0: cannot get min/max values for control 1 (id 60)
[  943.738965] usb 1-2: 60:0: cannot get min/max values for control 3 (id 60)
[  943.739216] usb 1-2: 60:0: cannot get min/max values for control 4 (id 60)
[  943.739464] usb 1-2: 11:0: cannot get min/max values for control 11 (id 11)
[  943.739715] usb 1-2: 60:0: cannot get min/max values for control 1 (id 60)
[  943.742217] usb 1-2: 60:0: cannot get min/max values for control 3 (id 60)
[  943.743965] usb 1-2: 60:0: cannot get min/max values for control 4 (id 60)
[  943.744966] usb 1-2: 11:0: cannot get min/max values for control 11 (id 11)

My soundcard is:

Bus 001 Device 003: ID 2708:0009 Audient Audient iD4

EDIT:

I see now it's beeing worked on. Tnx TomRobinsonIO

TomRobinsonIO wrote:

Looks like we’re not the only ones.
https://bugzilla.kernel.org/show_bug.cgi?id=216500

Last edited by skogsmaskin (2022-09-23 07:25:32)

Offline

#7 2022-09-26 18:21:47

flyineko
Member
Registered: 2022-09-26
Posts: 1

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

I am having the same problem with a Motu M4.
I managed to get back separate pulseaudio input and output profiles as well as pipewire's Pro Audio profile after downgrading alsa-ucm-conf to 1.2.6.2-2 (newer versions might also work) from 1.2.7.2-1, however only few applications could actually output or record sound using those.
Downgrading the kernel to 5.19.8 fixed the issue for me as well.

Offline

#8 2022-09-26 18:48:56

kelvie
Member
Registered: 2022-05-08
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Also ran into this with my Motu M4 on 5.19.10. I actually ended up modifying the PKGBUILD retrieved via

yay -G linux

to do a revert and makepkg linux and linux-headers.

I also commented out the building of the htmldocs cause that took forever.

Offline

#9 2022-09-27 11:08:31

hikki
Member
Registered: 2022-09-27
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

The issue still exists.

Card: Audient iD4 (2708:0009)
Kernel: 5.19.11-zen1-1-zen

Offline

#10 2022-09-27 16:33:49

kelvie
Member
Registered: 2022-05-08
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Should we file an archlinux bug to have them revert this commit? Or do the kernel package maintainers usually wait for upstream to sort this out?

Offline

#11 2022-09-28 11:25:30

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 17,073

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

The relevant revert is in 5.19.12 so should be fixed when that kernel lands.

Offline

#12 2022-09-30 05:08:53

hikki
Member
Registered: 2022-09-27
Posts: 2

Re: Audio interface not picked up by pipewire after 5.19.9 kernel update

Fixed in kernel v5.19.12.

Offline

Board footer

Powered by FluxBB