Created attachment 341535 [details] alsa-info.txt of this computer I'm filing this bug as per Adam Williamson's request https://www.redhat.com/archives/fedora-devel-list/2009-April/msg02321.html I can't get enough volume with the alsa default settings, not even if the Banshee volume slider and the gnome panel volume slider are both at 100%. This is what alsactl init says: # alsactl init Unknown hardware: "HDA-Intel" "SigmaTel STAC9271D" "HDA:83847627,80863001,00100201" "" "" Hardware is initialized using a guess method The alsa-info.txt file should be attached. I'll attach the alsa settings diff file next.
Created attachment 341537 [details] The diff between original and fixed amixer -c0 output I can't say that I know much about alsa, but here's what I did to get enough volume: I ran alsamixer -c0 and set PCM to full volume (dB gain 0). As that still wasn't enough, I added some Front volume as well, to dB gain -13.50. Now it's as much as my ears can possibly take :) I'm using headphones and there seems to be a Headphones volume slider as well, but that doesn't affect the volume at all.
There's one more thing we need (sorry, this is my fault, the instructions were bad) - please attach the original amixer_before.txt and amixer_after.txt files, not just the diff. Turns out the diff doesn't have enough context. sorry! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 341718 [details] The amixer output with default settings
Created attachment 341720 [details] The amixer output with fixed volume settings Ok, the files should be attached now.
I believe my Intel HDA [8086:284b] hardware suffers from the same problem -- is the difference in my PCI ID sufficient to file an additional bug in this case? Happy to do so if needed.
Sounds like a good candidate for inclusion in the ALSA db. Reassigning.
Paul: the main PCI ID is not sufficient to identify Intel HDA chips uniquely, they almost all show that PCI ID, they're better identified by the subsystem IDs. Please file a new bug following the instructions in comment #1 of the tracker bug (https://bugzilla.redhat.com/show_bug.cgi?id=497966 ) and let me know the number. If your hardware turns out to be the same as one of the existing reports, I'll close it as a dupe. Thanks!
Done, as bug 498612 -- thanks Adam.
Jaroslav, was this one done in 1.0.20?
The alsa-utils-1.0.20-3 package should fix this issue. Reopen this bug if the problem persist.