Re: [Alsa-user] alsamixer problem

[Michael C. <mch...@ve...>]

Thanks!  This helped me fix my problem.  In the end, I discovered a
possible bug with Fedora's system-config-soundcard.  Should I post this
to Fedora's bugzilla tracker?  Here's the full scoop:

Alsamixer was trying to access /dev/snd/controlC1.  This was strange
since I only had one audio device after disabling motherboard sound.  I
saw that /etc/asound.conf looked like:

# Generated by system-config-soundcard, do not edit by hand
defaults.pcm.card 1
defaults.ctl.card 1

This seemed totally wrong, so I started investigating why this happened.
 Here's why:

The system-config-soundcard tool presented two audio devices for my one
sb awe64: CTL7002 and CTL0044.  The CTL7002 is the game port (thanks
google), so I had selected the CTL0044 as the default audio device.  The
tool then wrote out device 1 to asound.conf!  If I select CTL0044 it
writes out 0 to asound.conf.

This seems totally wrong.  Why would Fedora's system-config-soundcard
present two options (not explaining what either one is)?  Shouldn't it
ignore the game port?  Should I take this up with the Fedora people and
if so, what is the correct forum for this?


noky

Takashi Iwai wrote:
> At Wed, 12 Oct 2005 10:10:35 -0400,
> Michael Charnoky wrote:
> 
>>Yes, the card does appear in /proc/asound/cards and /dev/snd/controlC0
>>does exist.  I can get the card to work, but it is spotty and some
>>things just don't work (like alsamixer).
> 
> 
> Check with strace what's really happening in the system call level.
> 
> 
> Takashi
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Alsa-user mailing list
> Als...@li...
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>