Bug 495148
| Summary: | Bad default mixer initialization | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sam Garrett <metacarpal> | ||||||
| Component: | alsa-utils | Assignee: | Jaroslav Kysela <jkysela> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | awilliam, jkysela, lkundrak, lpoetter, pfpschneider, wtogami | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-05-21 09:08:47 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: | 497966 | ||||||||
| Attachments: |
|
||||||||
|
Description
Sam Garrett
2009-04-09 22:16:14 UTC
Also applies to Intel HDAudio devices. These have "front" and need to be turned up in addition to PCM. If the PCM slider is not initialized properly by default this is a problem with the alsa default mixer database. Reassigning to alsa-utils. Sam, please tell us which sound card you have, i.e. paste the output of alsa-info.sh --no-upload. Created attachment 339082 [details]
Output of alsa-info.sh
Output of alsa-info.sh attached.
You may change /lib/alsa/init/hda files for your systems, but setting everything to max as default seems insane to me so I might not accept your changes. With the default settings sound should be hearable, but not on max. Lennart, why mixer applet does not allow to control also the hardware mixer? It's gnome issue? Not sure if it should be at max. But it should be at a level that 'makes sense', i.e. that everything has a good volume on default initialization. PA only exposes one volume control, which is usually 'Master' (if available), not 'PCM'. I'm okay with dropping the PCM max default part if we can get full mixer control back. Seems someone decided to oversimplify the interface at some point. I had a similar problem with an Ensoniq AudioPCI ENS1370. In my case the effective volume was 0! I used alsamixer -c to set everything "flat" and then the pulseaudio volume controls worked well. I'm attaching my alsa-info.txt file. Created attachment 343780 [details]
alsa-info for Ensoniq AudioPCI ENS1370
I initially had zero effective volume and had to rescue the situation with alsamixer -c
Well, this is basically an AlsaVolume bug, so setting it as blocking that. Jaroslav, as with all the other AlsaVolume cases, as Lennart said, we need the default ALSA setting to be 'sane' so that Pulse can effectively adjust the volume: the default should be such that Pulse modifying the Master slider gives a useful range of control. Sam: Pulse-type mixers are intended to be simplified to this level, they will not be made more complex in this respect. It ought to be possible for the underlying ALSA elements to be set such that the single control in a Pulse-type mixer gives a reasonable volume range. Peter, please create a bug report for your hardware. indeed, Peter, we need separate bugs for all different cards that exhibit this problem, we cannot combine them into one. please file a separate report according to the instructions here: https://bugzilla.redhat.com/show_bug.cgi?id=497966#c1 The alsa-utils-1.0.20-3 package should fix this issue. Reopen this bug if the problem persist. |