Fedora 34 - Headset audio doesn't work properly

Hi. I installed Fedora Silverblue 34 in a single-jack laptop, and I’m having some issues with audio. Specifically, with headset input support; when I first connected a pair of earphones, it just detected the speaker part, but not the microphone. Then, I navigated the web a bit in search of solutions. I found this: Fix Missing Audio Input Device in Ubuntu | Thomas Venturini

Even though the tutorial was geared to Ubuntu, the instructions were universal, so, I gave it a try. After some trial and error to find the correct entry for my sound card (Realtek alc668) on kernel.org, I settled on alc668-headset. The rest of the entries available worked only partially, as they would disable my internal’s laptop mic.

That entry kind of works; it detects an audio input from my earphones (yay!)… but the input it detects is from the output. So, my headset’s speakers are also the microphones (wut). Is there any way to re-route the input to my earphone mic?

An additional issue is that when I connect my earphones, when selecting “Internal Speakers” as an audio output, they don’t work. But I guess this is normal, as Windows (I think) doesn’t allow this kind of behaviour (integrated audio input with external headset mic at the same time).

1 Like

That bit about the speakers being disabled by the headphone is not necessarily a software issue. Most devices with speakers and a headphone jack have historically had a hardware switch that disabled the speakers when the headphone was connected. After all, the purpose of headphones is to avoid disturbing those around you (for a myriad of reasons).

Since now it is mostly done within the audio chipset that same thought is carried through. On my laptop when listening to audio through the speakers then plugging in the headset the output automatically switches to the headset and disables the speakers.

The mic is the same in that it automatically switches for me.

The real question about your headset is the type of plug on the end of the cord. Is it a 3 barrel (tip, barrel, barrel) or 4 barrel tip. The 3 barrel would not support the mic, the 4 barrel does. Also, what about the headphone plug on the laptop. It has to support the mic as well. If the chipset does not sense the mic it does not switch it.

The proper driver is critical to the device working properly.

Can you install inxi then post the output of “inxi -xxA” so we can see exactly which chipset and driver is involved?

3 Likes

That bit about the speakers being disabled by the headphone is not necessarily a software issue. Most devices with speakers and a headphone jack have historically had a hardware switch that disabled the speakers when the headphone was connected. After all, the purpose of headphones is to avoid disturbing those around you (for a myriad of reasons).

Though as much. Thanks for clarifying that.

The real question about your headset is the type of plug on the end of the cord. Is it a 3 barrel (tip, barrel, barrel) or 4 barrel tip. The 3 barrel would not support the mic, the 4 barrel does. Also, what about the headphone plug on the laptop. It has to support the mic as well. If the chipset does not sense the mic it does not switch it.

The headset has a four barrel jack connection. I actually use it on Windows 10 with no issues.

Can you install inxi then post the output of “inxi -xxA” so we can see exactly which chipset and driver is involved?

This is inxi’s output, though it’s from a toolbox instance, as I prefer to not layer more packages on Silverblue. Not sure if it’s the same.

Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio 
  driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 
  Sound Server-1: ALSA v: k5.13.9-200.fc34.x86_64 running: yes 
  Sound Server-2: PipeWire v: 0.3.33 running: yes

All that looks normal.
One big difference between your machine and mine is Silverblue. I am using the workstation install of F34 so things are definitely different. My motherboard has a much different audio chipset
Advanced Micro Devices [AMD] Starship/Matisse HD Audio
which still uses the same driver as yours shows.

Maybe someone else has some suggestions.

1 Like