Comment # 10 on bug 1233298 from Takashi Iwai

(In reply to Ralf Habacker from comment #8)
> Created attachment 878691 [details]
> hdajackretask screenshot
> 
> (In reply to Takashi Iwai from comment #6)
> > Then it's likely some missing speaker configuration.
> 
> With hdajackretask, the configuration can be seen in the attached screenshot.
> 
> What i cannot see there is the 'speaker_outs' compared with the dmesg output 
> 
> snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VC: line_outs=1
> (0x14/0x0/0x0/0x0/0x0) type:speaker

So the speaker has been already picked up here from NID 0x14 (see "type:
speaker").

That said, the pin configuration itself looks OK.  But it doesn't mean that the
correct pin is selected.  You can try different pins and check whether it makes
any difference in the speaker output, too.

(In reply to Ralf Habacker from comment #7)
> (In reply to Takashi Iwai from comment #6)
> > Then it's likely some missing speaker configuration.
> 
> > But it's not trivial at all, because there are hundreds of different
> > implementations for that, in all vendor-specific ways.
> 
> I did found a similar report for linux Mint
> https://forums.linuxmint.com/viewtopic.php?t=416919. Will try using
> `LC_ALL=C pacmd list sinks` to see if it is identical 

It's not about pulseaudio since the headphone works.
And, for testing the output, better to test via raw ALSA API, e.g.
  % speaker-test -twav -c2 -Dhw:0

while turning off other applications' sound.  (Usually the runtime suspend is
kicked in, and you can use the device exclusively.  If not, you'd need to turn
off pulseaudio via pasuspender temporarily.)

> > - Trial-and-error of existing quirks
> 
> I looked at
> https://www.kernel.org/doc/html/latest/sound/hd-audio/models.html but did
> not found any ALC269VC speaker specific settings.

ALC269VC is compatible with ALC269, and there are over 800 quirk entries for
those chips:
 
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/tree/sound/pci/hda/patch_realtek.c#n10085

In the link above, there is a big table of alc269_fixup_table[], and each entry
has the SSID (e.g. 1025:0283 for the first entry).  You can pass the model
option for snd-hda-intel module in the form of "XXXX:YYYY", e.g. boot with

   snd_hda_intel.model=1025:0283

boot option for applying the same quirk entry as the device 1025:0283 (Acer
TravelMate 837 in this case).  That's what I mentioned -- you can do
trial-and-error for all those entries, and it's a huge list.
Maybe you'd better to figure out a similar model and try those at first.