


























I have an JMTek, LLC. UM10 Mic, it is shown in lsusb,
inxi -SA shows this as an audio device as follows:
Device-4: JMTek LLC. UM10 driver: hid-generic,usbhid type: USB
It is not shown in pavucontrol either in input devices or configuration. Has this got the wrong driver i.e. my system is only seeing the mic button and not the audio input?
Any ideas how to get around this?
@ This post is ai generated - your system is currently only recognizing the Human Interface Device (HID) portion of the microphone.
Many USB microphones have two interfaces: one for the actual audio stream, and one for the physical buttons (like a hardware mute switch). Right now, the hid-generic and usbhid drivers are handling the buttons, but the driver responsible for the audio input—snd-usb-audio—is entirely missing from your inxi output.
Normally, a healthy USB mic output in inxi looks like this: driver: hid-generic,snd-usb-audio,usbhid.
Here is how you can force the system to see the audio interface.
It’s highly likely the snd-usb-audio kernel module simply didn’t load, or it was masked. You can force it to load manually.
Open your terminal and run:
Bash
sudo modprobe snd-usb-audio
Once the module is loaded, unplug the UM10 microphone and plug it back in so the system initializes it with the new driver available.
Run your inxi command again:
Bash
inxi -SA
Check if snd-usb-audio now appears in the driver list for the UM10. If it does, open pavucontrol and it should now be sitting in your Input Devices tab.
If snd-usb-audio still refuses to attach after manually loading it, the kernel might be rejecting the audio interface. Unplug the mic, plug it back in, and immediately run this command to read the kernel logs:
Bash
sudo dmesg | tail -n 20
Look for any red or error text regarding USB or audio. Sometimes, plugging the mic into a different USB port (especially a direct motherboard port rather than a hub) resolves weird interface handshake issues!
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。