Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: j_f@laposte.net
Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: Re: [Alsa-user] Re: Audigy and FPS 5300 rear speakers	problem
Date: Fri, 24 May 2002 17:55:05 +0200	[thread overview]
Message-ID: <aclnsj$krt$2@main.gmane.org> (raw)
In-Reply-To: <1022183789.1195.40.camel@localhost.localdomain>

At 23 May 2002 23:38:31 +0200,
j_f@laposte.net wrote:
> 
> Le jeu 23/05/2002 à 10:49, Takashi Iwai a écrit :
> (...)
> > 
> > could you send me your /etc/asound.state?
> I would be pleased to do so, but I don't have any /etc/asound.state
> file... May be I messed something ? I fact I haven't any asound.* file
> on my hard disk.... It seems to be wrong 'cause readind /etc/alsa.conf I
> saw a reference to a file named /etc/asound.conf...

/etc/asound.conf is the configuration for defining your own pcm or
controls.  /etc/asound.state is used to save and restore the status of
mixer and controls.
it's a bit confusing, because /etc/asound.conf was used for the
purpose of the present /etc/asound.state at the time of alsa 0.5.x.
anyway, if you have /etc/asound.state, better to remove it.

> > 
> > > Any others ideas ?
> > 
> > try to remove /etc/asound.state once, reload the driver and configure
> > the mixer status again.
> It would be nice but as I didn't have such a file, it is difficult for
> me to delete it ;)
> 
> Is it possible that a previous install of alsa 0.9 can cause such a
> problem ?

usually not.  a possible problem may be the files under
/usr/share/alsa directory...

anyway, can you once save your setting via "alsactl store" (as root)
and send me the generated /etc/asound.state to analyze the
configuration?


Takashi

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  reply	other threads:[~2002-05-24 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1022074808.4314.14.camel@bob.aix.diginext.fr>
2002-05-22 14:03 ` Audigy and FPS 5300 rear speakers problem Takashi Iwai
     [not found] ` <s5hn0usfff5.wl@alsa2.suse.de>
2002-05-22 21:52   ` j_f
     [not found]   ` <1022104324.1710.4.camel@localhost.localdomain>
2002-05-23  8:49     ` Takashi Iwai
     [not found]     ` <s5hadqrfdv5.wl@alsa2.suse.de>
2002-05-23 21:38       ` [Alsa-user] " j_f
2002-05-24 15:55         ` Takashi Iwai [this message]
     [not found] <1023918629.1921.8.camel@localhost.localdomain>
2002-07-03 17:56 ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='aclnsj$krt$2@main.gmane.org' \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=j_f@laposte.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox