Bug 131241
| Summary: | "volume" channel doesn't control sound volume. Only "PCM" does | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Julien Olivier <julo42> | ||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5 | CC: | marius.andreiana, pfrields, tpfennig, wtogami | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2006-10-17 23:46:13 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 165164 | ||||||
| Attachments: |
|
||||||
|
Description
Julien Olivier
2004-08-30 12:31:39 UTC
Created attachment 103245 [details]
/etc/modprobe.conf
I attached /etc/modprobe.conf, in case it helps.
I have the same problemq i can not start 5.1 chanell sound =[ Similar situation: "Master Surround", "PCM" and the first of the VIA DXS ALSA channels affect volume, noone else. Specifically, the "Master" does not affect the volume which gives the same problem for me as decribed above for the multimedia keys. My hw; VIA Technologies VT8233/A/8235/8237 AC97 Audio Controller. There are two analog outputs, the situation is basically the same for both. The multimedia keys is really a separate issue, there are bugs filed on them already. But it's still a problem that the Master control doesn't affect the volume: normal users expect such a channel to control the volume at least to some extent. Quote from bug #164894 : Comment #3 From Martin Stransky (stransky) on 2005-08-16 07:12 EST [reply] Yes, It's a common problem with the Master volume slider, it doesn't work for many cards. Upstream already works on this issue. *** Bug 159513 has been marked as a duplicate of this bug. *** I'm not sure, but I can solve that problem by adding "ac97_quirk=2" into
/etc/modprobe.conf.
How about trying that?
(I'm sorry, but I've forgot the news source)
# my /etc/modprobe.conf
alias eth0 e1000
alias scsi_hostadapter ata_piix
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
options snd-intel8x0 index=0 ac97_quirk=2 # <- I've heard that you can also put
0 or 1 here
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-intel8x0
At some point this issue went away (that was FC4). So it was not a matter of configuration. Don#t know but switching mixer back and forward / on and off did help. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. You can close this bug. This bug seemed to be fixed some kernels ago or I could not reproduce it. |