Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Cody Jung <funkycat32@gmail.com>
Cc: alsa-devel@alsa-project.org, alsa-user@alsa-project.org
Subject: Re: [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work?
Date: Sat, 28 Apr 2007 11:54:18 +0200	[thread overview]
Message-ID: <463319CA.4040309@gmail.com> (raw)
In-Reply-To: <d382e1990704272206y9712a84x1e07d07eda58fb18@mail.gmail.com>

On 04/28/2007 07:06 AM, Cody Jung wrote:

> As it suggests in the subject, I'm both a Linux-newbie and an
> ALSA-newbie. I have an old clunker of a machine running Ubuntu Feisty
> that I built out of parts left on curbs during spring cleanup, and that's
> how I came across my sound card. It's an Ensoniq SoundscapeVivo (Not a 
> Vivo90, AFAIK).

As far as I'm aware, there are no other VIVO's than the VIVO90.

> I've gone through install and troubleshooting guides galore, but I can't
> seem to get ALSA to recognize my card, and I'm confused and rather tired
> of it all.
> 
> Do you think you can help, and if so, what information do you need from
> me?

I probably can; I have both a Soundscape VIVO90 and a much older Soundscape 
S-2000. My VIVO90 is an ISA-PnP card and has a Ensoniq MARK5-RO, an OTTOR2C 
and a Analog Devices AD1845 codec:

http://en.wikipedia.org/wiki/Ensoniq_Soundscape_VIVO90

I tested that when I acquired it a while ago and if I remember correctly, it 
just worked... mmm. come to think of it, it might be the case that I needed 
to add its PnP ID to the driver. Not sure anymore. Could you confirm whether 
or not your Soundscape is an ISA-PnP card and if so (that's also a way to 
find out if you don't know if it is) run "pnpdump" with it installed and 
look for a PnP-ID for the card in it? Something of the form "ENSxxxx".

If your card is one of the older non-PnP soundscapes it's going to be a bit 
harder; they also need firmware and all that and I haven't tested that card 
myself yet.

(please use the @alsa-project.org list addresses by the way; in the case of 
alsa-devel, the sourceforge one is gone even).

Rene.

       reply	other threads:[~2007-04-28  9:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d382e1990704272206y9712a84x1e07d07eda58fb18@mail.gmail.com>
2007-04-28  9:54 ` Rene Herman [this message]
2007-04-28 11:52   ` [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work? Hannu Savolainen
2007-04-28 22:39     ` Rene Herman
     [not found]       ` <d382e1990704281918g42165aaas4cac717fe5b4bab0@mail.gmail.com>
2007-04-29  7:31         ` Rene Herman
2007-04-29  7:33           ` Rene Herman
2007-04-28 15:56   ` Cody Jung
2007-04-28 22:32     ` [Alsa-user] " Rene Herman

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=463319CA.4040309@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@alsa-project.org \
    --cc=funkycat32@gmail.com \
    /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