Bug 720721 - Alsamixer: missing entries in analog output
Summary: Alsamixer: missing entries in analog output
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-tools
Version: 15
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tim Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-12 15:44 UTC by Germano Massullo
Modified: 2011-07-31 19:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-31 19:42:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Germano Massullo 2011-07-12 15:44:19 UTC
I have a Asus Xonar Essence ST soundboard (Chip: AV200)
I can choose between these analog outputs: stereo, headphones and front panel headphones.
Sometimes from this list stereo disappears... So the headphones are enabled by default because stereo is not avaible.
By restarting the computer everything returns ok.

It does it since Fedora 14.
2.6.38.8-32.fc15.x86_64

Comment 1 Germano Massullo 2011-07-12 15:45:26 UTC
I forgot to write that I use alsamixer to choose between these analog outputs

Comment 2 Tim Jackson 2011-07-31 19:42:10 UTC
Sorry but this doesn't sound like a problem with alsa-tools. alsa-tools
contains some specific tools for dealing with specialist sound cards only.

Please be aware that problems with sound can be caused by many different
software components within a Fedora system (including ALSA kernel modules,
PulseAudio, desktop volume controls, individual applications and more) and
you may find it easier to get some informal help to track down the problem 
before filing bugs (if necessary), so that you can file them against the 
right component and the appropriate person can help.

Help resources are listed here:
http://fedoraproject.org/en/get-help

If you still believe that your problem is with alsa-tools, please re-open this bug with further details. Alternatively, if you identify the software causing the problem, you could change the Component accordingly and re-open it.


Note You need to log in before you can comment on or make changes to this bug.