From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000321]: Left front channel always muted on boot
Date: Fri, 17 Dec 2004 06:46:59 +0100 [thread overview]
Message-ID: <5fc1f882a4084cf467b1ced72ebf4c81@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=321>
======================================================================
Reported By: 64bitten
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 321
Category: PCI - ice1724
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution: gentoo
Kernel Version: 2.6.6
======================================================================
Date Submitted: 06-02-2004 08:09 CEST
Last Modified: 12-17-2004 06:46 CET
======================================================================
Summary: Left front channel always muted on boot
Description:
ice1724 (M Audio Revolution 7.1 in my case) always restores the mixer
settings at boot, but the left front channel is muted regardless. The fix
is to run alsamixer and adjust the slider again. This forces the channel
to unmute. Should I be worried "amixer scontrols" reports everything as
"Mono" as well?
======================================================================
----------------------------------------------------------------------
K6-III - 12-17-04 03:15
----------------------------------------------------------------------
Happens to me as well with the Revo 7.1.
----------------------------------------------------------------------
herby - 12-17-04 06:46
----------------------------------------------------------------------
I've got an M-Audio Revolution 7.1 as well. I noted that after boot it
mutes a channel as well. This was back using ALSA 0.9.6. What I did to
get around it was to set the level down, then up a bit. While it didn't
cure the base problem, it was a viable work around. The problem has
existed for quite a few revisions. While this does not provide a cure, it
does show that the problem has existed for a while. If I remember, the
problem might be described in the ALSA development mailing list archives.
Issue History
Date Modified Username Field Change
======================================================================
06-02-04 08:09 64bitten New Issue
06-02-04 08:09 64bitten Distribution => gentoo
06-02-04 08:09 64bitten Kernel Version => 2.6.6
12-17-04 03:15 K6-III Note Added: 0002845
12-17-04 06:46 herby Note Added: 0002846
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-17 5:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 5:46 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-05 15:29 [ALSA - driver 0000321]: Left front channel always muted on boot bugtrack
2006-06-23 13:44 bugtrack
2006-06-23 12:52 bugtrack
2006-06-23 12:20 bugtrack
2006-06-23 12:10 bugtrack
2006-06-23 12:03 bugtrack
2006-06-22 4:30 bugtrack
2006-06-21 8:00 bugtrack
2006-06-21 7:38 bugtrack
2006-06-21 7:05 bugtrack
2006-06-21 4:10 bugtrack
2006-06-20 21:29 bugtrack
2005-11-18 20:03 bugtrack
2005-10-21 1:51 bugtrack
2005-10-20 3:18 bugtrack
2005-10-20 0:36 bugtrack
2005-04-09 15:24 bugtrack
2004-12-21 6:10 bugtrack
2004-12-17 5:51 bugtrack
2004-12-17 2:15 bugtrack
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=5fc1f882a4084cf467b1ced72ebf4c81@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox