You are not logged in.

Pages: 1

#1 2020-10-15 09:13:41

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

[Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

Hello all whom click on this post.
I have confirmed this microphone works flawlessly within Windows 10.
I have only usb 3.0, 3.1 available.

Currently installed in the rear Audio IO:
1. 2.1 Channel Speaker plugged into Line out (green 3.5mm)
2. Headphones plugged into dac/amp, plugged into optical.
3. Microphone connected via rear usb.

output for "arecord -l"

**** List of CAPTURE Hardware Devices ****
card 1: Generic [HD-Audio Generic], device 0: ALC1220 Analog [ALC1220 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 2: ALC1220 Alt Analog [ALC1220 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Output of "pacmd list-sources | grep -e device.string -e 'name: ' "

name: <alsa_output.pci-0000_0c_00.4.iec958-stereo.monitor>
		device.string = "1"

Via following https://wiki.archlinux.org/index.php/Pu … PulseAudio

From "/etc/pulse/default.pa"

# This line should allow usb microphone to work
#load-module module-alsa-source device=hw:1,0
#else this should
#load-module module-alsa-source device=hw:1,2

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif

When commenting out hw:1,0

 pulseaudio -k

Returns no audio via optical out.

pulseaudio -D
E: [pulseaudio] main.c: Daemon startup failed.

Identical results when repeating the same steps for the other device.

I am unsure at to what to do. I've searched for methods with setting up usb microphones but have found no luck.
Any help is appreciated!

Kind Regards,
Boogz

Last edited by Boogz_Linux (2020-10-15 11:25:38)

Offline

#2 2020-10-15 09:28:16

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,863

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

Your usb mic is not detected on a kernel level, you can stop trying anything in pulseaudio until you have a listing in arecord -l

post 

pacman -Q linux
uname -a
sudo fuser -v /dev/snd/*
dmesg | grep snd

while the mic should be plugged

Do you have any modprobe config regarding sound modules? Post them if so.

Last edited by V1del (2020-10-15 09:28:52)

Offline

#3 2020-10-15 09:34:21

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

$ pacman -Q lnux
linux 5.8.14.arch1-1
$ uname -a 
Linux turing(very_original_i_know) 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux
$ sudo fuser -v /dev/snd/*                                                                                                                                       ✔ 
                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  username   4015 F.... pulseaudio
/dev/snd/controlC1:  username   4015 F.... pulseaudio
/dev/snd/pcmC1D1p:   username   4015 F...m pulseaudio
/dev/snd/timer:      username   4015 f.... pulseaudio
$ dmesg | grep snd                                                                                                                                                                                                                                                                                                                           ✔ 
[    1.484795] snd_hda_intel 0000:0a:00.1: enabling device (0000 -> 0002)
[    1.484866] snd_hda_intel 0000:0a:00.1: Disabling MSI
[    1.484875] snd_hda_intel 0000:0a:00.1: Handle vga_switcheroo audio client
[    1.484964] snd_hda_intel 0000:0c:00.4: enabling device (0000 -> 0002)
[    1.504293] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC1220: line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[    1.504295] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    1.504296] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    1.504297] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    1.504297] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0
[    1.504298] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    1.504299] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
[    1.504300] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
[    1.504301] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
[  116.863511] snd_hda_intel 0000:0c:00.4: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.

Last edited by Boogz_Linux (2020-10-15 09:53:01)

Offline

#4 2020-10-15 09:52:37

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

The only modprobe configs I have made:

blakclist ucsi_ccg
blacklist sp5100-tco

Both in seperate .conf files.

Offline

#5 2020-10-15 10:04:51

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,863

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

No indication of a usb sound module...

Is the port/mic/usb controller detected at all? 

lspci
lsusb -t
sudo lsusb -v -d$vendorId:$productId #Replace with the appropriate numbers that should show up in lsusb of the mic if it is present

slight suspicion of a Renesas controller - if it is a renesas controller you'll need: https://aur.archlinux.org/packages/upd72020x-fw/ to make it usable

Last edited by V1del (2020-10-15 10:07:32)

Offline

#6 2020-10-15 10:08:36

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

$lspci                                                                                                                                                                                                                                                                                                                                      ✔ 
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
05:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0a:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)
0a:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1)
0a:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1)
0a:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C UCSI Controller (rev a1)
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
0c:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0c:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0e:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
$ lsusb                                                                                                                                                                                                                                                                                                                                      ✔ 
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 04b4:0510 Cypress Semiconductor Corp. HID Keyboard
Bus 007 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Doesn't seem as though mic is present among this list.

Edit: Just installed from the link provided, will reboot and see what happens.

Last edited by Boogz_Linux (2020-10-15 10:11:09)

Offline

#7 2020-10-15 10:13:00

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,863

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

Are any of these devices from that same USB port/controller? Can you change the port  the headset is in?

Edit: It's not looking like a renesas controller is there so it's unlikely to help, maybe post a complete ungrepped dmesg, are there any failures initialising a certain USB device?

Last edited by V1del (2020-10-15 10:14:29)

Offline

#8 2020-10-15 10:20:05

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

Not too sure as to how I can do this nicely due to my 'newness' to arch/linux and the forums, but here's a shot.

Edit: I figured it out
https://pastebin.com/uNuEgd6q

Not sure if this is useful.

$systemctl --failed                                                        ✔ 
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
$journalctl -p 3 -xb                                                       ✔ 
-- Logs begin at Thu 2020-07-30 22:50:49 AEST, end at Fri 2020-10-16 04:09:37 AEDT>
-- No entries --

Edit: I've moved the usb from USB 3.1, reboot, USB 3.0. It's now plugged directly into the motherboard usb port (ASUS x570-F)

Last edited by Boogz_Linux (2020-10-15 11:01:42)

Offline

#9 2020-10-15 10:28:40

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

I noticed I sent the output for the wrong command, not sure if you edited it/

 lsusb -t                                                                                                                                                       ✔ 
/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 4: Dev 6, If 0, Class=Imaging, Driver=, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 4: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 4: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M

Offline

#10 2020-10-15 11:04:46

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,863

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

It's not really an issue that you posted the other command, the -t is just for a bit of visual fluff.

systemctl --failed is irrelevant here, journal output might be useful (but without the p3 lots of useful messages aren't necessarily errors and without the -x , that's just useless noise most of the time)

Im not seing anything related to the mic in the slightest... is it on, does it have a hardware on/off button ? Do you get any output at all when (un-)plugging and having a 

dmesg -w

running?

If that's not the case then you seem to have quite a weird usb controller here, maybe check in windows in e.g. the device manager or so what the actual USB controller device is into which you are plugging into.

FWIW have you tried without your blacklist (sp5100-tco is probably not related, but ucsi_ccg is definitely a usb type-c controller driver and you might have a weird internal wiring where the normal usb ports go through that, why do you have that blacklist in the first place?)

Last edited by V1del (2020-10-15 11:08:27)

Offline

#11 2020-10-15 11:17:35

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

So, ucsi_ccg was blacklisted with an ignorance to read man pages and an appetite for a random up voted solution to an error from journalctl. I've commented out the blacklist, rebooted.

dmesg -w
https://pastebin.com/ZuUxBGjT

journalctl -b
https://pastebin.com/WGF791mv

Edit: The microphone has a green led to show it's receiving power. All is good there.

Last edited by Boogz_Linux (2020-10-15 11:19:12)

Offline

#12 2020-10-15 11:26:37

Boogz_Linux
Member
Registered: 2020-06-19
Posts: 29

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

So, went to windows, all was well. Booted into linux, lsusb -> it now shows. I'm not entirely sure as to why. Thank you for the help non the less.

Offline

#13 2020-10-15 11:28:14

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 22,863

Re: [Solved]*Answer bot apparent -Blue Yeti Nano unable to recognise

I'd not expect dmesg -w to be the entire dmesg again (maybe I'm also just dumb and looking up the manpage it appears -W would be more in line with what I meant to have) In any case no change here, there's no mention of a mic in any shape or form.

Check on Windows, what's the USB controller that the mic is connected to be? Afaik device manager in system settings should give some information here

Edit: Hmm? Sounds like buggy firmware, ensure Windows fast boot is disabled/update your UEFI.

Last edited by V1del (2020-10-15 11:33:19)

Offline

Pages: 1

Board footer

Powered by FluxBB