On Wed, 5 Feb 2025 15:46:23 +0100
Franziska Menti <fme...@phys.ethz.ch> wrote:
> 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) …
Somewhere above and near those lines should be the date(s) they took
place. I suggest you use less (as root) to search for them, then go up
from the interesting ones. Something like:
cd /var/log/apt
zless term.log
Then use the / key to search withing that file.
(zless is like less, but it will decompress on the fly for you, so you
don't have to do that manually first.)
>
> > 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.
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.
> 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
>
I'm not sure why your IT person was looking at csc3551, but the output
is interesting. Apparently wanted firmware isn't being loaded
("spi0-CSC3551:00-cs35l41-hda.0: firmware: failed to load
cirrus/cs35l41-dsp1-spk-prot-103c8c49-r0.wmfw (-2)")
My next step would be to see what package provides the indicated file:
root@tiassa:~# apt-file search cs35l41-dsp1-spk-prot-103c8c49-r0.wmfw
root@tiassa:~#
And apparently nothing does! This is a hazard of running trixie. So I
shorten up the search pattern:
root@tiassa:~# apt-file search cs35l41-dsp1-spk-prot-103c8c49
firmware-cirrus: /usr/lib/firmware/cirrus/cs35l41-dsp1-spk-prot-103c8c49.bin
firmware-cirrus: /usr/lib/firmware/cirrus/cs35l41-dsp1-spk-prot-103c8c49.wmfw
root@tiassa:~#
That would lead me to check to see if the package firmware-cirrus is
installed:
root@tiassa:~# dpkg-query --show cirrus-firmware
dpkg-query: no packages found matching cirrus-firmware
root@tiassa:~#
Obviously I don't have it installed on tiassa. If you do have it
installed, the the problem is that the exact firmware blob you want
isn't in the package, and your remedies are to wait, or to query the
Debian maintainers.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
