public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.
Date: Fri, 09 Jan 2026 23:35:54 +0000	[thread overview]
Message-ID: <bug-220238-208809-rSALd1JnW7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220238-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220238

faaris (faaris.ansari@proton.me) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |faaris.ansari@proton.me

--- Comment #16 from faaris (faaris.ansari@proton.me) ---
I can confirm that this bug is still happening on kernel version 6.18.3. My
motherboard does actually have the options for ErP Ready, which by other
reports online should work around the problem, however even with this option I
still require a hotplug to get the microphone up and running again.

On my end, the mic works perfectly when I first boot my computer. It only stops
working and requires the hotplug after a reboot, or wake from suspend.

I've attempted using `usbreset` on the device, which didn't seem to bring it
back to life. Only physically unplugging it and plugging it back in has gotten
it up and running for me.

I've tried the microphone on Windows, where it works great through sleep cycles
and reboots.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-01-09 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:45 [Bug 220238] New: Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot bugzilla-daemon
2025-06-17  5:32 ` [Bug 220238] " bugzilla-daemon
2025-06-23  9:07 ` bugzilla-daemon
2025-06-23  9:29 ` bugzilla-daemon
2025-06-23  9:36 ` bugzilla-daemon
2025-06-23  9:42 ` bugzilla-daemon
2025-06-23 10:03 ` bugzilla-daemon
2025-06-23 10:40   ` Oliver Neukum
2025-06-23 10:40 ` bugzilla-daemon
2025-06-23 11:23 ` bugzilla-daemon
2025-06-23 11:24 ` bugzilla-daemon
2025-07-02  3:39 ` bugzilla-daemon
2025-07-21  8:39 ` bugzilla-daemon
2025-07-21 16:32 ` bugzilla-daemon
2025-07-26 23:17 ` bugzilla-daemon
2025-12-26 14:09 ` bugzilla-daemon
2025-12-26 14:09 ` bugzilla-daemon
2026-01-09 23:35 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-220238-208809-rSALd1JnW7@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox