[Bug 220238] New: Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[Bug 220238] New: Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

            Bug ID: 220238
           Summary: Blue Yeti microphone doesn't consistently work after
                    unplugging and plugging back in or reboot.
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: fewspotty@protonmail.com
        Regression: No

Arch Linux

Bus 001 Device 018: ID 046d:0ab1 Logitech, Inc. Yeti Nano

When my Blue Yeti microphone is unplugged it won't work again until I reboot.
After I reboot, sometimes it works, sometimes it doesn't. Sometimes unplugging
and replugging fixes it after reboot, but if I unplug it while it's working it
won't work again no matter what until I reboot. Although it will still be
listed under lsusb, it won't work or be listed in pavucontrol. I have asked
others with Blue Yeti microphones, and they have confirmed this as an issue as
of right now.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #1 from Ryan Walker (fewspotty@protonmail.com) ---
After tinkering I found I don't have to reboot, I just have to keep unplugging
and replugging the mic and after an average of 10 plugs it will work. It should
just work every time it's plugged in.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

Ryan Walker (fewspotty@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |IMPLEMENTED

--- Comment #2 from Ryan Walker (fewspotty@protonmail.com) ---
SOLUTION: I figured out if I plug the Blue Yeti microphone into a usb-a hub
dongle, it will work every time. It only doesn't work 90% of the time when it
is plugged into a usb port directly no matter what usb-a port I use for some
reason. I use an onn usb 2.0 travel hub S/N: 11B35351.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

Oliver Neukum (oliver@neukum.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oliver@neukum.org

--- Comment #3 from Oliver Neukum (oliver@neukum.org) ---
It is good that you have found a work around. But you were right. This is
supposed to work.

Could you please post dmesg of working and non-working cases?

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #4 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to Oliver Neukum from comment #3)
> It is good that you have found a work around. But you were right. This is
> supposed to work.
> 
> Could you please post dmesg of working and non-working cases?

Yeah, I'll email you it right now.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #5 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to Oliver Neukum from comment #3)
> It is good that you have found a work around. But you were right. This is
> supposed to work.
> 
> Could you please post dmesg of working and non-working cases?

Not working state:

❯ sudo dmesg
[ 3060.495262] usb 1-8: new full-speed USB device number 43 using xhci_hcd
[ 3060.620074] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 3060.620089] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 3060.620093] usb 1-8: Product: Yeti Nano
[ 3060.620097] usb 1-8: Manufacturer: Blue Microphones
[ 3060.620101] usb 1-8: SerialNumber: 8832D12120041006
[ 3065.850153] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1

~
❯

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to Oliver Neukum from comment #3)
> It is good that you have found a work around. But you were right. This is
> supposed to work.
> 
> Could you please post dmesg of working and non-working cases?

I emailed you the working state to you directly because it had a MAC address in
it.

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

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

Re: [Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[Oliver Neukum]

On 23.06.25 12:03, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220238
> 
> --- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
> (In reply to Oliver Neukum from comment #3)
>> It is good that you have found a work around. But you were right. This is
>> supposed to work.
>>
>> Could you please post dmesg of working and non-working cases?
> 
> I emailed you the working state to you directly because it had a MAC address in
> it.
> 

Hi,

are you referring to SerialNumber?
You could set it to XXX and indicate that you've done so for privacy reasons
in the public report.

	Regards
		Oliver

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #7 from oneukum@suse.com ---
On 23.06.25 12:03, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220238
> 
> --- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
> (In reply to Oliver Neukum from comment #3)
>> It is good that you have found a work around. But you were right. This is
>> supposed to work.
>>
>> Could you please post dmesg of working and non-working cases?
> 
> I emailed you the working state to you directly because it had a MAC address
> in
> it.
> 

Hi,

are you referring to SerialNumber?
You could set it to XXX and indicate that you've done so for privacy reasons
in the public report.

        Regards
                Oliver

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #8 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to oneukum from comment #7)
> On 23.06.25 12:03, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=220238
> > 
> > --- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
> > (In reply to Oliver Neukum from comment #3)
> >> It is good that you have found a work around. But you were right. This is
> >> supposed to work.
> >>
> >> Could you please post dmesg of working and non-working cases?
> > 
> > I emailed you the working state to you directly because it had a MAC
> address
> > in
> > it.
> > 
> 
> Hi,
> 
> are you referring to SerialNumber?
> You could set it to XXX and indicate that you've done so for privacy reasons
> in the public report.
> 
>       Regards
>               Oliver


Working state (plugged into USB hub):

❯ sudo dmesg
[ 3214.932134] [UFW BLOCK] IN=enp5s0 OUT=
MAC=XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX SRC=192.168.1.254 DST=224.0.0.1
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=36631 DF PROTO=2
[ 3221.407072] usb 1-8: USB disconnect, device number 44
[ 3221.407088] usb 1-8.3: USB disconnect, device number 45
[ 3221.407640] usb 1-8.4: cannot submit urb (err = -19)
[ 3221.411804] usb 1-8.4: cannot submit urb 0, error -19: no device
[ 3221.415127] usb 1-8.4: USB disconnect, device number 46
[ 3226.902448] usb 1-8: new high-speed USB device number 47 using xhci_hcd
[ 3227.026852] usb 1-8: New USB device found, idVendor=05e3, idProduct=0608,
bcdDevice=77.64
[ 3227.026866] usb 1-8: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[ 3227.026871] usb 1-8: Product: USB2.0 Hub
[ 3227.028627] hub 1-8:1.0: USB hub found
[ 3227.028887] hub 1-8:1.0: 4 ports detected
[ 3227.301471] usb 1-8.3: new full-speed USB device number 48 using xhci_hcd
[ 3227.375737] usb 1-8.3: New USB device found, idVendor=0b05, idProduct=190e,
bcdDevice= 2.00
[ 3227.375751] usb 1-8.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 3227.375756] usb 1-8.3: Product: ASUS USB-BT500
[ 3227.375760] usb 1-8.3: Manufacturer: Realtek
[ 3227.375764] usb 1-8.3: SerialNumber: 00E04C239987
[ 3227.387660] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b
lmp_ver=0a lmp_subver=8761
[ 3227.388677] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 3227.388691] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 3227.389462] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 3227.389586] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[ 3227.449367] usb 1-8.4: new full-speed USB device number 49 using xhci_hcd
[ 3227.526584] usb 1-8.4: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 3227.526600] usb 1-8.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 3227.526605] usb 1-8.4: Product: Yeti Nano
[ 3227.526609] usb 1-8.4: Manufacturer: Blue Microphones
[ 3227.526612] usb 1-8.4: SerialNumber: 8832D12120041006
[ 3227.537606] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[ 3227.604751] Bluetooth: MGMT ver 1.23
[ 3227.625515] input: Blue Microphones Yeti Nano Consumer Control as
/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.4/1-8.4:1.3/0003:046D:0AB1.0020/input/input117
[ 3227.676525] input: Blue Microphones Yeti Nano as
/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.4/1-8.4:1.3/0003:046D:0AB1.0020/input/input118
[ 3227.676580] hid-generic 0003:046D:0AB1.0020: input,hiddev99,hidraw8: USB HID
v1.11 Device [Blue Microphones Yeti Nano] on usb-0000:00:14.0-8.4/input3

~
❯

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #9 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to oneukum from comment #7)
> On 23.06.25 12:03, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=220238
> > 
> > --- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
> > (In reply to Oliver Neukum from comment #3)
> >> It is good that you have found a work around. But you were right. This is
> >> supposed to work.
> >>
> >> Could you please post dmesg of working and non-working cases?
> > 
> > I emailed you the working state to you directly because it had a MAC
> address
> > in
> > it.
> > 
> 
> Hi,
> 
> are you referring to SerialNumber?
> You could set it to XXX and indicate that you've done so for privacy reasons
> in the public report.
> 
>       Regards
>               Oliver




dmesg without the USB-A hub. The Blue Yeti mic is plugged directly into a USB-A
port and I unplugged and replugged a few times until it worked. It never works
the first time I plug it in directly. It always takes 3 or more tries plugging
it in.


sudo dmesg[ 4759.516762] usb 1-8: 6:0: failed to get current value for ch 0
(-110)
[ 4763.088699] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4763.108700] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4763.148698] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4763.149851] usbhid 1-8:1.3: can't add hid device: -71
[ 4763.149919] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4763.149966] usb 1-8: USB disconnect, device number 50
[ 4765.038713] usb 1-8: new full-speed USB device number 51 using xhci_hcd
[ 4765.163423] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4765.163436] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4765.163439] usb 1-8: Product: Yeti Nano
[ 4765.163442] usb 1-8: Manufacturer: Blue Microphones
[ 4765.163445] usb 1-8: SerialNumber: 8832D12120041006
[ 4767.856621] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1
[ 4767.859615] usb 1-8: 2:1: cannot set freq 48000 to ep 0x82
[ 4767.879616] usb 1-8: 6:0: failed to get current value for ch 0 (-22)
[ 4767.919637] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4767.939614] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4767.979614] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4767.980733] usbhid 1-8:1.3: can't add hid device: -71
[ 4767.980848] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4767.981031] usb 1-8: USB disconnect, device number 51
[ 4769.045676] usb 1-8: new full-speed USB device number 52 using xhci_hcd
[ 4769.170532] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4769.170542] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4769.170544] usb 1-8: Product: Yeti Nano
[ 4769.170547] usb 1-8: Manufacturer: Blue Microphones
[ 4769.170549] usb 1-8: SerialNumber: 8832D12120041006
[ 4770.241646] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1
[ 4770.245590] usb 1-8: 2:1: cannot set freq 48000 to ep 0x82
[ 4770.265595] usb 1-8: 6:0: failed to get current value for ch 0 (-22)
[ 4770.305574] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4770.325584] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4770.365572] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4770.366662] usbhid 1-8:1.3: can't add hid device: -71
[ 4770.366710] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4770.366763] usb 1-8: USB disconnect, device number 52
[ 4780.470461] usb 1-8: new full-speed USB device number 53 using xhci_hcd
[ 4780.595225] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4780.595240] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4780.595245] usb 1-8: Product: Yeti Nano
[ 4780.595249] usb 1-8: Manufacturer: Blue Microphones
[ 4780.595253] usb 1-8: SerialNumber: 8832D12120041006
[ 4782.501428] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1
[ 4782.504377] usb 1-8: 2:1: cannot set freq 48000 to ep 0x82
[ 4782.524372] usb 1-8: 6:0: failed to get current value for ch 0 (-22)
[ 4782.564364] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4782.584473] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4782.624438] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4782.625659] usbhid 1-8:1.3: can't add hid device: -71
[ 4782.625709] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4782.625746] usb 1-8: USB disconnect, device number 53
[ 4783.217486] usb 1-8: new full-speed USB device number 54 using xhci_hcd
[ 4783.342170] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4783.342185] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4783.342190] usb 1-8: Product: Yeti Nano
[ 4783.342194] usb 1-8: Manufacturer: Blue Microphones
[ 4783.342198] usb 1-8: SerialNumber: 8832D12120041006
[ 4783.988415] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1
[ 4783.992172] usb 1-8: 2:1: cannot set freq 48000 to ep 0x82
[ 4784.012333] usb 1-8: 6:0: failed to get current value for ch 0 (-22)
[ 4784.054333] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4784.074333] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4784.114332] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4784.115555] usbhid 1-8:1.3: can't add hid device: -71
[ 4784.115605] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4784.115643] usb 1-8: USB disconnect, device number 54
[ 4784.627368] usb 1-8: new full-speed USB device number 55 using xhci_hcd
[ 4784.752357] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4784.752375] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4784.752384] usb 1-8: Product: Yeti Nano
[ 4784.752391] usb 1-8: Manufacturer: Blue Microphones
[ 4784.752397] usb 1-8: SerialNumber: 8832D12120041006
[ 4785.516321] usb 1-8: 1:1: cannot set freq 48000 to ep 0x1
[ 4785.519319] usb 1-8: 2:1: cannot set freq 48000 to ep 0x82
[ 4785.539308] usb 1-8: 6:0: failed to get current value for ch 0 (-22)
[ 4785.578316] usb 1-8: 6:0: cannot get min/max values for control 2 (id 6)
[ 4785.598424] usb 1-8: 5:0: failed to get current value for ch 0 (-22)
[ 4785.638307] usb 1-8: 5:0: cannot get min/max values for control 2 (id 5)
[ 4785.639440] usbhid 1-8:1.3: can't add hid device: -71
[ 4785.639455] usbhid 1-8:1.3: probe with driver usbhid failed with error -71
[ 4785.639499] usb 1-8: USB disconnect, device number 55
[ 4786.080400] usb 1-8: new full-speed USB device number 56 using xhci_hcd
[ 4786.205344] usb 1-8: New USB device found, idVendor=046d, idProduct=0ab1,
bcdDevice= 4.0a
[ 4786.205359] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4786.205363] usb 1-8: Product: Yeti Nano
[ 4786.205367] usb 1-8: Manufacturer: Blue Microphones
[ 4786.205371] usb 1-8: SerialNumber: 8832D12120041006
[ 4786.302696] input: Blue Microphones Yeti Nano Consumer Control as
/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.3/0003:046D:0AB1.0021/input/input122
[ 4786.354610] input: Blue Microphones Yeti Nano as
/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.3/0003:046D:0AB1.0021/input/input123
[ 4786.354802] hid-generic 0003:046D:0AB1.0021: input,hiddev99,hidraw8: USB HID
v1.11 Device [Blue Microphones Yeti Nano] on usb-0000:00:14.0-8/input3

~

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #10 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to oneukum from comment #7)
> On 23.06.25 12:03, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=220238
> > 
> > --- Comment #6 from Ryan Walker (fewspotty@protonmail.com) ---
> > (In reply to Oliver Neukum from comment #3)
> >> It is good that you have found a work around. But you were right. This is
> >> supposed to work.
> >>
> >> Could you please post dmesg of working and non-working cases?
> > 
> > I emailed you the working state to you directly because it had a MAC
> address
> > in
> > it.
> > 
> 
> Hi,
> 
> are you referring to SerialNumber?
> You could set it to XXX and indicate that you've done so for privacy reasons
> in the public report.
> 
>       Regards
>               Oliver

Just curious, did my ticket get looked at and end up helping with fixing the
bug at all? Thanks

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #11 from Oliver Neukum (oliver@neukum.org) ---
The bug is marked resolved. Do you still get the issue with the latest kernel?

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

Ryan Walker (fewspotty@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|IMPLEMENTED                 |---

--- Comment #12 from Ryan Walker (fewspotty@protonmail.com) ---
(In reply to Oliver Neukum from comment #11)
> The bug is marked resolved. Do you still get the issue with the latest
> kernel?

I'm on Linux kernel 6.15.7, and my Blue Yeti microphone still doesn't work if
it's not plugged into a USB hub.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #13 from Ryan Walker (fewspotty@protonmail.com) ---
Is the issue resolved in the release candidate? I still get the issue.

On Mon, Jul 21, 2025 at 3:39 AM, <[bugzilla-daemon@kernel.org](mailto:On Mon,
Jul 21, 2025 at 3:39 AM,  <<a href=)> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=220238
>
> --- Comment #11 from Oliver Neukum (oliver@neukum.org) ---
> The bug is marked resolved. Do you still get the issue with the latest
> kernel?
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You reported the bug.

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

kernel.exact088@passmail.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel.exact088@passmail.ne
                   |                            |t

--- Comment #14 from kernel.exact088@passmail.net ---
I'm experiencing the same issue with the Blue Yeti (046d:0ab7) on kernel
6.17.12-300.fc43.x86_64 (Framework Laptop 16, AMD Ryzen 9 7940HS).
In my case, the mic works fine until suspend/resume. After resume:

Device enumerates correctly (no errors in dmesg)
ALSA can open the device
Recording fails with: arecord: pcm_read:2279: read error: Input/output error
sox shows 0 samples read, amplitude 0.000000

Physical replug restores functionality. USB unbind/rebind, usbreset, and
USB_QUIRK_RESET_RESUME do not fix it.
This appears related to Bug 215219 which reports the same device ID with
similar symptoms.
Attaching diagnostic data (dmesg, lsusb -v, sox analysis of working vs broken
state).

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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

--- Comment #15 from kernel.exact088@passmail.net ---
Created attachment 309086
  --> https://bugzilla.kernel.org/attachment.cgi?id=309086&action=edit
Diagnostic data: dmesg, lsusb, sox analysis

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

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

[Bug 220238] Blue Yeti microphone doesn't consistently work after unplugging and plugging back in or reboot.

[bugzilla-daemon]

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.