this post was submitted on 12 Jul 2024
13 points (93.3% liked)
Linux Hardware
956 readers
2 users here now
For news and discussion relating to Linux hardware.
Join us on the GamingOnLinux Discord!
Related Communities:
Quick rules:
- Be nice to each other.
- Report toxic people.
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful, and just be awesome to each other.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This shows up after I press F4: 3 devices in the middle all have the word "mic" in it, what should I do next?
I have no idea. This looks normal. I would play around with the settings in your situation. Like setting levels and toggling things.
wait, do you have a headset plugged in? in some systems it disables the internal mic whike a headset is plugged in.
I don't have a headset plugged in right now. But I think yesterday I might have a headset plugged in while shutting down my computer. Could that make the computer still think it has a headset plugged in? Though speakers work normally and I've restarted quite a few times and this problem still persists.
idk the headset thing is often hardware controlled, so it shouldn't be a problem after reboot, but if you want to be sure plug one in when it's off and remove it when on. that should trigger the unplug software event, if there is any.
i'm out if ideas. good luck!
I tried plugging in a headset and plugging it out. When I plugged it in 2 microphones showed up, one called "headset microphone" and the other just called "microphone", screenshot:
But when I unplugged the headset both microphones are gone, does it mean that my laptop recognizes its internal microphone when a headset is plugged in? Also when I switch to the one just called "microphone", speaking to the headset microphone doesn't make the bar move as much as patting the laptop, so the "microphone" should be the internal microphone.
wow, that is some progress. maybe check out what your system does when you do that, using kernel log (dmesg?), udev log and systemd log. but i can't help you past this point it's too weird.