[alsa-devel] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression)
acidjunk at gmail.com
Fri Feb 22 13:09:12 CET 2008
Thnx for you quick reply
De sound of the line out is working but quality is poor and the volume is
I didn't have it working with other versions of ALSA. Tested with 1.0.14,
then started reading, lots of suggestions stated that the problem would be
solved in 1.0.15, so i compiled 1.0.16.
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.
alsa-info.sh script output uploaded: http://pastebin.ca/913865
I wasn't aware of the fact that I communicated directly: I found the
discussion in google groups: and just hitted reply :-)
So sorry for that. I now subscribed myself to the ML
On Fri, Feb 22, 2008 at 8:09 AM, Takashi Iwai <tiwai at suse.de> wrote:
> At Thu, 21 Feb 2008 18:56:30 -0800 (PST),
> acidjunk at gmail.com wrote:
> > Hi,
> > I have exactly the same problem with my sound device:
> > hda_codec: Unknown model for ALC262: trying auto-probe
> > lspci output: 00:1b.0 Audio device: Intel Corporation 82801G (ICH7
> > Family) High Definition Audio Controller (rev 01) from BIOS.
> > I'm using alsa 1.0.16 compiled form source under ubuntu gutsy. I tried
> > hardy but is has the same results
> > The headphone output is working (not very loud, but usable), but the
> > front speakers are not working. Did the patches solve the speaker
> > issue? and how do I apply them (I am new to the patching technique).
> Please don't mix up. It is a totally different problem since your
> machine has another codec (and even 1.0.16 doesn't work). The patch
> cannot solve your problem. Save your time.
> Has any version of ALSA driver ever worked properly? If yes, we can
> check the difference.
> If not, we need to track down the problem more deeply. First of all,
> give more detailed hardware information: what is your laptop (or
> desktop) vendor, model, etc. Try different model options. And the
> output of alsa-info.sh -- it's vital information.
> Last but not least, don't forget to add alsa-devel ML to Cc in your
> next reply. This isn't a kind of thing to be communicated privately
> at all.
More information about the Alsa-devel