My Steelseries Pro Wireless headphones no longer work after upgrading to the 5.16.15 kernel

Before the upgrade it was working good, but now when I turn on my headphones, the USB device enters a cycle where it disconnects, connects,... It triggers a full power cycle on the USB receiver, making it reboot.

Here's some debugging output:

λ lsusb 
Bus 005 Device 090: ID 1038:1290 SteelSeries ApS Arctis Pro Wireless
λ inxi -Fxz
Audio:
Device-5: SteelSeries ApS Arctis Pro Wireless type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2.3:81

I found some relevant logs, but I'm not sure how to proceed:

23/03/2022 10:04	usb 3-10.3	new full-speed USB device number 32 using xhci_hcd
23/03/2022 10:04	usb 3-10.3	new full-speed USB device number 32 using xhci_hcd
23/03/2022 10:04	usb 3-10.3	New USB device found, idVendor=1038, idProduct=1294, bcdDevice= 1.12
23/03/2022 10:04	usb 3-10.3	New USB device strings: Mfr=4, Product=5, SerialNumber=0
23/03/2022 10:04	usb 3-10.3	Product: Arctis Pro Wireless
23/03/2022 10:04	usb 3-10.3	Manufacturer: SteelSeries
23/03/2022 10:04	usb 3-10.3	New USB device found, idVendor=1038, idProduct=1294, bcdDevice= 1.12
23/03/2022 10:04	usb 3-10.3	New USB device strings: Mfr=4, Product=5, SerialNumber=0
23/03/2022 10:04	usb 3-10.3	Product: Arctis Pro Wireless
23/03/2022 10:04	usb 3-10.3	Manufacturer: SteelSeries
23/03/2022 10:04	input	SteelSeries Arctis Pro Wireless Consumer Control as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.3/3-10.3:1.5/0003:1038:1294.0384/input/input695
23/03/2022 10:04	input	SteelSeries Arctis Pro Wireless Consumer Control as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.3/3-10.3:1.5/0003:1038:1294.0384/input/input695
23/03/2022 10:04	input	SteelSeries Arctis Pro Wireless as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.3/3-10.3:1.5/0003:1038:1294.0384/input/input696
23/03/2022 10:04	hid-generic 0003	038:1294.0384: input,hiddev96,hidraw0: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.3/input5
23/03/2022 10:04	input	SteelSeries Arctis Pro Wireless as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.3/3-10.3:1.5/0003:1038:1294.0384/input/input696
23/03/2022 10:04	hid-generic 0003	038:1294.0384: input,hiddev96,hidraw0: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.3/input5
23/03/2022 10:04	usb 3-10.2	new full-speed USB device number 33 using xhci_hcd
23/03/2022 10:04	usb 3-10.2	new full-speed USB device number 33 using xhci_hcd
23/03/2022 10:04	usb 3-10.2	New USB device found, idVendor=1038, idProduct=1290, bcdDevice= 6.00
23/03/2022 10:04	usb 3-10.2	New USB device strings: Mfr=1, Product=2, SerialNumber=0
23/03/2022 10:04	usb 3-10.2	Product: Arctis Pro Wireless
23/03/2022 10:04	usb 3-10.2	Manufacturer: SteelSeries
23/03/2022 10:04	usb 3-10.2	New USB device found, idVendor=1038, idProduct=1290, bcdDevice= 6.00
23/03/2022 10:04	usb 3-10.2	New USB device strings: Mfr=1, Product=2, SerialNumber=0
23/03/2022 10:04	usb 3-10.2	Product: Arctis Pro Wireless
23/03/2022 10:04	usb 3-10.2	Manufacturer: SteelSeries
23/03/2022 10:04	hid-generic 0003	038:1290.0385: hiddev97,hidraw1: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.2/input0
23/03/2022 10:04	hid-generic 0003	038:1290.0386: hiddev98,hidraw2: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.2/input1
23/03/2022 10:04	hid-generic 0003	038:1290.0385: hiddev97,hidraw1: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.2/input0
23/03/2022 10:04	hid-generic 0003	038:1290.0386: hiddev98,hidraw2: USB HID v1.11 Device [SteelSeries Arctis Pro Wireless] on usb-0000:00:14.0-10.2/input1
23/03/2022 10:04	usb 3-10.2	USB disconnect, device number 33
23/03/2022 10:04	usb 3-10.2	USB disconnect, device number 33
23/03/2022 10:04	usb 3-10.3	USB disconnect, device number 32
23/03/2022 10:04	usb 3-10.3	USB disconnect, device number 32

Interestingly, the problem only starts when I turn on my wireless headphones; when I plug in another pair op headphones by wire into the receiver, it works and I get sound.

If anyone could provide some guidance in tackling this problem I would be very grateful, I'm a developer, but this digs too deep into Linux for me to be able to figure it out with my current knowledge...

Install and test the linux-lts kernel.

If no love, test linux-mainline or linux kernels.

Post full garuda-inxi.

Welcome to the forum.

2 Likes

You could bisect kernels--a lengthy, hardware-intensive process--but how much time do you wish to devote to a problem that may well disappear with the next iteration? If the fault lies entirely with that kernel version as your topic header implies. How sure are you of that?

I have a kinda similar issue with my Steelseries Arctis 7. Booting the lts kernel solved my issue timewise. It occured again later on.
Post of my issue: No system audio when joining a discord channel - #2 by Kottonballs

Thanks for the warm welcome on the forums and your kind responses! :slight_smile:

@c00ter :

You could bisect kernels--a lengthy, hardware-intensive process--but how much time do you wish to devote to a problem that may well disappear with the next iteration? If the fault lies entirely with that kernel version as your topic header implies. How sure are you of that?

Exactly what I'm trying to prevent :smiley: I mainly mentioned this as a "throw tech stuff at me that might fix the issue, I'll probably manage :stuck_out_tongue:

@tbg:
I tried booting with the kernels you suggested, but sadly enough no love for other reasons:

[FAILED] Failed to start Samba NMB Daemon

Here's my garuda-inxi:

λ garuda-inxi
System:
Kernel: 5.16.16-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=3606f1b1-df30-4c04-b0fc-c54b599552fc rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=c4482d6a-3f62-4191-98e8-70270b44cbbc loglevel=3
Desktop: KDE Plasma 5.24.3 tk: Qt 5.15.3 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: MAXIMUS VII FORMULA v: Rev 1.xx
serial: <superuser required> UEFI-[Legacy]: American Megatrends v: 2902
date: 08/27/2015
CPU:
Info: model: Intel Core i7-4790K bits: 64 type: MT MCP arch: Haswell
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3999 high: 4003 min/max: 800/4400 scaling:
driver: intel_cpufreq governor: performance cores: 1: 4000 2: 4000 3: 3994
4: 4000 5: 4000 6: 4001 7: 4001 8: 4003 bogomips: 63994
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GM204 [GeForce GTX 980] vendor: ASUSTeK driver: nvidia
v: 510.54 alternate: nouveau,nvidia_drm pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:13c0 class-ID: 0300
Device-2: Logitech HD Webcam C910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 3-3:6 chip-ID: 046d:0821
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 5760x1080 s-dpi: 92 s-size: 1590x301mm (62.6x11.9")
s-diag: 1618mm (63.7")
Monitor-1: DP-0 pos: primary,center res: 1920x1080 dpi: 92
size: 531x299mm (20.9x11.8") diag: 609mm (24")
Monitor-2: DP-2 pos: primary,left res: 1920x1080 dpi: 92
size: 531x299mm (20.9x11.8") diag: 609mm (24")
Monitor-3: DP-4 pos: right res: 1920x1080 dpi: 92
size: 531x299mm (20.9x11.8") diag: 609mm (24")
OpenGL: renderer: NVIDIA GeForce GTX 980/PCIe/SSE2 v: 4.6.0 NVIDIA 510.54
direct render: Yes
Audio:
Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
class-ID: 0403
Device-2: NVIDIA GM204 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403
Device-3: Creative Labs EMU20k2 [Sound Blaster X-Fi Titanium Series]
driver: snd_ctxfi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 0a:00.0 chip-ID: 1102:000b class-ID: 0403
Device-4: SteelSeries ApS Arctis Pro Wireless type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-10.3:12
chip-ID: 1038:1294 class-ID: 0300
Device-5: Logitech HD Webcam C910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 3-3:6 chip-ID: 046d:0821
class-ID: 0e02 serial: <filter>
Sound Server-1: ALSA v: k5.16.16-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: kernel
port: f020 bus-ID: 00:19.0 chip-ID: 8086:15a1 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Qualcomm Atheros AR93xx Wireless Network Adapter
vendor: D-Link System DWA-566 driver: ath9k v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 168c:0030
class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Drives:
Local Storage: total: 532.84 GiB used: 218.58 GiB (41.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 PRO 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1B6Q scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: OCZ model: VERTEX2 size: 55.9 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD
serial: <filter> rev: 1.37 scheme: GPT
Partition:
ID-1: / raw-size: 459.81 GiB size: 459.81 GiB (100.00%)
used: 218.58 GiB (47.5%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-2: /home raw-size: 459.81 GiB size: 459.81 GiB (100.00%)
used: 218.58 GiB (47.5%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-3: /var/log raw-size: 459.81 GiB size: 459.81 GiB (100.00%)
used: 218.58 GiB (47.5%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
ID-4: /var/tmp raw-size: 459.81 GiB size: 459.81 GiB (100.00%)
used: 218.58 GiB (47.5%) fs: btrfs dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.57 GiB used: 2 MiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 17.12 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 58 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 23%
Info:
Processes: 287 Uptime: 4m wakeups: 0 Memory: 15.57 GiB
used: 4.37 GiB (28.1%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1598 lib: 455 Shell: fish
v: 3.3.1 default: Zsh v: 5.8.1 running-in: konsole inxi: 3.3.13
Garuda (2.5.6-2):
System install date:     2022-01-06
Last full system update: 2022-03-23
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       <superuser required>
Snapshots:               Snapper
Failed units:            bluetooth-autoconnect.service

@Leetsch2002

Booting the lts kernel solved my issue timewise. It occured again later on.

That would make sense, as at some point the LTS kernel catches up.

Maybe you could try disabling the nmb.service (if you don't need it) from the zen kernel and try again with the linux-lts?

@filo I tried this, and after remove quiet and splash from the boot options in grub, it still looks like the boot process is getting stuck; I left it alone for a good 15 minutes, but it wouldn't continue.

That being said... I noticed that during all this (rebooting, grub, bios,...) my receiver was displaying the same behaviour. So to some point, my conclusion currently is that the kernel upgrade and my headphones having issues might be an unlucky coincidence of events. I think my headphones are probably just broken.

Try linux-xanmod-lts.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.