My debian problem: My inbuilt microphone of my laptop stopped working
since about one month. It worked smoothly for months before then. I
believe the issue
appeared after an update.
You did not mention what sort of hardware you are running. Running
lspci as root should give us what we need. Something like:
I hope you can help me by either confirming I should send a bugreport
on package
firmware-sof-signed or suggest an alternative action.
You can check for what packages were upgraded about that time by
inspecting (as root) the term.log* files in /var/log/apt. That should
help you narrow down the suspect packages.
You did not mention what sort of hardware you are running. Running
lspci as root should give us what we need. Something like:
Notice the list of kernel drivers and modules. Rooting around in theoutput
from dmesg or journalctl with those should locate any messages about initializing the sound card, including any error messages.
Hi Charles
Thanks for the tipps where I could start looking to solve my problem.
You can check for what packages were upgraded about that time by inspecting (as root) the term.log* files in /var/log/apt. That
should help you narrow down the suspect packages.
That is lots of lines and package names that I as a novice don't
understand very well. I did copy out the ones that have sound,
pipewire, alsa or some warning in there, in case that helps narrow
down the package:
Unpacking pipewire-pulse (1.2.7-1+b1) over (1.2.7-1) …
Unpacking libasound2t64:amd64 (1.2.13-1) over (1.2.12-1+b1) …
Unpacking libasound2-data (1.2.13-1) over (1.2.12-1) …
You did not mention what sort of hardware you are running. Running
lspci as root should give us what we need. Something like:
Here my output:
00:1f.3 Multimedia audio controller: Intel Corporation Meteor Lake-P
HD Audio Controller (rev 20)
Subsystem: Hewlett-Packard Company Device 8c26
Flags: bus master, fast devsel, latency 64, IRQ 244, IOMMU group
16 Memory at 5019310000 (64-bit, non-prefetchable) [size=16K]
Memory at 5019000000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [50] Power Management version 3
Capabilities: [c0] Vendor Specific Information: Len=14 <?>
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_sof_pci_intel_mtl
Notice the list of kernel drivers and modules. Rooting around inoutput
the
from dmesg or journalctl with those should locate any messages
about initializing the sound card, including any error messages.
Can you break down this advise a bit more or me as novice debian user
and non native english speaker? I don't fully get it.
One of my attached outputs of my first message was along that line, something
my IT support person produced:
journalctl -b -1 | grep -i csc3551
On Wed, 5 Feb 2025 15:46:23 +0100
Franziska Menti <fmenti@phys.ethz.ch> wrote:
Hi Charles
What I had in mind here is something like:
dmesg | less -X
then use the search function (the / key) to search for snd_hda_intel
and (separately) snd_sof_pci_intel_mtl. Check in the neighbor of any
entries for error messages.
For journalctl, the setup will be a bit more complex. depending on
what you want.
journalctl -b | less
for everything since the last boot.
journalctl -S YYYY-MM-DD | less
for everything since the given date (e.g. 2012-10-30).
man less and man journalctl are your friends. And your IT person
should be familiar with these tools.
Indeed so, and in particular the bit in journalctl's man page where it
says "The output is paged through less by default ..." !
Piping journalctl's output through less is pointless, I think.
dmesg -H might also be worth looking at.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 146:18:42 |
| Calls: | 10,383 |
| Calls today: | 8 |
| Files: | 14,054 |
| D/L today: |
2 files (1,861K bytes) |
| Messages: | 6,417,708 |