USB sound card doesn't initialize properly after 6.11.9

AlexKobrys · 2025-01-03 08:39:31

After updating to 6.12.0 kernel, the Sound Blaster G6 sound card does not initialize completely. The operating frequency is fixed at 48000. In addition, the sound card control menu (alsamixer) does not show all the sliders. If I reconnect the card, the card works fully. Installing the 6.11.9 kernel fixes the problem. All frequencies are listed in pipewire config.

MB: Gigabyte Aorus B650 ELITE AX V2
CPU: Ryzen 9 7900

6.11.9 card stream log:

Creative Technology Ltd Sound BlasterX G6 at usb-0000:10:00.0-5, high speed : USB Audio

Playback:
Status: Running
Interface = 1
Altset = 2
Packet Size = 288
Momentary freq = 192004 Hz (0x18.0021)
Feedback Format = 16.16
Interface 1
Altset 1
Format: S24_3LE
Channels: 2
Endpoint: 0x01 (1 OUT) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 24
Channel map: FL FR
Sync Endpoint: 0x81 (1 IN)
Sync EP Interface: 1
Sync EP Altset: 1
Implicit Feedback Mode: No
Interface 1
Altset 2
Format: S32_LE
Channels: 2
Endpoint: 0x01 (1 OUT) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 32
Channel map: FL FR
Sync Endpoint: 0x81 (1 IN)
Sync EP Interface: 1
Sync EP Altset: 2
Implicit Feedback Mode: No

Capture:
Status: Stop
Interface 2
Altset 1
Format: S24_3LE
Channels: 2
Endpoint: 0x82 (2 IN) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 24
Channel map: FL FR
Interface 2
Altset 2
Format: S32_LE
Channels: 2
Endpoint: 0x82 (2 IN) (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
Bits: 32
Channel map: FL FR

6.12.0 card stream log:

Creative Technology Ltd Sound BlasterX G6 at usb-0000:10:00.0-5, full speed : USB Audio

Playback:
Status: Stop
Interface 1
Altset 1
Format: S24_3LE
Channels: 2
Endpoint: 0x01 (1 OUT) (ASYNC)
Rates: 48000
Bits: 24
Channel map: FL FR
Sync Endpoint: 0x81 (1 IN)
Sync EP Interface: 1
Sync EP Altset: 1
Implicit Feedback Mode: No

Capture:
Status: Stop
Interface 2
Altset 1
Format: S24_3LE
Channels: 2
Endpoint: 0x82 (2 IN) (ASYNC)
Rates: 48000
Bits: 24
Channel map: FL FR

Last edited by AlexKobrys (2025-01-03 08:40:09)

gromit · 2025-01-03 10:11:02

Does that latest development release candidate already fix the issue?

sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.13rc5-1-x86_64.pkg.tar.zst

AlexKobrys · 2025-01-03 10:22:03

gromit wrote:

Does that latest development release candidate already fix the issue?
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.13rc5-1-x86_64.pkg.tar.zst

no. Still the same problem

gromit · 2025-01-03 10:29:03

This looks like a kernel regression, which should be bisected and reported upstream to the kernel developers and the regression mailing list ...

Are you confident to do the bisection on your own or do you need some help?
If you want we could also provide you with prebuilt kernel images for you to test

Good info to get you started is:
- https://docs.kernel.org/admin-guide/rep … sions.html
- https://wiki.archlinux.org/title/Kernel … egressions

In order for the issue to be properly bisectable it would need to be reproducible, so do you already know how you can trigger the bug reliably?

AlexKobrys · 2025-01-03 10:54:39

gromit wrote:

This looks like a kernel regression, which should be bisected and reported upstream to the kernel developers and the regression mailing list ...
Are you confident to do the bisection on your own or do you need some help?
If you want we could also provide you with prebuilt kernel images for you to test
In order for the issue to be properly bisectable it would need to be reproducible, so do you already know how you can trigger the bug reliably?

Yes, I'm confident enough to attempt bisection on my own. I can also test your prebuilt images. Are they organized by commits? Regarding reproducing this bug, I believe I know how to reproduce it.

gromit · 2025-01-03 11:09:52

Yes they always have the commit in the name, you can get the needed one like so if you're in the checkout of the kernel sources and already started the bisection:

URL="https://pkgbuild.com/~gromit/linux-bisection-kernels/linux-mainline-$(git describe --long --abbrev=7 | sed 's/\([^-]*-g\)/r\1/;s/-/./g')-1-x86_64.pkg.tar.zst"; curl --output /dev/null --silent --head --fail "${URL}" && echo "sudo pacman -U ${URL/\~/\~}" || echo "Not in cache"

The first one is the following if you bisect between 6.11 and 6.12:

sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.11.r7272.g509d2cd-1-x86_64.pkg.tar.zst

Arch Linux

#1 2025-01-03 08:39:31

USB sound card doesn't initialize properly after 6.11.9

#2 2025-01-03 10:11:02

Re: USB sound card doesn't initialize properly after 6.11.9

#3 2025-01-03 10:22:03

Re: USB sound card doesn't initialize properly after 6.11.9

#4 2025-01-03 10:29:03

Re: USB sound card doesn't initialize properly after 6.11.9

#5 2025-01-03 10:54:39

Re: USB sound card doesn't initialize properly after 6.11.9

#6 2025-01-03 11:09:52

Re: USB sound card doesn't initialize properly after 6.11.9

Board footer