no front speaker sound with ALC262

no front speaker sound with ALC262

[Rene Dohmen]

Dear List,

I have a problem with an Intel HDA soundcard
lspci output:
-----
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 01)

The sound volume is very very low when i use the headphone output. The
device has integrated speakers but i don't hear any sound coming out of them
(maybe because the volume is so low...). I've put all the mixer channels to
the maximum values. When booted in Win XP the soundcard works correctly.

Is see one line in my logs that indicate that something is wrong: hda_codec:
Unknown model for ALC262, trying auto-probe from BIOS...

I didn't have it working with other versions of ALSA.  Tested with
1.0.14(provided with ubunty gutsy), then started reading, lots of
suggestions
stated that the problem would be solved in 1.0.15, so i compiled 1.0.16 from
src and replaced the default alsa modules with the new ones.

De device i 'm using is supplied by tangent (
http://www.tangent.com/t_all_in_one_LCDPC/vita_8000s.htm) its an all in one
solution with touchscreen and speakers integrated in one small cabinet.

I runned the alsa-info.sh script output and uploaded it:
http://pastebin.ca/913865

I don't know if this is the correct place for getting help but all help is
appreciated,

Best Regards,
Rene Dohmen

Re: no front speaker sound with ALC262

[Matthew R. Hurne]

Rene Dohmen wrote:
> Dear List,
> 
> I have a problem with an Intel HDA soundcard
> lspci output:
> -----
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
> Audio Controller (rev 01)
> 
> The sound volume is very very low when i use the headphone output. The
> device has integrated speakers but i don't hear any sound coming out of them
> (maybe because the volume is so low...). I've put all the mixer channels to
> the maximum values. When booted in Win XP the soundcard works correctly.
> 
> Is see one line in my logs that indicate that something is wrong: hda_codec:
> Unknown model for ALC262, trying auto-probe from BIOS...
> 
> I didn't have it working with other versions of ALSA.  Tested with
> 1.0.14(provided with ubunty gutsy), then started reading, lots of
> suggestions
> stated that the problem would be solved in 1.0.15, so i compiled 1.0.16 from
> src and replaced the default alsa modules with the new ones.
> 
> De device i 'm using is supplied by tangent (
> http://www.tangent.com/t_all_in_one_LCDPC/vita_8000s.htm) its an all in one
> solution with touchscreen and speakers integrated in one small cabinet.
> 
> I runned the alsa-info.sh script output and uploaded it:
> http://pastebin.ca/913865
> 
> I don't know if this is the correct place for getting help but all help is
> appreciated,

I have the exact same issue, Rene.  So far not much progress has been made - unfortunately I'm an ALSA user, not an ALSA developer.  I did create a bug here:

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3725 (that's bug ID 0003725)

I suspect the issue boils down to the driver not recognizing the way things are "wired" together.  See the bug report for more details about what I've done thus far, which is essentially collection of as much information as possible for the ALSA developers to use in troubleshooting the issue.

Regards,
Matt Hurne

Re: no front speaker sound with ALC262

[Matthew R. Hurne]

Matthew R. Hurne wrote:
> Rene Dohmen wrote:
>> Dear List,
>>
>> I have a problem with an Intel HDA soundcard
>> lspci output:
>> -----
>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
>> Audio Controller (rev 01)
>>
>> The sound volume is very very low when i use the headphone output. The
>> device has integrated speakers but i don't hear any sound coming out of them
>> (maybe because the volume is so low...). I've put all the mixer channels to
>> the maximum values. When booted in Win XP the soundcard works correctly.
>>
>> Is see one line in my logs that indicate that something is wrong: hda_codec:
>> Unknown model for ALC262, trying auto-probe from BIOS...
>>
>> I didn't have it working with other versions of ALSA.  Tested with
>> 1.0.14(provided with ubunty gutsy), then started reading, lots of
>> suggestions
>> stated that the problem would be solved in 1.0.15, so i compiled 1.0.16 from
>> src and replaced the default alsa modules with the new ones.
>>
>> De device i 'm using is supplied by tangent (
>> http://www.tangent.com/t_all_in_one_LCDPC/vita_8000s.htm) its an all in one
>> solution with touchscreen and speakers integrated in one small cabinet.
>>
>> I runned the alsa-info.sh script output and uploaded it:
>> http://pastebin.ca/913865
>>
>> I don't know if this is the correct place for getting help but all help is
>> appreciated,
> 
> I have the exact same issue, Rene.  So far not much progress has been made - unfortunately I'm an ALSA user, not an ALSA developer.  I did create a bug here:
> 
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3725 (that's bug ID 0003725)
> 
> I suspect the issue boils down to the driver not recognizing the way things are "wired" together.  See the bug report for more details about what I've done thus far, which is essentially collection of as much information as possible for the ALSA developers to use in troubleshooting the issue.
> 
> Regards,
> Matt Hurne

I added your message to the mailing list as a note on the bug report as well, Rene.

Thanks,
Matt

Re: no front speaker sound with ALC262

[Rene Dohmen]

Hi List,

Is there any chance that this bug will be fixed soon?

I did some C/C++ progtramming in the last years and i'm willing to  
help where possible.
But I am new to Open Source Development with a community of  
developers and users.

Regards,
	Rene Dohmen



Op Feb 23, 2008, om 3:29 AM heeft Matthew R. Hurne het volgende  
geschreven:

> Matthew R. Hurne wrote:
>> Rene Dohmen wrote:
>>> Dear List,
>>>
>>> I have a problem with an Intel HDA soundcard
>>> lspci output:
>>> -----
>>> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High  
>>> Definition
>>> Audio Controller (rev 01)
>>>
>>> The sound volume is very very low when i use the headphone  
>>> output. The
>>> device has integrated speakers but i don't hear any sound coming  
>>> out of them
>>> (maybe because the volume is so low...). I've put all the mixer  
>>> channels to
>>> the maximum values. When booted in Win XP the soundcard works  
>>> correctly.
>>>
>>> Is see one line in my logs that indicate that something is wrong:  
>>> hda_codec:
>>> Unknown model for ALC262, trying auto-probe from BIOS...
>>>
>>> I didn't have it working with other versions of ALSA.  Tested with
>>> 1.0.14(provided with ubunty gutsy), then started reading, lots of
>>> suggestions
>>> stated that the problem would be solved in 1.0.15, so i compiled  
>>> 1.0.16 from
>>> src and replaced the default alsa modules with the new ones.
>>>
>>> De device i 'm using is supplied by tangent (
>>> http://www.tangent.com/t_all_in_one_LCDPC/vita_8000s.htm) its an  
>>> all in one
>>> solution with touchscreen and speakers integrated in one small  
>>> cabinet.
>>>
>>> I runned the alsa-info.sh script output and uploaded it:
>>> http://pastebin.ca/913865
>>>
>>> I don't know if this is the correct place for getting help but  
>>> all help is
>>> appreciated,
>>
>> I have the exact same issue, Rene.  So far not much progress has  
>> been made - unfortunately I'm an ALSA user, not an ALSA  
>> developer.  I did create a bug here:
>>
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3725  
>> (that's bug ID 0003725)
>>
>> I suspect the issue boils down to the driver not recognizing the  
>> way things are "wired" together.  See the bug report for more  
>> details about what I've done thus far, which is essentially  
>> collection of as much information as possible for the ALSA  
>> developers to use in troubleshooting the issue.
>>
>> Regards,
>> Matt Hurne
>
> I added your message to the mailing list as a note on the bug  
> report as well, Rene.
>
> Thanks,
> Matt

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Mon, 25 Feb 2008 13:49:43 +0100,
Rene Dohmen wrote:
> 
> Hi List,
> 
> Is there any chance that this bug will be fixed soon?

Well, it's up to you.

One of the problems is that BIOS on your machine doesn't give the
useful information for auto-probing at all.  A typical workaround in
such a case is to try the existing preset models.  Pass model=basic or
model=benq to snd-hda-intel module, for example.  The available model
values can be found in ALSA-Configuration.txt.  Don't forget to
check and adjust the mixer status again after changing the model
because the mixers appear completly differently depending on the
model.

If none of the existing models doesn't match with your device, we have
to figure out the exact codec configuration.  For some codecs like
ALC880 or ALC260, you have model=test option that allows you to test
all codec configurations via mixer interface.  Unfortunately, ALC262
has no model=test support, so you have to do check it literally
manually.  Below is a brief instruction how to explore the mysterious
world of HD-audio codecs.

First of all, install the very latest ALSA HG version.  Don't stick
with 1.0.16 release.  You can use the daily snapshot tarball instead,
too.

Then, get hda-verb program found on
	ftp://ftp.suse.com/pub/people/tiwai/misc/
Extract the tarball, run make.  Install it or invoke it locally.  This
program can be usable only as root.

The next step is to get ALC262 datasheet from Realtek web site.  Take
a look at the block diagram page.  There are pins in the right side
and two DACs in the left side.  We have to set up the correct pins and
connect to the DAC properly.

Now, assume the port-D (NID 0x14) is the speaker output.  Check
/proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
entry like the following:

	Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
	  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
	  Amp-In vals:  [0x00 0x00] [0x00 0x00]
	  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
	  Amp-Out vals:  [0x80 0x80]
	  Pincap 0x083e: IN OUT HP Detect Trigger
	  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
	    Conn = 1/8, Color = Black
	    DefAssociation = 0xf, Sequence = 0x0
	    Misc = NO_PRESENCE
	  Pin-ctls: 0x20: IN
	  Unsolicited: tag=00, enabled=0
	  Connection: 2
	     0x0c* 0x0d

For this widget, we have a couple of things to do: fix the pin type,
adjust the amp and check the connection.  First, change the pin type
to the correct one, the output type.  Usually, it's either 0x40 or
0xc0.  The latter type is with a headphone amplifier.  Let's take
0xc0 as an example.  Call hda-verb like below (as root user):

	# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0

Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
properly.  Similarly, unmute the output volume of this widget with
hda-verb.  For this, pass 0xb000 to SET_AMP verb:

	# hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000

0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
matter because this widget has no volume but only mute control.)

In the example above, this pin is connected from the NID 0x0c, which
is a mixer amp.  That's fine and let's keep as is.
Check this widget 0x0c whether the first Amp-In vals is unmuted
(i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
to the DAC, 0x02, directly.  If it's muted, call like below 

	# hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000

0x7000 means to set the AMP-input of the first element (index 0) to
0x00.  For the second element, it'd be 0x7100.

OK, all set ready.  Try aplay and pray.  If this doesn't work, try
other ports as well until you find a gold mine.

You could check the inputs similarly if anything doesn't work.
Once after you figure out all pin configurations, we can create a new
model (or fix the existing model) to adapt your device.

Have fun,


Takashi

Re: no front speaker sound with ALC262

[Rene Dohmen]

Thnx for your answer.
The preset models ( i tested the ones in 1.0.16 didn't work so i'll  
have a try with the latest HG version)

Having fun,

	Rene

Op Feb 26, 2008, om 1:10 PM heeft Takashi Iwai het volgende geschreven:

> At Mon, 25 Feb 2008 13:49:43 +0100,
> Rene Dohmen wrote:
>>
>> Hi List,
>>
>> Is there any chance that this bug will be fixed soon?
>
> Well, it's up to you.
>
> One of the problems is that BIOS on your machine doesn't give the
> useful information for auto-probing at all.  A typical workaround in
> such a case is to try the existing preset models.  Pass model=basic or
> model=benq to snd-hda-intel module, for example.  The available model
> values can be found in ALSA-Configuration.txt.  Don't forget to
> check and adjust the mixer status again after changing the model
> because the mixers appear completly differently depending on the
> model.
>
> If none of the existing models doesn't match with your device, we have
> to figure out the exact codec configuration.  For some codecs like
> ALC880 or ALC260, you have model=test option that allows you to test
> all codec configurations via mixer interface.  Unfortunately, ALC262
> has no model=test support, so you have to do check it literally
> manually.  Below is a brief instruction how to explore the mysterious
> world of HD-audio codecs.
>
> First of all, install the very latest ALSA HG version.  Don't stick
> with 1.0.16 release.  You can use the daily snapshot tarball instead,
> too.
>
> Then, get hda-verb program found on
> 	ftp://ftp.suse.com/pub/people/tiwai/misc/
> Extract the tarball, run make.  Install it or invoke it locally.  This
> program can be usable only as root.
>
> The next step is to get ALC262 datasheet from Realtek web site.  Take
> a look at the block diagram page.  There are pins in the right side
> and two DACs in the left side.  We have to set up the correct pins and
> connect to the DAC properly.
>
> Now, assume the port-D (NID 0x14) is the speaker output.  Check
> /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
> entry like the following:
>
> 	Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> 	  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> 	  Amp-In vals:  [0x00 0x00] [0x00 0x00]
> 	  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> 	  Amp-Out vals:  [0x80 0x80]
> 	  Pincap 0x083e: IN OUT HP Detect Trigger
> 	  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> 	    Conn = 1/8, Color = Black
> 	    DefAssociation = 0xf, Sequence = 0x0
> 	    Misc = NO_PRESENCE
> 	  Pin-ctls: 0x20: IN
> 	  Unsolicited: tag=00, enabled=0
> 	  Connection: 2
> 	     0x0c* 0x0d
>
> For this widget, we have a couple of things to do: fix the pin type,
> adjust the amp and check the connection.  First, change the pin type
> to the correct one, the output type.  Usually, it's either 0x40 or
> 0xc0.  The latter type is with a headphone amplifier.  Let's take
> 0xc0 as an example.  Call hda-verb like below (as root user):
>
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
>
> Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
> properly.  Similarly, unmute the output volume of this widget with
> hda-verb.  For this, pass 0xb000 to SET_AMP verb:
>
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
>
> 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
> 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
> matter because this widget has no volume but only mute control.)
>
> In the example above, this pin is connected from the NID 0x0c, which
> is a mixer amp.  That's fine and let's keep as is.
> Check this widget 0x0c whether the first Amp-In vals is unmuted
> (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
> to the DAC, 0x02, directly.  If it's muted, call like below
>
> 	# hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
>
> 0x7000 means to set the AMP-input of the first element (index 0) to
> 0x00.  For the second element, it'd be 0x7100.
>
> OK, all set ready.  Try aplay and pray.  If this doesn't work, try
> other ports as well until you find a gold mine.
>
> You could check the inputs similarly if anything doesn't work.
> Once after you figure out all pin configurations, we can create a new
> model (or fix the existing model) to adapt your device.
>
> Have fun,
>
>
> Takashi

Re: no front speaker sound with ALC262

[Matthew R. Hurne]

Takashi Iwai wrote:
> At Mon, 25 Feb 2008 13:49:43 +0100,
> Rene Dohmen wrote:
>> Hi List,
>>
>> Is there any chance that this bug will be fixed soon?
> 
> Well, it's up to you.
> 
> One of the problems is that BIOS on your machine doesn't give the
> useful information for auto-probing at all.  A typical workaround in
> such a case is to try the existing preset models.  Pass model=basic or
> model=benq to snd-hda-intel module, for example.  The available model
> values can be found in ALSA-Configuration.txt.  Don't forget to
> check and adjust the mixer status again after changing the model
> because the mixers appear completly differently depending on the
> model.
> 
> If none of the existing models doesn't match with your device, we have
> to figure out the exact codec configuration.  For some codecs like
> ALC880 or ALC260, you have model=test option that allows you to test
> all codec configurations via mixer interface.  Unfortunately, ALC262
> has no model=test support, so you have to do check it literally
> manually.  Below is a brief instruction how to explore the mysterious
> world of HD-audio codecs.
> 
> First of all, install the very latest ALSA HG version.  Don't stick
> with 1.0.16 release.  You can use the daily snapshot tarball instead,
> too.
> 
> Then, get hda-verb program found on
> 	ftp://ftp.suse.com/pub/people/tiwai/misc/
> Extract the tarball, run make.  Install it or invoke it locally.  This
> program can be usable only as root.
> 
> The next step is to get ALC262 datasheet from Realtek web site.  Take
> a look at the block diagram page.  There are pins in the right side
> and two DACs in the left side.  We have to set up the correct pins and
> connect to the DAC properly.
> 
> Now, assume the port-D (NID 0x14) is the speaker output.  Check
> /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
> entry like the following:
> 
> 	Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> 	  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> 	  Amp-In vals:  [0x00 0x00] [0x00 0x00]
> 	  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> 	  Amp-Out vals:  [0x80 0x80]
> 	  Pincap 0x083e: IN OUT HP Detect Trigger
> 	  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> 	    Conn = 1/8, Color = Black
> 	    DefAssociation = 0xf, Sequence = 0x0
> 	    Misc = NO_PRESENCE
> 	  Pin-ctls: 0x20: IN
> 	  Unsolicited: tag=00, enabled=0
> 	  Connection: 2
> 	     0x0c* 0x0d
> 
> For this widget, we have a couple of things to do: fix the pin type,
> adjust the amp and check the connection.  First, change the pin type
> to the correct one, the output type.  Usually, it's either 0x40 or
> 0xc0.  The latter type is with a headphone amplifier.  Let's take
> 0xc0 as an example.  Call hda-verb like below (as root user):
> 
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
> 
> Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
> properly.  Similarly, unmute the output volume of this widget with
> hda-verb.  For this, pass 0xb000 to SET_AMP verb:
> 
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
> 
> 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
> 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
> matter because this widget has no volume but only mute control.)
> 
> In the example above, this pin is connected from the NID 0x0c, which
> is a mixer amp.  That's fine and let's keep as is.
> Check this widget 0x0c whether the first Amp-In vals is unmuted
> (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
> to the DAC, 0x02, directly.  If it's muted, call like below 
> 
> 	# hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
> 
> 0x7000 means to set the AMP-input of the first element (index 0) to
> 0x00.  For the second element, it'd be 0x7100.
> 
> OK, all set ready.  Try aplay and pray.  If this doesn't work, try
> other ports as well until you find a gold mine.
> 
> You could check the inputs similarly if anything doesn't work.
> Once after you figure out all pin configurations, we can create a new
> model (or fix the existing model) to adapt your device.
> 
> Have fun,
> 
> 
> Takashi

Thanks, Takashi!  If it so happens I have the time, I will try to play with this in tandem to Rene.

Regards,
-- 
Matthew Hurne
Versatile Systems, Inc.
717.919.9102
matthew.hurne@versatile.com

Re: no front speaker sound with ALC262

[Rene Dohmen]

Hi,

I compiled the HG version. The driver behaves in the exact same way as the
1.0.16 version. Very very low volume on the headphone output, like hearing
sound form another channel on a mixer because of crosstalk (i don't know is
this is the correct translation).

I also compiled hda_verb and used it to twiddle around with some of the
connections. So far no luck.

Can I do something to boost the volume level? Or is this also caused by the
incorrect pin wiring of the device? Maybe the speakers do output some sound
but because of the the low soundlevel i can't hear it.

Thanks,

Rene


On Tue, Feb 26, 2008 at 1:21 PM, Rene Dohmen <acidjunk@gmail.com> wrote:

> Thnx for your answer.
> The preset models ( i tested the ones in 1.0.16 didn't work so i'll
> have a try with the latest HG version)
>
> Having fun,
>
>        Rene
>
> Op Feb 26, 2008, om 1:10 PM heeft Takashi Iwai het volgende geschreven:
>
> > At Mon, 25 Feb 2008 13:49:43 +0100,
> > Rene Dohmen wrote:
> >>
> >> Hi List,
> >>
> >> Is there any chance that this bug will be fixed soon?
> >
> > Well, it's up to you.
> >
> > One of the problems is that BIOS on your machine doesn't give the
> > useful information for auto-probing at all.  A typical workaround in
> > such a case is to try the existing preset models.  Pass model=basic or
> > model=benq to snd-hda-intel module, for example.  The available model
> > values can be found in ALSA-Configuration.txt.  Don't forget to
> > check and adjust the mixer status again after changing the model
> > because the mixers appear completly differently depending on the
> > model.
> >
> > If none of the existing models doesn't match with your device, we have
> > to figure out the exact codec configuration.  For some codecs like
> > ALC880 or ALC260, you have model=test option that allows you to test
> > all codec configurations via mixer interface.  Unfortunately, ALC262
> > has no model=test support, so you have to do check it literally
> > manually.  Below is a brief instruction how to explore the mysterious
> > world of HD-audio codecs.
> >
> > First of all, install the very latest ALSA HG version.  Don't stick
> > with 1.0.16 release.  You can use the daily snapshot tarball instead,
> > too.
> >
> > Then, get hda-verb program found on
> >       ftp://ftp.suse.com/pub/people/tiwai/misc/
> > Extract the tarball, run make.  Install it or invoke it locally.  This
> > program can be usable only as root.
> >
> > The next step is to get ALC262 datasheet from Realtek web site.  Take
> > a look at the block diagram page.  There are pins in the right side
> > and two DACs in the left side.  We have to set up the correct pins and
> > connect to the DAC properly.
> >
> > Now, assume the port-D (NID 0x14) is the speaker output.  Check
> > /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
> > entry like the following:
> >
> >       Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> >         Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> >         Amp-In vals:  [0x00 0x00] [0x00 0x00]
> >         Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> >         Amp-Out vals:  [0x80 0x80]
> >         Pincap 0x083e: IN OUT HP Detect Trigger
> >         Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> >           Conn = 1/8, Color = Black
> >           DefAssociation = 0xf, Sequence = 0x0
> >           Misc = NO_PRESENCE
> >         Pin-ctls: 0x20: IN
> >         Unsolicited: tag=00, enabled=0
> >         Connection: 2
> >            0x0c* 0x0d
> >
> > For this widget, we have a couple of things to do: fix the pin type,
> > adjust the amp and check the connection.  First, change the pin type
> > to the correct one, the output type.  Usually, it's either 0x40 or
> > 0xc0.  The latter type is with a headphone amplifier.  Let's take
> > 0xc0 as an example.  Call hda-verb like below (as root user):
> >
> >       # hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
> >
> > Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
> > properly.  Similarly, unmute the output volume of this widget with
> > hda-verb.  For this, pass 0xb000 to SET_AMP verb:
> >
> >       # hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
> >
> > 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
> > 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
> > matter because this widget has no volume but only mute control.)
> >
> > In the example above, this pin is connected from the NID 0x0c, which
> > is a mixer amp.  That's fine and let's keep as is.
> > Check this widget 0x0c whether the first Amp-In vals is unmuted
> > (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
> > to the DAC, 0x02, directly.  If it's muted, call like below
> >
> >       # hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
> >
> > 0x7000 means to set the AMP-input of the first element (index 0) to
> > 0x00.  For the second element, it'd be 0x7100.
> >
> > OK, all set ready.  Try aplay and pray.  If this doesn't work, try
> > other ports as well until you find a gold mine.
> >
> > You could check the inputs similarly if anything doesn't work.
> > Once after you figure out all pin configurations, we can create a new
> > model (or fix the existing model) to adapt your device.
> >
> > Have fun,
> >
> >
> > Takashi
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Wed, 27 Feb 2008 00:19:58 +0100,
Rene Dohmen wrote:
> 
> Hi,
> 
> I compiled the HG version. The driver behaves in the exact same way as the
> 1.0.16 version. Very very low volume on the headphone output, like hearing sound
> form another channel on a mixer because of crosstalk (i don't know is this is
> the correct translation).

And is it so with all module options?

> I also compiled hda_verb and used it to twiddle around with some of the
> connections. So far no luck.
> 
> Can I do something to boost the volume level? Or is this also caused by the
> incorrect pin wiring of the device? Maybe the speakers do output some sound but
> because of the the low soundlevel i can't hear it.

EAPD might be the case.  Set via "SET_EAPD 0x02" to turn on the
amplifier (if any).


Takashi

> 
> Thanks,
> 
> Rene
> 
> On Tue, Feb 26, 2008 at 1:21 PM, Rene Dohmen <acidjunk@gmail.com> wrote:
> 
>     Thnx for your answer.
>     The preset models ( i tested the ones in 1.0.16 didn't work so i'll
>     have a try with the latest HG version)
>    
>     Having fun,
>    
>            Rene
>    
>     Op Feb 26, 2008, om 1:10 PM heeft Takashi Iwai het volgende geschreven:
>    
>     > At Mon, 25 Feb 2008 13:49:43 +0100,
>     > Rene Dohmen wrote:
>     >>
>     >> Hi List,
>     >>
>     >> Is there any chance that this bug will be fixed soon?
>     >
>     > Well, it's up to you.
>     >
>     > One of the problems is that BIOS on your machine doesn't give the
>     > useful information for auto-probing at all.  A typical workaround in
>     > such a case is to try the existing preset models.  Pass model=basic or
>     > model=benq to snd-hda-intel module, for example.  The available model
>     > values can be found in ALSA-Configuration.txt.  Don't forget to
>     > check and adjust the mixer status again after changing the model
>     > because the mixers appear completly differently depending on the
>     > model.
>     >
>     > If none of the existing models doesn't match with your device, we have
>     > to figure out the exact codec configuration.  For some codecs like
>     > ALC880 or ALC260, you have model=test option that allows you to test
>     > all codec configurations via mixer interface.  Unfortunately, ALC262
>     > has no model=test support, so you have to do check it literally
>     > manually.  Below is a brief instruction how to explore the mysterious
>     > world of HD-audio codecs.
>     >
>     > First of all, install the very latest ALSA HG version.  Don't stick
>     > with 1.0.16 release.  You can use the daily snapshot tarball instead,
>     > too.
>     >
>     > Then, get hda-verb program found on
>     >       ftp://ftp.suse.com/pub/people/tiwai/misc/
>     > Extract the tarball, run make.  Install it or invoke it locally.  This
>     > program can be usable only as root.
>     >
>     > The next step is to get ALC262 datasheet from Realtek web site.  Take
>     > a look at the block diagram page.  There are pins in the right side
>     > and two DACs in the left side.  We have to set up the correct pins and
>     > connect to the DAC properly.
>     >
>     > Now, assume the port-D (NID 0x14) is the speaker output.  Check
>     > /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
>     > entry like the following:
>     >
>     >       Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
>     >         Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
>     >         Amp-In vals:  [0x00 0x00] [0x00 0x00]
>     >         Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
>     >         Amp-Out vals:  [0x80 0x80]
>     >         Pincap 0x083e: IN OUT HP Detect Trigger
>     >         Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
>     >           Conn = 1/8, Color = Black
>     >           DefAssociation = 0xf, Sequence = 0x0
>     >           Misc = NO_PRESENCE
>     >         Pin-ctls: 0x20: IN
>     >         Unsolicited: tag=00, enabled=0
>     >         Connection: 2
>     >            0x0c* 0x0d
>     >
>     > For this widget, we have a couple of things to do: fix the pin type,
>     > adjust the amp and check the connection.  First, change the pin type
>     > to the correct one, the output type.  Usually, it's either 0x40 or
>     > 0xc0.  The latter type is with a headphone amplifier.  Let's take
>     > 0xc0 as an example.  Call hda-verb like below (as root user):
>     >
>     >       # hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
>     >
>     > Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
>     > properly.  Similarly, unmute the output volume of this widget with
>     > hda-verb.  For this, pass 0xb000 to SET_AMP verb:
>     >
>     >       # hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
>     >
>     > 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
>     > 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
>     > matter because this widget has no volume but only mute control.)
>     >
>     > In the example above, this pin is connected from the NID 0x0c, which
>     > is a mixer amp.  That's fine and let's keep as is.
>     > Check this widget 0x0c whether the first Amp-In vals is unmuted
>     > (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
>     > to the DAC, 0x02, directly.  If it's muted, call like below
>     >
>     >       # hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
>     >
>     > 0x7000 means to set the AMP-input of the first element (index 0) to
>     > 0x00.  For the second element, it'd be 0x7100.
>     >
>     > OK, all set ready.  Try aplay and pray.  If this doesn't work, try
>     > other ports as well until you find a gold mine.
>     >
>     > You could check the inputs similarly if anything doesn't work.
>     > Once after you figure out all pin configurations, we can create a new
>     > model (or fix the existing model) to adapt your device.
>     >
>     > Have fun,
>     >
>     >
>     > Takashi
>    
>     _______________________________________________
>     Alsa-devel mailing list
>     Alsa-devel@alsa-project.org
>     http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 
> 

Re: no front speaker sound with ALC262

[Rene Dohmen]

I tried it with all avalialable NIDS:

sudo ./hda-verb /dev/snd/hwC0D0  0x14 SET_EAPD 0x02
Is this correct?

And is it so with all module options?
>

Yes with all tested codecs: are there any more options that i can use?

Thanks,
 Rene

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Wed, 27 Feb 2008 19:16:23 +0100,
Rene Dohmen wrote:
> 
> I tried it with all avalialable NIDS:
> 
> sudo ./hda-verb /dev/snd/hwC0D0  0x14 SET_EAPD 0x02
> Is this correct?

Looks OK.  Check /proc/asound/card0/codec#0 after you run the
command.  The EAPD value shown there must be changed.

>     And is it so with all module options?
> 
> Yes with all tested codecs: are there any more options that i can use?

Did you figure out that 0x14 is really the speaker output?
You can check it by muting the AMP of this widget manually via
hda-verb command.


Takashi

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Thu, 28 Feb 2008 12:14:50 +0100,
I wrote:
> 
> At Wed, 27 Feb 2008 19:16:23 +0100,
> Rene Dohmen wrote:
> > 
> > I tried it with all avalialable NIDS:
> > 
> > sudo ./hda-verb /dev/snd/hwC0D0  0x14 SET_EAPD 0x02
> > Is this correct?
> 
> Looks OK.  Check /proc/asound/card0/codec#0 after you run the
> command.  The EAPD value shown there must be changed.
> 
> >     And is it so with all module options?
> > 
> > Yes with all tested codecs: are there any more options that i can use?
> 
> Did you figure out that 0x14 is really the speaker output?
> You can check it by muting the AMP of this widget manually via
> hda-verb command.

Err, disregard this comment, of course :)

AFAIK, ALC268 doesn't use GPIOs for EAPD controls but only EAPD
verbs.  So, setting EAPD on the widget should suffice.

Anyway, it'd be better to show codec#0 proc at the state you believe
that you've set up correctly but no sound comes out from the speaker.
Also, clarify what you've tested, too.


Takashi

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Fri, 29 Feb 2008 17:24:03 +0100,
Rene Dohmen wrote:
> 
> No I still don't know where the speakers are conencted.
> I asked the support engineers at tangent to send me a detailed  
> blockdiagram of their sound solution and ik think i'll receive that  
> sooner or later.
> 
> So, for now, I just tried passing the EAPD option to all NIDS in the  
> codec#0 file.
> 
> I attached the code#0 file while working with very low volume
> 
> When I run
> sudo hda-verb/hda-verb /dev/snd/hwC0D0  0x03 SET_EAPD 0x02
> or
> sudo hda-verb/hda-verb /dev/snd/hwC0D0  0x02 SET_EAPD 0x02

Doh, I actually misunderstood that your codec were ALC268 but it's
ALC262.  EAPD command can be issued only on widgets that support.
ALC262 has no EAPD pin caps at all. so it doesn't work like that.

Instead, ALC262 (and other Realtek codecs) has a special sequence with
coefficients to the vendor-defined widget.  Yes, it's a black magic.

Try the following sequence:

	0x20 SET_COEF_INDEX 0x07
	0x20 SET_PROC_COEF 0x3060

0x3060 can be different numbers like 0x3070 or 0x3050.
If you set a different number, reset the coef index again (i.e. always
call as a pair).


Takashi

Re: no front speaker sound with ALC262

[Rene Dohmen]

Hi List,

I tried it with the NID's i think are connected to headphone and  
speaker but so far no luck.

I'll have more time next friday but i was just wondering:
Is there a way to be 100% sure that this model is a new, not  
supported model yet?

Can you explain what numbers i can use instead of the 0x3060?

I am trying to get the datasheets of the soundsystem used, i think  
some custom board is used tot wire up the soundcard tot the internal  
speakers.

Thanks

Grz Rene


Op Feb 29, 2008, om 5:57 PM heeft Takashi Iwai het volgende geschreven:

> Instead, ALC262 (and other Realtek codecs) has a special sequence with
> coefficients to the vendor-defined widget.  Yes, it's a black magic.
>
> Try the following sequence:
>
> 	0x20 SET_COEF_INDEX 0x07
> 	0x20 SET_PROC_COEF 0x3060
>
> 0x3060 can be different numbers like 0x3070 or 0x3050.
> If you set a different number, reset the coef index again (i.e. always
> call as a pair).

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Tue, 4 Mar 2008 14:37:39 +0100,
Rene Dohmen wrote:
> 
> Hi List,
> 
> I tried it with the NID's i think are connected to headphone and speaker but so
> far no luck.

The coef verbs are only for the realtek vendor-specific widget, not
for other pins.

> I'll have more time next friday but i was just wondering:
> Is there a way to be 100% sure that this model is a new, not supported model
> yet?

No.  You'd better to ask the hardware vendor than me.  If the HG
version still doesn't work, it's not supported by ALSA driver yet.
That's all what I can tell.

> Can you explain what numbers i can use instead of the 0x3060?

Ask Realtek.  It's their black magic :)

> I am trying to get the datasheets of the soundsystem used, i think some custom
> board is used tot wire up the soundcard tot the internal speakers.

That's uncommon.  It's possible that BIOS or ACPI setup influences on
the behavior, but it's a rare case as well.


Takashi


> 
> Thanks
> 
> Grz Rene
> 
>  
> Op Feb 29, 2008, om 5:57 PM heeft Takashi Iwai het volgende geschreven:
> 
>     Instead, ALC262 (and other Realtek codecs) has a special sequence with
>    
>     coefficients to the vendor-defined widget.  Yes, it's a black magic.
> 
>     Try the following sequence:
> 
>     0x20 SET_COEF_INDEX 0x07
>    
>     0x20 SET_PROC_COEF 0x3060
> 
>     0x3060 can be different numbers like 0x3070 or 0x3050.
>    
>     If you set a different number, reset the coef index again (i.e. always
>    
>     call as a pair).
> 
> 

Re: no front speaker sound with ALC262

[Matthew R Hurne]

Rene Dohmen wrote:
> Hi List,
> 
> I tried it with the NID's i think are connected to headphone and  
> speaker but so far no luck.
> 
> I'll have more time next friday but i was just wondering:
> Is there a way to be 100% sure that this model is a new, not  
> supported model yet?
> 
> Can you explain what numbers i can use instead of the 0x3060?
> 
> I am trying to get the datasheets of the soundsystem used, i think  
> some custom board is used tot wire up the soundcard tot the internal  
> speakers.
> 
> Thanks
> 
> Grz Rene
> 
> 
> Op Feb 29, 2008, om 5:57 PM heeft Takashi Iwai het volgende geschreven:
> 
>> Instead, ALC262 (and other Realtek codecs) has a special sequence with
>> coefficients to the vendor-defined widget.  Yes, it's a black magic.
>>
>> Try the following sequence:
>>
>> 	0x20 SET_COEF_INDEX 0x07
>> 	0x20 SET_PROC_COEF 0x3060
>>
>> 0x3060 can be different numbers like 0x3070 or 0x3050.
>> If you set a different number, reset the coef index again (i.e. always
>> call as a pair).

Rene,
   Just wanted to let you know that if you still haven't gotten sound working with the Tangent 8000S (we haven't), you should look into its counterpart.  The Tangent 8000S is really the MSI Crystal 945 barebones unit, with parts installed and optionally Windows installed.  MSI has a newer unit with identical case and external connections - the Crystal A410 .  It uses an ATI chipset, but still an ALC262 codec.  We got one in today and audio "just worked" for us!  I suspect that the BIOS on the Crystal A410 is giving ALSA the info it needs when it auto-probes the BIOS, unlike the BIOS on the Crystal 945 (Tangent 8000S).  So, you might want to check it out.  Unfortunately for us, we already have several of the Crystal 945's deployed to customers, so we still need to try and resolve the audio 
 issue with those units.

Regards,
-- 
Matthew Hurne
Versatile Systems, Inc.
717.919.9102
matthew.hurne@versatile.com

Re: no front speaker sound with ALC262

[Matthew R Hurne]

Takashi Iwai wrote:
> At Mon, 25 Feb 2008 13:49:43 +0100,
> Rene Dohmen wrote:
>> Hi List,
>>
>> Is there any chance that this bug will be fixed soon?
> 
> Well, it's up to you.
> 
> One of the problems is that BIOS on your machine doesn't give the
> useful information for auto-probing at all.  A typical workaround in
> such a case is to try the existing preset models.  Pass model=basic or
> model=benq to snd-hda-intel module, for example.  The available model
> values can be found in ALSA-Configuration.txt.  Don't forget to
> check and adjust the mixer status again after changing the model
> because the mixers appear completly differently depending on the
> model.
> 
> If none of the existing models doesn't match with your device, we have
> to figure out the exact codec configuration.  For some codecs like
> ALC880 or ALC260, you have model=test option that allows you to test
> all codec configurations via mixer interface.  Unfortunately, ALC262
> has no model=test support, so you have to do check it literally
> manually.  Below is a brief instruction how to explore the mysterious
> world of HD-audio codecs.
> 
> First of all, install the very latest ALSA HG version.  Don't stick
> with 1.0.16 release.  You can use the daily snapshot tarball instead,
> too.
> 
> Then, get hda-verb program found on
> 	ftp://ftp.suse.com/pub/people/tiwai/misc/
> Extract the tarball, run make.  Install it or invoke it locally.  This
> program can be usable only as root.
> 
> The next step is to get ALC262 datasheet from Realtek web site.  Take
> a look at the block diagram page.  There are pins in the right side
> and two DACs in the left side.  We have to set up the correct pins and
> connect to the DAC properly.
> 
> Now, assume the port-D (NID 0x14) is the speaker output.  Check
> /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
> entry like the following:
> 
> 	Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> 	  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> 	  Amp-In vals:  [0x00 0x00] [0x00 0x00]
> 	  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> 	  Amp-Out vals:  [0x80 0x80]
> 	  Pincap 0x083e: IN OUT HP Detect Trigger
> 	  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> 	    Conn = 1/8, Color = Black
> 	    DefAssociation = 0xf, Sequence = 0x0
> 	    Misc = NO_PRESENCE
> 	  Pin-ctls: 0x20: IN
> 	  Unsolicited: tag=00, enabled=0
> 	  Connection: 2
> 	     0x0c* 0x0d
> 
> For this widget, we have a couple of things to do: fix the pin type,
> adjust the amp and check the connection.  First, change the pin type
> to the correct one, the output type.  Usually, it's either 0x40 or
> 0xc0.  The latter type is with a headphone amplifier.  Let's take
> 0xc0 as an example.  Call hda-verb like below (as root user):
> 
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
> 
> Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
> properly.  Similarly, unmute the output volume of this widget with
> hda-verb.  For this, pass 0xb000 to SET_AMP verb:
> 
> 	# hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
> 
> 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
> 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
> matter because this widget has no volume but only mute control.)
> 
> In the example above, this pin is connected from the NID 0x0c, which
> is a mixer amp.  That's fine and let's keep as is.
> Check this widget 0x0c whether the first Amp-In vals is unmuted
> (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
> to the DAC, 0x02, directly.  If it's muted, call like below 
> 
> 	# hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
> 
> 0x7000 means to set the AMP-input of the first element (index 0) to
> 0x00.  For the second element, it'd be 0x7100.
> 
> OK, all set ready.  Try aplay and pray.  If this doesn't work, try
> other ports as well until you find a gold mine.
> 
> You could check the inputs similarly if anything doesn't work.
> Once after you figure out all pin configurations, we can create a new
> model (or fix the existing model) to adapt your device.
> 
> Have fun,
> 
> 
> Takashi

Takashi,
   For my part, I have no idea what you're talking about.  That's not a criticism of you, its a criticism of myself.  :-)  Is there somewhere where things like "verb" and "NID" and "widget" are documented?  I skimmed through the driver development guide and didn't see such references.  I played with hda-verb briefly, but since I have no clue what I'm doing, decided that I'm better off trying to learn the fundamentals I need to understand before messing with hda-verb.  I know its tough dealing with someone like myself who is a user, not a developer (well, not a hardware driver developer, anyway).  I apologize for that.  Perhaps my company could send you a unit?  I'd have to discuss with them, but I suspect they would be willing to do so.

Thanks,
-- 
Matthew Hurne
Versatile Systems, Inc.
717.919.9102
matthew.hurne@versatile.com

Re: no front speaker sound with ALC262

[Tobin Davis]

I am finishing up my current course tomorrow night, and the next
{required} course I am taking is "Linux Fundamentals" - which is to say
I will have spare cycles to help out again on this.

Going through the message thread, you mentioned a Crystal A410 system
that works, whereas your Tangent 8000S does not.    It would be
interesting to recompile the drivers with "--with-debug=detect" and see
what shows up in dmesg (for alsa only, not the entire boot log).  Based
on that, we may be able to construct a driver model.  Also, if you have
access to the Crystal still, could you run alsa-info.sh on it as well?
I'd like to verify the audio subsystem ID.

In reviewing an earlier alsa-info posting, it shows your mixer as all
channels muted.  I'm assuming you tried changing the volume levels in
alsamixer?

At any rate, they list a 30 day trial unit.  I'll see if I can get one
for driver development.  Nothing ventured, nothing gained.

Tobin 




On Mon, 2008-03-17 at 13:07 -0400, Matthew R Hurne wrote:

> Takashi Iwai wrote:
> > At Mon, 25 Feb 2008 13:49:43 +0100,
> > Rene Dohmen wrote:
> >> Hi List,
> >>
> >> Is there any chance that this bug will be fixed soon?
> > 
> > Well, it's up to you.
> > 
> > One of the problems is that BIOS on your machine doesn't give the
> > useful information for auto-probing at all.  A typical workaround in
> > such a case is to try the existing preset models.  Pass model=basic or
> > model=benq to snd-hda-intel module, for example.  The available model
> > values can be found in ALSA-Configuration.txt.  Don't forget to
> > check and adjust the mixer status again after changing the model
> > because the mixers appear completly differently depending on the
> > model.
> > 
> > If none of the existing models doesn't match with your device, we have
> > to figure out the exact codec configuration.  For some codecs like
> > ALC880 or ALC260, you have model=test option that allows you to test
> > all codec configurations via mixer interface.  Unfortunately, ALC262
> > has no model=test support, so you have to do check it literally
> > manually.  Below is a brief instruction how to explore the mysterious
> > world of HD-audio codecs.
> > 
> > First of all, install the very latest ALSA HG version.  Don't stick
> > with 1.0.16 release.  You can use the daily snapshot tarball instead,
> > too.
> > 
> > Then, get hda-verb program found on
> > 	ftp://ftp.suse.com/pub/people/tiwai/misc/
> > Extract the tarball, run make.  Install it or invoke it locally.  This
> > program can be usable only as root.
> > 
> > The next step is to get ALC262 datasheet from Realtek web site.  Take
> > a look at the block diagram page.  There are pins in the right side
> > and two DACs in the left side.  We have to set up the correct pins and
> > connect to the DAC properly.
> > 
> > Now, assume the port-D (NID 0x14) is the speaker output.  Check
> > /proc/asound/card0/codec#0 and look for Node 0x14.  It may have the
> > entry like the following:
> > 
> > 	Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> > 	  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> > 	  Amp-In vals:  [0x00 0x00] [0x00 0x00]
> > 	  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
> > 	  Amp-Out vals:  [0x80 0x80]
> > 	  Pincap 0x083e: IN OUT HP Detect Trigger
> > 	  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
> > 	    Conn = 1/8, Color = Black
> > 	    DefAssociation = 0xf, Sequence = 0x0
> > 	    Misc = NO_PRESENCE
> > 	  Pin-ctls: 0x20: IN
> > 	  Unsolicited: tag=00, enabled=0
> > 	  Connection: 2
> > 	     0x0c* 0x0d
> > 
> > For this widget, we have a couple of things to do: fix the pin type,
> > adjust the amp and check the connection.  First, change the pin type
> > to the correct one, the output type.  Usually, it's either 0x40 or
> > 0xc0.  The latter type is with a headphone amplifier.  Let's take
> > 0xc0 as an example.  Call hda-verb like below (as root user):
> > 
> > 	# hda-verb /dev/snd/hwC0D0 0x14 SET_PIN_WID 0xc0
> > 
> > Check /proc/asound/card0/codec#0 again whether the pin-ctls is changed
> > properly.  Similarly, unmute the output volume of this widget with
> > hda-verb.  For this, pass 0xb000 to SET_AMP verb:
> > 
> > 	# hda-verb /dev/snd/hwC0D0 0x14 SET_AMP 0xb000
> > 
> > 0xb000 means to set the AMP-output to 0x00.  The mute bit is 0x80, so
> > 0x00 means to unmute and set the volume 0.  (The volume 0 doesn't
> > matter because this widget has no volume but only mute control.)
> > 
> > In the example above, this pin is connected from the NID 0x0c, which
> > is a mixer amp.  That's fine and let's keep as is.
> > Check this widget 0x0c whether the first Amp-In vals is unmuted
> > (i.e. has *no* 0x80 bit mask).  The first element of 0x0c is connected
> > to the DAC, 0x02, directly.  If it's muted, call like below 
> > 
> > 	# hda-verb /dev/snd/hwC0D0 0x0c SET_AMP 0x7000
> > 
> > 0x7000 means to set the AMP-input of the first element (index 0) to
> > 0x00.  For the second element, it'd be 0x7100.
> > 
> > OK, all set ready.  Try aplay and pray.  If this doesn't work, try
> > other ports as well until you find a gold mine.
> > 
> > You could check the inputs similarly if anything doesn't work.
> > Once after you figure out all pin configurations, we can create a new
> > model (or fix the existing model) to adapt your device.
> > 
> > Have fun,
> > 
> > 
> > Takashi
> 
> Takashi,
>    For my part, I have no idea what you're talking about.  That's not a criticism of you, its a criticism of myself.  :-)  Is there somewhere where things like "verb" and "NID" and "widget" are documented?  I skimmed through the driver development guide and didn't see such references.  I played with hda-verb briefly, but since I have no clue what I'm doing, decided that I'm better off trying to learn the fundamentals I need to understand before messing with hda-verb.  I know its tough dealing with someone like myself who is a user, not a developer (well, not a hardware driver developer, anyway).  I apologize for that.  Perhaps my company could send you a unit?  I'd have to discuss with them, but I suspect they would be willing to do so.
> 
> Thanks,

-- 
Tobin Davis 


Now I think I just reached the state of HYPERTENSION that comes JUST
BEFORE you see the TOTAL at the SAFEWAY CHECKOUT COUNTER!

Re: no front speaker sound with ALC262

[Matthew R Hurne]

Tobin Davis wrote:
> I am finishing up my current course tomorrow night, and the next
> {required} course I am taking is "Linux Fundamentals" - which is to say
> I will have spare cycles to help out again on this.

I appreciate it!  Just to clear up any confusion; Tangent is a value-add reseller here.  The Tangent 8000S is *really* the MSI Crystal 945 barebones unit, with parts installed/Windows installed and re-branded.  Tangent doesn't yet resell the MSI Crystal A410.  In fact, since Tangent doesn't really touch anything we're discussing here, we're probably best off talking about the MSI Crystal 945 and MSI Crystal A410, and just leaving Tangent out of it.  :-)  Here are links to the products on MSI's website:

Crystal 945: http://www.msicomputer.com/product/p_spec.asp?model=Crystal_945&class=npc
Crystal A410: http://www.msicomputer.com/product/p_spec.asp?model=Crystal_A410&class=npc

> Going through the message thread, you mentioned a Crystal A410 system
> that works, whereas your Tangent 8000S does not.    It would be
> interesting to recompile the drivers with "--with-debug=detect" and see
> what shows up in dmesg (for alsa only, not the entire boot log).  Based
> on that, we may be able to construct a driver model.  Also, if you have
> access to the Crystal still, could you run alsa-info.sh on it as well? 
> I'd like to verify the audio subsystem ID.

I have done the --with-debug=detect and alsa-info.sh data collection you describe above, though that was a few weeks ago.  I'll do it again with the latest from hg ASAP.

> In reviewing an earlier alsa-info posting, it shows your mixer as all
> channels muted.  I'm assuming you tried changing the volume levels in
> alsamixer?

Yes, definitely.  I probably failed to do so when I ran alsa-info, however.  In fact, I've tried loading the module with every possible value for the model parameter, and then raising all playback mixer levels each time before running aplay /usr/share/sounds/alsa/Front_Center.wav .
 
> At any rate, they list a 30 day trial unit.  I'll see if I can get one
> for driver development.  Nothing ventured, nothing gained.

If you can get a 30-day eval. Crystal 945 from Tangent, great!  Hopefully you'll actually get the Crystal 945, but Tangent is unfortunately vague about their model names, so it won't surprise me if they start sending out A410s instead of 945s labeled as model "8000S".  Probably not anytime soon, from what we can tell.  You'll know you have the Crystal 945 if it has an Intel chipset (the A410 uses an ATI chipset).  Both use the ALC262.  The *real* way (IMHO) to know which one you have is to look at the model number printed on the mainboard inside the unit; in the U.S., the Crystal 945's mainboard is labeled MS-7290, while the Crystal A410's mainboard is labeled MS-7341.

If you *can't* get an eval. unit, let me know.  I strongly suspect we could loan you one.

Matt

Re: no front speaker sound with ALC262

[Matthew R Hurne]

[-- Attachment #1: Type: text/plain, Size: 1997 bytes --]

Tobin Davis wrote:
> Ok, it looks like it may be a couple of weeks out, but they are more
> than happy to get me a unit.  Their sales staff has been bugging for
> Linux support for 6 months apparently.
> 
> In the mean time, if you can get me that output, I can at least start
> making a dent on this.  From the photo, it looks like you have a speaker
> jack (green) , line-in (blue), and mic (pink), plus speakers and mic
> built in?  I'll review the online documents again to be sure.
> 
> Tobin

We put some pressure on Tangent to get Linux audio working, and the tech. support guys I spoke with were clearly clueless.  :-(

I have attached the relevant output from dmesg, and a new alsa-info.sh output.

Thanks!

Matt

> 
> 
> On Mon, 2008-03-17 at 15:50 -0400, Matthew R Hurne wrote:
>> Tobin Davis wrote:
>> > 
>> > On Mon, 2008-03-17 at 15:04 -0400, Matthew R Hurne wrote:
>> >> The *real* way (IMHO) to know which one you have is to look at the
>> >> model number printed on the mainboard inside the unit; in the U.S.,
>> >> the Crystal 945's mainboard is labeled MS-7290, while the Crystal
>> >> A410's mainboard is labeled MS-7341.
>> > 
>> > This info should also come up in the output from dmidecode.  Most
>> > motherboard vendors have that info etched in their bios.
>>  
>> Good call.  That's the first time I've heard of dmidecode, and I just tried it out on the A410.  Sure enough, I see 
>>
>> ...
>> Base Board Information
>> 	Manufacturer: MSI
>> 	Product Name: MS-7341
>> ...
>>
>> Bingo.
>>
>> > At any rate, I have sent in the request for a demo unit.  We'll see if
>> > they contact me.  I have other systems with the same codec here at work,
>> > so I can do some reproduction (in my off time).
>> > 
>> > Most of my Alsa time is non-work related, so I have to squeeze it in
>> > where I can.
> -- Tobin Davis
> 
> I want the presidency so bad I can already taste the hors d'oeuvres.
> 


-- 
Matthew Hurne
Versatile Systems, Inc.
717.919.9102
matthew.hurne@versatile.com

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 2768 bytes --]

ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/alsa-kernel/pci/hda/hda_intel.c:1842: chipset global capabilities = 0x4401
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/alsa-kernel/pci/hda/hda_intel.c:739: codec_mask = 0x1
hda_codec: Unknown model for ALC262, trying auto-probe from BIOS...
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:3019: autoconfig: line_outs=1 (0x15/0x0/0x0/0x0/0x0)
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:3023:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:3027:    hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:3028:    mono: mono_out=0x0
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:3036:    inputs: mic=0x18, fmic=0x0, line=0x1a, fline=0x0, cd=0x0, aux=0x0
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Surround Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Center Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave LFE Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Side Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Headphone Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Speaker Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Mono Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Line-Out Playback Volume, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Surround Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Center Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave LFE Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Side Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Headphone Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Speaker Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave Mono Playback Switch, skipped
ALSA /mnt/sdc1/kiosk/slax5/ALSA/alsa-driver/pci/hda/hda_codec.c:1123: Cannot find slave IEC958 Playback Switch, skipped

[-- Attachment #3: alsa-info.txt --]
[-- Type: text/plain, Size: 18766 bytes --]

name=root&type=33&description=/tmp/alsa-info.txt&expiry=&s=Submit+Post&content=
!!################################
!!ALSA Information Script v 0.4.41
!!################################

!!Script ran on: Tue Mar 18 14:03:42 GMT 2008


!!Linux Distribution
!!------------------

:: SLAX 5.0.7 :: :: Standard Edition :: ^[[1;32m .cOC: :o. oCO: ^[[0;39m slax login:^[[1;34m root ^[[0;39m Slackware 10.2.0 SLAX 5.0.7


!!Kernel Information
!!------------------

Kernel release:    2.6.15.7-kiosk-1
Operating System:  GNU/Linux
Architecture:      i686
Processor:         unknown
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     1.0.16
Library version:    1.0.16
Utilities version:  1.0.16


!!Loaded ALSA modules
!!-------------------

snd_hda_intel


!!Soundcards recognised by ALSA
!!-----------------------------

 0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfdff8000 irq 16


!!PCI Soundcards installed in the system
!!--------------------------------------

00:1b.0 Class 0403: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)


!!Advanced information - PCI Vendor/Device/Susbsystem ID's
!!--------------------------------------------------------

00:1b.0 Class 0403: 8086:27d8 (rev 01)
	Subsystem: 1462:2900


!!Loaded sound module options
!!--------------------------

!!Module: snd_hda_intel
enable : Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : 0
id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
index : -1,-1,-1,-1,-1,-1,-1,-1
model : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>
position_fix : 0,0,0,0,0,0,0,0
power_save : 0
power_save_controller : Y
probe_mask : -1,-1,-1,-1,-1,-1,-1,-1
single_cmd : N


!!HDA-Intel Codec information
!!---------------------------
--startcollapse--

Codec: Realtek ALC262
Address: 0
Vendor Id: 0x10ec0262
Subsystem Id: 0x1462043d
Revision Id: 0x100202
No Modem Function Group found
Default PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=4, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=1, dir=1, wake=0, sticky=0, data=1
  IO[1]: enable=1, dir=1, wake=0, sticky=0, data=1
  IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0
  IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0
Node 0x02 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x03 [Audio Output] wcaps 0x11: Stereo
  Converter: stream=0, channel=0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Node 0x04 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x05 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x06 [Audio Output] wcaps 0x211: Stereo Digital
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0x1e]: 16 20 24 32
    formats [0x1]: PCM
Node 0x07 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x08, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x00 0x00]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x160]: 44100 48000 96000
    bits [0x6]: 16 20
    formats [0x1]: PCM
  Connection: 1
     0x24
Node 0x08 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x08, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x00 0x00]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x160]: 44100 48000 96000
    bits [0x6]: 16 20
    formats [0x1]: PCM
  Connection: 1
     0x23
Node 0x09 [Audio Input] wcaps 0x10011b: Stereo Amp-In
  Amp-In caps: ofs=0x08, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x00 0x00]
  Converter: stream=0, channel=0
  SDI-Select: 0
  PCM:
    rates [0x160]: 44100 48000 96000
    bits [0x6]: 16 20
    formats [0x1]: PCM
  Connection: 1
     0x22
Node 0x0a [Audio Input] wcaps 0x100391: Stereo Digital
  Converter: stream=0, channel=0
  SDI-Select: 0
  Digital:
  Digital category: 0x0
  PCM:
    rates [0x560]: 44100 48000 96000 192000
    bits [0x1e]: 16 20 24 32
    formats [0x1]: PCM
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x1f
Node 0x0b [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x1f 0x1f] [0x80 0x80] [0x1f 0x1f] [0x80 0x80] [0x80 0x80] [0x81 0x81] [0x81 0x81] [0x81 0x81]
  Connection: 8
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15
Node 0x0c [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x00 0x00]
  Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
  Amp-Out vals:  [0x1f 0x1f]
  Connection: 2
     0x02 0x0b
Node 0x0d [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x00 0x00]
  Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
  Amp-Out vals:  [0x00 0x00]
  Connection: 2
     0x03 0x0b
Node 0x0e [Audio Mixer] wcaps 0x20010e: Mono Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00] [0x00]
  Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=0
  Amp-Out vals:  [0x00]
  Connection: 2
     0x02 0x0b
Node 0x0f [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x10 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x11 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x12 [Pin Complex] wcaps 0x400001: Stereo
  Pincap 0x0820: IN
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x00:
Node 0x13 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x14 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x083e: IN OUT HP Detect Trigger
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x15 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x00 0x00]
  Pincap 0x083e: IN OUT HP Detect Trigger
  Pin Default 0x0121411f: [Jack] HP Out at Ext Rear
    Conn = 1/8, Color = Green
    DefAssociation = 0x1, Sequence = 0xf
    Misc = NO_PRESENCE
  Pin-ctls: 0xc0: OUT HP
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x16 [Pin Complex] wcaps 0x40010c: Mono Amp-Out
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80]
  Pincap 0x0810: OUT
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Connection: 1
     0x0e
Node 0x17 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x03 0x03]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x08173e: IN OUT HP Detect Trigger
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x01a19920: [Jack] Mic at Ext Rear
    Conn = 1/8, Color = Pink
    DefAssociation = 0x2, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x19 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x08173e: IN OUT HP Detect Trigger
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x08173e: IN OUT HP Detect Trigger
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x0181312f: [Jack] Line In at Ext Rear
    Conn = 1/8, Color = Blue
    DefAssociation = 0x2, Sequence = 0xf
    Misc = NO_PRESENCE
  Pin-ctls: 0x24: IN VREF_80
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x1b [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
  Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
  Amp-In vals:  [0x00 0x00]
  Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-Out vals:  [0x80 0x80]
  Pincap 0x08173e: IN OUT HP Detect Trigger
    Vref caps: HIZ 50 GRD 80
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN VREF_HIZ
  Unsolicited: tag=00, enabled=0
  Connection: 2
     0x0c* 0x0d
Node 0x1c [Pin Complex] wcaps 0x400001: Stereo
  Pincap 0x0820: IN
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
Node 0x1d [Pin Complex] wcaps 0x400000: Mono
  Pincap 0x0820: IN
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
Node 0x1e [Pin Complex] wcaps 0x400380: Mono Digital
  Pincap 0x0810: OUT
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
     0x06
Node 0x1f [Pin Complex] wcaps 0x400280: Mono Digital
  Pincap 0x0820: IN
  Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
    Conn = 1/8, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x20: IN
  Unsolicited: tag=00, enabled=0
Node 0x20 [Vendor Defined Widget] wcaps 0xf00040: Mono
  Processing caps: benign=0, ncoeff=17
Node 0x21 [Volume Knob Widget] wcaps 0x600080: Mono
  Volume-Knob: delta=0, steps=32, direct=0, val=64
  Unsolicited: tag=00, enabled=0
  Connection: 0
Node 0x22 [Audio Selector] wcaps 0x300101: Stereo
  Connection: 10
     0x18* 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x0b 0x12
Node 0x23 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 9
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x0b
Node 0x24 [Audio Mixer] wcaps 0x20010b: Stereo Amp-In
  Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
  Amp-In vals:  [0x00 0x00] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80]
  Connection: 9
     0x18 0x19 0x1a 0x1b 0x1c 0x1d 0x14 0x15 0x0b
--endcollapse--


!!ALSA Device nodes
!!-----------------

crw-rw-rw-  1 root audio 116,  0 Mar 18 13:58 /dev/snd/controlC0
crw-rw--w-  1 root audio 116,  4 Mar 18 13:58 /dev/snd/hwC0D0
crw-rw--w-  1 root audio 116, 24 Mar 18 13:58 /dev/snd/pcmC0D0c
crw-rw-rw-  1 root audio 116, 16 Mar 18 13:58 /dev/snd/pcmC0D0p
crw-rw-rw-  1 root audio 116, 33 Mar 18 13:58 /dev/snd/timer


!!Aplay/Arecord output
!!------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

!!Amixer output
!!-------------

!!-------Mixer controls for card 0 [Intel]

Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 31
  Mono: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [0.00dB] [on]
  Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'Line',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [on]
  Front Right: Playback 31 [100%] [12.00dB] [on]
Simple mixer control 'Mic',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [on]
  Front Right: Playback 31 [100%] [12.00dB] [on]
Simple mixer control 'Mic Boost',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 3
  Front Left: 3 [100%]
  Front Right: 3 [100%]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 31
  Front Left: Capture 0 [0%] [-12.00dB] [on]
  Front Right: Capture 0 [0%] [-12.00dB] [on]
Simple mixer control 'Capture',1
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 31
  Front Left: Capture 0 [0%] [-12.00dB] [on]
  Front Right: Capture 0 [0%] [-12.00dB] [on]
Simple mixer control 'Capture',2
  Capabilities: cvolume cswitch
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 31
  Front Left: Capture 0 [0%] [-12.00dB] [on]
  Front Right: Capture 0 [0%] [-12.00dB] [on]
Simple mixer control 'Input Source',0
  Capabilities: cenum
  Items: 'Mic' 'Line'
  Item0: 'Mic'
Simple mixer control 'Input Source',1
  Capabilities: cenum
  Items: 'Mic' 'Line'
  Item0: 'Mic'
Simple mixer control 'Input Source',2
  Capabilities: cenum
  Items: 'Mic' 'Line'
  Item0: 'Mic'


!!Alsactl output
!!-------------

--startcollapse--
state.Intel {
	control.1 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -4650
		comment.dbmax 0
		iface MIXER
		name 'Front Playback Volume'
		value.0 31
		value.1 31
	}
	control.2 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Front Playback Switch'
		value.0 true
		value.1 true
	}
	control.3 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Mic Playback Volume'
		value.0 31
		value.1 31
	}
	control.4 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Mic Playback Switch'
		value.0 true
		value.1 true
	}
	control.5 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -3450
		comment.dbmax 1200
		iface MIXER
		name 'Line Playback Volume'
		value.0 31
		value.1 31
	}
	control.6 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Line Playback Switch'
		value.0 true
		value.1 true
	}
	control.7 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 3'
		comment.dbmin 0
		comment.dbmax 3000
		iface MIXER
		name 'Mic Boost'
		value.0 3
		value.1 3
	}
	control.8 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -1200
		comment.dbmax 3450
		iface MIXER
		name 'Capture Volume'
		value.0 0
		value.1 0
	}
	control.9 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		value.0 true
		value.1 true
	}
	control.10 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -1200
		comment.dbmax 3450
		iface MIXER
		name 'Capture Volume'
		index 1
		value.0 0
		value.1 0
	}
	control.11 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		index 1
		value.0 true
		value.1 true
	}
	control.12 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 31'
		comment.dbmin -1200
		comment.dbmax 3450
		iface MIXER
		name 'Capture Volume'
		index 2
		value.0 0
		value.1 0
	}
	control.13 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 2
		iface MIXER
		name 'Capture Switch'
		index 2
		value.0 true
		value.1 true
	}
	control.14 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 Line
		iface MIXER
		name 'Input Source'
		value Mic
	}
	control.15 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 Line
		iface MIXER
		name 'Input Source'
		index 1
		value Mic
	}
	control.16 {
		comment.access 'read write'
		comment.type ENUMERATED
		comment.count 1
		comment.item.0 Mic
		comment.item.1 Line
		iface MIXER
		name 'Input Source'
		index 2
		value Mic
	}
	control.17 {
		comment.access 'read write'
		comment.type INTEGER
		comment.count 1
		comment.range '0 - 31'
		comment.dbmin -4650
		comment.dbmax 0
		iface MIXER
		name 'Master Playback Volume'
		value 31
	}
	control.18 {
		comment.access 'read write'
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Master Playback Switch'
		value true
	}
	control.19 {
		comment.access 'read write user'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 255'
		comment.tlv '0000000100000008ffffec1400000014'
		comment.dbmin -5100
		comment.dbmax 0
		iface MIXER
		name 'PCM Playback Volume'
		value.0 255
		value.1 255
	}
}
--endcollapse--


!!All Loaded Modules
!!------------------

Module
snd_hda_intel
snd_pcm
snd_timer
snd_page_alloc
snd_hwdep
snd
soundcore
ipv6
yealink
intel_agp
shpchp
i8xx_tco
i2c_i801
i2c_core
e1000
joydev
pcmcia
yenta_socket
rsrc_nonstatic
pcmcia_core
nls_utf8
agpgart
psmouse
usb_storage
uhci_hcd
ohci_hcd
ehci_hcd
nls_iso8859_2
nls_iso8859_1
nls_cp437
unionfs
squashfs



[-- Attachment #4: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: no front speaker sound with ALC262

[Takashi Iwai]

At Tue, 18 Mar 2008 09:11:47 -0400,
Matthew R Hurne wrote:
> 
> Tobin Davis wrote:
> > Ok, it looks like it may be a couple of weeks out, but they are more
> > than happy to get me a unit.  Their sales staff has been bugging for
> > Linux support for 6 months apparently.
> > 
> > In the mean time, if you can get me that output, I can at least start
> > making a dent on this.  From the photo, it looks like you have a speaker
> > jack (green) , line-in (blue), and mic (pink), plus speakers and mic
> > built in?  I'll review the online documents again to be sure.
> > 
> > Tobin
> 
> We put some pressure on Tangent to get Linux audio working, and the tech. support guys I spoke with were clearly clueless.  :-(
> 
> I have attached the relevant output from dmesg, and a new alsa-info.sh output.

In your case, the driver cannot work as is because the hardware tells
that you have no speaker output.  It's a bug of BIOS.

As mentioned in the earlier mail, then you'll have to figure out which
pin corresponds to the speaker output actually manually by trial and
error.  This requires some least knowledge of HD-audio codec.  See
HD-audio documentation available on intel or other web sites.

Regarding the words you listed: the HD-audio codec contains small
components (called widgets) that are connected with each other.  Each
widget has a unique number id (NID) and has a different role, such as
DAC/ADC, mixer, selector, pin (the actual I/O), etc.  Each widget can
get/set certain commands, called verbs.  You can see the widgets on
your codec in the codec#* proc file output in alsa-info.sh output.


Takashi

Re: no front speaker sound with ALC262

[Tobin Davis]

Everything is set in motion for me to get an eval unit.  I should see it
in about a week.  As soon as it comes in, I'll hit the ground running,
and see what I can figure out.

Tobin

On Tue, 2008-03-18 at 14:24 +0100, Takashi Iwai wrote:

> At Tue, 18 Mar 2008 09:11:47 -0400,
> Matthew R Hurne wrote:
> > 
> > Tobin Davis wrote:
> > > Ok, it looks like it may be a couple of weeks out, but they are more
> > > than happy to get me a unit.  Their sales staff has been bugging for
> > > Linux support for 6 months apparently.
> > > 
> > > In the mean time, if you can get me that output, I can at least start
> > > making a dent on this.  From the photo, it looks like you have a speaker
> > > jack (green) , line-in (blue), and mic (pink), plus speakers and mic
> > > built in?  I'll review the online documents again to be sure.
> > > 
> > > Tobin
> > 
> > We put some pressure on Tangent to get Linux audio working, and the tech. support guys I spoke with were clearly clueless.  :-(
> > 
> > I have attached the relevant output from dmesg, and a new alsa-info.sh output.
> 
> In your case, the driver cannot work as is because the hardware tells
> that you have no speaker output.  It's a bug of BIOS.
> 
> As mentioned in the earlier mail, then you'll have to figure out which
> pin corresponds to the speaker output actually manually by trial and
> error.  This requires some least knowledge of HD-audio codec.  See
> HD-audio documentation available on intel or other web sites.
> 
> Regarding the words you listed: the HD-audio codec contains small
> components (called widgets) that are connected with each other.  Each
> widget has a unique number id (NID) and has a different role, such as
> DAC/ADC, mixer, selector, pin (the actual I/O), etc.  Each widget can
> get/set certain commands, called verbs.  You can see the widgets on
> your codec in the codec#* proc file output in alsa-info.sh output.
> 
> 
> Takashi

-- 
Tobin Davis 


BOFH excuse #64:

CPU needs recalibration

Re: no front speaker sound with ALC262

[Rene Dohmen]

Hi Guys,

I'm glad t o read that there are other people with the same problem  
on the same system.
I just opened my Tangent 8000S and it has indeed a MSI mainboard:  
MS7290. The speakers are connected to a small custom board: MS-4088
There's no extra chip on this customboard and the board is directly  
connected to the mainboard. So probably the signal leaving the  
mainboard in amplified already. (or there's a amplifier builtin the  
speakers)

Next week i'll have some time to put tangent under some more pressure  
for info, so maybe that will speed up things a little bit.

Grz Rene

Re: no front speaker sound with ALC262

[Tobin Davis]

Rene, don't bother bugging Tangent.  I have a demo unit on the way.  My
first priority is getting the driver working.

Tangent really won't help much - their a distributor, not the OEM.  This
is an MSI Crystal 945 in a Tangent shell.

If you want to try something, see if the bios can be reflashed with the
Crystal 945 firmware.

As to the speaker board, where on the main board is it mounted?  Is the
header labeled?  How many pins?  It sounds like the speakers may be on
the front panel header, which would make them function like headphones.
Or this board is custom build for this application and I don't know what
I'm talking about.

Tobin


On Sat, 2008-03-22 at 18:59 +0100, Rene Dohmen wrote:

> Hi Guys,
> 
> I'm glad t o read that there are other people with the same problem  
> on the same system.
> I just opened my Tangent 8000S and it has indeed a MSI mainboard:  
> MS7290. The speakers are connected to a small custom board: MS-4088
> There's no extra chip on this customboard and the board is directly  
> connected to the mainboard. So probably the signal leaving the  
> mainboard in amplified already. (or there's a amplifier builtin the  
> speakers)
> 
> Next week i'll have some time to put tangent under some more pressure  
> for info, so maybe that will speed up things a little bit.
> 
> Grz Rene
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
Tobin Davis 


love, n.:
	When you don't want someone too close--because you're very sensitive
	to pleasure.

Re: no front speaker sound with ALC262

[Rene Dohmen]

Op Mar 22, 2008, om 8:09 PM heeft Tobin Davis het volgende geschreven:

> Rene, don't bother bugging Tangent.  I have a demo unit on the  
> way.  My first priority is getting the driver working.
>
> Tangent really won't help much - their a distributor, not the OEM.   
> This is an MSI Crystal 945 in a Tangent shell.
>

I know that the system is actually a Crystal 945. I got the  
touchscreen working via a dev driver from salt (so not tangent)
On the mainboard there is a conenctor: JFP1that goes to the ms4088  
board. The mainboard connects to:
- power led
- hdd led
- speakers
- main power switch

I can provide you with some photoos if you like.

As stated earlier: the sound is working by with very low volume levels


> If you want to try something, see if the bios can be reflashed with  
> the Crystal 945 firmware.
>

I sound working with the original crystal? I don't think tangent has  
flshed their BIOS to another version.
In the crystal 945 specs I found that the're using a Realtek ALC262  
with azalia codec, maybe this helps.

Rene


> As to the speaker board, where on the main board is it mounted?  Is  
> the header labeled?  How many pins?  It sounds like the speakers  
> may be on the front panel header, which would make them function  
> like headphones.  Or this board is custom build for this  
> application and I don't know what I'm talking about.
>
> Tobin
>
>
> On Sat, 2008-03-22 at 18:59 +0100, Rene Dohmen wrote:
>>
>> Hi Guys,
>>
>> I'm glad t o read that there are other people with the same problem
>> on the same system.
>> I just opened my Tangent 8000S and it has indeed a MSI mainboard:
>> MS7290. The speakers are connected to a small custom board: MS-4088
>> There's no extra chip on this customboard and the board is directly
>> connected to the mainboard. So probably the signal leaving the
>> mainboard in amplified already. (or there's a amplifier builtin the
>> speakers)
>>
>> Next week i'll have some time to put tangent under some more pressure
>> for info, so maybe that will speed up things a little bit.
>>
>> Grz Rene
>>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> -- Tobin Davis 
>
> love, n.:
> 	When you don't want someone too close--because you're very sensitive
> 	to pleasure.

Re: no front speaker sound with ALC262

[Tobin Davis]

I'm still waiting for my demo unit from Tangent.  Latest update is they
think it may be a hardware issue (missing a resistor).  I should know
more Monday.  If this is the case, then the driver should work with very
minor modifications (subsystem ID addition).

Tobin


On Tue, 2008-03-25 at 11:40 +0100, Rene Dohmen wrote:

> 
> 
> Op Mar 22, 2008, om 8:09 PM heeft Tobin Davis het volgende geschreven:
> 
> 
> 
> > Rene, don't bother bugging Tangent.  I have a demo unit on the way.
> > My first priority is getting the driver working.
> > 
> > Tangent really won't help much - their a distributor, not the OEM.
> > This is an MSI Crystal 945 in a Tangent shell.
> > 
> > 
> 
> 
> I know that the system is actually a Crystal 945. I got the
> touchscreen working via a dev driver from salt (so not tangent)
> On the mainboard there is a conenctor: JFP1that goes to the ms4088
> board. The mainboard connects to:
> - power led
> - hdd led
> - speakers
> - main power switch
> 
> 
> I can provide you with some photoos if you like.
> 
> 
> As stated earlier: the sound is working by with very low volume
> levels 
> 
> 
> 
> 
> > 
> > If you want to try something, see if the bios can be reflashed with
> > the Crystal 945 firmware.
> > 
> > 
> 
> 
> I sound working with the original crystal? I don't think tangent has
> flshed their BIOS to another version.
> In the crystal 945 specs I found that the're using a Realtek ALC262
> with azalia codec, maybe this helps.
> 
> 
> Rene
> 
> 
> 
> 
> 
> > As to the speaker board, where on the main board is it mounted?  Is
> > the header labeled?  How many pins?  It sounds like the speakers may
> > be on the front panel header, which would make them function like
> > headphones.  Or this board is custom build for this application and
> > I don't know what I'm talking about.
> > 
> > Tobin
> > 
> > 
> > On Sat, 2008-03-22 at 18:59 +0100, Rene Dohmen wrote: 
> > 
> > > Hi Guys,
> > > 
> > > I'm glad t o read that there are other people with the same problem  
> > > on the same system.
> > > I just opened my Tangent 8000S and it has indeed a MSI mainboard:  
> > > MS7290. The speakers are connected to a small custom board: MS-4088
> > > There's no extra chip on this customboard and the board is directly  
> > > connected to the mainboard. So probably the signal leaving the  
> > > mainboard in amplified already. (or there's a amplifier builtin the  
> > > speakers)
> > > 
> > > Next week i'll have some time to put tangent under some more pressure  
> > > for info, so maybe that will speed up things a little bit.
> > > 
> > > Grz Rene
> > > 
> > > _______________________________________________
> > > Alsa-devel mailing list
> > > Alsa-devel@alsa-project.org
> > > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> > 
> > -- Tobin Davis 
> > 
> > 
> > love, n.:
> > 	When you don't want someone too close--because you're very sensitive
> > 	to pleasure.
> 
> 

-- 
Tobin Davis 


I can hire one half of the working class to kill the other half.
		-- Jay Gould

Re: no front speaker sound with ALC262

[Rene Dohmen]

Tobin,


Did you receive the unit?
I'm wondering if you had some progress already.

Greets,
Rene


Op Mar 31, 2008, om 3:30 PM heeft Tobin Davis het volgende geschreven:

> Yes, it would.  Hmmm
>
> Well, I hope they send the unit today.
>
> Tobin
>
> On Mon, 2008-03-31 at 13:57 +0200, Rene Dohmen wrote:
>>
>> with the preinstalled win XP the sound is working OK.
>> So that would rule out hardware problems with the soundcard.
>>
>>
>> Rene
>>
>>
>>
>>
>>
>>
>> Op Mar 28, 2008, om 7:28 PM heeft Tobin Davis het volgende  
>> geschreven:
>>
>>> I'm still waiting for my demo unit from Tangent.  Latest update  
>>> is they think it may be a hardware issue (missing a resistor).  I  
>>> should know more Monday.  If this is the case, then the driver  
>>> should work with very minor modifications (subsystem ID addition).
>>>
>>> Tobin
>>>
>>>
>>> On Tue, 2008-03-25 at 11:40 +0100, Rene Dohmen wrote:
>>>>
>>>> Op Mar 22, 2008, om 8:09 PM heeft Tobin Davis het volgende  
>>>> geschreven:
>>>>
>>>>> Rene, don't bother bugging Tangent.  I have a demo unit on the  
>>>>> way.  My first priority is getting the driver working.
>>>>>
>>>>> Tangent really won't help much - their a distributor, not the  
>>>>> OEM.  This is an MSI Crystal 945 in a Tangent shell.
>>>>>
>>>>
>>>>
>>>> I know that the system is actually a Crystal 945. I got the  
>>>> touchscreen working via a dev driver from salt (so not tangent)
>>>> On the mainboard there is a conenctor: JFP1that goes to the  
>>>> ms4088 board. The mainboard connects to:
>>>> - power led
>>>> - hdd led
>>>> - speakers
>>>> - main power switch
>>>>
>>>>
>>>> I can provide you with some photoos if you like.
>>>>
>>>>
>>>> As stated earlier: the sound is working by with very low volume  
>>>> levels
>>>>
>>>>
>>>>
>>>>
>>>>> If you want to try something, see if the bios can be reflashed  
>>>>> with the Crystal 945 firmware.
>>>>>
>>>>
>>>>
>>>> I sound working with the original crystal? I don't think tangent  
>>>> has flshed their BIOS to another version.
>>>> In the crystal 945 specs I found that the're using a Realtek  
>>>> ALC262 with azalia codec, maybe this helps.
>>>>
>>>>
>>>> Rene
>>>>
>>>>
>>>>
>>>>> As to the speaker board, where on the main board is it  
>>>>> mounted?  Is the header labeled?  How many pins?  It sounds  
>>>>> like the speakers may be on the front panel header, which would  
>>>>> make them function like headphones.  Or this board is custom  
>>>>> build for this application and I don't know what I'm talking  
>>>>> about.
>>>>>
>>>>> Tobin
>>>>>
>>>>>
>>>>> On Sat, 2008-03-22 at 18:59 +0100, Rene Dohmen wrote:
>>>>>>
>>>>>> Hi Guys,
>>>>>>
>>>>>> I'm glad t o read that there are other people with the same  
>>>>>> problem
>>>>>> on the same system.
>>>>>> I just opened my Tangent 8000S and it has indeed a MSI mainboard:
>>>>>> MS7290. The speakers are connected to a small custom board:  
>>>>>> MS-4088
>>>>>> There's no extra chip on this customboard and the board is  
>>>>>> directly
>>>>>> connected to the mainboard. So probably the signal leaving the
>>>>>> mainboard in amplified already. (or there's a amplifier  
>>>>>> builtin the
>>>>>> speakers)
>>>>>>
>>>>>> Next week i'll have some time to put tangent under some more  
>>>>>> pressure
>>>>>> for info, so maybe that will speed up things a little bit.
>>>>>>
>>>>>> Grz Rene
>>>>>>
>>>>>> _______________________________________________
>>>>>> Alsa-devel mailing list
>>>>>> Alsa-devel@alsa-project.org
>>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>>> -- Tobin Davis 
>>>>>
>>>>> love, n.:
>>>>> 	When you don't want someone too close--because you're very  
>>>>> sensitive
>>>>> 	to pleasure.
>>>>
>>> -- Tobin Davis 
>>>
>>> I can hire one half of the working class to kill the other half.
>>> 		-- Jay Gould
>>
>>
> -- Tobin Davis 
>
> He is no lawyer who cannot take two sides.

Re: no front speaker sound with ALC262

[Tobin Davis]

I'm still waiting for them to send it to me.  Last I heard it was held
up due to some resistor modifications, but that was two weeks ago.

Tobin

On Tue, 2008-04-15 at 12:02 +0200, Rene Dohmen wrote:

> Tobin,
> 
> 
> Did you receive the unit?
> I'm wondering if you had some progress already.
> 
> Greets,
> Rene
> 
> 
> Op Mar 31, 2008, om 3:30 PM heeft Tobin Davis het volgende geschreven:
> 
> > Yes, it would.  Hmmm
> >
> > Well, I hope they send the unit today.
> >
> > Tobin
> >
> > On Mon, 2008-03-31 at 13:57 +0200, Rene Dohmen wrote:
> >>
> >> with the preinstalled win XP the sound is working OK.
> >> So that would rule out hardware problems with the soundcard.
> >>
> >>
> >> Rene
> >>
> >>
> >>
> >>
> >>
> >>
> >> Op Mar 28, 2008, om 7:28 PM heeft Tobin Davis het volgende  
> >> geschreven:
> >>
> >>> I'm still waiting for my demo unit from Tangent.  Latest update  
> >>> is they think it may be a hardware issue (missing a resistor).  I  
> >>> should know more Monday.  If this is the case, then the driver  
> >>> should work with very minor modifications (subsystem ID addition).
> >>>
> >>> Tobin
> >>>
> >>>
> >>> On Tue, 2008-03-25 at 11:40 +0100, Rene Dohmen wrote:
> >>>>
> >>>> Op Mar 22, 2008, om 8:09 PM heeft Tobin Davis het volgende  
> >>>> geschreven:
> >>>>
> >>>>> Rene, don't bother bugging Tangent.  I have a demo unit on the  
> >>>>> way.  My first priority is getting the driver working.
> >>>>>
> >>>>> Tangent really won't help much - their a distributor, not the  
> >>>>> OEM.  This is an MSI Crystal 945 in a Tangent shell.
> >>>>>
> >>>>
> >>>>
> >>>> I know that the system is actually a Crystal 945. I got the  
> >>>> touchscreen working via a dev driver from salt (so not tangent)
> >>>> On the mainboard there is a conenctor: JFP1that goes to the  
> >>>> ms4088 board. The mainboard connects to:
> >>>> - power led
> >>>> - hdd led
> >>>> - speakers
> >>>> - main power switch
> >>>>
> >>>>
> >>>> I can provide you with some photoos if you like.
> >>>>
> >>>>
> >>>> As stated earlier: the sound is working by with very low volume  
> >>>> levels
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> If you want to try something, see if the bios can be reflashed  
> >>>>> with the Crystal 945 firmware.
> >>>>>
> >>>>
> >>>>
> >>>> I sound working with the original crystal? I don't think tangent  
> >>>> has flshed their BIOS to another version.
> >>>> In the crystal 945 specs I found that the're using a Realtek  
> >>>> ALC262 with azalia codec, maybe this helps.
> >>>>
> >>>>
> >>>> Rene
> >>>>
> >>>>
> >>>>
> >>>>> As to the speaker board, where on the main board is it  
> >>>>> mounted?  Is the header labeled?  How many pins?  It sounds  
> >>>>> like the speakers may be on the front panel header, which would  
> >>>>> make them function like headphones.  Or this board is custom  
> >>>>> build for this application and I don't know what I'm talking  
> >>>>> about.
> >>>>>
> >>>>> Tobin
> >>>>>
> >>>>>
> >>>>> On Sat, 2008-03-22 at 18:59 +0100, Rene Dohmen wrote:
> >>>>>>
> >>>>>> Hi Guys,
> >>>>>>
> >>>>>> I'm glad t o read that there are other people with the same  
> >>>>>> problem
> >>>>>> on the same system.
> >>>>>> I just opened my Tangent 8000S and it has indeed a MSI mainboard:
> >>>>>> MS7290. The speakers are connected to a small custom board:  
> >>>>>> MS-4088
> >>>>>> There's no extra chip on this customboard and the board is  
> >>>>>> directly
> >>>>>> connected to the mainboard. So probably the signal leaving the
> >>>>>> mainboard in amplified already. (or there's a amplifier  
> >>>>>> builtin the
> >>>>>> speakers)
> >>>>>>
> >>>>>> Next week i'll have some time to put tangent under some more  
> >>>>>> pressure
> >>>>>> for info, so maybe that will speed up things a little bit.
> >>>>>>
> >>>>>> Grz Rene
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Alsa-devel mailing list
> >>>>>> Alsa-devel@alsa-project.org
> >>>>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>>>> -- Tobin Davis 
> >>>>>
> >>>>> love, n.:
> >>>>> 	When you don't want someone too close--because you're very  
> >>>>> sensitive
> >>>>> 	to pleasure.
> >>>>
> >>> -- Tobin Davis 
> >>>
> >>> I can hire one half of the working class to kill the other half.
> >>> 		-- Jay Gould
> >>
> >>
> > -- Tobin Davis 
> >
> > He is no lawyer who cannot take two sides.
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
Tobin Davis 


"Life is a garment we continuously alter, but which never seems to fit."
-- David McCord

Re: no front speaker sound with ALC262

[Tobin Davis]

Thought I'd post an updated email regarding the status of this.  I have
sent another email to Tangent to find out what the status of my demo
unit is.  I apologize for not getting any progress on this earlier, but
I don't have any hardware to test this on, and the previous attempts
failed to enable audio.   I'll also ping Realtek to see if I can at
least get a test board for this (I only have an ALC268, which seems to
be non-functioning).  Hopefully we can get this resolved soon.


-- 
Tobin Davis 


Can you MAIL a BEAN CAKE?