| View previous topic :: View next topic |
| Author |
Message |
AndrewAmmerlaan
Developer
Joined: 25 Jun 2014
Posts: 285
Location: Nijmegen
|
 Posted: Thu Dec 03, 2020 3:16 pm Post subject: Internal Microphone shown as "(unplugged)" |
 |
|
Hi, on my dynabook satellite pro l50-g-188 the internal microphone is unusable, pavucontrol shows it as "(unplugged)". A external microphone plugged into the audio jack works just fine.
The specs list the microphone as a "Dual-Mic" built into the "HD Webcam": https://nl.dynabook.com/laptops/satellite-pro/satellite-pro-l50/satellite-pro-l50-g-188/ (could not find an English version, sorry)
I get the exact same behaviour with the pre-compiled kernel gentoo-kernel-bin, and a systemrescue-cd also shows the same problem. Therefore, I'm pretty confident that this is not a issue with the kernel config file. If the webcam is on, the internal microphone still doesn't work. It however does work when booting Windows 10.
Here's the relevant output of pacmd list-sources:
| Code: |
* index: 1
name: <alsa_input.pci-0000_00_1f.3.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause: (none)
priority: 9039
volume: front-left: 20726 / 32% / -30.00 dB, front-right: 20726 / 32% / -30.00 dB
balance 0.00
base volume: 6554 / 10% / -60.00 dB
volume steps: 65537
muted: no
current latency: 0.26 ms
max rewind: 0 KiB
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 1
linked by: 1
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
card: 0 <alsa_card.pci-0000_00_1f.3>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC255 Analog"
alsa.id = "ALC255 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb1510000 irq 150"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "02c8"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC255"
alsa.components = "HDA:10ec0255,3100f003,00100002 HDA:8086280b,80860101,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-input-internal-mic: Internal Microphone (priority 8900, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: yes)
properties:
device.icon_name = "audio-input-microphone"
active port: <analog-input-mic>
|
And here's the output of the same command but now there is no microphone connected to the jack
| Code: |
index: 1
name: <alsa_input.pci-0000_00_1f.3.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause: (none)
priority: 9039
volume: front-left: 65540 / 100% / 0.00 dB, front-right: 65540 / 100% / 0.00 dB
balance 0.00
base volume: 6554 / 10% / -60.00 dB
volume steps: 65537
muted: no
current latency: 0.34 ms
max rewind: 0 KiB
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 2
linked by: 2
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
card: 0 <alsa_card.pci-0000_00_1f.3>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC255 Analog"
alsa.id = "ALC255 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb1510000 irq 150"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "02c8"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC255"
alsa.components = "HDA:10ec0255,3100f003,00100002 HDA:8086280b,80860101,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-input-internal-mic: Internal Microphone (priority 8900, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: yes)
properties:
device.icon_name = "audio-input-microphone"
active port: <analog-input-internal-mic>
|
And here's the output of pacmd list-sinks:
| Code: |
3 sink(s) available.
* index: 0
name: <alsa_output.pci-0000_00_1f.3.analog-stereo>
driver: <module-alsa-card.c>
flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause: (none)
priority: 9039
volume: front-left: 26216 / 40% / -23.87 dB, front-right: 26216 / 40% / -23.87 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 40.04 ms
max request: 6 KiB
max rewind: 6 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 1
linked by: 3
configured latency: 40.00 ms; range is 0.50 .. 2000.00 ms
card: 0 <alsa_card.pci-0000_00_1f.3>
module: 6
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC255 Analog"
alsa.id = "ALC255 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xb1510000 irq 150"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-0000:00:1f.3"
sysfs.path = "/devices/pci0000:00/0000:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "02c8"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC255"
alsa.components = "HDA:10ec0255,3100f003,00100002 HDA:8086280b,80860101,00100000"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
analog-output-speaker: Speakers (priority 10000, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: yes)
properties:
device.icon_name = "audio-headphones"
active port: <analog-output-headphones>
|
Upon plugging a external microphone into the jack the active port automatically switches to it, however upon unplugging it again it does not switch back automatically. I can do this manually via pavucontrol, however the internal microphone still does not work and is shown as "unplugged".
My guess is there is some sort of switch that is enabled automatically upon request on windows, but which is not switched on automatically on Linux, maybe there is some way to switch it on manually?
Here's the output of dmesg: https://dpaste.com/C2R8MZNPT
And here's lspci -vvk: https://dpaste.com/F54D7CCL4
_________________
OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
 |
AndrewAmmerlaan
Developer
Joined: 25 Jun 2014
Posts: 285
Location: Nijmegen
|
| Posted: Fri Dec 04, 2020 11:45 am Post subject: |
|
|
For some reason the microphone works just fine today, yesterday I couldn't get it to work in anything except windows and today it works just fine.
Strange, but I'm not complaining  hopefully it will keep working from now on
_________________
OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 21785
|
| Posted: Fri Dec 04, 2020 5:14 pm Post subject: |
|
|
| Have you cold-booted the system between when it worked in Windows and when it worked today? Some hardware has been known to keep state across a warm reboot, leading to situations where booting Windows, then warm booting over to Linux works differently than running Windows, powering down the system, then booting directly into Linux. I think I have seen cases where the warm boot path leaves the device broken because Windows put it into a state Linux was not expecting, and also cases where the warm boot path was required to make the device work because Windows did undocumented initialization that was required for proper operation, and that Linux did not know to do. |
|
| Back to top |
|
|
AndrewAmmerlaan
Developer
Joined: 25 Jun 2014
Posts: 285
Location: Nijmegen
|
| Posted: Sat Dec 05, 2020 11:14 am Post subject: |
|
|
| Hu wrote: | | Have you cold-booted the system between when it worked in Windows and when it worked today? Some hardware has been known to keep state across a warm reboot, leading to situations where booting Windows, then warm booting over to Linux works differently than running Windows, powering down the system, then booting directly into Linux. I think I have seen cases where the warm boot path leaves the device broken because Windows put it into a state Linux was not expecting, and also cases where the warm boot path was required to make the device work because Windows did undocumented initialization that was required for proper operation, and that Linux did not know to do. |
If I remember correctly I had not done a full shutdown when I was trying to fix this earlier, the day after when it suddenly started working the laptop had been off for some time. So this might very well be the cause of the problem I've been observing. I'll try to remember to completely power off the machine before switching between operating systems in the future and hopefully that will prevent such things from happening.
Thanks
_________________
OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
garrison
Apprentice
Joined: 18 Mar 2003
Posts: 251
|
| Posted: Fri Dec 18, 2020 7:45 pm Post subject: |
|
|
| AndrewAmmerlaan wrote: | | I'll try to remember to completely power off the machine before switching between operating systems in the future and hopefully that will prevent such things from happening. |
If cold-booting would show a change in behavior, this is surely alsa/kernel issue. A few of these got fixes last weeks.
To double-check the issue is due to jack state reporting, compare 'pa-info' output before and after plugging the jack.
If you will not see a difference in 'jacks_do' section of output, this is alsa/kernel issue.
If there is a difference then this is a bug to pulseaudio which needs to be reported along with pa-info output. |
|
| Back to top |
|
|
AndrewAmmerlaan
Developer
Joined: 25 Jun 2014
Posts: 285
Location: Nijmegen
|
| Posted: Fri Dec 18, 2020 7:52 pm Post subject: |
|
|
| garrison wrote: | | AndrewAmmerlaan wrote: | | I'll try to remember to completely power off the machine before switching between operating systems in the future and hopefully that will prevent such things from happening. |
If cold-booting would show a change in behavior, this is surely alsa/kernel issue. A few of these got fixes last weeks.
To double-check the issue is due to jack state reporting, compare 'pa-info' output before and after plugging the jack.
If you will not see a difference in 'jacks_do' section of output, this is alsa/kernel issue.
If there is a difference then this is a bug to pulseaudio which needs to be reported along with pa-info output. |
I've been observing this for some time now, and I'm 100% sure this problem only occurs when rebooting from windows into Linux without fully powering down the machine in between. I'll check again with the newest kernel/alsa, perhaps it is fixed now. And otherwise it is not that big of an inconvenience to shutdown the machine instead of rebooting when switching operating systems.
_________________
OS: Gentoo 6.8.10-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400 |
|
| Back to top |
|
|
garrison
Apprentice
Joined: 18 Mar 2003
Posts: 251
|
| Posted: Fri Dec 18, 2020 8:46 pm Post subject: |
|
|
| AndrewAmmerlaan wrote: | | And otherwise it is not that big of an inconvenience to shutdown the machine instead of rebooting when switching operating systems. |
Mind that alsa-devel list takes such reports pretty seriously (do not forget to mention behavior change after booting the other os, and also the behavior itself, quoting jack state change evidence) so for mainstream hardware these should get fixes quite soon, so worth taking that route. Hope you are not planning to boot to that other thing first forever |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
