Re: [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy book

[Takashi Iwai <tiwai@suse.de>]

On Mon, 17 Feb 2020 15:03:16 +0100,
Aurélien Croc wrote:
> 
> > The BIOS seems broken, it just sets a single output pin.
> > You need to try to figure out the pin connections, e.g. via
> > hdajackretask program.  The headphone might work with that.
> > But the speaker output might need another special handling, and it's
> > nothing but trial-and-test with the existing quirks for similar
> > devices.  Take a look at sound/pci/hda/patch_realtek.c.
> 
> Thank you for your answer. I tried hdajackretask but I didn't succeed to get 
> sound from headsets.. Maybe I didn't tried all the advanced features of this 
> tool..
> I also tried some quirks from  your file but it changes nothing. There are too 
> many possibilities. It seems to be hard to test them all.

Yeah, that's the problem -- there are way too many device-specific
implementations and workarounds :-<

> Don't you know a solution to get what is bugged or to get information about 
> which channel is linked to headets or internal speakers from Windows drivers? 
> I think about a tool to sniff communication between the driver and the sound 
> card? or read information from the sound card under windows?

Sometimes you have some data in *.INF file or such.  At least, if the
standard Windows driver (not the h/w vendor's one) works, the extra
configuration is usually put there.

Also, when you test the sound, don't use PulseAudio but test directly
with ALSA native apps (e.g. aplay with -Dhw:0 or -Dplughw:0, etc).
You can use speaker-test program, too.

And always try a headphone output at first.  The headset mic might not
work, but the headphone output is usually the easiest one to get
working.


Takashi

> Reverse engineering the Windows driver would lead to the solution but will be 
> very long for me since I'm not familiar with the Intel HDA card and how this 
> Realtek chip internally works.
> Don't hesitate if you have any hints which could help me (and all the other 
> users of this laptop..)
> Cheers, 
> 
> Aurélien
> 
> Le lundi 17 février 2020, 09:00:42 CET Takashi Iwai a écrit :
> > On Sat, 15 Feb 2020 17:56:58 +0100,
> > 
> > Aurélien Croc wrote:
> > > Dear ALSA community,
> > > 
> > > I just bought a Samsung Galaxy book 12" laptop and I installed the latest
> > > Fedora version (31) on it. Unfortunately when I try to listen something
> > > there is absolutely no sound from speaker nor headsets. I checked that
> > > volumes of the different channels were max. I also checked for muting
> > > system but I didn't found anything.
> > > Of course it works perfectly under Windows.
> > > I saw on internet that many ALC298 users had troubles with it. I tried
> > > different options to the intel hda driver (especially the model one) but
> > > it
> > > changes nothing.
> > > 
> > > Here is the alsa-info.sh output: http://alsa-project.org/db/?
> > > f=871881e295972b9ecf252b25e90d659e38d939b8
> > > I would appreciate some help in order to find a solution.
> > > Tell me if you need more information.
> > > Thanks in advance.
> > 
> > The BIOS seems broken, it just sets a single output pin.
> > You need to try to figure out the pin connections, e.g. via
> > hdajackretask program.  The headphone might work with that.
> > But the speaker output might need another special handling, and it's
> > nothing but trial-and-test with the existing quirks for similar
> > devices.  Take a look at sound/pci/hda/patch_realtek.c.
> > 
> > 
> > Takashi
> 
> 
> 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel