Bug 598686

Created attachment 418809 [details]
alsa-info.sh output

Created attachment 418810 [details]
Setting before changing settings

Created attachment 418811 [details]
Changes after changing settings

I am experiencing similar problems. Before the upgrade to Fedora 13 (actually a fresh reinstall) audio was fine. Now many files that I play sound like they are being clipped.

I will provide the same information as the original poster.

# alsactl init 0
Unknown hardware: "HDA-Intel" "Conexant CX20551 (Waikiki)" "HDA:14f15047,1179ff31,00100000" "0x1179" "0xff31"
Hardware is initialized using a guess method

Created attachment 419189 [details]
output of alsa-info.sh --output

Same problem here since the preupgrade from F12 to F13. the sound is very low at boot and the only solution is to level up the master front with gmixer.

#alsactl init 0
Unknown hardware: "HDA-Intel" "VIA VT1708S" "HDA:11060397,10431111,00100000" "0x1111" "0x1043"
Hardware is initialized using a guess method

Created attachment 423840 [details]
alsa-info.sh output

I manage to keep the driver configuration with an init.d script.

I'm not very experienced with bash scripting.

Created attachment 424127 [details]
script which store driver setup at shut down and restore it at boot

Why alsa-driver , alsa-lib , alsa-utils are different version ?


!!ALSA Version
!!------------

Driver version:     1.0.21
Library version:    
Utilities version:  1.0.22




!!ALSA Version
!!------------

Driver version:     1.0.21
Library version:    1.0.23
Utilities version:  1.0.22

I don' know. i use packages from official repo, and did not made any updates with rawhide repo (except for qt).

Here are the packages versions :

[eponyme@FEDOBOX ~]$ rpm -qa alsa-driver alsa-lib alsa-utils
alsa-lib-1.0.23-1.fc13.x86_64
alsa-utils-1.0.22-1.fc13.x86_64
[eponyme@FEDOBOX ~]$ 

Fabien

(In reply to comment #0)
> Description of problem:
> 
>
> 
> When I launched alsactl for tests : 
> [root@FEDOBOX ~]# alsactl init
> Unknown hardware: "HDA-Intel" "VIA VT1708S" "HDA:11060397,18490397,00100000"
> "0x1849" "0x0397"
> Hardware is initialized using a guess method

In previous version of Fedora , 

alsactl store when system shutdown 

and

alsactl restore after system boot up



"alsactl init" seem to be used to initialise the volume of the sound to a certain value so that LiveCD work without require the user to unmute the volume controls

I have this problem on two computers with (different) Asus motherboards. I used the gmixer trick to increase the volume. What can I do to help this get fixed properly? I'm willing to provide log files, etc.

(In reply to comment #1)
> Created attachment 418809 [details]
> alsa-info.sh output

Total dB = Master Front + PCM + Front = -75.5dB , so low volume is normal


Simple mixer control 'Master Front',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 0 [0%] [-34.50dB] [on]
  Front Right: Playback 0 [0%] [-34.50dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 155 [61%] [-20.00dB]
  Front Right: Playback 155 [61%] [-20.00dB]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 42
  Mono:
  Front Left: Playback 28 [67%] [-21.00dB] [on]
  Front Right: Playback 28 [67%] [-21.00dB] [on]

So it seems the default settings are too low. Any idea why?

open a terminal and run "alsamixer -c0"



try to increase/decrease volume by using the slider in the gnome volume applet at system tray


does the three volume controls "Master Front", "PCM" and "Front" of alsamixer  change as you move the slider from minimum to maximum in gnome volume applet ?

Moving the volume slide from min to max, first the PCM display increases until it maxes out, then the Front display increases until it maxes out, approximately when the volume slider reaches the top. The Master Front display stays at maximum and never changes.

do you mean the volume is still low when the three volume controls are at max level ?

or the system did not restore the volume properly after reboot ?


The "PCM" is a softvol plugin 

	control.32 {
		comment.access 'read write user'
		comment.type INTEGER
		comment.count 2
		comment.range '0 - 255'
		comment.tlv '0000000100000008ffffec1400000014'
		comment.dbmin -5100
		comment.dbmax 0
		iface MIXER
		name 'PCM Playback Volume'
		value.0 249
		value.1 249
	}


so in theory PA should control Front Playback Volume and Master Front Playback Volume instead of the softvol 



Node 0x10 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Front Playback Volume", index=0, device=0
  Device: name="VT1708S Analog", type="Audio", device=0
  Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
  Amp-Out vals:  [0x26 0x26]
  Converter: stream=0, channel=0
  PCM:
    rates [0x5e0]: 44100 48000 88200 96000 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
  Power states:  D0 D1 D2 D3
  Power: setting=D0, actual=D0

Node 0x16 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In
  Control: name="Master Front Playback Volume", index=0, device=0
  Control: name="Master Front Playback Switch", index=0, device=0
  Control: name="Mic Playback Volume", index=0, device=0
  Control: name="Mic Playback Switch", index=0, device=0
  Control: name="Line Playback Volume", index=0, device=0
  Control: name="Line Playback Switch", index=0, device=0
  Control: name="CD Playback Volume", index=0, device=0
  Control: name="CD Playback Switch", index=0, device=0
  Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
  Amp-In vals:  [0x00 0x00] [0x17 0x17] [0x00 0x00] [0x00 0x00] [0x00 0x00] [0x97 0x97] [0x97 0x97]
  Power states:  D0 D1 D2 D3
  Power: setting=D0, actual=D0
  Connection: 7
     0x10 0x1f 0x1a 0x1b 0x1e 0x1d 0x25

the problem describe in first post still exists with F14

>> The Master Front display stays at maximum and never changes.

you can open a terminal and run PA server in foreground

pulseaudio -k;pulseaudio -vvvvv

the output of PA server tell you which volume controls are used by PA server

Fixed for me in F15 \o/

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.