Internal microphone detected but not selectable in apps

apodyopsisx · April 12, 2023, 9:22pm

[Hi!! I hope someone can help me.
I have installed Manjaro Gnome for the first time on a new laptop: Medion Akoya E15415 Intel Core i5-10210U/8GB/256GB SSD

Everything is working fine apart from the microphone, which isn’t being recognized by the os.
I’ve been searching for various possible solutions but nothing I tried has worked.
Here is the output of a couple of commands that might be useful for understanding the problem, I hope this can help you in helping me!
Thank you so much in advance!!

arecord -l

**** List of CAPTURE Hardware Devices ****
card 0: sofessx8336 [sof-essx8336], device 0: ES8336 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

pactl list cards

 Card #42
	Name: alsa_card.pci-0000_00_1f.3-platform-sof-essx8336
	Driver: alsa
	Owner Module: n/a
	Properties:
		device.enum.api = "udev"
		device.api = "alsa"
		media.class = "Audio/Device"
		api.alsa.path = "hw:0"
		api.alsa.card = "0"
		api.alsa.card.name = "sof-essx8336"
		api.alsa.card.longname = "MEDION-E15415-NONE-NP1xCM"
		device.plugged.usec = "4529968"
		device.bus_path = "pci-0000:00:1f.3-platform-sof-essx8336"
		sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sof-essx8336/sound/card0"
		device.bus = "pci"
		device.subsystem = "sound"
		device.vendor.id = "0x8086"
		device.vendor.name = "Intel Corporation"
		device.product.id = "0x02c8"
		device.product.name = "Comet Lake PCH-LP cAVS"
		device.name = "alsa_card.pci-0000_00_1f.3-platform-sof-essx8336"
		device.description = "Comet Lake PCH-LP cAVS"
		device.nick = "sof-essx8336"
		device.icon_name = "audio-card-pci"
		api.alsa.use-acp = "true"
		api.acp.auto-profile = "false"
		api.acp.auto-port = "false"
		api.dbus.ReserveDevice1 = "Audio0"
		factory.id = "14"
		client.id = "31"
		object.id = "42"
		object.serial = "42"
		object.path = "alsa:pcm:0"
		alsa.card = "0"
		alsa.card_name = "sof-essx8336"
		alsa.long_card_name = "MEDION-E15415-NONE-NP1xCM"
		alsa.driver_name = "snd_soc_sof_es8336"
		device.string = "0"
	Profiles:
		off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
		output:stereo-fallback+input:stereo-fallback: Stereo Output + Stereo Input (sinks: 1, sources: 1, priority: 5151, available: yes)
		output:stereo-fallback: Stereo Output (sinks: 1, sources: 0, priority: 5100, available: yes)
		input:stereo-fallback: Stereo Input (sinks: 0, sources: 1, priority: 51, available: no)
		pro-audio: Pro Audio (sinks: 4, sources: 1, priority: 1, available: yes)
	Active Profile: output:stereo-fallback+input:stereo-fallback
	Ports:
		analog-input-headset-mic: Headset Microphone (type: Headset, priority: 8800, latency offset: 0 usec, availability group: Legacy 1, not available)
			Properties:
				port.type = "headset"
				port.availability-group = "Legacy 1"
				device.icon_name = "audio-input-microphone"
				card.profile.port = "0"
			Part of profile(s): input:stereo-fallback, output:stereo-fallback+input:stereo-fallback
		analog-output-speaker: Speakers (type: Speaker, priority: 10000, latency offset: 0 usec, availability unknown)
			Properties:
				port.type = "speaker"
				device.icon_name = "audio-speakers"
				card.profile.port = "1"
			Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback
		analog-output-headphones: Headphones (type: Headphones, priority: 9900, latency offset: 0 usec, availability group: Legacy 1, not available)
			Properties:
				port.type = "headphones"
				port.availability-group = "Legacy 1"
				device.icon_name = "audio-headphones"
				card.profile.port = "2"
			Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback](https://)

TriMoon · April 12, 2023, 11:06pm

Hi and welcome to the Forum

If the OS doesn’t recognize it (eg detect it) how were you able to provide info about it using the commands you show?

Maybe the application you want to use for recording has not been configured properly to use it as input?

PS:
Edit your post acording to the info in below thread, it will make it easier for the rest to read the output

apodyopsisx · April 13, 2023, 9:17am

Sorry, what I meant to say is that the system app of the os doesn’t detect any mic and when I try to use Skype or Google Meet the same thing happens.

done! thanks for the tip

apodyopsisx · April 13, 2023, 9:25am

more info that could be helpful

sudo alsa-info.sh --upload

http://alsa-project.org/db/?f=0ba9c312de89b355cdb8644264dc769903549972

Community Assistant EDIT: show inactive link in preformatted text

ruziel · April 14, 2023, 11:42am

Just to be safe, have you tried a couple of different kernels? If not, that can sometimes solve such issues. I always go for open-source drivers & have had few issues with sound etc, on multiple machines. Hopefully you find a solution soon…

apodyopsisx · April 15, 2023, 11:34am

Yeah, I tried updating to the latest kernel version and rebooting, sadly, it didn’t change a thing.
I’ll try installing open-source drivers and see if one of them fixes the mic problem!

apodyopsisx · April 18, 2023, 11:22am

Tried what @ruziel suggested and the problem still continues, plus now my camera isnt working either

ruziel · April 18, 2023, 12:33pm

Do you have Timeshift installed? If not, that’s always good to have in situations where an update breaks something. I hope you find a solution soon. R

TriMoon · April 18, 2023, 7:16pm

Because you are able to post hardware info about your microphone input, it is already detected by the “system”, eg. kernel…

If it doesn’t show up in your application(s), it is a misconfiguration of said app(s) or the sound system you are using pipewire going by the tag on the topic…

Unfortunately im unable to assist with audio issues, because i lack the knowledge about that.

PS:
I changed the topic title, to prevent misguiding interested readers.

apodyopsisx · April 19, 2023, 9:37am

I do have timeshift installed and I was able to go back to the version where the camera was working.
No advances with the mic problem tho

ruziel · April 19, 2023, 10:33am

Ah okay. Hopefully you find a solution soon. All the best with this one…

cscs · April 19, 2023, 10:35am

If you run

sudo mkinitcpio -P

Do you get any ‘possibly missing firmware’ messages?

apodyopsisx · April 20, 2023, 11:04am

it does! this is the output I got:

    ~  sudo mkinitcpio -P                                       ✔  48s  
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
  -> -k /boot/vmlinuz-6.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.1-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.23-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
  -> -k /boot/vmlinuz-6.1-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.1.23-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img'
==> Image generation successful

cscs · April 20, 2023, 6:56pm

Install the corresponding package and run it again
https://wiki.archlinux.org/title/Mkinitcpio#Possibly_missing_firmware_for_module_XXXX

Yochanan · April 20, 2023, 8:34pm

Those are only warnings and can be safely ignored. You most likely do not need any of them. Reference the Arch Wiki article in the post above for more info.

cscs · April 20, 2023, 8:36pm

You can safely ignore the warnings, if you know that you do not use the affected hardware.

(emphasis mine)

Of course OP can choose to ignore them … but as the thread is about non-functioning hardware … its not out of the realm of possibiities that this is related.
Specifically this firmware is to do with USB host.

Yochanan · April 20, 2023, 10:10pm

Try installing sof-firmware and reboot.

apodyopsisx · April 21, 2023, 1:09pm

I installed all of the “possibly missing firmware” packages and sof-firmware. After rebooting I double checked and the issue continues.

apodyopsisx · April 28, 2023, 4:43pm

any other ideas? please