27 Jul
2021
27 Jul
'21
5:10 p.m.
On 7/27/21 2:01 AM, Dr. Nikolaus Klepp wrote:
Anno domini 2021 Mon, 26 Jul 17:56:08 -0400
Edward scripsit:
~$ cat /proc/asound/cards
0 [Creative ]: HDA-Intel - HDA Creative
HDA Creative at 0xfe9fc000 irq 18
1 [Headset ]: USB-Audio - Logitech USB Headset
Logitech USB Headset Logitech USB Headset at
usb-0000:00:12.0-1, full speed
--
Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
On 7/25/21 10:46 PM, E. Liddell wrote:
can you post the output
of
$ cat /proc/asound/cards
Nik On Sun, 25 Jul 2021 22:41:34 +0200
"Dr. Nikolaus Klepp" <office(a)klepp.biz> wrote:
02:00.0 Audio device: Creative Labs Sound Core3D [Sound
Blaster Recon3D
/ Z-Series] (rev 01)
Subsystem: Creative Labs SB1570 SB Audigy Fx
Flags: bus master, fast devsel, latency 0, IRQ 18, NUMA node 0
Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
Memory at fe9f8000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
Output of lsusb -v for the Logitiech headphones, attached. Oh, I see, your headset is on USB :) That means
that audio playback is not managed by your soundlbaster card, but by the USB headset
itself - it's a different soundcard. But your volume keys change volume of the
soundblaster aka default soundcard only. That will not work as intended.
If the
problem is indeed that the headset is being treated as a second soundcard,
I can see two potential solutions:
Change the config (probably the ALSA config) to make the headset the default
(first) soundcard.
More radically, blacklist the driver for the Audigy soundcard so that it (hopefully)
doesn't get picked up at all.
If you're ever using the main soundcard, either of those things might cause other
problems, of course.