You are not logged in.
Don't forget to delete .config/pulse/*
I had done it before but tried again and it didn't make any difference.
Definitely something is odd. Today boot was clean of alsactl errors but after reboot/poweroff they appear again.
Led seemed to be always ON first but then went OFF on subsequent boots.
Offline
Yes.
But mic status led is not only bug.
It seems to work great using headset, but if you enable mic headset and status led turns off you had enable internal mic too...
Offline
Downgraded packages. Microsophone is too low, but led status work.
I need to test audio in virtualbox if it's work.
Offline
Just an update, everything is now working as it was before. Microphone is now detected and the mute-LED is also working. This thread can be marked as solved.
Seems I spoke too soon, the internal microphone is detected and working. However the mute-LED indicates the mute status of the headset rather than that of the internal microphone
Offline
Form me, led is fixed... Update not resolve!
Did you use gnome? What you change?
Only seen your post now, I had changed the file /usr/share/alsa/ucm2/HDA-Intel/HDA-Intel.conf to reflect this change https://github.com/alsa-project/alsa-uc … eaa224b766. Just changed the line Syntax 3 to Syntax 4. The other change I made was just updating my system the normal way. This solved the problem with the internal microphone not being detected but I have an issue with LED where the led indicates mute status of the headset rather than the internal microphone
Offline
but I have an issue with LED where the led indicates mute status of the headset rather than the internal microphone
I have the same issue, but on Fedora 34. A bit annoyed since it is a regression (the led was working fine until some updates ago) but I haven't found any solution yet.
Offline
Last update.
After kernel lts update, mic led status not working using headsets... fantastic!
Offline
After updated to new lts kernel it's work!!!!!!
Offline
Here we go again.... Not working anymore
[2022-01-19T09:17:08+0100] [ALPM] upgraded alsa-card-profiles (1:0.3.43-1 -> 1:0.3.43-5)
[2022-01-19T09:17:09+0100] [ALPM] upgraded pipewire (1:0.3.43-1 -> 1:0.3.43-5)
[2022-01-19T09:17:09+0100] [ALPM] upgraded gst-plugin-pipewire (1:0.3.43-1 -> 1:0.3.43-5)
Last edited by gca (2022-01-20 10:12:54)
Offline
It's extremely unlikely that that set of package changes is related to that since these rebuilds mostly related to how jack (the API, not the physical connector) support is handled.
Did you update the kernel as well?
Last edited by V1del (2022-01-20 10:41:42)
Offline
It's extremely unlikely that that set of package changes is related to that since these rebuilds mostly related to how jack (the API, not the physical connector) support is handled.
Did you update the kernel as well?
Here we go again.... Not working anymore
[2022-01-27T22:14:18+0100] [ALPM] upgraded glib2 (2.70.2-2 -> 2.70.3-1)
[2022-01-27T22:14:18+0100] [ALPM] upgraded pipewire (1:0.3.43-5 -> 1:0.3.44-1)
[2022-01-27T22:14:18+0100] [ALPM] upgraded gst-plugin-pipewire (1:0.3.43-5 -> 1:0.3.44-1)
[2022-01-27T22:14:18+0100] [ALPM] upgraded lua (5.4.3-1 -> 5.4.4-1)
[2022-01-27T22:14:18+0100] [ALPM] upgraded openexr (3.1.3-1 -> 3.1.4-1)[2022-01-28T09:46:57+0100] [ALPM] upgraded linux-lts (5.15.16-1 -> 5.15.17-1)
[2022-01-28T09:46:57+0100] [ALPM] upgraded acpi_call-lts (1.2.2-12 -> 1.2.2-13)
[2022-01-28T09:46:59+0100] [ALPM] upgraded linux-lts-headers (5.15.16-1 -> 5.15.17-1)
[2022-01-28T09:46:59+0100] [ALPM] upgraded nvme-cli (1.16-1 -> 1.16-2)
Where is the problem?
Offline
For those interested in tracking the LED issue: https://gitlab.freedesktop.org/pipewire … ssues/1849
Offline