[alsa-devel] model needed for Clevo P150HM (Realtek ALC892)

Takashi Iwai tiwai at suse.de
Mon Jul 18 10:52:55 CEST 2011


At Mon, 18 Jul 2011 09:35:33 +0200,
Takashi Iwai wrote:
> 
> At Sun, 17 Jul 2011 14:17:22 +0200,
> Julian Sikorski wrote:
> > 
> > W dniu 17.07.2011 13:55, Julian Sikorski pisze:
> > > W dniu 05.07.2011 03:31, Raymond Yau pisze:
> > >> 2011/7/5 Julian Sikorski<belegdol at gmail.com>:
> > >>
> > >>> From what I was able to decipher, 0x1e is a jack, external rear, with
> > >>> spdif out default output and optical connection. It is black. The same
> > >>> physical socket is used for the last 2 surround channels. Could you
> > >>> please clarify? Thanks in advance.
> > >>
> > >> Take a look at Block Diagram of alc892 datasheet
> > >>
> > >> http://www.realtek.com/products/productsView.aspx?Langid=1&PNid=24&PFid=28&Level=5&Conn=4&ProdID=284
> > >>
> > >>
> > >> if you can confirmed the internal mic, mic jack ,line in , line out
> > >> and internal speaker work as expected
> > >>
> > >> the only pin complex which can be connected to rear [Audio Output]
> > >> 0x0d is 0x15
> > >>
> > >> seem that the pin complex for 4 jack 8-ch notebook are different from
> > >> desktop with 6 jacks at rear panel
> > >>
> > >> a 10 channel codec is able to provide volume control for internal
> > >> speaker and 4 jacks
> > >
> > > Thanks to Raymond's advice I was finally able to make the sound come out
> > > of the copper part of the spdif/side surround jack. I am pasting the
> > > diff created with hda-analyzer, please let me know if this gives you
> > > enough information to add proper 7.1 sound support for this laptop.
> > > Here is the alsa-info.sh with all jacks playing sound:
> > > http://www.alsa-project.org/db/?f=8f23e499727ec612ed925b81d3f38928e8f6aebb
> > > Of course, there is still no specific volume control for the side channel.
> > >
> > > Julian
> > >
> > 
> > Upon further investigation I discovered that with the volume on the 0x17 
> > can be controlled with center/lfe in alsamixer. I don't think it is the 
> > intended behaviour.
> 
> Is it with the very latest alsa-driver snapshot?

And I can't reproduce your problem with the alsa-info.sh output above.
Give more exact information what you did and what is the problem.


thanks,

Takashi


More information about the Alsa-devel mailing list