From: Matej Laitl <strohel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ALSA] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression)
Date: Tue, 12 Feb 2008 11:50:36 +0100 [thread overview]
Message-ID: <200802121150.36743.strohel@gmail.com> (raw)
In-Reply-To: <s5hfxvyv5x4.wl%tiwai@suse.de>
Takashi Iwai wrote:
> Matej Laitl wrote:
> > after upgrading from 2.6.24 to 2.6.25-rc1, I lost headphone-out sound
> > output of my Intel HDA card - it is quiet no matter what the mixer
> > settings are.
> >
> > (...)
> >
> > The box is Fujitsu-Siemens Esprimo Mobile M9400 laptop.
>
> Could you give the output of alsa-info.sh for both working and
> non-working kernels?
The locations of alsa-info.sh outputs:
no sound in headphones: http://pastebin.ca/901022
sound ok: http://pastebin.ca/901016
Both kernels are Linus' tree snapshots as of commit cc13e442952a347f7, the one
with working sound has just the f889fa91ad47e commit reverted.
Matej Laitl
WARNING: multiple messages have this Message-ID (diff)
From: Matej Laitl <strohel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ALSA] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression)
Date: Tue, 12 Feb 2008 11:50:36 +0100 [thread overview]
Message-ID: <200802121150.36743.strohel@gmail.com> (raw)
In-Reply-To: <s5hfxvyv5x4.wl%tiwai@suse.de>
Takashi Iwai wrote:
> Matej Laitl wrote:
> > after upgrading from 2.6.24 to 2.6.25-rc1, I lost headphone-out sound
> > output of my Intel HDA card - it is quiet no matter what the mixer
> > settings are.
> >
> > (...)
> >
> > The box is Fujitsu-Siemens Esprimo Mobile M9400 laptop.
>
> Could you give the output of alsa-info.sh for both working and
> non-working kernels?
The locations of alsa-info.sh outputs:
no sound in headphones: http://pastebin.ca/901022
sound ok: http://pastebin.ca/901016
Both kernels are Linus' tree snapshots as of commit cc13e442952a347f7, the one
with working sound has just the f889fa91ad47e commit reverted.
Matej Laitl
next prev parent reply other threads:[~2008-02-12 10:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:58 [ALSA] HDA: no sound in headphone-out caused by commit f889fa91ad47e (2.6.25-rc1 regression) Matej Laitl
2008-02-11 20:58 ` Matej Laitl
2008-02-12 10:13 ` Takashi Iwai
2008-02-12 10:13 ` Takashi Iwai
2008-02-12 10:50 ` Matej Laitl [this message]
2008-02-12 10:50 ` Matej Laitl
2008-02-12 11:02 ` Takashi Iwai
2008-02-12 11:02 ` Takashi Iwai
2008-02-12 11:34 ` Takashi Iwai
2008-02-12 11:34 ` Takashi Iwai
2008-02-12 12:06 ` Matej Laitl
2008-02-12 12:06 ` Matej Laitl
2008-02-12 14:02 ` Takashi Iwai
2008-02-12 14:02 ` Takashi Iwai
2008-02-12 14:13 ` Takashi Iwai
2008-02-12 14:13 ` Takashi Iwai
2008-02-12 15:27 ` Matej Laitl
2008-02-12 17:14 ` Takashi Iwai
2008-02-12 18:24 ` Matej Laitl
2008-02-12 22:57 ` Matej Laitl
2008-02-13 10:59 ` Takashi Iwai
2008-02-13 12:05 ` Matej Laitl
2008-02-13 13:06 ` Takashi Iwai
2008-02-13 15:00 ` Matej Laitl
2008-02-13 15:25 ` Takashi Iwai
2008-02-13 11:01 ` Takashi Iwai
2008-02-12 11:36 ` Matej Laitl
2008-02-12 11:36 ` Matej Laitl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802121150.36743.strohel@gmail.com \
--to=strohel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.