[alsa-devel] Bug report for: [P7xxDM2(-G), Realtek ALC898, issue: Headphone Jack, External] No sound at all

[Dennis Mungai]

Cool, thanks!

Rewiring the pins via hdajack retask tool fixes the detection, but still no
sound from the headphones jack is heard. Only the temporary click off the
audio jack when plugged in.

On Jan 12, 2018 11:11, "Takashi Iwai" <tiwai at suse.de> wrote:

> On Thu, 11 Jan 2018 19:21:03 +0100,
> Dennis Mungai wrote:
> >
> > Hello there,
> >
> > I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed
> > as the Origin Eon 15-X (Late 2016 model), the System76's Serval WS
> > (2017 model), the Eurocom Sky X4E2, among others.
> >
> > The sound card is the Realtek ALC898 with the following output
> configuration:
> >
> > 1. One SPDIF/headphone combo jack (to the right)
> > 2. One Line Out.
> > 3. One Line-In.
> > 4. One Mic-In.
> >
> > Background information:
> >
> > On Windows, one can use the Realtek HD Audio control panel pop-up menu
> > on jack detection to set the output type when an audio device is
> > plugged in to an appropriate jack, combined with Sound Blaster X-Fi
> > MB5 software to enable post-processing effects such as Bass, noise
> > cancellation, etc.
> >
> > What I have tried so far:
> >
> > 1. Setting the model definition at /etc/modprobe.d/sound.conf with the
> > following entries:
> >
> > options snd-hda-intel model=no-primary-hp enable=1 index=0
> >
> > Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that
> > also has the same (or a similar) ESS Sabre Audio DAC component.
> >
> > Expected behavior:
> >
> > When plugged into the microphone jack, the ESS Sabre DAC should be
> > activated and sound should be routed to the headset.
> >
> > Observed anomaly:
> >
> > Sound comes out through the speakers instead.
> >
> > However, the line-out output works. In that case, when plugged into
> > the line out, Audio works as expected.
>
> Judging from alsa-info.sh output, BIOS doesn't seem to give the proper
> headphone pin (or the headset output), and that's the culprit.
> It's a bug of BIOS.  You can try to figure out the pin and override
> the pin config via hdajackretask or such a tool.
>
>
> Takashi
>