Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Cornelius Creedon <neil@box1.staller.sunysb.edu>
To: linux-sound@vger.kernel.org
Subject: Re: solo-1 chip
Date: Fri, 12 Mar 1999 00:05:02 +0000	[thread overview]
Message-ID: <marc-linux-sound-92119789313190@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92066824429576@msgid-missing>

On Thu, 11 Mar 1999, Dan Boger wrote:

> On Thu, 11 Mar 1999 01:10:13 -0500 Bill Nottingham <notting@redhat.com> wrote
>  concerning 'Re: solo-1 chip':
> > 
> > To get native ESS Solo support ATM, you'd either have to use the
> > 2.2.*-ac patches (ftp.linux.org.uk:/pub/linux/alan/2.2), or ALSA
> > (http://alsa.jcu.cz/)
> 
> Great!  So I download the alsa driver install it.  But when I try to
> modprobe it says that the device is already in use.  I look at

i have seen this error when trying to load the sb module and it seemed to
happen simply because i did not specify enough or the right options.

> proc/modules, it did load a bunch of stuff, but still no sound.  Do I
> need to edit my /etc/conf.modules for options?  The solo1 isn't
> mentioned in any of the documents - how do I know the name of the
> options?

i believe the names of the options are uniform, at least the generic ones.
try io=0x... irq=... dma1=... and such.

you can supply these on the command line, until you get it working, then
put the right values into your conf.modules
ie 'modprobe ess-solo irq=x io=0xwhatever ...'

-cc

      parent reply	other threads:[~1999-03-12  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-05 21:07 solo-1 chip Dan Boger
1999-03-11  6:10 ` Bill Nottingham
1999-03-11 17:09 ` Thomas Sailer
1999-03-11 18:21 ` Dan Boger
1999-03-12  0:05 ` Cornelius Creedon [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=marc-linux-sound-92119789313190@msgid-missing \
    --to=neil@box1.staller.sunysb.edu \
    --cc=linux-sound@vger.kernel.org \
    /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