On 23/06/2022 08:15, Carlos E. R. wrote:
On 2022-06-23 02:10, Masaru Nomiya wrote:
Hello,
PS.
In the Message;
Subject : Re: [oS-EN] New sound problem Message-ID : <87pmj048jg.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Thu, 23 Jun 2022 07:50:43 +0900
[MN] == Masaru Nomiya <nomiya@galaxy.dti.ne.jp> has written:
MN> Hello,
MN> In the Message;
MN> Subject : Re: [oS-EN] New sound problem MN> Message-ID : <97e5f170-6e87-0b4c-c29b-8bb5367fc6cf@telefonica.net> MN> Date & Time: Wed, 22 Jun 2022 20:38:14 +0200
MN> [CER] == "Carlos E. R." <> has written:
CER> On 2022-06-22 14:26, Masaru Nomiya wrote:
[...] MN> First of all, Soundblaster is not interested in Linux, and what you MN> are using is a kernel driver, and what you say "should" be possible by MN> creating a separate software?
MN> It's not about the driver.
If I were you, I would use pavucontrol (or pavucontrol-qt).
I already tried the former. It shows the headphones as playing, there is sound activity in the moving graph, but the headphones remain silent no matter if I crank their volume to max.
There is a hiss in them, which proves they are connected to the hardware.
I can switch, in pavucontrol, to the loudspeakers, but they also remain silent.
It means that some software is silencing them both, and forcing this.
I remember having problems similar to this on my old laptop, but it's a few years ago and I don't recall if I ever found a perfect solution, or just things that sometimes worked erratically. It seemed that the audio got somehow reversed and plugging in to the headphone jack would mute it and vice-versa. Things were complicated by my having a full docking station with additional audio outs. What I do remember is that I frequently would have to open alsamixer in a terminal to fix it. By default when opening alsamixer I'd be presented with just the one slider due to PulseAudio. I'd then do F6 to select the soundcard. Somewhere along the line of audio outs I'd need to flip a switch or two, but I don't know which. gumb