All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim Feise <jfeise+alsa@ics.uci.edu>
To: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: cs46xx (Turtle Beach Santa Cruz), kernel 2.6 recording silence
Date: Sat, 14 Feb 2004 10:08:48 -0800	[thread overview]
Message-ID: <402E6430.9050001@ics.uci.edu> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

System:
Slackware 9.0, upgraded to kernel 2.6.2, using devfs.

I wanted to replace my aging sbawe (which works fine with Alsa)
with a Turtle Beach Santa Cruz card.
I can play sound, but recording from Line-In does not work.
I just get silence.
The recording sw (RealProducer 8.5) uses the OSS emulation.
It finds /dev/dsp just fine, but there just seems to be no
data delivered on the device (btw, with devfs, /dev/dsp
is a symlink to /dev/sound/dsp.)

I tried using the latest drivers (1.0.2c), and the cvs version,
but no change.

There are no error logs.

Does anybody have an idea what's going on?

TIA,
- -Joe



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)

iD8DBQFALmQwKc8oZ1MoTeoRArXdAJ98R5bwEFMyRdHDJdZ2Ap8JEVsgZACeNISb
S/vrEKq07jj9e7sISI0eWlc=
=i4V8
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

             reply	other threads:[~2004-02-14 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-14 18:08 Joachim Feise [this message]
2004-02-14 19:08 ` cs46xx (Turtle Beach Santa Cruz), kernel 2.6 recording silence Bill Unruh
2004-02-14 19:50   ` [Alsa-user] " Joachim Feise
2004-02-14 20:44     ` Bill Unruh
2004-02-14 20:59       ` Joachim Feise

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=402E6430.9050001@ics.uci.edu \
    --to=jfeise+alsa@ics.uci.edu \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.