From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000321]: Left front channel always muted on boot
Date: Wed, 21 Jun 2006 10:00:38 +0200 [thread overview]
Message-ID: <73f05657dcd2a108ecec95d92b147f1e@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: acknowledged
Distribution: gentoo
Kernel Version: 2.6.6
======================================================================
Date Submitted: 06-02-2004 08:09 CEST
Last Modified: 06-21-2006 10:00 CEST
======================================================================
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?
======================================================================
----------------------------------------------------------------------
herby - 06-21-06 09:37
----------------------------------------------------------------------
This problem has been around for quite a while (couple of years). It
manifests itself by NOT doing the first volume set. This is usually the
left front. Since the driver saves the value (so it won't send the data
twice) it persists. What I did to "workaround" is to set the value to 80%
(any value other than what you want), and then set the "real" value. This
has alsways worked for me. I suspect that something in the init sequence
(run at driver load) leaves something in a bad state. At the moment I
don't have the card in close proximity (to test), but be assured that this
fault has been around since the 0.9 era. I will also note that after the
first set, the card behaves quite properly.
----------------------------------------------------------------------
Raymond - 06-21-06 10:00
----------------------------------------------------------------------
alsactl nad alsamixer expect index controls are continuous, but the driver
implemented in non-standard way (i.e. Deemphasis appear between DAC volume
controls).
control.20 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
value 15
}
control.21 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 1
value 15
}
control.22 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 '44.1kHz'
comment.item.1 Off
comment.item.2 '48kHz'
comment.item.3 '32kHz'
iface MIXER
name Deemphasis
value Off
}
control.23 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 2
value 0
}
control.24 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 3
value 0
}
control.25 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 4
value 0
}
control.26 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 5
value 0
}
control.27 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 6
value 0
}
control.28 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 255'
iface MIXER
name 'DAC Volume'
index 7
value 0
}
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
12-17-04 06:51 rlrevell Note Added: 0002847
12-21-04 07:09 64bitten File Added: amixer.bad
12-21-04 07:10 64bitten Note Added: 0002896
04-09-05 17:24 jdthood Status new => acknowledged
10-20-05 02:36 sst4 Note Added: 0006497
10-20-05 05:18 Fran Note Added: 0006498
10-21-05 03:51 64bitten Note Added: 0006509
11-18-05 21:03 goldenfish Note Added: 0006758
11-18-05 21:04 goldenfish File Added: proc_changes.diff
06-20-06 22:55 effie Issue Monitored: effie
06-20-06 23:05 effie Issue End Monitor: effie
06-20-06 23:29 effie Note Added: 0010356
06-20-06 23:31 effie Note Edited: 0010356
06-21-06 06:10 Raymond Note Added: 0010382
06-21-06 09:05 goldenfish Note Added: 0010384
06-21-06 09:07 goldenfish File Added: asound.state
06-21-06 09:37 herby Note Added: 0010388
06-21-06 10:00 Raymond Note Added: 0010389
======================================================================
next reply other threads:[~2006-06-21 8:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 8:00 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 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 5:46 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=73f05657dcd2a108ecec95d92b147f1e@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