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) …
Unpacking pipewire-alsa:amd64 (1.2.7-1+b1) over (1.2.7-1) …
Unpacking libpipewire-0.3-modules:amd64 (1.2.7-1+b1) over (1.2.7-1) …
Unpacking pipewire:amd64 (1.2.7-1+b1) over (1.2.7-1) …
Setting up libasound2-data (1.2.13-1) …
Updating certificates in /etc/ssl/certs...
rehash: warning: skipping ca-certificates.crt, it does not contain
exactly one certificate or CRL
Setting up libasound2t64:amd64 (1.2.13-1) …
Setting up libpipewire-0.3-0t64:amd64 (1.2.7-1+b1) …
#[0;1;39m/usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path
"/run/lock", ignoring.#[0m
Setting up libpipewire-0.3-modules:amd64 (1.2.7-1+b1) …
Setting up systemd-timesyncd (257.1-5) ...
systemd-time-wait-sync.service is a disabled or a static unit not
running, not starting it.
Setting up pipewire-bin (1.2.7-1+b1) …
Setting up pipewire:amd64 (1.2.7-1+b1) …
Setting up pipewire-alsa:amd64 (1.2.7-1+b1) ...
Setting up pipewire-pulse (1.2.7-1+b1) …
Preparing to unpack .../07-alsa-utils_1.2.13-1_amd64.deb ...
Unpacking alsa-utils (1.2.13-1) over (1.2.12-1) …
Setting up alsa-ucm-conf (1.2.13-1) …
Setting up alsa-utils (1.2.13-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 in the
output
> 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
