Triagers and reporters, when reporting bugs of this type, the following procedure should be followed. Please do *not* report issues of this type by commenting on this bug, file a new bug and mark it as blocking this bug ('AlsaVolume').

1. Attach the file /tmp/alsa-info.txt, after running 'alsa-info.sh --no-upload'

2. To find out exactly what you had to change to control your volume, please do this, as root:

alsactl init
amixer -c0 > amixer_before.txt

Now verify that your problem exists again. Then run a mixer and make the changes you have to make to 'resolve' your problem. Then go back to running commands:

amixer -c0 > amixer_after.txt

Then attach the files 'amixer_before.txt' and 'amixer_after.txt' to the bug report. The commands above assume the important sound device is card #0 in the output of 'cat /proc/asound/cards' . If this is not the case, change -c0 in each of the above commands to -cN, where N is the actual number of the important device in 'cat /proc/asound/cards' - for instance, if it's card number 2 in that list, change all -c0 to -c2 .

3. Also please include an exact description of the problem, including how your card behaves before the problem is fixed, how it behaves after the problem is fixed, and information on your actual sound output device - are you using a simple pair of computer speakers? Internal speakers on a laptop? Headphones? A digital S/PDIF connection to an external decoder?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Another problem is that I can't chose mic input device with that and I used xfce UI to do that.

"Another problem is that I can't chose mic input device with that and I used
xfce UI to do that."

That's far outside the scope of this tracker and is a known missing feature in g-v-c which will be addressed in future. No need to talk about it here.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Created attachment 341806 [details]
/tmp/alsainfo.txt as required by the tracker bug

Sorry, I attached the file in this tracker bug instead of in my own bug -_-

I can't delete it now...

/me goes to flagellate himself

I don't agree that this should be a blocker.

I agree with Lennart, it doesn't make sense for it to be a blocker as finding these bugs will likely be an ongoing process. (Wasn't me who set it as one.)

dropping from f11target then.

jens knutson: I saw you added yourself to CC - do you have a bug of this type? If so, has it already been reported? Thanks!

Note that changes in alsa-utils-1.0.20 should resolve most of issues reported in depedendent bugs.

jaroslav: can we get those changes into F11, maybe as 0-day updates?

Adding 'Tracking' keyword to be excluded from rawhide rebase to Fedora 11

I see several people adding themselves to CC for this bug without adding extra reports to the blocker list.

This type of bug has no single, central fix: if you are experiencing a bug of this type with hardware that does not already have a bug report filed, you *need to file a report for your hardware*, or it will never get fixed. If you've filed such a report, please add it to the list of bugs that blocks this bug, so we can track it properly. Thanks.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

I have a problem that I´d like to report following the above procedure, however, after having verified that I get it resolved using the legacy mixer, I am unable to reset my setup so as to reproduce the problem with alsactl init, and of course I did not take amixer -c0 output prior to fixing it :( Is there anything else I can try to fully reset my setup?

(In reply to comment #14)
Never mind, I got it not working again after rebooting.

I have low sound problems, too. I have Lenovo Thinkpad T400 with Intel HDA sound and the level of sound is very low compared to under Windows.

I have maxed out all settings with different mixers such as alsamixer, xfce4-mixer, gnome-volume-control, etc. but nothing fixed that.

I even tried putting "options snd-hda-intel model=auto" into /etc/modprobe.d/alsa-base but that one didn't help, too.

my alsa-info output is at:
http://www.alsa-project.org/db/?f=acca09bacfa60c0a08831fdc95608b013fb32dfb

and I have a little suggestion as a fix. Maybe a "boost sound" tickbox or parameter can help us improve the sound output, just like the mic settings for various sound chips under Windows. The only thing in does will be multiplying of the level of sound by a fixed value (maybe 3x or 4x). At the moment, the sound is barely hearable even around 25%.

(In reply to comment #16)
> I have low sound problems, too. I have Lenovo Thinkpad T400 with Intel HDA
> sound and the level of sound is very low compared to under Windows.
> 
> I have maxed out all settings with different mixers such as alsamixer,
> xfce4-mixer, gnome-volume-control, etc. but nothing fixed that.
> 
> I even tried putting "options snd-hda-intel model=auto" into
> /etc/modprobe.d/alsa-base but that one didn't help, too.
> 
> my alsa-info output is at:
> http://www.alsa-project.org/db/?f=acca09bacfa60c0a08831fdc95608b013fb32dfb
> 
> and I have a little suggestion as a fix. Maybe a "boost sound" tickbox or
> parameter can help us improve the sound output, just like the mic settings for
> various sound chips under Windows. The only thing in does will be multiplying
> of the level of sound by a fixed value (maybe 3x or 4x). At the moment, the
> sound is barely hearable even around 25%.

http://git.alsa-project.org/?p=alsa-kernel.git;a=blob;f=Documentation/laptops/thinkpad-acpi.txt


The ThinkPad-ACPI volume control:

The preferred way to interact with the Console Audio control is the
ALSA interface.

The legacy procfs interface allows one to read the current state,
and if volume control is enabled, accepts the following commands:

	echo up   >/proc/acpi/ibm/volume
	echo down >/proc/acpi/ibm/volume
	echo mute >/proc/acpi/ibm/volume
	echo unmute >/proc/acpi/ibm/volume
	echo 'level <level>' >/proc/acpi/ibm/volume

The <level> number range is 0 to 14 although not all of them may be
distinct. To unmute the volume after the mute command, use either the
up or down command (the level command will not unmute the volume), or
the unmute command.

You can use the volume_capabilities parameter to tell the driver
whether your thinkpad has volume control or mute-only control:
volume_capabilities=1 for mixers with mute and volume control,
volume_capabilities=2 for mixers with only mute control.


!!Module: thinkpad_acpi
	brightness_enable : 2
	brightness_mode : 4
	enable : Y
	experimental : 0
	fan_control : N
	force_load : N
	hotkey_report_mode : 0
	id : ThinkPadEC
	index : -536870912
	volume_capabilities : 0
	volume_control : N
	volume_mode : 3



state.ThinkPadEC {
	control.1 {
		comment.access read
		comment.type BOOLEAN
		comment.count 1
		iface MIXER
		name 'Console Playback Switch'
		value true
	}
}







does it mean that Fedora no longer use "alsactl restore" and "alsactl store" to keep the mixer setting of the sound card

does Fedora 13 use "alsactl init" to provide default value ?

Created attachment 891462 [details]
amixer settings before and after running 'alsactl init'

I guess my bug can be posted here.
Fedora 20 x86_64 KDE.
Intel HDA sound card.
After every reboot the speaker volume in alsamixer is set to zero. I tried running 'alsactl store' as root after manually adjusting the settings, but it didn't help. The bug was not present after the installation, it was introduced during one of the updates in the end of 2013.
Running alsactl init as root fixes bug for current session. After reboot the sound is zeroed again.
I added an attachment with settings before and after running 'alsactl init'.

Sorry, this bug is the *tracking* bug - can you please file a new report? (you can set it to block this bug if you like, but I don't know if anyone's paying special attention to bugs that block this bug any more, it's been a long time). Please include all the info listed at https://fedoraproject.org/wiki/How_to_debug_sound_problems . thanks!