Re: OSS emulation, CS46xx, 2.6.12-rc2

[Takashi Iwai <tiwai@suse.de>]

At Tue, 12 Apr 2005 04:18:07 -0700,
Andrew Morton wrote:
> 
> Takashi Iwai <tiwai@suse.de> wrote:
> >
> > > > It seems that the recent change of the "reversed EAPD" hack sets this
> >  > > control off as default unexpectedly.
> >  > > 
> >  > > Anyway, /etc/asound.state (if you have) and
> >  > 
> >  > Attached
> > 
> >  The problem is that "DAC Volume" is set to 0 by any reason.
> >  I don't know how this happend.  The driver default is 100%.
> > 
> >  To fix this, again, start alsamixer, choose 'DAC', and raise with the
> >  up/down key.
> > 
> 
> well I went into alsamixer and increased everything to max and now sounds
> are coming out.  I wonder what happened to my defaults?  It's running FC3.

My suspect is a mixer app on desktop.  For example, kmix keeps the
sound configuration by itself and saves/restores on ~/.kde/somewhere.
If you have a NFS-home directory shared among different hardwares, the
h/w configuration would be confused.  (Also, kmix seems to have some
odd side-effects to turn on/off automatically switches unexpectedly.)

> gmplayer is getting segv on startup now, and I didn't change anything :(

No idea about this.  Is mplayer set up to use ALSA or OSS mode?
Possible to get a backtrace?


> >  > > /proc/asound/card0/codec97#0/* files would be helpful for debugging.
> >  > 
> >  > I don't seem to have such a thing.  I tarred up /proc/asound.  Also attached.
> > 
> >  Hmm, it's ridiculous.  You don't have /proc/asound/card0 directory?
> 
> Nope.  Where did it go?

Could you check snd_info_card_create() in sound/info.c is called
and returns successfully?


At Tue, 12 Apr 2005 04:21:23 -0700,
Andrew Morton wrote:
> 
> Andrew Morton <akpm@osdl.org> wrote:
> >
> >  well I went into alsamixer and increased everything to max and now sounds
> >  are coming out.  I wonder what happened to my defaults?  It's running FC3.
> 
> I rebooted and sounds are coming out again.  Looks like something was
> permanently wrong in asound.state, yes?

We need to check in which stage it's broken.
Login to console after reboot will use the sound h/w configuration
which "alsactl restore" does (i.e. /etc/asound.state is used).
You can check whether the sound works on it.

Then, try to login to a graphical desktop (KDE/GNOME).  On this, the
mixer state is restored again by the desktop system component
(e.g. kmix).  So, the h/w configuration changes from the system
default.  If the former console login worked and now it doesn't work,
it implies that the configuration saved for the desktop is broken
rather than /etc/asound.state.


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click