public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joaquin Rapela <rapela@usc.edu>
To: Kristian Peters <kristian.peters@korseby.net>
Cc: linux-kernel@vger.kernel.org, sailer@ife.ee.ethz.ch, hb9jnx@hb9w.che.eu
Subject: Re: es1371 sound problem
Date: Thu, 9 May 2002 08:54:13 -0700	[thread overview]
Message-ID: <20020509085413.E2389@plato.usc.edu> (raw)
In-Reply-To: <20020507215024.B11180@plato.usc.edu> <20020508095713.1f661dd1.kristian.peters@korseby.net> <20020508142014.A1665@plato.usc.edu> <20020509093017.79f29936.kristian.peters@korseby.net>

> > May  8 12:08:39 vpl kernel: ac97_codec: AC97 Audio codec, id: 0x4352:0x5903
> > (Cirrus Logic CS4297)
> 
>   ^^^^^^^^^^^^^ 
>      Maybe you own a Cirrus Logic soundcard instead ?
>      ac97 reports that your soundcard uses a codec from Cirrus L.
>      See /usr/src/linux/Documentation/sound/cs46xx maybe
>      It could be possible that your sndconfig from RedHat detects a wrong one..

Unsuccesfully I tried to load cs46xx or cs4232 from sndconfig.
qqqqqqqqqqqqqqqqqqqqqqu modprobe error tqqqqqqqqqqqqqqqqqqqqqqk
x                                                              x 
x The following error occurred running the modprobe program:   x 
x
x 
x /lib/modules/2.4.7-10/kernel/drivers/sound/cs46xx.o:
x 
x init_module: No such device
x 
x /lib/modules/2.4.7-10/kernel/drivers/sound/cs46xx.o: insmod x 
x /lib/modules/2.4.7-10/kernel/drivers/sound/cs46xx.o failed
x 
x /lib/modules/2.4.7-10/kernel/drivers/sound/cs46xx.o: insmod x 
x sound-slot-0 failed
x 

> So you can try to modprobe cs46xx or cs4232 for a Cirrus Logic Soundcard - but I suspect that this won't work correctly. Or try to load ac97_codec and ac97 only. Those es1371 soundcards have 2 dsps. ;-) But one should be enough for now.
> 
> If your model is not a Creative one try to use ES1370. Try lspci -n for that.
> The PCI ID "1274:1371" should indicate that your card is from Creative, the ID "1274:5000" incidates that it is from Ensoniq.

lspci -n reports a Creative soundcard:

00:0c.0 Class 0401: 1274:1371 (rev 08)

I am cc Thomas Sailer the author of the module.

Thanks for your great comments, Joaco

> 
> *Kristian
> 
>   :... [snd.science] ...:
>  ::                             _o)
>  :: http://www.korseby.net      /\\
>  :: http://gsmp.sf.net         _\_V
>   :.........................:

-- 
Joaquin Rapela
PhD Student, Visual Processing Group
University of Southern California
3650 South McClintock Ave.
Olin Hall of Engineering 500
Los Angeles, CA 90089-1451
tel/fax: (213) 821-2070
----------------------------------

"Respectfully keep at your studies constantly, and then you will have results."

                                                                     Confucius

      reply	other threads:[~2002-05-09 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08  4:50 es1371 sound problem Joaquin Rapela
2002-05-08 12:05 ` David D. Hagood
2002-05-08 21:29   ` Joaquin Rapela
     [not found] ` <20020508095713.1f661dd1.kristian.peters@korseby.net>
2002-05-08 21:20   ` Joaquin Rapela
2002-05-09  7:30     ` Kristian Peters
2002-05-09 15:54       ` Joaquin Rapela [this message]

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=20020509085413.E2389@plato.usc.edu \
    --to=rapela@usc.edu \
    --cc=hb9jnx@hb9w.che.eu \
    --cc=kristian.peters@korseby.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sailer@ife.ee.ethz.ch \
    /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