On Tue 29 Aug 2023 at 23:54:41 (-0400), Karl Vogel wrote: > On Tue, Aug 29, 2023 at 10:53:39PM -0400, gene heskett wrote: > > And that is the problem, and why I read thru all those man ages trying to > > find a way to make it log what it did. Sadly no. > > Install and configure file auditing on Debian: > https://www.daemon.be/maarten/auditd.html > > Auditing can help you find anything trying to write to your sound device. > Look at these manpages: > auditd.conf (5) > audit.rules (7) > audispd (8) > ausearch (8) > aureport (8) > auditctl (8) > augenrules (8) > > To find your sound cards and/or devices: > https://wiki.debian.org/Sound > https://wiki.debian.org/SoundCard > https://wiki.debian.org/PulseAudio > > I don't have a Debian system to play with, but in the (good|bad) old > days, we had a /devices directory with all sorts of weirdness inside. > If you have one of those, try > find /devices -print | grep sound > > That might point you to an actual device name.
As Gene has the habit of thoughtlessly pasting commands posted here, it might be better instead to try: $ find /dev | grep snd /dev/snd /dev/snd/controlC0 /dev/snd/hwC0D0 /dev/snd/pcmC0D2c /dev/snd/pcmC0D2p /dev/snd/pcmC0D0c /dev/snd/pcmC0D0p /dev/snd/by-path /dev/snd/by-path/pci-0000:00:1b.0 /dev/snd/by-path/pci-0000:02:00.1 /dev/snd/controlC1 /dev/snd/hwC1D0 /dev/snd/pcmC1D3p /dev/snd/seq /dev/snd/timer $ Cheers, David.
