From: Rene Herman <rene.herman@gmail.com>
To: Cody Jung <funkycat32@gmail.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
ALSA user <alsa-user@alsa-project.org>
Subject: Re: [Alsa-user] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work? [Solved]
Date: Mon, 30 Apr 2007 00:04:20 +0200 [thread overview]
Message-ID: <46351664.2010509@gmail.com> (raw)
In-Reply-To: <d382e1990704291418x20550cc7l17239562227f2a61@mail.gmail.com>
On 04/29/2007 11:18 PM, Cody Jung wrote:
> Instead I added the following 4 lines to a file and included it in my
> init scripts.
>
> echo activate > /sys/bus/pnp/devices/01\:01.00/resources
> sleep 1
> modprobe snd
> modprobe snd-cs4231 port=0x534 irq=5 dma1=1 dma2=0
Sure, that'll do as well. Bit strange that (/if) you need to "modprobe snd"
seperately; "modprobe snd-cs4231" should pull it in automatically, but not
important.
Do note that if you change the machine's hardware configuration the VIVOs
resources migth change again. If you for example put another card on IRQ9,
the PnP layer won't be able to use the VIVOs preferred options, and will
configure it on irq 7 instead of 5. Checking the resources in the /sys tree
after activating as I showed will work...
> And it works great!
>
> Thanks again for putting up with my incompetence.
Not so much incompetence; just the misfortune that your card isn't (really)
supported by ALSA. That's the kind of thing that immediately gets you deep
into the bowels of a Linux system. Glad I could at least help and as said,
some future verson of ALSA will probably grow a real/better driver for the card.
Rene.
prev parent reply other threads:[~2007-04-29 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 21:18 [alsa-devel] ALSA Newbie - Getting Ensoniq SoundscapeVivo to work? [Solved] Cody Jung
2007-04-29 22:04 ` Rene Herman [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=46351664.2010509@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 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.