From: "Rafael J. Wysocki" <rjw@sisk•pl>
To: Takashi Iwai <tiwai@suse•de>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for June 20: [regression] No sound on SB600
Date: Tue, 24 Jun 2008 12:32:07 +0200 [thread overview]
Message-ID: <200806241232.08387.rjw@sisk.pl> (raw)
In-Reply-To: <s5hvdzztjhz.wl%tiwai@suse.de>
On Tuesday, 24 of June 2008, Takashi Iwai wrote:
> At Tue, 24 Jun 2008 00:48:34 +0200,
> Rafael J. Wysocki wrote:
> >
> > On Monday, 23 of June 2008, Takashi Iwai wrote:
> > > At Mon, 23 Jun 2008 17:05:02 +0200,
> > > Rafael J. Wysocki wrote:
> > > >
> > > > On Monday, 23 of June 2008, Takashi Iwai wrote:
> > > > > At Mon, 23 Jun 2008 16:32:08 +0200,
> > > > > Rafael J. Wysocki wrote:
> > > > > >
> > > > > > On Monday, 23 of June 2008, Takashi Iwai wrote:
> > > > > > > At Sat, 21 Jun 2008 21:25:41 +0200,
> > > > > > > Rafael J. Wysocki wrote:
> > > > > > > >
> > > > > > > > On Saturday, 21 of June 2008, Takashi Iwai wrote:
> > > > > > > > > At Sat, 21 Jun 2008 17:28:09 +0200,
> > > > > > > > > Rafael J. Wysocki wrote:
> > > > > > > > > >
> > > > > > > > > > On Friday, 20 of June 2008, Stephen Rothwell wrote:
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > Changes since next-20080619:
> > > > > > > > > > >
> > > > > > > > > > > The net tree lost its conflict against Linus' tree.
> > > > > > > > > > >
> > > > > > > > > > > The bkl-removal tree lost a conflict.
> > > > > > > > > >
> > > > > > > > > > On one of my test boxes with the ATI chipset (SB600 south bridge) there's no
> > > > > > > > > > sound output. Bisection shows that the following commit causes this to happen
> > > > > > > > > > and reverting the commit fixes the problem for me:
> > > > > > > > > >
> > > > > > > > > > commit cf97e6678f1e1e7bbdb566c36771540123832a31
> > > > > > > > > > Author: Takashi Iwai <tiwai@suse•de>
> > > > > > > > > > Date: Mon Jun 16 15:47:26 2008 +0200
> > > > > > > > > >
> > > > > > > > > > ALSA: hda - Fix wrong volumes in AD1988 auto-probe mode
> > > > > > > > > >
> > > > > > > > > > Don't create mixer volume elements for Headphone and Speaker if they
> > > > > > > > > > use the same DAC as normal line-outs on AD1988. Otherwise the amp
> > > > > > > > > > value gets screwed up, e.g.
> > > > > > > > > > https://bugzilla.novell.com/show_bug.cgi?id=398255
> > > > > > > > > >
> > > > > > > > > > Signed-off-by: Takashi Iwai <tiwai@suse•de>
> > > > > > > > > >
> > > > > > > > > > Please let me know if you need any additional information.
> > > > > > > > >
> > > > > > > > > Could you run alsa-info.sh with --no-upload option and attach the
> > > > > > > > > output for both states with and without that commit? The script is
> > > > > > > > > found at
> > > > > > > > > http://www.alsa-project.org/alsa-info.sh
> > > > > > > > > Also, show the relevant kernel message from snd-hda-intel (informing
> > > > > > > > > the auto-parsing of pins, etc), too.
> > > > > > > >
> > > > > > > > dmesg outputs and the outputs of 'alsa-info.sh --no-upload' for the kernel with
> > > > > > > > the patch applied (1) and with the reverted (2) are at:
> > > > > > > >
> > > > > > > > http://www.sisk.pl/kernel/debug/20080620/box2/dmesg-1.log
> > > > > > > > http://www.sisk.pl/kernel/debug/20080620/box2/alsa-info-1.txt
> > > > > > > >
> > > > > > > > http://www.sisk.pl/kernel/debug/20080620/box2/dmesg-2.log
> > > > > > > > http://www.sisk.pl/kernel/debug/20080620/box2/alsa-info-2.txt
> > > > > > >
> > > > > > > Well, this is actually no regression but an unlucky side-effect of the
> > > > > > > fix.
> > > > > > >
> > > > > > > In the old version, "Front" volume didn't work properly because of
> > > > > > > confliction with a bogus "Headphone" volume. Now, a wrong volume
> > > > > > > element is removed but only "Front" remains while "Front" wasn't set
> > > > > > > up properly.
> > > > > > >
> > > > > > > In short, the below should fix the problem:
> > > > > > >
> > > > > > > % amixer set Front 90%
> > > > > >
> > > > > > Well, okay, but where should I add that to make KDE mixers work, for example?
> >
> > Ah, there is a "Front" volume control that works instead of the "Headphone" one.
>
> It's been there but it didn't work because of conflict with a bogus
> "Headphone" volume.
>
> > > > >
> > > > > You must have "Master" volume control now. This also changes Front,
> > > > > etc. Try to reassign Master as the default volume in kmix.
> > >>
> > > > Yes, I have the "Master" control and I had it before the patch too, but it has
> > > > no effect both after and before the patch AFAICS (will double check).
> > >
> > > Oh, yes, let me know if "Master" still doesn't work.
> >
> > No, it doesn't.
>
> Hmm...
>
> > > This should have been fixed with the last patch, too.
> >
> > Oh well ... ;-)
>
> Just to be sure, did you adjust Front volume properly before testing
> Master volume? Master volume is only attenuation and no gain. Thus,
> if Front is low, you won't get any high volumes even if you raise
> Master to full.
Ah, I see. OK, it works this way. Sorry for the confusion.
> To be noted, you have also other mixer elements like Surround, Center,
> etc. Together with Front, these correspond to the volumes of 7.1
> output channels individually. Your hardware has no individual
> headphone volume but it's connected from the front channels. That's
> why "Front" controls the headphone volume, too.
Thanks for the explanation.
Rafael
prev parent reply other threads:[~2008-06-24 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 7:25 linux-next: Tree for June 20 Stephen Rothwell
2008-06-21 15:28 ` linux-next: Tree for June 20: [regression] No sound on SB600 Rafael J. Wysocki
2008-06-21 16:03 ` Takashi Iwai
2008-06-21 19:25 ` Rafael J. Wysocki
2008-06-23 10:11 ` Takashi Iwai
2008-06-23 14:32 ` Rafael J. Wysocki
2008-06-23 14:35 ` Takashi Iwai
2008-06-23 15:05 ` Rafael J. Wysocki
2008-06-23 15:07 ` Takashi Iwai
2008-06-23 22:48 ` Rafael J. Wysocki
2008-06-24 6:49 ` Takashi Iwai
2008-06-24 10:32 ` Rafael J. Wysocki [this message]
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=200806241232.08387.rjw@sisk.pl \
--to=rjw@sisk$(echo .)pl \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox