All of lore.kernel.org
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: via82xx: unreliable audio, strange mixer behavior
Date: Fri, 21 Nov 2008 11:32:56 -0500	[thread overview]
Message-ID: <20081121163256.GE3899@storm.local.network> (raw)
In-Reply-To: <s5hfxll8cj0.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 2240 bytes --]

Hi Takashi,

On Fri, Nov 21, 2008 at 01:54:43PM +0100, Takashi Iwai wrote:
> At Fri, 21 Nov 2008 07:08:23 -0500,
> Forest Bond wrote:
> > On Fri, Nov 21, 2008 at 12:59:10PM +0100, Takashi Iwai wrote:
> > > At Thu, 20 Nov 2008 12:04:09 -0500,
> > > Forest Bond wrote:
> > >> 
> > >> Hi,
> > >> 
> > >> I'm using snd-via82xx on an Ubuntu 8.04 system.  alsa-info.sh output is here:
> > >> 
> > >> http://www.alsa-project.org/db/?f=1c3d5570e7b57d4d2f79b964a323dd7b4efd7e78
> > >> 
> > >> Here are the symptoms:
> > >> 
> > >> Audio goes away after a semi-random interval.  Sometimes it returns after
> > >> `modprobe -r snd-via82xx' followed by `modprobe snd-via82xx', but sometimes it
> > >> seems to take a full reboot.
> > >> 
> > >> This looks similar to:
> > >> 
> > >> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3D3194
> > >> 
> > >> Some folks think that this kind of issue is triggered by audio volume being
> > >> above a certain level.  I'm not entirely sure if this is true, but I think it
> > >> is.  One time, I apparently triggered the issue by unplugging and replugging the
> > >> audio cable from the mainboard during playback.
> > >> 
> > >> Audio can be heard even when the PCM volume level is 0 (as told by alsamixer).
> > >> The volume does get louder when I turn up that mixer control, but it never goes
> > >> away entirely when I turn the volume to zero.  Mute works as expected.
> > > 
> > > The volume 0 doesn't always mean the mute on several hardwares.
> > > So this can be irrelevant if it happens always.
> > > 
> > > I vaguely remember about the low-power mode of some codec chips.
> > > Which codec chip does your system have?  Please run alsa-info.sh with
> > > --no-upload option, and attach the output file.
> > 
> > The output would be the same as what was already uploaded, right?  I've attached
> > that output here for your convenience.
> 
> Thanks, it's always better to post the content than a URL.
> 
> Any chance to try the later version of alsa-driver?
> Yours looks pretty old.

I can try this a bit later today.  I'll report the results ASAP.

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

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

  reply	other threads:[~2008-11-21 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20 17:04 via82xx: unreliable audio, strange mixer behavior Forest Bond
2008-11-21 11:59 ` Takashi Iwai
2008-11-21 12:08   ` Forest Bond
2008-11-21 12:54     ` Takashi Iwai
2008-11-21 16:32       ` Forest Bond [this message]
2008-11-21 16:36         ` Takashi Iwai
2008-11-24 20:03           ` Forest Bond
2008-11-24 23:09             ` Takashi Iwai
2008-11-25 20:51               ` Forest Bond

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=20081121163256.GE3899@storm.local.network \
    --to=forest@alittletooquiet.net \
    --cc=alsa-devel@alsa-project.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.