I have a 7artisans RX wireless microphone that comes with multiple adapters. When I connect the microphone to my Rocky Linux system using a USB adapter, the OS does not recognize it. However, when I use the 3.5mm jack, the microphone works but produces a humming noise. I had hoped that using a USB connection would eliminate this noise.
Micro with usb connection works perfectly fine on Windows systems.
tail -f /var/log/messages
Plug in the microphone.
Post what comes up.
Here are the results:
Feb 14 16:24:27 peptides kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 4 bytes away.
Feb 14 16:24:40 peptides kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 5 bytes away.
Feb 14 16:24:40 peptides gnome-shell[2566]: libinput error: event5 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded.
Feb 14 16:24:40 peptides gnome-shell[2566]: See https://wayland.freedesktop.org/libinput/doc/1.19.3/touchpad-jumping-cursors.html for details
Feb 14 16:24:40 peptides gnome-shell[2566]: libinput error: event5 - SynPS/2 Synaptics TouchPad: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
Feb 14 16:24:57 peptides kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 5 bytes away.
Feb 14 16:24:58 peptides systemd[1]: Starting Fingerprint Authentication Daemon...
Feb 14 16:24:58 peptides systemd[1]: Started Fingerprint Authentication Daemon.
Feb 14 16:25:28 peptides systemd[1]: fprintd.service: Deactivated successfully.
Feb 14 16:26:36 peptides kernel: psmouse serio2: TouchPad at isa0060/serio2/input0 lost synchronization, throwing 4 bytes away.
Correct me if I’m wrong, but that doesn’t look to me like you started the:
tail -f /var/log/messages
PRIOR to plugging in your USB for your microphone. Every message there is for the touchpad. Yes?
If so, unplug the USB microphone. Then start the tail command, and THEN, plugin the microphone and look at the end of the output and copy and paste that here. If it is identical, then either your USB port doesn’t recognize your microphone as a device at all, or the USB port is not functioning? If should come up wwith something related to the microphone in /var/log/messages.
1 Like
The word “microphone” might be a bit misleading here. Does it mean there’s a wireless microphone (no cable) and it transmits to a control box, and then the control box is the thing that connects to the PC using 3.5mm or USB? If so, it’s the control box spec that’s important, for example it might present the signal as a line-out, as opposed to a tradtional microphone. e.g. it could be mono or split stereo, or real stereo.
Yeah, right. I tried to plug in to different USB ports, and it shows nothing but:
Feb 15 10:34:22 peptides gnome-shell[2614]: See https://wayland.freedesktop.org/libinput/doc/1.19.3/touchpad-jumping-cursors.html for details
Feb 15 10:34:27 peptides systemd[1]: packagekit.service: Deactivated successfully.
Feb 15 10:34:27 peptides systemd[1]: packagekit.service: Consumed 29.604s CPU time.
But if I try jack port instead, it prints this log:
Feb 15 10:35:28 peptides gsd-media-keys[2820]: Unable to get default source
Yes, you’re right. It doesn’t connect to the microphone itself, it connects to the receiver that gets wireless signals from mic.
The display shows these specs:
Try installing usbutils package:
dnf install usbutils
and then do:
lsusb
to see if it shows the device, most likely it won’t if you are not seeing dmesg output, but worth looking at. You can also get more info from that command by adding verbose parameter so:
lsusb -v
1 Like
Yes, I’ve checked this. I tried to use lsusb with and without the receiver, it shows the same results:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
I plugged a flash drive in, it’s identified as device 004:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 5986:066d Bison Electronics Inc. BisonCam, NB Pro
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 004: ID 1221:3234 Unknown manufacturer Disk (Thumb drive)
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Maybe try turning down the input volume within Rocky’s sound settings. For example:
if that then works, just use it over the 3.5mm jack.
Okey, I’ll try it later and tell about it
Okay, I tried turning down. This solution is not ideal, the noise is still heard, but it works.
If your microphone has its own power supply, you might have a situation called “ground loop”. There are several things you can try to eliminate groud loops:
- Make shure, your microphone’s power supply is plugged into the same outlet like your computer
- If the power supply only has two pins (no ground pin) or you are in germany or some country where outlets are symmetrically shaped, try plugging it into the outlet 180° rotated.
- Finally, if nothing helps, get a cheap ground loop isolator. I don’t want to be accused of advertising here so I wont write a link to Amazon here, but you will find one, if you search for
ground loop isolatoron amazon.
1 Like
My microphone doesn’t have its own power supply. It just connects to pc. I’ve just checked how the ground loop sounds like. I don’t really have that noise, microphone sounds like it has a white noise more.
I guess I understand the problem. It’s not about Rocky Linux, the laptop has that defect itself. I just can take it to the repair shop, and I hope it would be fixed.
I just looked up that microphone and some of the comments say that it has a relatively high noise level unless you use the built-in noise reduction.
Here is what it says:
The main issue is that there is noticeable background hiss when noise reduction is off. When noise reduction is on, it has to be aggressive to remove the hiss, resulting in slight “warble” artifacts affecting the voice. Unfortunately, there doesn’t appear to be a way to adjust the strength of the noise reduction to balance out the effect.
I think the best compromise is to only use noise reduction for live events/streaming. For audio that will be recorded and edited, capture the original audio and use software to find the right balance between noise reduction and artifacts. The voice signal itself is rich and captures the full spectrum of frequencies.
So your issue may be in the microphone itself rather than the computer or operating system.
1 Like