Blue Yeti Microphone needs replugging

Issues & Assistance
1

Hello all!

My Blue Yeti microphone requires to be replugged after every restart/suspend to function. It is always recognized by the system, but no input detected until I replug it. I have had this issues on other Linux Distros aswell, but I hope that over here somebody may have a solution.

The output of dmesg after suspending (with the microphone **not working)
**
[ 2614.089716] Disabling lock debugging due to kernel taint
[ 2614.089719] usbcore: deregistering interface driver snd-usb-audio
[ 2614.188509] usb 1-4: 1:1: cannot get freq at ep 0x81
[ 2614.190614] usb 1-4: 2:1: cannot get freq at ep 0x1
[ 2614.249776] usb 1-4: 1:1: cannot get freq at ep 0x81
[ 2614.552869] usbcore: registered new interface driver snd-usb-audio
[ 2633.075319] usbcore: deregistering interface driver snd-usb-audio
[ 2633.186775] usb 1-4: 1:1: cannot get freq at ep 0x81
[ 2633.188858] usb 1-4: 2:1: cannot get freq at ep 0x1
[ 2633.298505] usb 1-4: 1:1: cannot get freq at ep 0x81
[ 2633.543446] usbcore: registered new interface driver snd-usb-audio
[ 2886.543397] usb 1-7: USB disconnect, device number 8
[ 2886.824175] usb 1-7: new high-speed USB device number 9 using xhci_hcd
[ 2887.086739] usb 1-7: New USB device found, idVendor=046d, idProduct=0ab7, bcdDevice= 0.19
[ 2887.086743] usb 1-7: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[ 2887.086744] usb 1-7: Product: Blue Microphones
[ 2887.086745] usb 1-7: Manufacturer: Generic
[ 2887.086745] usb 1-7: SerialNumber: 2033BAB02YC8
[ 2887.235163] usb 1-7: 2:2: cannot set freq 48000 to ep 0x4
[ 2887.255165] usb 1-7: 19:0: failed to get current value for ch 0 (-22)
[ 2887.295162] usb 1-7: 19:0: cannot get min/max values for control 2 (id 19)
[ 2887.315163] usb 1-7: 25:0: failed to get current value for ch 0 (-22)
[ 2887.375160] usb 1-7: 35:0: failed to get current value for ch 0 (-22)
[ 2887.415161] usb 1-7: 35:0: cannot get min/max values for control 2 (id 35)
[ 2887.435161] usb 1-7: 22:0: failed to get current value for ch 0 (-22)
[ 2887.475161] usb 1-7: 22:0: cannot get min/max values for control 2 (id 22)
[ 2887.477352] usbhid 1-7:1.3: can’t add hid device: -71
[ 2887.477367] usbhid 1-7:1.3: probe with driver usbhid failed with error -71
[ 2887.477424] usb 1-7: USB disconnect, device number 9
[ 2890.001149] usb 1-7: new high-speed USB device number 10 using xhci_hcd
[ 2891.095195] usb 1-7: device descriptor read/64, error -71

Specs

System Details Report

Report details

  • Date generated: 2025-10-19 10:15:44

Hardware Information:

  • Hardware Model: Micro-Star International Co., Ltd. MEG Z490 Trident X MS-B926
  • Memory: 16.0 GiB
  • Processor: Intel® Core™ i7-10700K Ă— 16
  • Graphics: NVIDIA GeForce RTX™ 2080 SUPER
  • Disk Capacity: 3.0 TB

Software Information:

  • Firmware Version: C.10
  • OS Name: CachyOS
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 49
  • Windowing System: Wayland
  • Kernel Version: Linux 6.17.3-3-cachyos

Best Regards

Sebastian

2

If the microphone is not detected at the kernel level, it may be due to a missing firmware for a Renesas USB controller, which some Blue Yeti models use. In such cases, installing the upd72020x-fw package from the Arch User Repository (AUR) can resolve the issue.
This firmware is necessary for the USB controller to function properly.

For users experiencing the microphone not working until manually unplugged and replugged, a simple fix involves reloading the snd_usb_audio kernel module:

sudo rmmod snd_usb_audio -f
sudo modprobe snd_usb_audio

This command sequence can resolve the issue without requiring persistent boot scripts.

3

Thank you for your time and help! Unfortunately both, the firmware and the commands, dont fix the issue. I have read about sudo rmmod snd_usb_audio -f and sudo modprobe snd_usb_audio in the Arch forum and generally it seems to do nothing for many people, which I find strange, since it is essentially the same as manually replugging from what I can understand.

4

Did you try the firmware update as well?

What is the output of inxi -A or better inxi -F?

5

I do sudo pacman -Syu and yay -Syu once per day. Is anything else requiered?

Output of inxi -F:

System:
Host: Poseidon-Trident Kernel: 6.17.3-3-cachyos arch: x86_64 bits: 64
Desktop: GNOME v: 49.1 Distro: CachyOS
Machine:
Type: Desktop Mobo: Micro-Star model: MEG Z490I UNIFY (MS-7C77) v: 1.2
serial: UEFI: American Megatrends v: C.10
date: 05/04/2020
CPU:
Info: 8-core model: Intel Core i7-10700K bits: 64 type: MT MCP cache:
L2: 2 MiB
Speed (MHz): avg: 800 min/max: 800/5100 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
15: 800 16: 800
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630] driver: i915 v: kernel
Device-2: NVIDIA TU104 [GeForce RTX 2080 SUPER] driver: nvidia
v: 580.95.05
Display: wayland server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
compositor: gnome-shell driver: gpu: nv_platform,nvidia,nvidia-nvswitch
resolution: 1920x1080~144Hz
API: EGL v: 1.5 drivers: iris,nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.95.05
renderer: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2
API: Vulkan v: 1.4.328 drivers: nvidia,llvmpipe surfaces: N/A
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
gpu: nvidia-settings,nvidia-smi x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Comet Lake PCH cAVS driver: snd_hda_intel
Device-2: NVIDIA TU104 HD Audio driver: snd_hda_intel
Device-3: Kingston HyperX 7.1 Audio
driver: hid-generic,snd-usb-audio,usbhid type: USB
Device-4: Logitech Blue Microphones
driver: hid-generic,snd-usb-audio,usbhid type: USB
API: ALSA v: k6.17.3-3-cachyos status: kernel-api
Server-1: PipeWire v: 1.4.9 status: active
Network:
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi
IF: wlan0 state: down mac: 36:5a:c6:23:3e:c8
Device-2: Realtek RTL8125 2.5GbE driver: r8169
IF: enp59s0 state: up speed: 1000 Mbps duplex: full mac: 2c:f0:5d:35:bb:ce
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb type: USB
Report: btmgmt ID: hci0 state: up address: 40:EC:99:0D:DA:35 bt-v: 5.2
Drives:
Local Storage: total: 2.75 TiB used: 399.37 GiB (14.2%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: PC SN730
SDBPNTY-1T00-1032 size: 953.87 GiB
ID-2: /dev/sda vendor: Samsung model: SSD 870 EVO 2TB size: 1.82 TiB
Partition:
ID-1: / size: 1.82 TiB used: 149.45 GiB (8.0%) fs: btrfs dev: /dev/sda2
ID-2: /boot/efi size: 299.4 MiB used: 636 KiB (0.2%) fs: vfat
dev: /dev/sda1
ID-3: /home size: 1.82 TiB used: 149.45 GiB (8.0%) fs: btrfs
dev: /dev/sda2
ID-4: /var/log size: 1.82 TiB used: 149.45 GiB (8.0%) fs: btrfs
dev: /dev/sda2
ID-5: /var/tmp size: 1.82 TiB used: 149.45 GiB (8.0%) fs: btrfs
dev: /dev/sda2
Swap:
ID-1: swap-1 type: zram size: 15.45 GiB used: 8.2 MiB (0.1%) dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.0 C pch: 69.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.45 GiB used: 5.11 GiB (33.1%)
Processes: 447 Uptime: 5h 21m Shell: fish inxi: 3.3.39

6

Yep. Paru or yay -S upd72020x-fw

See AUR (en) - upd72020x-fw

Unfortunately I cannot see something special in your systems details.
There is only one thing you can try in addition. Restart COS and choose the LTS Kernel in the advanced Menu of CachyOS.

If the problem still presists, somebody else may handle your case with better care.

7

Alright, I already installed the firmware after your first response. Sorry, should’ve stated it more clearly.

I tried the LTS Kernel, but it still doesn’t work, unfortunately. Maybe an update of the firmware will fix it, since the version now available in the AUR dates to 2025-05-25, which of course is a while back. In the meantime I will have to continue to replug.

But still, thank you so much for your time and effort! It’s really appreciated. People like you help to make Linux more accessible to new users.

8

Same for me. However, I also have this problem on Ubuntu, so it’s not a CachyOS-specific issue. I still don’t have a solution for this.

9

I also have a Blue Yeti microphone but mine works just fine. Not very helpful but I thought I chip it in.

10

So it turns out to be the usual logitech firmware thing. One can try Blue Sherpa or G Hub for updates. :smiley:
You are lucky, a logitech mouse would have lead into serious system errors making any linux gui unusable.

For early adoptors: There is no chance of getting a new firmware. So heading for a new mic would be the easiest solution.

11

Hello,

I have exactly the same issue with my blue yeti.

inxi -A
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio
driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
driver: snd_hda_intel
Device-3: Logitech Blue Microphones
driver: hid-generic,snd-usb-audio,usbhid type: USB
API: ALSA v: k7.0.0-rc7-2-cachyos-rc status: kernel-api
Server-1: PipeWire v: 1.6.3 status: active

12

Hi all!

Same issue here with me and I haven’t found a fix for it even in this thread

Here’s my inxi -A output

inxi -A 
Audio:
   Device-1: NVIDIA GB203 High Definition Audio driver: snd_hda_intel 
   Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
     driver: snd_hda_intel
   Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
     driver: snd_hda_intel
   Device-4: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
     type: USB
   Device-5: Logitech Blue Microphones
     driver: hid-generic,snd-usb-audio,usbhid type: USB
   API: ALSA v: k6.19.12-1-cachyos status: kernel-api
   Server-1: PipeWire v: 1.6.3 status: active
13

The issue is gone, I don’t need to unplug/replug my mic now :

inxi -A
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 HDMI/DP Audio
driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
driver: snd_hda_intel
Device-3: Logitech Blue Microphones
driver: hid-generic,snd-usb-audio,usbhid type: USB
API: ALSA v: k7.0.12-1-cachyos status: kernel-api
Server-1: PipeWire v: 1.6.7 status: active